- #BASILISK II QUESTION MARK FLOPPY HOW TO#
- #BASILISK II QUESTION MARK FLOPPY FOR MAC#
- #BASILISK II QUESTION MARK FLOPPY FULL#
- #BASILISK II QUESTION MARK FLOPPY MAC#
Mini vMac is actually checking whether any disks are still mounted,so ejecting all disks first will get rid of the message when tryingto quit.ĭisk images that are not locked will most always be modified whenmounted by Mini vMac. Yes, there is no Shut Down command in the earliest system versions.You are instead supposed to eject all disks before turning off thepower, using the "Eject" command in the "File" menu of the Finder. PS to previous message: I did force quit Mini vMac once because of thelack of a Shut Down command in System 1.0, but then when I did Get Infoon the "sys1.1.img" file, I found it had been modified, which made menervous. I did look in both documentation and FAQ, but found nothing about this.You might add something to documentation about it.
#BASILISK II QUESTION MARK FLOPPY MAC#
So should I just force quit Mini vMac whenrunning a Mac System that has no Shut Down command? I sort-of vaguelyremember that on the earliest Macs, one simply turned the hardwareswitch off to shut it down. I see I canforce quit Mini vMac, but "at the risk of corrupting the mounted diskimage file"-which I certainly don't want to do. Onlythere is no Shut Down command in the earliest Mac Systems. When I tried to Quit Mini vMac, a message appeared saying Ishould Shut Down the emulated computer before quitting Mini vMac. I started up Mini vMac using the "sys1.1.img" disk, to see the earliestMac OS.
#BASILISK II QUESTION MARK FLOPPY FOR MAC#
You could download the source codeof zydeco's port,merge it with the latest Mini vMac source code, add colorsupport in the platform dependent layer, andthen compile for Mac II emulation. How do I get color in the iOS version of Mini vMac See the FAQsection “Emulation of a PowerPC Macintosh”. My emulated 68000 Mac will play quicktime (v1.5 or earlier) Even for Mac II emulation, the choicewas made to emulate the Mac II FPU using integer arithmetic,to ensure getting identical results on all platforms. Regardless of how it is compiled, Mini vMac would not makeany use of the ARM FPU. Is the soft float version notcompatible with your version of linux? The thought was thatcompiling a version that doesn't use the FPU ought to work onmachines with or without one.
#BASILISK II QUESTION MARK FLOPPY HOW TO#
I don't know how to cross compilein this case. After playing around with mini vMac,I decided to own a vintage real Macintosh SE.Ĭan you compile MinivMac in ARM hard floating point? The current armversion seem to use soft float. I'm considering having an option to always draw color images,though that would be less efficient. This sort of thing on Linux has been reportedbefore. I suspect the problem is that Mini vMac is drawing single bitimages to the screen, which is apparently rare these days, andso buggy on some systems. In HaveChangedScreenBuff(in MYOSGLUE.c) at the top, after the variable declarations,insert some assignments: top = 0 left = 0 bottom = vMacScreenHeight right = vMacScreenWidth
#BASILISK II QUESTION MARK FLOPPY FULL#
But the source code could be modifiedto always do a full redraw. Tabbingaway to an application (outside of the emulator) that covers theemulator window and then back to the emulator clears these artifacts.Is there an option I can use that will force a full redraw? If I drag the cursor across the screen I get littlecopies of the cursor left behind in the path of the cursor. I just compiled the latest Mini vMac from source on my x86-64laptop and it works great except for this one thing:Įvery time anything changes on the screen the graphics in that areaget messed up. Any suggestionsor patches for small changes to make Mini vMac work better withNetBSD are welcome.
It is true though that I'm no expert in NetBSD. Otherwise, I'd prefer people use a binary that I have compiled,especially if it is using the name Mini vMac. People whoknow what they're doing are welcome and encouraged tocompile their own variation of Mini vMac for their ownuse. See the topic in the FAQ -“What format is the Mini vMac source code in,and why don't you use something more standard?”.įrom my point of view, complicating making a NetBSD pkgsrc packageis feature, not a bug. Is there some place or some way where a source tarball can bedownloaded and some documentation explaining where the options can beset when compiling for the first time? I know it's neat and all that the emulation can build a tar of allthe files, but this really complicates trying to make a NetBSD pkgsrcpackage of the latest versions of Mini vMac.
0 kommentar(er)
