The first line is fine, but the build system won't acceptthe second. I've tried building the Mini vMac 3.1.1 withthe following options: -t imch -m IIx -depth 3-t imch -mem 8M -hres 800 -vres 600 -depth 3 Sorry to pester you about this, but I'm wondering what I'mdoing wrong. Unfortunately, your email address didn't work. But I could make it publicly available,such as is done for David Sibleys's OS X icons. I may not include it in thedefault compile, because of the emphasis on minimizingsize. It is now 48x48 pixels - default for an icon in a window.Could I email it to you? I have madea higher-resolution icon for it based on the current one andthe ones for the Mac OS X version. Thismakes the mini vMac icon slightly fuzzy-looking. In Windows XP (or at least, on my computer), icons in awindow are slightly enlarged to make them easy to read. So Mini vMacwill be need to be ported eventually. They'vepicked Cocoa, and are pushing hard to kill Carbon. But Apple doesn't want to waste their time supportingtwo different ways of programming a Macintosh. Which is why the port toCocoa hasn't happened yet - it's a lot of work for littlebenefit, and there are always other things to do with higherpriority. It should not make much difference to the user whetherMini vMac is programmed in Cocoa or Carbon. ![]() I just installedthe latest Mac OS X 10.6 'Snow Leopard' developer preview,and I'm itching to see how mini vmac performs on it in purecocoa. Couldyou? That would be awesome if you could. I read your latest release notes, and near the end yousuggest you might convert your code over to Cocoa. (i.e."GunShy game for Macintosh", to make it super easy.) I assume you mean the freeware game by E. I don't know of any reason to expect problems, but one can neverbe sure without testing. So it would be helpful for people who have gotten the updatealready to try out Mini vMac (both 3.0.4 and 3.1.2) and let me know ifthere are problems or if it works fine. Let me know if there is anything I can do to help. If there are any reports of problems,I will go ahead and buy the update (as happened for OS X 10.5). I don't generally move to a new OS X releaseuntil 10.x.4 or later. ![]() Not too surprisingly, I'm not really an earlyadopter type. Assume you are gearing up forcompatibility checks. In this case you should first uncompressit on a modern Macintosh, and then transfer the uncompressed files intoa disk image, as described in the Disk Image page." (Oralternatively, use a different emulator, such as Basilisk II.) 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 aStuffit file that requires a more recent version of Stuffit Expander thanwill run on a Macintosh Plus. sit.hqx file into a Mini vMac disk image.As mentioned in the FAQ,this can be done using either the ImportFlutility, or else use the host operating system to work withdisk images as described in the Disk Imagepage. Beginningwith the page“ How to get started with Mini vMac”. When all else fails, you might try reading the documentation. complete wasteof time and am going to post an honest review about this. I have tried writing theseimages to hfs800k.DSK and to mfs800k.DSK, all taken from your blanks offering.Īpparently sending email to you doesn't work (again), since Ialready replied to this.Īnyway, Disk Copy directly accesses the floppy disk hardware,which Mini vMac doesn't emulate.įortunately, you don't need to use Disk Copy. Then tried using disk Copy6.1.3 under System 7.0.1, same images, same error. ![]() Ithen rebooted to System 7.0.1 (which was downloaded from another resource andbundled with an older version of minivmac), I repeated using Disk Copy 4.2, Iused the same image files, I got the same error -17. ![]() I have raised the memory allotment for Diskcopy, no success. I have tried writing 3rd party diskette images (that were intended for 800kdiskettes in the real world), I have tried writing 800k versions of System 7.0diskette images that I downloaded from Apple I have tried writing those imagesusing Diskcopy 4.2 under both System 6.0.8 and 7.0.1, all images fail to writewith error -17.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |