Boot disk too small, any options?

jrindfuss · Post by **jrindfuss** » Tue Apr 29, 2008 1:32 am

Hi ... I'm having trouble getting going with Sheepshaver. I originally tried to install off of a boot disk that was from an iMac, not an original install disk. I found the work around with modifying the one preference file and got past the first error, but it still would not work. So, I then found online someone who had a virutal boot disk all ready with a system already loaded, but they created it very small, only 120MB.

Here's my problem ... this virtual disk will work, but it's not very functional ... I can't load many fonts onto it (not enough room) and it also will not allow me to delete anything off of it .. gives me an error -127 whenever I try to move anything to trash.

I don't know what to do ... I have an original install disk for OS 8, but for some reason, it will not work. I have a MILLION update disks because I've had Macs for 15+ years. I don't want to buy another original 9.0 disk because (1) it makes me mad that I should have to do it and (2) I'm not convinced that it will work for me, either, since I'm having with the 8.0 install.

Please help...
(1) Can someone help me get my update disks to work for the install so I can create a virtual boot disk that is larger, or
(2) Is there anyway to modify this virtual disk from 120MB to be larger, or
(3) Does anyone have a virtual boot disk that IS larger that they would be willing to email to me?

I'm tired and I just need it to work ... any help would be appreciated.

boyanml · Post by **boyanml** » Tue Apr 29, 2008 6:27 am

You can see this:

http://www.emaculation.com/forum/viewto ... 6667#26667

HTH

jrindfuss · Post by **jrindfuss** » Wed Apr 30, 2008 1:20 am

Thank you so much ... that post would be helpful except every time I try to copy or trash anything within the Sheepshaver environment, I get the error -127 or an error that says I don't have the correct priviledge. I don't understand what I'm doing wrong.

Post by **Cat_7** » Wed Apr 30, 2008 7:37 am

Hi,

Assuming you are running on OSX, this might work:

-You can open the current disk image with diskimagemounter (for easy access change the file extension to .dmg)
-Create a new larger disk image with SheepShaver's GUI and open it with diskimagemounter as well.
-Copy the contents of the old image to the new one.

You can then run sheepshaver with both disk images (make sure to boot from the old one, so keep it at the top of the volumes list) and bless the system folder on the new disk image. Then change the order of the disks in the volumes list and boot with the new image.

But if this remedies the error you are getting remains to be seen. They might be related to the installation/partial installation of the system software of an unsupported Mac model on your original disk.

Good luck,
Cat_7[/b]

jrindfuss · Post by **jrindfuss** » Thu May 01, 2008 6:25 pm

I'm running 10.5.2 on a new MacBookPro. I had to really look to find the diskimagemounter, but when I did, I clicked it to open it up and it expanded like it was opening, but then nothing else happened. I tried to drag the disk image onto the diskimagemounter icon and it attempted to open it, but came up with the warning 'disk image may be damaged and could damage your system'. When I click either open or don't open, it still tried to mount it, but said 'unmountable'.

I'm at a loss.

I tried to start all over using an 8.1 original install disk, but when I launch Sheepshaver through the GUI, it says 'this startup disk will not work on this Macintosh model. Use the latest installer to update the disk'.

Nothing seems straight forward.

Thu May 01, 2008 9:07 pm

SheepShaver for MacOSX needs MacOS 8.5, 8.6, 9.0 or 9.0.4. A original generic install CD (generic = not one provided with a new Mac) for any one of those MacOS versions should work fine. MacOS 8.0 or 8.1 cannot be used with SheepShaver for MacOSX, anyway not with most ROM files.

Cat7 pointed you to diskimagemounter, but it is not supposed to be used this way. When you change the image file name to have a .dmg file name extension, the image should mount by simple double-clicking the image file icon. If that does not work, accessing diskimagemounter directly will also not work.

The best way to do the copying is to do that in the MacOS Finder in SheepShaver. I do not understand why copying files from your boot volume to a newly created volume in MacOS in SheepShaver does not work. It should be easy. A error -127 is a file system error. It could be that the file system on the boot image is corrupted.

I wonder why the system is on such a very small image. Maybe the image is not supposed to be used the way you do. maybe it is only intended for transporting the installation to be used on a larger image? Where have you found that file? (Send the url in a private message, it should not be published here.)

JeanJacquesCortes · Post by **JeanJacquesCortes** » Sat May 03, 2008 11:34 pm

Under Leopard or XP, I use a boot disk which weights 1 GB, and it runs fine.
It contains Mac OS 9.0.4 with Finder 9.2.2 and tons of programs.
If you have a lot of programs, you can create several boot disk by duplicating the first one, and adding different programs in each disk.

yksoft1 · Post by **yksoft1** » Wed May 07, 2008 10:15 am

Ronald P. Regensburg wrote:SheepShaver for MacOSX needs MacOS 8.5, 8.6, 9.0 or 9.0.4. A original generic install CD (generic = not one provided with a new Mac) for any one of those MacOS versions should work fine. MacOS 8.0 or 8.1 cannot be used with SheepShaver for MacOSX, anyway not with most ROM files.

with my 9500 ROM, Sheepshaver for Mac OS X can even run System 7.5.3 (without network support).