marksmithhfx
Member
Hi, I started this topic in *NIX by accident. Forthwith, I will copy the conversation here and continue...
"I was wondering if anyone could help me load Double Helix (Motorola 68k version) downloaded from the Macintosh Archive into Mini vMac version 36.04. I have tried a couple of things but so far no luck. Part of the challenge seems to be the size of the file which is around 1MB. Thanks"
"Just to provide a bit more detail, I have Mini vMac v36.04 running fine on my laptop running Mojave (10.14.6). I have installed System Software 6.0.8 and ImportFl-1.2.1 all working fine. I dloaded the Double Helix.sit file from the repository (https://www.macintoshrepository.org/7324-double-helix) but when I launch ImportFl and copy the .sit file to it I get a "Disk full" error message. Wondering what I can try next."
olePigeon: "You might want to try using Basilisk because it has a built-in Shared Folder feature that shows up as a hard drive in the VM. You can then readily transfer files back and forth between the host computer and the VM just by dropping files into the shared folder."
"Thanks, I will give this a try and let you know how I make out. Cheers!!"
So, tried to get Basilisk going but no luck. I followed the Youtube example exactly, made sure all of the files are in the right place, but when I fire it up i get this message: BasiliskII error: Could not start BasiliskII: (no such file or directory). So, a path problem somewhere but I've been unable to track it down. And the message seems to suggest the it can't find BasiliskII which is in fact in the same folder as this "launcher" program (its called BasiliskGUI, and it doesn't let you configure where BasiliskII is (an oversight in my view) but it is in the same folder so should be findable. Anyway, my setup looks identical to the one being demo'ed on Youtube so still a bit of work to sort this one out.
In the meantime I also posted a message to Paul Pratt (in Gryphel Project Mail) ... Paul currently maintains Mini vMac and he responded very promptly with the solution. Basically, using the "blanks" disk archive you can add more disk space to Mini vMac (he suggested 3 MB, I ended up going with 4 because of needing room to unzip and install Stuffit Expander). Once I followed his advice I was able to launch Double Helix. Really, it feels like a small miracle when you can run a '91 68020 (or thereabouts) piece of software on a 2017 Intel Core i5 processor. Very nice stuff indeed, and my hats off to Paul and the many others who have continued to develop Mini vMac.
I'm hoping to get back to Basilisk later in the week, there is a program in my directory called BasiliskII Disk Image Chooser which, when launched, offers a number of possibilities. This might be the solution. If I get it sorted I will let you know.
Tip of the hat to olePigeon as well for responding and getting me started down one path, that may yet prove fruitful.
Mark
"I was wondering if anyone could help me load Double Helix (Motorola 68k version) downloaded from the Macintosh Archive into Mini vMac version 36.04. I have tried a couple of things but so far no luck. Part of the challenge seems to be the size of the file which is around 1MB. Thanks"
"Just to provide a bit more detail, I have Mini vMac v36.04 running fine on my laptop running Mojave (10.14.6). I have installed System Software 6.0.8 and ImportFl-1.2.1 all working fine. I dloaded the Double Helix.sit file from the repository (https://www.macintoshrepository.org/7324-double-helix) but when I launch ImportFl and copy the .sit file to it I get a "Disk full" error message. Wondering what I can try next."
olePigeon: "You might want to try using Basilisk because it has a built-in Shared Folder feature that shows up as a hard drive in the VM. You can then readily transfer files back and forth between the host computer and the VM just by dropping files into the shared folder."
"Thanks, I will give this a try and let you know how I make out. Cheers!!"
So, tried to get Basilisk going but no luck. I followed the Youtube example exactly, made sure all of the files are in the right place, but when I fire it up i get this message: BasiliskII error: Could not start BasiliskII: (no such file or directory). So, a path problem somewhere but I've been unable to track it down. And the message seems to suggest the it can't find BasiliskII which is in fact in the same folder as this "launcher" program (its called BasiliskGUI, and it doesn't let you configure where BasiliskII is (an oversight in my view) but it is in the same folder so should be findable. Anyway, my setup looks identical to the one being demo'ed on Youtube so still a bit of work to sort this one out.
In the meantime I also posted a message to Paul Pratt (in Gryphel Project Mail) ... Paul currently maintains Mini vMac and he responded very promptly with the solution. Basically, using the "blanks" disk archive you can add more disk space to Mini vMac (he suggested 3 MB, I ended up going with 4 because of needing room to unzip and install Stuffit Expander). Once I followed his advice I was able to launch Double Helix. Really, it feels like a small miracle when you can run a '91 68020 (or thereabouts) piece of software on a 2017 Intel Core i5 processor. Very nice stuff indeed, and my hats off to Paul and the many others who have continued to develop Mini vMac.
I'm hoping to get back to Basilisk later in the week, there is a program in my directory called BasiliskII Disk Image Chooser which, when launched, offers a number of possibilities. This might be the solution. If I get it sorted I will let you know.
Tip of the hat to olePigeon as well for responding and getting me started down one path, that may yet prove fruitful.
Mark
Last edited by a moderator: