I’d think the first step, if you haven’t already,is to ask the original developer. So, how canI get Classic Menu to be 64-bit? Is there someone to hire to do this.Ĭurrently, Classic Menu is not being developed.But you can get thesource code from you suggest anything that might help me keep this app alive? I'll stay on the case.Ĭode 0301 indicates Mini vMac reached a part of the FPU emulationthat hasn’t been implemented yet.ĭo you know about Classic Menu? I've used it for years and love it.However, it is 32-bit. The host is running Windows 10(32) on an Atom processor.Īs regards the 'sound' error I got the other day I haven't yet been ableto reproduce it. Mini vMac stopped with code 0301 when I tried to open the backgroundscript of a card (the last card, where the user level is set) ofHypercard 2.2's Home stack.

Update - Mini vMac 3.5.8 should fix this. The fix should be included in the next version, probablyMini vMac 3.6, unless some other serious problem turns up in 3.5.(Since nobody reported this in the 4 month beta period, I guessit isn’t too high priority.)

I think I have a fix (changing the command line argumentsgenerated by the Mini vMac build system). I have verified this issue on PowerPC G3.It turns out my GCC compiler version defaults to requiring G4 orlater. New version Mini vMac 3.5.7 wont run on PPC G3 systems.Ĭonsole crash log: 'incompatible cpu-subtype'

I’m thinking I should split the directions for sponsoringto a separate page, and link to it from places like thelatest variations page.

Let me know if anything isn’t clear, or if you have anysuggestions for improving the Variation Service. The bottom of the Variations Service Directionspage gives directions for sponsoring a variation. I would like to know ifis possible I sponsor one. I would like to know about sponsor versions.

Opcode galaxy mac emulator