But the main emphasis in Mini vMac is compile time options,which allows Mini vMac to be smaller and simpler. “-hres” and “-vres” are not commandline options, they are options to the Mini vMac build system.The few supported command line options are documented in the Mini vMac User Interfacepage. People that are new to Mini vMac don’t necessarilyneed to deal with the import issue much at first, sinceI provide lots of software already imported into disk image formaton my Macintosh Plus software page. These hooksdon’t exist in the earliest versions of Macintosh OS.Third, host drive access seems the kind of thing that could mostlywork, but frequently run into edge case issues that people wouldcomplain to me about, taking up a lot of my time. Second, if I recall correctly, Basilisk II useshooks for external file systems in the Macintosh OS. First,it would require a lot more platform specific code, making Mini vMacharder to port.
I wouldn’t completely rule out ever adding a host drive accessfeature to Mini vMac, but I don’t have much enthusiasm. Each can run some software that the other can’t. Mini vMac has more emphasis on emulating the earliestMacs, while Basilisk II has more emphasis on later Mac 68ksoftware. If you prefer to access host drives in Basilisk II, it makessense to do that, and use the disk images you create there inMini vMac. Most archivefile formats are safe to move between Windows and Mac.) (If you are not dealing with plain text,then you have to deal with the issue of files moved to Windows losingMacintosh specific information like resource forks. If you are just dealing with plain text, the utilities ClipIn and ClipOutmay be more convenient. If you have lots of files you want to import, it may be easierto create an archive of them first on Windows (in some formatthat old Macs can deal with), import the archive, and thenextract the archive inside Mini vMac. Mini vMac really really needs the ability to access host drives likebasilisk II can, I had to quit using it after 15 minutes because of howtedious it is to pack hfv disks with hfv explorer just to satisfy minivmac, the emulator is all but cut off from the outside world in it'scurrent rendition.Īlso i found that mini vmac did not recognize any of the command lineswitches you have in your documentation (like -hres and -vres).īesides HFVExplorer for Windows, my utilities ImportFl and ExportFlcan be used to get files into and out of Mini vMac disk images.(HFVExplorer is old and unmaintained, so I have doubts about howwell it will continue to work in the future.) (Note that I am not involved with this port.) Getting the actual files out might not be entirely trivial, but once you have the data it should be possible,īoth use their own hardware rather then a PC floppy controller.I would like to know if I can get Windows on my android phone?ĭo you mean running Microsoft Windows on Android? That isout of the scope of Mini vMac.īut Mini vMac, which runs versions of Classic Mac OSthat had windows before Microsoft Windows existed, has been portedto Android. Kryoflux which samples the disk to a raw data stream.There seem to be two solution for the PC: Sadly the only answer to this seems to be to find an old Mac. That leaves the problem of getting the right hardware. (OS/X 10.4 has read only access, so I guess just for backing them up modern is not even needed). Once you have them as an image you can open them with a recent Mac OS/X. Once you have that it is a simple matter of using ``dd if=/dev/floppy of=/home/mybackup bs=84 `. The downside to this is that you need a drive which can do that, and the mac was the only common computer of that era which did that.Īll of this means it that you need some non-standard-pc hardware to read the disk. This does not optimally use the capacity of the disk. If you do not vary the rotation speed then the outside part of a disk will pass much more quickly beneath the RW head. Amiga's, which skipped the inter-sector gap, and wrote 11 sectors per track.sector 1, sector gap, sector 2, sector gap.
These used up to 720KB of the maximum of 1MB which could be stored.
0 kommentar(er)
