Justin wrote:Mini vMac variations work well, but aren't official. Mini vMac works for system 1-6, but you have to drag and drop(there is no way to double click to run a virtual machine), but PCE uses configuration files.
Mini vMac variations are official. It's the official variations service; you can download whatever variation you need. Mini vMac works by compiling a binary with custom PRAM values instead of having a preference setting after the fact. The default Mac Plus is only the default.
You do not need to drag and drop for Mini vMac; if a file called disk1.dsk is found in the same folder as the executable, it will be auto-loaded. This goes from disk1 to diskn, where n is the maximum number of simultaneous disks you've set as the maximum in your build of Mini vMac (hard ceiling is 32). It will only load up until it doesn't find a number, so if you have disk1, disk2, disk3, disk5... only the first 3 will auto-load.
On OS X host, you can also drop a mnvm_dat folder inside the application's contents folder, and toss your disk images and ROM inside there. This location is treated just like the folder Mini vMac is in.
So with Mini vMac, instead of fiddling with a prefs file, you set it all on the website in the variations area, and download a unique executable for each combination of settings you want to use. Toss the executable in a folder with the ROM and disk images you want to use, and then create a shortcut to the executable elsewhere. Mini vMac can also take images as command line arguments, which can be embedded in the shortcut, but that's not really needed since an easier method is already available.
I haven't tested it on Windows with shortcuts, but on OS X with aliases, the ROM and disk image files located in the folder with the executable can be aliases, not the original files. This might not work with Windows, due to the shortcuts having the wrong file extension. However, with Windows 10, you can also use symbolic links instead of shortcuts; those should work in the same way.
Justin wrote:OS X 10.4 and 10.5 USB audio devices can be emulated on qemu can't they?
For Pre-OS X 10.4, the USB audio device driver will output to whatever the host's default audio out happens to be. For 10.4 and 10.5, the driver enables the guest OS to connect to USB audio devices on the host. Non USB audio devices won't play the audio. I think this is due to the fact that 10.4 and 10.5 actually recognize USB audio as addressable serial devices, whereas earlier versions just see the driver as an audio output device.