Emulating Ancient Macs with Mini vMac. I own a Mac Plus, but since it’s so old and slow, I Mini vMac is a Mac Plus emulator based on vMac. Development of vMac has stagnated for a long time. I had an idea of using an old mac mini as a way to play old video games on a tv. There are a number of emulators for old video games systems that can be loaded on a mac mini. What is Mini vMac (for PPC Mac OS 7-8-9 & OSX)? Mini vMac (formerly vMac) is a 68K Mac emulator (Macintosh Plus and more recently Macintosh II) capable of booting and emulating the earliest versions of Mac OS from 1.0 to 7.5.5. It was ported to all major platforms including: Windows, DOS, Linux, OS/2, NeXT, Mac OS X and iOS. Mini vMac lets you adjust the emulation speed in real time. It also lets you drag and drop DSK disk images onto it for instantaneously mounting them within the emulated environment. Overall, Mini vMac is the best, most compatible, most stable and most ported 68K Mac emulator ever made. Download Mini vMac (for PPC Mac OS 7-8-9 & OSX) for Mac. I'm having trouble running the Android SDK on both of my Macs running OS X 10.6.2 Snow Leopard. This appears to be a 64-bit vs. 32-bit issue, as Snow Leopard now defaults to 64-bit everything, including the Java virtual machine. I found with instructions on how to get the Android tools to run in the 32-bit Java VM, and I am now able to run the Android GUI tool to download SDK files, create AVM's, etc. However, when I try the and get to the point where I run my application under the Android emulator, everything goes south. The emulator appears to start but it hangs (spinning beachball of death cursor) without displaying anything. (This only hangs the emulator; the rest of the system still works fine.) If I follow the exact same steps (minus the 32-bit Java hack) in a Windows virtual machine, everything works fine. This occurs on both my Mac Pro tower and 13' MacBook Pro. Does anyone have any suggestions? I was digging around the other day and saw this message appear on the terminal: emulator: warning: opening audio input failed I've seen this message many times before and I had always assumed that it was because the emulator didn't support sound or something like that. But I decided to try an experiment that one particular day. Turns out the emulator has a '-noaudio' command line option, and when I ran it with that, it worked!! Office 365 for mac sign in. So now I just run emulator with the -noaudio option always, no freezes. No sound support either, but at least I can run the emulator now. Now, that works if I manually call the emulator from the command line. What about when the Eclipse ADT plugin calls it? Well I was feeling rather lazy at that point and didn't want to dig around in the ADT plugin to see if it had a 'add these command line flags whenever running the emulator' option, so I made a little 'wrapper' shell script for the emulator command that always adds the -noaudio option. It's a bit of a kludge, but it works. Here's how: (note: $ represents the shell prompt, don't type it yourself) $ cd /tools $ mv emulator emulator.real $ cat > emulator /tools/emulator.real -noaudio $* EOF. All the above tips sure works. The solution to the freezing problem is to just pass the -noaudio option flag when starting the emulator. To further accelerate the startup of the emulator, you can add two other flags/options -cpu-delay and -no-boot-anim as follows: $ emulator -cpu-delay 0 -no-boot-anim -no-audio -avd where -no-audio actually fixes the freezing problem. -no-boot-anim disables the boot animation and should be replaced with the name of the avd image you want to run.
0 Comments
Leave a Reply. |