www.gryphel.com/c/mail/v3 - feedback
copyright (c) 2015 Paul C. Pratt

Mini vMac Mail

Volume 3

To send mail to me, use the feedback form.

( - latest - )

permanent link

Sent: Mon Jan 4 23:24:43 2016

Hello :)

I have a few bugs that could probably be squashed.

First one has existed for a while, I understand this game doesn't work in 7.5.3+ so I am using System 6.0.8 to run it.

Whenever I start Phrase Craze plus the audio works fine then after you spin the wheel the first second of the sound loops and doesn't stop even when you exit the app. Demonstrated here [ ... link ... ]

Second issue is annoying and affects OSX Clients, if you go full screen with more than one display in Mini VMac both screens are blank.


According to clockwise, for Phrase Craze Plus “you must slow down Mini vMac to 1x speed for the sound to work properly.”

As mentioned in the Mini vMac Emulated Hardware Reference, “Also a few programs may break in other ways at faster than 1x. When running faster, the emulated computer thinks time is running normally for each sixtieth of a second, but at the end of each sixtieth, a lot of instructions get executed instantaneously. This gives quite good, but not perfect, compatibility.”

For Full Screen Mode, it is intended behavior to cover all screens. In Full Screen Mode, Mini vMac will use a more accurate emulation of the Macintosh mouse, that looks at motion of the mouse on the host computer, rather than its absolute position. So you can, for example, scroll to the right for as long as you want, and still be generating mouse motion in the emulated machine, rather than getting stuck at the edge of the screen. Which is important for some games.

For the method Mini vMac uses to get mouse motion, there is a small chance of undesirable behavior if all screens were not covered. I think there is a better way on OS X to get mouse motion which doesn't have this problem, but even then I'm not sure it would be desirable to have other programs on other screens, but no way to move the mouse over to them. That would likely result in confusion and bug reports.

An alternative would be to not use the more accurate mouse emulation. There is already a compile time option for this, “-emm 0”. So perhaps when this option is chosen, then Mini vMac could not cover all screens in Full screen mode, and the mouse could be moved off the screen containing Mini vMac as normal. Unfortunately, I'm unlikely to have time to implement this in the foreseeable future. (see this earlier question)

permanent link

Sent: Thu Nov 19 21:08:43 2015

[ ... domain name issue ... ]

As far as I can tell, you are complaining that a page on www.gryphel.com is near the top of search engine results for the name of a domain you own. This is because it is the name of an old Macintosh game that www.gryphel.com hosts a copy of, and the name is not being used else on the web. If you create a website on your domain, it should quickly get to the top of search engine results for that name.

If you want legal protection for your name, I think Trademark is what applies. Trademarks have limitations - for one thing you have to be actively doing business with your trademarked name. So again, you should put up a website on your domain.

permanent link

Sent: Tue Nov 3 19:57:47 2015


I own a Macintosh SE and have been using copyroms-1.1.0 to extract the ROM from it. When I tried the MacSE build of Mini vMac with my ROM file the checksum was wrong. According to this page the checksum should be 0xB2E362A8: http://gryphel.com/c/mac68k/index.html

Looking into my ROM file, it looks like it contains some kind of file header:

$ od MacSE.ROM -tx1 -tc| head -c 1024

[... hex data ...]

In the last row, the correct checksum is found:0000200 b2 e3 62 a8

With the following command, I was able to skip the first 128 bytes of the file. After this the ROM works and minivMac calculates the correct checksum for it:

$ tail -c +129 MacSE.ROM > MacSE_working.ROM

Best regards

Daniel Gullberg, Sweden

[... email address ...]

It sounds like you are using some sort of Unix like system, such as Linux. My guess is that somewhere in transferring the ROM file from a Macintosh style disk to a native disk on your system, a header got added to preserve Macintosh specific information, such as the file type and creator fields. The exact details of what happened and how to prevent it would depend on what operating system and other software you are using.

permanent link

Sent: Sun Oct 25 22:27:30 2015

are you going to include color to mini vmac for ios

I'm not involved in the iOS port of Mini vMac.

permanent link

Sent: Sun Oct 25 18:06:20 2015

its not working

See the reply to this similar previous message.

permanent link

Sent: Sun Oct 25 16:33:33 2015


I would like to add an experience of transferring files to Mini vMac using Linux. On the page http://www.gryphel.com/c/image/ there is some information about how to create a hfs disk image and open it directly with Mini vMac. I used the following command:

genisoimage -hfs -hfs-unlock -probe -V "My stuff" -o mystuff.hfs MyStuff/

Then it was possible to open the mystuff.hfs image in MinivMac using System 7.1 (which I found here: [... a URL ...]) But, and here is what I have been struggling with: The image won't open with System 6.0.8! The error message is "The disk "My stuff" is so full that the desktop file can't be created" when mystuff.hfs is dragged to Mini vMac. The workaround is thus: Open mystuff.hfs with a System 7.1. Then transfer all the files (inside Mini vMac) to a System 6.0.8 image. This image will then work with System 6.0.8!

Thanks for your report. I have added this information to the working with disk images page.

permanent link

Sent: Sat Oct 24 20:56:22 2015

Dear Paul, thank you very much for your work. Could there be an option in the variations service for 3.4.0 to have Display Size of 1280 x 720? That would be in combination with magnify 2 great at the current iMac 27 inch Retina Display. Thanks, Robert

Sorry for the delay due to travel.

Sure, I have added that option to the Variations Service.

permanent link

Sent: Fri Oct 23 15:18:19 2015

Hi! A couple of years ago, I added support for sparsebundle disk images to Basilisk II and SheepShaver. I'd like to be able to share those images with Mini vMacˇwould you have any objection to me adding that feature? Also, what's the best way to contribute back changes? (patch files, some sort of version control...)


[... email address ...]

Sorry for the delay due to travel.

Sure, you are quite welcome to add this feature to Mini vMac. Whether I'd include it in the version I maintain is a bit more of a question. The biggest issue is that I currently have very limited time to work on Mini vMac. I don't tend to merge in code unless I understand it thoroughly, and have edited it to follow the source code conventions of Mini vMac, which takes time. It depends a lot on how complex the code is. (It wouldn't help that much for you to try to make your code follow Mini vMac conventions exactly, because that editing pass is part of my way of understanding code.)

As to how to get changes to me, the easiest may be to just post it on the web somewhere, in the form of the complete source code that compiles for you. (Or you could just email me your source archive.) I have my own preferred tools for finding the differences.

Even if I didn't merge your changes immediately to my version, I would still publicize it to make it available to others.


For earlier mail, see the mail index.


www.gryphel.com/c/mail/v3 - feedback