:
Began: Mon, 07 Dec 2009 04:24:35
[mmmmna] I have tried writing 3rd party diskette images (that were intended for 800k diskettes in the real world), I have tried writing 800k versions of System 7.0 diskette images that I downloaded from Apple; I have tried writing those images using Diskcopy 4.2 under both System 6.0.8 and 7.0.1, all images fail to write with error -17. I have raised the memory allotment for Diskcopy, no success. I then rebooted to System 7.0.1 (which was downloaded from another resource and bundled with an older version of minivmac), I repeated using Disk Copy 4.2, I used the same image files, I got the same error -17. Then tried using disk Copy 6.1.3 under System 7.0.1, same images, same error. I have tried writing these images to hfs800k.DSK and to mfs800k.DSK, all taken from your blanks offering.
Apparently sending email to you doesn't work (again), since I already replied to this.
Anyway, Disk Copy directly accesses the floppy disk hardware, which Mini vMac doesn't emulate.
Fortunately, you don't need to use Disk Copy. Th
http://download.info.apple.com/Apple_Support_Area/Apple_Software_Updates/English-British/Macintosh/System/System_7.0.1/
Began: Sat, 5 Dec 2009 20:41:25
[anon] When started, doesnt work. just sits there. complete waste of time and am going to post an honest review about this.
When all else fails, you might try reading the documentation. Beginning with the page “How to get started with Mini vMac”.
Began: Sat, 29 Aug 2009 15:32:18
[anon] how do i use .sit.hqx files in system 7[?]
[me] Short answer: Stuffit Expander 4.0.1.
The first step is to get your .sit.hqx file into a Mini vMac disk image. As mentioned in the FAQ, this can be done using either the ImportFl utility, or else use the host operating system to work with disk images as described in the Disk Image page.
You can then use Stuffit Expander to unpack the file in Mini vMac. However, as mentioned in the ImportFl page, "it is common to encounter a Stuffit file that requires a more recent version of Stuffit Expander than will run on a Macintosh Plus. In this case you should first uncompress it on a modern Macintosh, and then transfer the uncompressed files into a disk image, as described in the Disk Image page." (Or alternatively, use a different emulator, such as Basilisk II.)
Began: Fri, 28 Aug 2009 00:06:53
Well, Snow Leopard is upon us. Assume you are gearing up for compatibility checks.
[me] Er, I suppose. Not too surprisingly, I'm not really an early adopter type. I don't generally move to a new OS X release until 10.x.4 or later. And as an open source programmer, i.e. poor, I'm in no hurry to spend money. If there are any reports of problems, I will go ahead and buy the update (as happened for OS X 10.5).
Let me know if there is anything I can do to help.
[me] So it would be helpful for people who have gotten the update already to try out Mini vMac (both 3.0.4 and 3.1.2) and let me know if there are problems or if it works fine.
I don't know of any reason to expect problems, but one can never be sure without testing.
Began: Wed, 12 Aug 2009 08:39:36
[anon] Can we have GunShy?
[me] I assume you mean the freeware game by E. C. Horvath.
Yes, that is easy to find with Google. (i.e. "GunShy game for Macintosh", to make it super easy.)
Began: Sat, 1 Aug 2009 14:58:35
[anon] I read your latest release notes, and near the end you suggest you might convert your code over to Cocoa. Could you?? That would be awesome if you could. I just installed the latest Mac OS X 10.6 'Snow Leopard' developer preview, and I'm itching to see how mini vmac performs on it in pure cocoa.
[me] It should not make much difference to the user whether Mini vMac is programmed in Cocoa or Carbon. Which is why the port to Cocoa hasn't happened yet - it's a lot of work for little benefit, and there are always other things to do with higher priority. But Apple doesn't want to waste their time supporting two different ways of programming a Macintosh. They've picked Cocoa, and are pushing hard to kill Carbon. So Mini vMac will be need to be ported eventually.
Began: Mon, 20 Jul 2009 13:17:40
[Vince] In Windows XP (or at least, on my computer), icons in a
window are slightly enlarged to make them easy to read. This
makes the mini vMac icon slightly fuzzy-looking. I have made
a higher-resolution icon for it based on the current one and
the ones for the Mac OS X version.
It is now 48x48 pixels - default for an icon in a window.
Could I email it to you?
[me] Sure, I'd be interested. I may not include it in the default compile, because of the emphasis on minimizing size. But I could make it publicly available, such as is done for David Sibleys's OS X icons.
Unfortunately, your email address didn't work.
Began: Tue, 14 Jul 2009 13:35:24
[Charles] Sorry to pester you about this, but I'm wondering what I'm doing wrong. I've tried building the Mini vMac 3.1.1 with the following options:
-t imch -m IIx -depth 3 -t imch -mem 8M -hres 800 -vres 600 -depth 3
[me] The first line is fine, but the build system won't accept the second. I assume there was a "-m IIx" in this one also. You could use ClipOut so I could be sure of exactly what options you are using.
[Charles] Ah, my bad. [...] The original did indeed have a -m IIx in it. [...]
However, the resulting build never shows anything but Black & White in the "Monitors" control panel. I know it's *possible* to get color to work, because your prepackaged build #27 works fine with color with the same ROM and disk image. However, I'd like to build it myself, and my perfectionist gene isn't going to allow me to quit until I figure out what I've been doing wrong, especially since it's probably something fairly simple.
Any pointers?
[me] What version of XCode are you using? If not 2.4.1, then you should use the "-ev" option. (the Mini vMac alpha also supports "-ev 3100")
The generated "CNFGGLOB.h" file should contain the line:
"#define vMacScreenDepth 3"Does it?
[Charles] That did it. I'm using Xcode 3.1.2, so I tried adding -ev 3120 and it now works in color. Thanks! [...]
[me] That narrows down what I should look into. Thanks.
[me] I've looked into it now, but I wasn't able to reproduce the problem. If you can reproduce the problem, I'd be interested in seeing the ".tgz" archive the build system generated. It may also help to know what system version you're using in Mini vMac.
Began: Tue, 7 Jul 2009 21:54:04
[Sen Holiday] I've been trying to get the mini vmac to work on my Mac OS X (Intel) laptop, and I've been able to open the old desktop screen, however I can't interact with it. I can drag things into it and open them in that way, but I can't click on anything on the screen, and my computer doesn't recognize the mini vmac as the selected program.
I've no idea what the problem is, but I was pretty fond of the old Apple - but as durable as it is, it's dying on me. I'd appreciate any tips.
[me] That's very odd. One thing to try is making a new account on your computer (System Preferences -> Account Panel, unlock if needed, and click the plus button). Then log in to the new account, and see if Mini vMac works there. If so, something in your old account is corrupted. (Or possibly Mini vMac might be incompatible with some valid preference setting.)
Otherwise, some further information would be useful to me:
* What version of OS X are you using (like 10.4.11 or 10.5.7)?
* I assume you're using Mini vMac 3.0.4? Does the new alpha version behave the same way?
* When you say "my computer doesn't recognize the mini vmac as the selected program", do you mean that it doesn't show up in the Dock, and in the Command-Tab list of running programs? Or if it is in the dock, if you control click on its dock icon, do you see some message about application not responding? (Your description of the problem would be consistent with Mini vMac completely hanging at some point.)
* When you say "I can drag things into it and open them in that way", do you mean dragging disk images onto the Mini vMac icon, or can you drag images into the Mini vMac window? Do you mean Mini vMac successfully booted off the disk image (you see the Finder running in the Mini vMac window)? Did you hear the start up beep?
* Does keyboard emulation work? If you can drag a bootable image into Mini vMac, you should be able to try Command-A, Command-O, Command-W (Select All, Open, Close). Otherwise, does the Mini vMac control mode work? That is, if you hold down the control key, do you see the Control Mode overlay (with the words: "Control Mode (Type 'H' for help)")? (If Mini vMac is completely hung, then neither of these will work.)
* What other non Apple software have you installed? Especially, what software that required an administrator password to install?
[Sen] Oh, wow. Nope, the alpha version works perfectly. Thanks for getting back to me so quickly and with so much detail--I'm really looking forward to using this!
[me] Well, good. If not very informative.
no older mail (Index)