To send mail to me, use the feedback form.( - latest - )
Sent: Sun Apr 24 00:03:16 2016
Well its [... email address ...] agien the reason why I can't put Mario teaches typing on a dsk or img. Because I don't have a computer. I only have and android so that's why I need you to make one and add it to the game list
Sorry, because of trying to follow the letter of copyright law, I have nothing to add to the previous reply.
Sent: Fri Apr 22 21:07:37 2016
I have a problem while trying to compile Mini vMac using Xcode 7. It keeps showing up an error saying that it cant save it to my Mac or something like that. What do I do?
See the reply to this similar previous message.
Sent: Thu Apr 21 22:02:42 2016
I Want You to make a dsk image of Mario Teaches Typing And here is a link to the Mario teaches typing sit file. [ ... url ... ]
From [... email address ...]
Sorry, the policy of gryphel.com is to not link to or host abandonware.
Sent: Wed Apr 20 20:26:31 2016
Now that we've been able to compile and deploy iOS apps for almost a year, any chance that we can get an iOS target direct from you?
I've been deploying Provenance to my non-jailbroken phone since last summer, and it works great! Seems to me Mini vMac should be of similar or simpler complexity to deploy this way.
- [... email address ...]
I might eventually learn something about programming for Android and iOS for paid work, which could lead to including ports to them in my version of Mini vMac. But not likely anytime soon.
Sent: Mon Apr 18 16:04:11 2016
I've been struggling a bit to use mini vMac on ubuntu 15.10 for the past few days.
I'd like to let you know that I had graphic troubles on two different computers (screen is only partially refreshing) when using default builds for linux (both 32 and 64 bits versions).
However, when I rebuild using the sdl api option, everything works perfectly.
It might come handy for future users to let a sdl pre-compiled version available in the downloads section.
By the way, I had troubles with my keyboard layout with sdl2 but I don't think it has anything to do with mini vMac...
Anyway, thanks a lot for your work, it was really fun to be able to play with my children to Lode Runner in all its glory!
Have a good day
This sort of thing has been reported before. “I suspect the problem is that Mini vMac is drawing single bit images to the screen, which is apparently rare these days, and so buggy on some systems. [...] I'm considering having an option to always draw color images, though that would be less efficient.”
The original SDL port was made as a stepping stone to other ports. It wasn't intended to be used because it lacked certain features. Recently though there is the port to SDL 2, thanks to Manuel Alfayate, which is less lacking. So it might be worth considering making available builds using it.
Sent: Sat Apr 16 19:48:31 2016
I am on android and I was wondering how to import . sit archives with an android phone without a computer. If there is a way please reply. Thank you.
Sorry, I'm not involved in the Android port of Mini vMac.
Sent: Sat Apr 16 05:42:22 2016
how to use this project because I'm not engineer and I'm not computer worker
You could start with Getting Started with Mini vMac. If you then have any more specific questions, ask me, so that I can try to improve the documentation.
Sent: Fri Apr 15 20:12:12 2016
I want to play Mario Teaches Typing
That's good. I found a report that it works in Mini vMac (and also SheepShaver and Basilisk II). You could first learn to use Mini vMac (starting with Getting Started with Mini vMac), and then try getting Mario Teaches Typing to work in it.
Sent: Wed Apr 13 20:22:30 2016
I can't seem to compile either Mini vMac 3.3.3 or the 3.4 Alpha under Xcode 7.3. It gives an error with the My Mac destination but I can't find any obvious way to adjust it (control-clicking it didn't let me change the build type or anything).
I'd rather compile my variations myself rather than load you with more requests.
Appreciate any reply, my email is [... email address ...]
Did you use the “Development Environment Version” option in the build system, and use “-ev 6400” for Xcode 6.4, for the last version I checked this with? It won't compile with the default for this option in recent versions of Xcode.
Not requesting a variation from the Mini vMac Variations Service won't save me time. It's pretty automated, and each additional variation can take me as little as a few additional seconds. Responding to feedback takes way, way longer.
On the other hand, it is good to get feedback on issues like this.
Sent: Wed Apr 6 02:48:49 2016
Hi, I’ve been a user of Mini vMac for about 9-10 years now, and enjoyed every moment of using it. I do have a possible bug report though. The ClipIn Desk Accessory extra does not work in System 6 with MultiFinder turned on, the standard non-multitasking Finder must be enabled for it to work. I have tried System Software versions 6.0.3, 6.0.5 & 6.0.8, using a freshly installed copy of each, with a fresh copy of Mini vMac and ROM, with the same results. I primarily use a custom variation of Mini vMac, but for these quick tests, I downloaded the standard x86 Mac one.
The ClipOut Desk Accessory does work without issue as far as I can tell, however.
Thank you for this bug report. I have reproduced this issue. It seems to have to do with the “DA Handler” application used by Multifinder in System 6 to contain Desk Accessories.
So a work around for now that seems to work is to hold down the option key before running ClipIn. This causes the Desk Accessory to be run in the heap of the current application, instead of in DA Handler.
Actually, without the option key it doesn't work correctly for another reason. If another Desk Accessory is already running in DA Handler, then after ClipIn quits the DA Handler remains the active application. (If no other Desk Accessory is running, then DA Handler quits after ClipIn does, and the original application is reactivated, as desired.)
Sent: Fri Apr 1 00:18:21 2016
Your minimac stuff looks to be awesome. Please help me with the following request. I have to use a bunch of old MacPlus software (I have all the original disks) and get information off of floppy disks and old Mac Hard Drives.
The MacPlus CRT screens are failing, but I would like to run a bunch of my old software and files (I even have a version of Mathematica that ran on my 4MB of ram MacPlus that I want to use).
Can you compile a version of the MacPlus emulator that will work on Jessie Raspian Linux? In particular, I want to use it on the Raspberry Pi 3. I currently have DOSBOX for the raspberry Pi 3, and can run my original disks version of Win 3.11 and associated software, including an old DOS version of Lotus 123.
I would like to be able to do the same with my Mac Stuff. I think the last system with Motorola 68000 that worked decent was system 6.0 or 6.2 if I recall correctly. When they went to System 7, again if I recall correctly, you had to buy new versions of all the software, or else there was some other problem running system 7 on the Plus (like it was too big and a memory hog and slow, I don't remember.
Anyway, would you compile a version of your program for the MacPlus emulation to run on the Raspberry Pi3 running the Jessie Raspian Linux operating system? This will make a lot of good Mac software available to a lot of people. I still have my old Mac Plus, but alas, the external SCSI hard drives have failed (I'm hoping I can still get them to run or recover the information on both of them, they were big for the time, like 200 and 300MB drives with lots of stuff on them.
The RPI's are really catching on like wildfire and especially with the younger generation. This would really be a service, not only to us old guys, but also the next generation who have never seen a MacPlus and how good they were with a memory upgrade and fast and large hard drives.
I also would like to be able to print to my original Apple Laser Writer (postscript) from the emulator. I can not toss it, since I paid 4,000 back in 1986-87 or so for it, and used it with PC's but it does not have enough memory for the lastest generation of printing software drivers. I would like to be able to print from the MacEmulator on the RPI3 to the Apple Laser Writer (Yes, i have spent money to replace the gum rubber rollers and other components that turn to goo after about 15-20 years and fixed my Laser Writer Plus. Now I would like to use it, it has a giant toner cartridge (prints like 7k pages with one toner cartridge) and also has a nice RS232 serial input that one can print postcript to, without having to use the appletalk.
Keith [... last name, email address, position ...]
Mini vMac for Linux on ARM, available from the Download page, should work on Raspbian as far as I know. I haven't tried it out recently myself, to make sure it still works on recent versions. Hopefully someone would have told me if it didn't.
Transferring information from your old floppies and hard drives to a modern machine is tricky. You could use a machine of intermediate age to translate - the exact details depend on the exact hardware you have. Or you could hire a Disk Conversion Service. Or, for as long as your Mac Plus still functions, you could use the Floppy Emu Disk Emulator by BMOW to transfer files to an SD card.
If you have a way to send a postscript file to your Laser Writer, then there is a way to print from Mini vMac. See the "How can I print from Mini vMac?" question in the FAQ.
Sent: Thu Mar 31 13:56:45 2016
I'm trying to get vMac to work so I can use Macintalk for a music project. I've done everything except extract the floppy image (that is going to be tricky), so I should be able to see the startup screen asking for the disc but instead all I get is a black screen. I suspect it's a graphics issues as I can hear a Mac beep at the beginning.
I'm runnning windows 10.
It does sound like it could be a graphics issue. I've seen a few similar reports of issues on Linux systems, where I suspect drawing images with one bit per pixel to the screen isn't properly implemented. This is the first I've heard that Windows could have the same problem.
I'm contemplating modifying Mini vMac to avoid drawing one bit per pixel images by default, converting the emulated black and white screen bitmap to at least 8 bits before drawing. This would be less efficient, but more likely to work on modern systems. I'd make a compile time option to allow the current more efficient one bit drawing.
Sent: Wed Mar 30 11:59:10 2016
Hi Paul, great job so far on your work with Mini vMac. I do have a question for you though: wouldn't it have been easier to have worked on emulation for the 68000 Color Classic system first then start adding in the Mac II systems?
Sorry if it has been asked before and I missed your reply or posts about it.
Not really. A Macintosh Color Classic is not a Macintosh Classic with color added. It is basically a descendent of the Macintosh II (with a 68030 CPU, not 68000) in approximately the shape of a Macintosh Classic.
Sent: Fri Mar 18 02:05:43 2016
do you have mini vMac for 2001 palm pilot
i have Sony clie Palm OS PDF
No. But it seems someone did at least start a Palm SDL port, which could at least be used as a start of a Mini vMac for Palm port, if anyone wanted to work on it. See the “-api sdl” build option. And this previous message regarding porting to DOS.
Sent: Fri Mar 18 18:01:56 2016
I'm working on a port for the Nintendo 3DS and I have a question.
I did the DS port ages ago and I would like to try again and hopefully do a waaaay better job and not make another bad hackjob like the last one was.
What is the best way to determine how well the emulator is performing?
I'm running into a situation in RunEmulatedTicksToTrueTime where EmVideoDisabled is being set to true, yet it's also not showing that the emulation isn't fast enough.
I'm not going to try optimizing any further at the moment since I still need to get a working user interface but I thought it was strange.
Email: [... email address ...]
One possibility is that the whatever timer you are using doesn't have high enough resolution (not enough to give 60 distinct ticks a second).
One way to getting a sense of what is going on is by adding calls to log debug information.
Mini vMac has infrastructure for doing logging fast enough to not interfere with the operation of the program too much. This is enabled in the build system with the "-log" option, which turns on the "dbglog_HAVE" flag in CNFGGLOB.h. You have to implement dbglog_open0, dbglog_write0, and dbglog_close0 in your MYOSGLUE code.
See the "dbglog_HAVE" section of MYOSGLUE.h for available debug log routines.
You could, for example, call dbglog_writeln at the start and end of RunEmulatedTicksToTrueTime, also at the places in it where EmVideoDisable is turned on and off. And then you could call dbglog_writelnNum in your ExtraTimeNotOver routine to report the current time.
Sent: Mon Mar 7 14:27:18 2016
IÝve been playing with macOSX Server 1.2 Rhapsody and was wondering if Mini vMac could be build for this platform . It as a BSD base, and seeing Free/net/Open BSDs are supported (but X86 only), maybe it could be done ? Note IÝm really not a coder , and Rhapsody is really a dead OS now, but if you have any lead to do that, would appreciate.
According to Wikipedia, Rhapsody has a "Blue Box environment" for running classic Macintosh applications, though only on PowerPC. So Mini vMac for Macintosh OS 9 and earlier should work, if you are using the PowerPC version.
Otherwise, the Yellow Box environment is said to have later evolved into Cocoa. So the Cocoa port of Mini vMac (compiling it with -api cco), may work, or more likely, could be made to work.
The Free/net/Open BSDs ports of Mini vMac use the X Window System, which perhaps could be adapted for Rhapsody if it has an X Server like modern OS X does (The X11.app utility.)
By the way, Mini vMac could probably be compiled without problems for BSDs for other architectures besides x86 and x64. I just haven't tried it myself.
Sent: Mon Jan 4 23:24:43 2016
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)
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.
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
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.
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.
Sent: Sun Oct 25 18:06:20 2015
its not working
See the reply to this similar previous message.
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.
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.
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.