E-Maculation

Used sheeps saver witht MacBook Pro under OS Catalina just finer- After upgrading to Ventura (OS 13.01) and migrating all data from Time machine Backupsheep , Ssaver would not want to launch. Its just popping up for a second to shut down again . what went wrong. I followed the suggestions in the posting ( crash- Ventura) but without suceess. Im stuck. .. appreciated any help .

A simple upgrade in place from Catalina to Ventura will not stop SheepShaver to work. But you would also not need the backup. So I suppose you changed to a new Mac.

I do not know how you "migrated" from the Time Machine backup. If you copied the SheepShaver files instead of migrating all of the user files using Migration Assistant, SheepShaver will not work in its new location and you will need to recreate the setup. You can use the copied files, though.

Exactly how did you "migrate" and if you copied the SheepShaver files, exactly which files and folders did you copy?

thanks for the quick response. I only used the migration tool with TM backup and did not manually copy anything The MacBok is still the same.
Tried to make a fresh installation, didnt work - maybe soemthing is still mssing, Im not quiet clear what is meant by the "ROM". I tried it with the newworld86.rom and the OS9 img from the source captured in one of your posts.
I got this in my progranm folder:
sheepS app
sheeps folder with build history,keycodes, 9 mac OS ROM, setup manual and the 2 scrpt foles delet Prefs and zap pram , which I ran both.

Can you possibly guide me through the setup steps. especially the section of getting the classic enviromet (OS 9) involved. The procedure described on their homepage is not very clear- especially the part of getting a "ROM" ?? very confusing.....
Thanks for your help

I am not sure why you used a migration tool (Migration Assistant?) or the Time Machine backup when you upgraded from Catalina to Ventura on the same machine. After upgrading, everything should still be in place and working as before.

Anyway:
- As described in te setup manual, to start a fresh SheepShaver setup the SheepShaver application should be inside the SheepShaver folder (with at least also the Mac OS ROM file).
- Whether you use the old world rom or the new world rom from Redundant Robot depends on the MacOS version you will be using. For MacOS 9 best use the new world rom (see setup manual).
- Make sure that the rom file is renamed Mac OS ROM without the file name extension. You can check in Finder Info for the file if the extension is indeed removed and not just hidden.
- Do not use the OS9 boot disk image from Redundant Robot. Download a proper OS installation disk image like the one from Macintosh Garden (see setup manual).

Our setup manual is here: https://www.emaculation.com/doku.php/sh ... os_x_setup

many thnaks again- sorry I forgot to mention- that since the upgrade tool for ventura somehow crashed my whole HD I had to do a complete clean inst. of VEntura- erasing my entire HD before that. So this is why i had to use the migration tool to get my data back from the TM backup.
Ill try the steps suggested and will rveret back.
cheers

great guide!! thank you so much. This one was clear and precise. My main mistake was that the SS app was not in tthe same ss folder.
All works perfect now -almost as it used to before with one exception:
In my previous version under Mojave and catalina I was able to directly access fiels from my Mac OS 10 HD and even from volumes mounted on the desktop. I have no clue how I did it- Now I cant see my HD or anything else on my mac users desktop anymore in the unix or Mac OS 9 HD. It was a very conveniant solution and better than copying files needed first to the shared folder in oder to access them on the "other side" with the unix folder. or OS 9 HD. Any ideas?

Maybe you kept the default "Unix Root" setting "/" , which would have made all of your macOS 10 HD the shared folder. We always discouraged users to do that because in the past the Unix/shared folder feature had issues that could lead to file loss. But I am not sure what your "Unix Root" setting could have been. This setting would not make mounted volumes on the host accessible from within SheepShaver. You could make a mounted volume the shared folder, but that would give only access to that volume in "Unix".

With recent macOS versions the organisation of the internal HD (or SSD) has become much more complex and making that disk the shared folder will not work the same anymore. If you want wider access, you could try and make your Desktop folder or your Documents folder the shared folder.

I find the safest folder to use as the "shared" folder is /Users/Shared/ . It's always guaranteed to have the right default permissions and is accessible to every account on the machine. Although I actually share a folder inside the Shared folder, just so I can use Shared for other things and not have conflicts.