Mini vMac full changelog

New features in default compile:
If Mini vMac doesn't find the ROM file in the folder containing the application, it will now also look in a specific central location. In Windows XP, quot;C:Documents and Settings[your_UserName]Application DataGryphelmnvm_romquot;. Windows 98, quot;C:WINDOWSApplication DataGryphelmnvm_romquot;. And in Vista, I think quot;C:Users[your_UserName]AppDataRoamingGryphelmnvm_romquot;. Usually quot;mnvm_romquot; would be an alias (on OS X, on Windows this is called a short cut) to where ever you keep your ROM collection. This avoids having to create an alias to the ROM image for each emulated Mac you use.
Changed behavior in default compile:
The alternate CPU emulation of Mini vMac 3.0.4 is now the main and only emulation. (The “-alt-cpu” build option is gone.) This makes Mini vMac slightly faster, and allows more accurate detection of illegal instructions without speed penalty.

New features in default compile:
· If Mini vMac doesn't find the ROM file in the folder containing the application, it will now also look in a specific central location. In Windows XP, quot;C:Documents and Settings[your_UserName]Application DataGryphelmnvm_romquot;. Windows 98, quot;C:WINDOWSApplication DataGryphelmnvm_romquot;. And in Vista, I think quot;C:Users[your_UserName]AppDataRoamingGryphelmnvm_romquot;. Usually quot;mnvm_romquot; would be an alias (on OS X, on Windows this is called a short cut) to where ever you keep your ROM collection. This avoids having to create an alias to the ROM image for each emulated Mac you use.

Changed behavior in default compile:
· The alternate CPU emulation of Mini vMac 3.0.4 is now the main and only emulation. (The “-alt-cpu” build option is gone.) This makes Mini vMac slightly faster, and allows more accurate detection of illegal instructions without speed penalty. It also reduces the amount of code to be optimized in assembly language (Currently only done for PowerPC)....