To send mail to me, use the feedback form.
( - latest - )
Sent: Sun May 21 15:08:11 2017
Hi, thanks for the great work. But I want to report some bugs with the keyboard when running under Windows 10. I am judging the experience when running Dark Castle. The keyboard doesn't work when in "windowed" or "magnified" mode. It only works when in Full screen mode. Can you fix this? Thank you.
Sent: Mon May 22 13:33:31 2017
Thanks for the great work on the Mini vMac project. It brings back a lot of great memory. Just one note about the Windows version, the keyboard doesn't work properly when in "Windowed" or "Magnified" mode. It only works with "Full screen" mode. I tested it with Windows 7 and Windows 10. Can you try to fix it?
Thank you for the bug report. Sorry for the delay. I’m back from travel.
Could you be more specific about how the keyboard doesn’t work? Do you type and nothing at all happens? Is this the same in both Windows 7 and 10? Are you using the same hardware for both Windows 7 and 10, or two different computers? What keyboard layout are you using? (Something other than US English?) Are you using any third party software that might affect the keyboard?
Are you using the standard variation of Mini vMac 3.4.1 (stable)?
Sent: Mon May 15 14:59:24 2017
Sent: Mon May 15 15:02:37 2017
Sent: Mon May 15 15:04:34 2017
Can you help me with compiling the mini vmac for macintosh se/30 emulation? I don't have programs to compile this.
If you can please compile and send me (without the roms because i have one from my mac se). my email: [... email address ...]
Please see the Variations Service.
Mini vMac can not yet emulate a Mac SE/30, but the Macintosh II emulation should be able to use a Mac SE/30 ROM image, if you rename the image to “MacII.ROM”
Sent: Tue May 9 17:34:07 2017
Your website says June 7 2017 instead of May 7 2017 on the latest 3.3.5 update
Oops. Thank you for telling me. It’s fixed now.
Sent: Sat May 6 07:56:50 2017
I have been using Mini vMac for years. Simply fabulous.
I recently installed it on my Android phone (Android 5.1) and it boots up with the floppy disk icon with flashing question mark.
This is obviously looking for the boot disk image but unfortunately there is no menu to allow me to either drag the image or look for it. This is similar to the Linux version but at least here, the Mini vMac doesn't fill the whole screen so I can just drag the image into it and hey Presto!
I am pretty conversant with the emulator, but I cannot for the life of me figure out how to access the boot image.
Tell me I am stupid because I am fairly certain I am missing something very obvious.
In the meantime, keep up the good work. Are you planning to to ever do a colour version that runs say OS 8 or 9?
Kevin [... last name ...]
[... email address ...]
Sent: Sat May 6 08:33:53 2017
G'day again Paul,
Yep... I'm stupid.
I finally worked it out. On Samsung Galaxy there is no menu button but rather it is a long press on the left hand screen button.
This brings up the opportunity to insert the boot image.
Perhaps you might want to post this to FAQ so other idiots like me can figure it out.
Works like a charm. Thanks again Paul
Kevin [... last name ...]
[... email address ...]
I’m glad you figured it out.
I’m not involved in the Android port of Mini vMac, and don’t know much about, and in fact have never used it, which is why there is no documentation about it on this website. Perhaps in the future this may change.
The last version of system software that Mini vMac may eventually be able to run is 8.1, as mentioned in the FAQ (and the last version Mini vMac can currently run is 7.5.5).
The incomplete Mac II emulation of Mini vMac can do color, and works well enough to play many games. (It should not yet be relied upon for more serious uses.)
Sent: Thu Apr 27 12:40:39 2017
Thanx for great software!
I wish that you in future versions could include some easier way to exchange files between host computer (OSX) and Mini vMac - perhaps a folder that would look like a volume in Mini vMac.
Also, support for reading the host computers's CD-drive would be great!
Thank you for your donation.
I wouldn’t say never to a shared folder, but it would be complicated, and there are many other things with higher priority. Meanwhile, there is ImportFl, ExportFl, and MiniUnZp.
Using a CD-drive might work on some operating systems by mounting the device file as if it was a disk image file. Otherwise, you could make an image file from a CD and then mount the image in Mini vMac. Making an image file is a good idea anyway, for backup. A CD won’t last forever.
Sent: Tue Apr 25 22:24:43 2017
I tested your beta mini vmac 3.5.3 on Mac OS X 10.5.8 on Power PC. It Works for me.
Are you doing away Mac OS classic build ? I look they are no Mac OS classic build on this Beta page.
I hope to bring back classic 680x0 and PowerPC builds eventually. Both appear to be currently broken by compiler bugs. Perhaps sometime I’ll try harder to get the Retro68 compiler working, and then port changes to GCC version 4.7.4, which I use for all other targets. The 680x0 build turns out to have been broken in Mini vMac 3.4.1, and no one reported it until recently.
Sent: Tue Apr 25 09:42:57 2017
Hi. I downloaded "SSW_6.0.8-1.4MB_Disk1of2.sea.bin" and "SSW_6.0.8-1.4MB_Disk2of2.sea.bin", but I get the message "the document ... could not be opened because it is damaged or incomplete". Trying with Stuffit, I get a System Startup Image, but when I click on it, I get the message "legacy image should be converted". Is there something that I can do to continue? I use OS X (10.12.3) and a late 2013 iMac. My email is [... email address ...]. Thank you
Sent: Tue Apr 25 10:50:11 2017
Problem solved. [... email address ...]
THANK YOU It is great!
I’m not sure what the issue was, but I’m glad you solved it.
For anyone else, the Getting Started with Mini vMac page discusses ways to extract the System disk images and what to do next.
Sent: Tue Apr 25 07:01:02 2017
I noticed that all the Dynamix adventure games (Willy Beamish, Heart of China, Rise of the Dragon) cause the system to crash when launched when emulating a Mac II. It displays the bomb icon and states a system error has occurred, illegal instruction. Are you aware of this issue and is there any prospect of it being resolvable in future releases?
Thanks for the bug report. This was much easier to debug than I expected. It turns out that for the CMPI instruction Mini vMac is considering some addressing modes to be illegal when they are actually fine. This should be fixed in the next 3.5 beta.
Sent: Tue Apr 25 04:11:30 2017
Moving the rom file to "[Application Bundle]/Contents/mnvm_dat/" worked perfectly for the Mac Sierra issue I was having with the custom builds. I missed that self-contained write-up when looking through the site.
That’s good you have it working. I should get OS X 10.12 and look into the Path Randomization stuff. (But there may not be anything to do except document work arounds.)
Sent: Mon Apr 24 23:29:17 2017
My apologies for not including enough details in my original message.
I cannot get custom variations from the variations service to recognize the necessary ROM file. Checksums match although the message is "unable to locate ROM image" rather than corrupt or incorrect ROM.
OS: OS X 10.12.4 (Sierra)
Path: "/Applications/Classic Mac Emu"
My primary issue is with builds for the Mac II rom (e.g. builds 7976, 7977, 7978, 7980, 7981, 7982, 7983).
The md5 checksum for file "MacII.rom" located with the apps in "/Applications/Classic Mac Emu" is 66223be1497460f1e60885eeb35e03cc which matches one of the expected Mac II md5 checkums at http://www.gryphel.com/c/mac68k/
I also tried the MacII.rom file included in the CJ-Classics app, but it failed with same message even though it works with the 3.4.1 Intel build inside the app bundle and reports "Macintosh II" in "About This Macinstosh...".
This rom file has the md5 checksum 2a8a4c7f2a38e0ab0771f59a9a0f1ee4 which matches the Mac II FDHD/Mac IIx/Mac IIcx/Mac SE/30 checksum at http://www.gryphel.com/c/mac68k/
The rom is named "MacII.rom" rather than "MacIIx.rom" which confuses me. Based on earlier messages in the archive, I take it you built the CJ-Classics app (thank you again), so I must be missing something. I've searched your entire site to see if 3.5.x beta is set up different or what I might be doing wrong, but can't figure it out.
I previously had an issue with build 7984 and vMac.ROM but it works fine now and I can't recreate the issue. But build 7847 in the same folder with the same vMac.rom that works with the standard 3.4.1 build fails with "unable to locate ROM image" for "vMac.ROM" message.
Standard Mac drive format so it's not case sensitive, but renaming the files to .ROM do not resolve the issue.
Thanks for the further details.
I’m suspecting this has something to do with a new security “feature” in OS X 10.12: Path Randomization. The operating system can copy the application somewhere else before executing it. If so, moving an application into another folder from where you first unzipped it is supposed to be one way to disable this.
Otherwise, as documented in the ROM section in the Emulated Hardware Reference, there are two other place Mini vMac for OS X will look for the ROM image: “/Users/[your_UserName]/Library/Preferences/Gryphel/mnvm_rom/” and “[Application Bundle]/Contents/mnvm_dat/”.
update - follow-up message
Sent: Sun Apr 23 23:45:48 2017
I'm putting together a system using a raspberry pi, a 1024x768 lcd and a touch panel.
My intent is to run minivmac, full screen, magnified 2x.
Works great with a mouse, and the touch screen works if windowed.
What happens in the full screen is that the scaling of touch is off. A middle rectangle of 1x size is getting scaled corner to corner in the 2x screen.
Can you suggest where in the code would be a good place to fix this scaling?
Using a touch screen in Full Screen mode will probably work better with the “-emm 0” option.
Sent: Sun Apr 23 18:45:37 2017
Thank you for mini vMac. I've searched your site and apologize if I missed a easy answer but I cannot figure out where to store the associated ROM file for the custom 3.5.x builds. When stored in the same folder as app, the emulator complains it can't find the required file ("MacII.ROM" or "vMac.ROM" respectively). The filenames and md5 checksums are correct. What am I missing?
Thanks for the bug report. By custom builds, do you mean from the variation service (in which case, what is the variation number), or that you have compiled yourself (in which case, with which options, and what development enviroment, including version)? In either case, what is the host operating system and version? Are there any odd characters (anything besides a-z and 0-9) in the path (the names of all enclosing folders)? Does it make any difference if you move the application and ROM image somewhere else (like the root folder of the boot disk)?
update - follow-up message
Sent: Sun Apr 23 05:53:45 2017
After trying to compile in Visual c++ 2005, i keep getting this message.
c:\users\emu\desktop\minivmac-3.4.1-wx86\src\CNFGRAPI.h(16) : fatal error C1083: Cannot open include file: 'windows.h': No such file or directory
See this similar previous question.
For earlier mail, see the mail index.