* A call to XFlush was missing in the X version (such asthe Linux port), and the most noticeable effect wasthe lack of drawing when Mini vMac was in thebackground with the run in background option on. (It'ssurprising that it worked previously.) * Mini vMac for PowerPC Macintosh OS X was not compatible with OS X 10.5,due to a bug in the PowerPC assembly code used for 680x0 emulation. Such asminivmac-3.0.4-imch, for the Intel Macintoshversion of Mini vMac 3.0.4. * The variation name displayedin the about message, and used for program binary archive names,no longer includes the development environmentused to compile it or the debug status, but onlyhas the program name abbreviation, theversion number, and the target. * An even moreobscure change is that in the control mode,changes to the caps lock key take effectimmediately, instead of waiting until leavingthe control mode. * An obscure change is that when entering thecontrol mode, or the open dialog, or switchingto another application, all the emulatedkeys (except for caps lock) are releasedimmediately, instead of waiting untilnormal emulation resumes. However,the keys that map to command and option canhave special meanings in other operating systems.(For example, in OS X, clicking on the windowof another application with command and optiondown will hide all other applications.) Soit usually works better to press command-optionright before dropping, instead of before dragging.(Thanks to a complaint by David Sibleyfor this feature.) This makes it easierto rebuild the desktop of disk images byholding down command and option. There is nowa special case such that immediately aftera drag and drop on to the Mini vMac window, it will not ignorekeys already held down. * When switching back to the Mini vMac application,previous versions would always ignore keysthat were already held down. Before I had wanted to makeit quick to type, but now I think it is more importantto prevent hitting it accidentally. * The stopped mode toggle is now Control-S-Dinstead of Control-S-S. You can then make sureto have only one copy of Mini vMac compiledthis way on your computer. This is because whenyou have lots of copies of Mini vMac around,all of which claim ownership of disk images,it is unpredictable what happens when youdouble click on one, making the feature useless.Instead there is a compile time option, -im 1,to make Mini vMac claim ownership as hasbeen done previously. So double clicking on disk imageswill not launch Mini vMac. * By default, the Macintosh versions ofMini vMac will now not claim ownership to disk image andROM image files. But if this is a concern, all the new capabilities canbe disabled with the compile time option -min-extn. The new capabilities were carefully designed to avoid allowingsoftware running in the virtual machine to do any seriousharm. Software using these capabilities include: * Mini vMac now provides certain new capabilitiesfor software running within the emulated machine, includinggetting and setting the host clipboard, using raw fileson the host computer (disabling any interpretation asa disk image), creating new files (disk images or raw files),deleting files mounted with write permission, and gettingthe names of files. What has changed in Mini vMac 3.0.4, compared to Mini vMac 2.8.2.This only lists changes that affect behavior, and so doesn'tinclude cleanups of the source code.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |