![]() Mini vMac on Microsoft Windows will now recognize the Virtual-Key code of VK_OEM_102, and translate it to the Macintosh key code of 0x0A.Why has no one complained about this issue in the last decade? But also because I'm not sure I really understand this. There is a new build option to disable this fix, -ikb 0”, because this is fairly large amount of code and US only users don't need it. Mini vMac will now check the current Keyboard Layout, and attempt to unscramble the codes, so that the Keyboard Layout chosen in Macintosh operating system running within Mini vMac will work properly. Changing the Keyboard Layout to something other than "US" may scramble the Virtual-Key Codes, strangely enough. The Virtual-Key Codes of Microsoft Windows, that are independent of differences in keyboard hardware, turn out not to be independent of the choice of Keyboard Layout.With this change, all ports can use the same platform independent event loop, as described above. Mini vMac used to use a standard Carbon event loop with a complicated system of timer events only because a manual event loop didn't get quite as good performance. The same fix actually also applies to Carbon.(Apple has declared Carbon very, very deprecated.) This allows matching the performance of the Carbon version, making the Cocoa version more ready for prime time. In the Cocoa port, when the platform dependent code checks for events, rather than using a time out value, it turns out there is a bit less overhead to check for events, sleep, and then check for events again.To minimize glitches in sound output when emulation starts, stops, or just isn't running fast enough, the sound call back functions in the various Macintosh versions and the SDL version will now try to play an appropriate transition in each of these circumstances.The exact situations this happens varies for each platform. A visible consequence of this is that the emulation will now stop running in certain circumstances when it used to continue running, such as during the open disk image dialog. Instead of the platform dependent code calling a routine to emulate one tick (sixtieth of a second) whenever appropriate, the main loop of the program is now in platform independent code, which periodically calls platform dependent code to check for events. To make Mini vMac simpler and more maintainable, the interaction between platform dependent code and platform independent code has been changed a bit.Changed URL displayed in about screen to " ".In my case, would DiskDup+ be the best choice? I could also find DiskDoubler but I don't really know. I've found online that ShrinkWrap would do the job, but it only runs on System 7 and higher. I already have DiskCopy 4.2 but I can't seem to find a way to use it to mount images. Now I need to find a program to mount the disk images of the games I want to play on the Mac. That is the only website I could find it not in a. zip file, unzip it with WinZip and the MacBinary you get is the executable application itself. I've finally managed to get a working copy of Stuffit Expander on my Mac Plus. (DropStuff didn't want to install on Mini vMac so I opted for Compact Pro, which worked like a charm) EDIT: I wrote a post about this which explains how to deal with floppy disk images.
0 Comments
Leave a Reply. |