SheepShaver Preferences mangled by COI
Moderators: Cat_7, Ronald P. Regensburg, ClockWise
-
- Inquisitive Elf
- Posts: 26
- Joined: Wed Nov 01, 2017 11:18 pm
SheepShaver Preferences mangled by COI
Hello
Maybe someone has some insight. I think I was not careful enough.
So here is the issue.
I once used COI (Classic on Intel) but I thought I should move over to the official SheepShaver. I had the latter working fine but then I thought I should run COI just to compare the mouse pointer tracking — yes COI is perfectly smooth but then I launched SheepShaver and realized that it just quits now. The problem is that I can't find a way to open the SheepShaver preferences dialogue because it just quits before I get a chance to reach for the menu to call it up.
I understand from something I read on github that the plist file can be simply edited but before I go that more cryptic route is there a workaround to get the preferences for SheepShaver version 2.5 (2019-04-01) on screen?
Maybe someone has some insight. I think I was not careful enough.
So here is the issue.
I once used COI (Classic on Intel) but I thought I should move over to the official SheepShaver. I had the latter working fine but then I thought I should run COI just to compare the mouse pointer tracking — yes COI is perfectly smooth but then I launched SheepShaver and realized that it just quits now. The problem is that I can't find a way to open the SheepShaver preferences dialogue because it just quits before I get a chance to reach for the menu to call it up.
I understand from something I read on github that the plist file can be simply edited but before I go that more cryptic route is there a workaround to get the preferences for SheepShaver version 2.5 (2019-04-01) on screen?
-
- Inquisitive Elf
- Posts: 26
- Joined: Wed Nov 01, 2017 11:18 pm
Re: SheepShaver Preferences mangled by COI
For now, I am using the script to delete the plist and will try to get the Mac ROM in the same folder as SheepShaver.app. From what I understand, the initial setup calls for this. If I am genuinely stuck I will come back but this appears to be the workaround.
- adespoton
- Forum All-Star
- Posts: 4284
- Joined: Fri Nov 27, 2009 5:11 am
- Location: Emaculation.com
- Contact:
Re: SheepShaver Preferences mangled by COI
Yes, both methods are documented on this site. You can either manually edit the preferences file by going to Terminal.app and typing , or run the script that should be in your SheepShaver folder that just erases that file so you can start from scratch in the graphical prefs editor.
And yes... COI works by overwriting ~/.sheepshaver_prefs with its own custom settings every time you launch it.
I get around this by a) not using COI, and b) using .sheepvm bundles that contain my ROM image, disk images, and preference file.
Code: Select all
open ~/.sheepshaver_prefs
And yes... COI works by overwriting ~/.sheepshaver_prefs with its own custom settings every time you launch it.
I get around this by a) not using COI, and b) using .sheepvm bundles that contain my ROM image, disk images, and preference file.
-
- Inquisitive Elf
- Posts: 26
- Joined: Wed Nov 01, 2017 11:18 pm
Re: SheepShaver Preferences mangled by COI
Code: Select all
$ /Applications/SheepShaver/SheepShaver.app/Contents/MacOS/SheepShaver ; exit;
SheepShaver V2.5 by Christian Bauer and Mar"c" Hellwig
ERROR: Cannot open ROM file.
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...none found.
[Process completed]
-
- Inquisitive Elf
- Posts: 26
- Joined: Wed Nov 01, 2017 11:18 pm
Re: SheepShaver Preferences mangled by COI
Thanks for the insight, I will investigate the vm method, sounds like a sandboxy kind of thing. COI was easy because there is actually a turn key solution on archive.org. Although I have a good number of physical machines and original OSs laying around, there are advantages to just run things inside a VM on my High Sierra and Majove machines.
Really apprecaite strategies 1 and 2. I've done 1 but I will certainly dig a little deeper on the second approach.
Really apprecaite strategies 1 and 2. I've done 1 but I will certainly dig a little deeper on the second approach.
-
- Inquisitive Elf
- Posts: 26
- Joined: Wed Nov 01, 2017 11:18 pm
Re: SheepShaver Preferences mangled by COI
Something strange is going on.
So I have
and within it I have only the new world ROM from Redundant Robot, named and the SheepShaver app version 2.5 (2019-04-01).
I killed the
I launch SheepShaver, a new is created but SheepShaver just quits.
Isn't what I have the bare minimum to allow me to get a flashing question mark screen — enough to allow for the preferences dialogue to open?
A little confused at this rate so I will give the solo prefs app a whirl — http://www.emaculation.com/sheepshaver/ ... rPrefs.zip
So I have
Code: Select all
~/Desktop/SheepShaver
Code: Select all
Mac OS ROM
I killed the
Code: Select all
~/.sheepshaver_prefs
Code: Select all
~/.sheepshaver_prefs
Isn't what I have the bare minimum to allow me to get a flashing question mark screen — enough to allow for the preferences dialogue to open?
A little confused at this rate so I will give the solo prefs app a whirl — http://www.emaculation.com/sheepshaver/ ... rPrefs.zip
-
- Inquisitive Elf
- Posts: 26
- Joined: Wed Nov 01, 2017 11:18 pm
Re: SheepShaver Preferences mangled by COI
The 'solo prefs app' as I referred to it, rightly called SheepShaverPrefs.app, saved the day. Back up and running.
- Ronald P. Regensburg
- Expert User
- Posts: 7835
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Re: SheepShaver Preferences mangled by COI
- The download from Redundant Robot is newworld86.rom.zipAlexSantos wrote:and within it I have only the new world ROM from Redundant Robot, namedCode: Select all
~/Desktop/SheepShaver
and the SheepShaver app version 2.5 (2019-04-01)Code: Select all
Mac OS ROM
- After decompression you get the file newworld86.rom
- Rename that file Mac OS ROM without the .rom extension!
Note: After renaming the file the .rom extension may still be there, now hidden in the Finder. You can check that (and remove it if it is still there) in the Finder Info panel for the file (select the file and hit command-I).
Last edited by Ronald P. Regensburg on Thu Apr 11, 2019 7:56 pm, edited 1 time in total.
Reason:
Reason: