first time configuration of SheepShaver .. no startup

About SheepShaver, a PPC Mac emulator for Windows, MacOS X, and Linux that can run System 7.5.3 to MacOS 9.0.4.

Moderators: Cat_7, Ronald P. Regensburg, ClockWise

Post Reply
dragonfly
Student Driver
Posts: 21
Joined: Sun Mar 06, 2005 9:24 pm

first time configuration of SheepShaver .. no startup

Post by dragonfly »

So far, I have installed Basilisk II, Mac System 7.5.3 on Win XP Pro.

Now I am trying to install Mac OS 8.5 on SheepShaver.
I have a Mac OS 8.5 CD, with ROM on this disk in system folder, so I thought I might start there.

...

Following the instructions here to extract ROM .. reads ..
If you have the OS 8.5 or 8.6 cd at hand and run Basilisk II you can copy the required file from the system folder on the CD straight to the linux drive on the desktop. Then move it to a place where SheepShaver can find it.
My installation:-

c:\sheepshaver\

In Basilisk, dragged a copy the Mac OS ROM from Mac OS 8.5 system folder in CD onto Basilisk desktop, with My Computer enabled giving access to c:\sheepshaver in windows.

In Basilisk, copied Mac OS ROM from desktop into c:\sheepshaver and it shows as MacOS_ROM.ROM size 1,901,826 bytes.

In Basilisk, created MacOS_8.5.HFV (200 MB) to be placed in c:\sheepshaver ready for installation of Mac OS 8.5.

clicked on sheepshaver.exe ... nothing happens!
no startup window as I expected to see.

______________________________________

I did try downloading TomeViewer
and Mac OS ROM Update 1.0.smi.bin
into here ..

c:\basiliskII\Setup\Virtual Desktop\Desktop Folder\

this places Mac OS ROM 1.0.smi.bin directly on desktop.

but when I click on this it cannot be opened.

How do I use TomeViewer + Mac OS ROM Update 1.0.smi.bin ?

I also have HFVExplorer installed.

I'm puzzled that whatever I do there is no SheepShaver startup window .. even if the configuration might be wrong .. and here follows the preferences:-

________________________________________

nosound false
nogui false
noclipconversion false
ignoresegv true
idlewait true
seriala file
serialb file
nonet false
jit true
jit68k false
frameskip 8
ramsize 67108864
rom c:\sheepshaver\macos_rom.rom
windowmodes 3
screenmodes 63
gfxaccel true
disk c:\sheepshaver\macos_8.5.hfv
cdrom H:
nocdrom false
bootdrive 0
bootdriver 0
pollmedia true
enableextfs false
debugextfs false
extdrives CDH
keyboardtype 5
keycodes false
mousewheelmode 1
mousewheellines 3

________________________________________
User avatar
Cat_7
Expert User
Posts: 6172
Joined: Fri Feb 13, 2004 8:59 am
Location: Sittard, The Netherlands

Post by Cat_7 »

Dragonfly,

You need the rom coming from the mac os rom update from the apple website to start sheepshaver for windows.
pick it up here:

http://download.info.apple.com/Apple_Su ... .0.smi.bin


But be aware this windows version is the first try of a developer normally writing Linux stuff....

Cat_7
dragonfly
Student Driver
Posts: 21
Joined: Sun Mar 06, 2005 9:24 pm

extracting the ROM

Post by dragonfly »

Cat_7,

I had already downloaded that file and it does not do anything when clicking on it in desktop

Also I read the paper "SheepShaver V2.2 Installation and User's Guide (Linux)" .. noting that this is Linux and not Windows.
Rom files known to work with SheepShaver

The following NewWorld ROMs are known to work:
- MacOS ROM 1.1.2 from MacOS 8.5
- MacOS ROM 1.2.1 from "iMac Update 1.1"
- MacOS ROM 1.4 from MacOS 8.6
- MacOS ROM 1.6 from "MacOS ROM Update 1.0"
and I had hoped that "MacOS ROM 1.1.2 from MacOS 8.5 " might work ..

but I'll stick with "MacOS ROM Update 1.0" as you advise.

Now .. how do I extract the ROM?

I have MacOS ROM Update 1.0.smi.bin on Basilisk desktop and also have TomeViewer but I can't get beyond this point.

...

postscript

O.K.
I have used Stuffit directly and progressed to getting MacOS ROM Update 1.0.smi .. (without bin extension) .. on Basilisk desktop. Now what do I do with this file to create ROM to go into SheepShaver?


Thanks.
User avatar
Cat_7
Expert User
Posts: 6172
Joined: Fri Feb 13, 2004 8:59 am
Location: Sittard, The Netherlands

Post by Cat_7 »

the .smi file is a self mounting image, so you double click it and a diskette image should appear on the desktop. Then use tome viewer to open the tome and extract the rom file.

Cat_7
dragonfly
Student Driver
Posts: 21
Joined: Sun Mar 06, 2005 9:24 pm

Post by dragonfly »

I launch Basilisk II .. Mac OS 7.5.3 boot up

I can see Mac OS ROM Update 1.0.smi .. and TomeViewer .. on the desktop ..

Mac OS ROM Update 1.0.smi has a diskette icon on it.

I double-click on Mac OS ROM Update 1.0.smi .. as you suggest ..

Software licence .. Agree .. then warning message appears

Unable to execute "Mac OS ROM Update 1.0.smi".
This file cannot be used on this file system.
Copy to a Macintosh HFS or Macintosh.


I'm still puzzled.
User avatar
Cat_7
Expert User
Posts: 6172
Joined: Fri Feb 13, 2004 8:59 am
Location: Sittard, The Netherlands

Post by Cat_7 »

Well, it seems the smi needs a newer file system only mac os 8.1 has.

You're in a bit of a trouble. You can try to install mac os 8.1 on basiliskII (if you have it.)

Cat_7
denli
Student Driver
Posts: 16
Joined: Sun Mar 20, 2005 9:05 am

Post by denli »

I had the same problem but it still doesn't work with that ROM mentioned above neither.

Someone mentioned SheepShaver exiting without an errormessage if the filepath to the diskfile was incorrect but I have double checked that possibility too.

Perhaps I have missed something else in the config file?

Code: Select all

rom Mac OS ROM
disk Sys86.HFV
cdrom e:\
enableextfs true
windowmodes 7
screenmodes 63
bootdrive 0
bootdriver 0
ramsize 67108864
frameskip 0
gfxaccel true
nocdrom false
pollmedia true
nonet true
nosound true
nogui false
noclipconversion false
ignoresegv false
jit true
jit68k false
keyboardtype 5
keycodes true
mousewheelmode 1
mousewheellines 3
idlewait true
denli
Student Driver
Posts: 16
Joined: Sun Mar 20, 2005 9:05 am

Post by denli »

SheepShaver do generate a stderr.txt file but is is empty.
Mac Emu
Forum All-Star
Posts: 1208
Joined: Mon May 20, 2002 11:50 am
Location: Ouraion

Post by Mac Emu »

Try renaming the ROM file to something without spaces.
gb
Real Swell Guy!
Posts: 115
Joined: Tue Jun 22, 2004 4:20 am

Post by gb »

Mac Emu wrote:Try renaming the ROM file to something without spaces.
Or fully specify the path to disk image and ROM file.
denli
Student Driver
Posts: 16
Joined: Sun Mar 20, 2005 9:05 am

Post by denli »

I tried both suggestions. No luck :cry:
boyanml
Inquisitive Elf
Posts: 35
Joined: Tue Oct 19, 2004 11:15 am
Location: Sofia, Bulgaria

Post by boyanml »

Denli,

You have to add:

seriala file
serialb file

in addition try:

cdrom e: (without \)
ignoresegv true
nogui true
keycodes false ("true" needs BasiliskII_keycodes file in SS directory)
extdrives C (or the letter of desired drive)
denli
Student Driver
Posts: 16
Joined: Sun Mar 20, 2005 9:05 am

Post by denli »

Nope. Still no luck.
User avatar
Cat_7
Expert User
Posts: 6172
Joined: Fri Feb 13, 2004 8:59 am
Location: Sittard, The Netherlands

Post by Cat_7 »

Denli,

What version of SheepShaver are you using? Are you running in Windows or Linux?

Could you post your latest sheepshaver_prefs file?

Cat_7
The Balance Of Judgement
Apple Corer
Posts: 271
Joined: Mon Sep 23, 2002 6:53 am

Post by The Balance Of Judgement »

Maybe it's time to start fresh. Sometimes if you work at something for a while and make modifications you get lost and miss things.
denli
Student Driver
Posts: 16
Joined: Sun Mar 20, 2005 9:05 am

Post by denli »

Iv'e got about the same setup as Dragonfly that started this thread.

WinXP Pro SP1
Mac OS 8.5 CDROM
ShapeShifter v2.2 2005-03-31, and the version before, binarie for Windows
SDL 1.2.7 and 1.2.8 for Windows

The funny part is that I had Sheepshaver up and running with MacOS 8.6 with the old binary and one day it just stoped working (I'm sure I didn't alter anything in Sheepshaver).

I tried a complete fresh setup with the following minimaly altered prefs-file in vain.

Code: Select all

disk f:\sheepshaver\Empty.HFV
rom f:\sheepshaver\Mac OS ROM
cdrom e:\
enableextfs true
windowmodes 7
screenmodes 63
bootdrive 0
bootdriver 0
ramsize 67108864
frameskip 0
gfxaccel true
nocdrom false
pollmedia true
nonet true
nosound true
nogui false
noclipconversion false
ignoresegv false
jit true
jit68k false
keyboardtype 5
keycodes true
mousewheelmode 1
mousewheellines 3
idlewait true
dragonfly
Student Driver
Posts: 21
Joined: Sun Mar 06, 2005 9:24 pm

setup struggles ..

Post by dragonfly »

Hello .. just noticed that you have the same teething problems that I experienced ..

I now have BasiliskII and Sheepshaver working
here are some of my notes from my struggles to get it working.

I now have Mac OS 8.5 working on SheepShaver.
________________

Mac OS Rom .. I used macos8.6 (1,945,746 bytes)

try deleting this file .. SheepShaver_nvram.dat (8,192 bytes) .. before restarting SheepShaver

try the SheepShaverGUI.exe to setup prefs file

try increasing ramsize to .. ramsize 134217728

try changing frameskip to .. frameskip 0

try removing the backward slash in cdrom definition

define the extdrives .. CEF (my setup below is CH, but yours is in EF)
_________________

SheepShaverGUI.exe should help in setting up.

Here is my configuration file (for comparison).
_________________

Code: Select all

nosound false
nogui false
noclipconversion false
ignoresegv false
idlewait false
seriala file
serialb file
nonet false
jit true
jit68k false
frameskip 8
ramsize 134217728
rom c:\sheepshaver_2.2\romfile\macos8.6.rom
windowmodes 7
screenmodes 63
gfxaccel true
disk c:\sheepshaver_2.2\volumes\macos_8.5.hfv
cdrom H:
nocdrom false
bootdrive 0
bootdriver 0
pollmedia true
enableextfs true
debugextfs false
extdrives CH
keyboardtype 5
keycodes true
mousewheelmode 1
mousewheellines 3
_________________

The funny part is that I had Sheepshaver up and running with
MacOS 8.6 with the old binary and one day it just stoped working
(I'm sure I didn't alter anything in Sheepshaver).
This clue suggests a corrupted SheepShaver_nvram.dat which you should delete.
denli
Student Driver
Posts: 16
Joined: Sun Mar 20, 2005 9:05 am

Post by denli »

Thanks for the input, but it still won't buldge.

I tried deleting the nvram-file and using this prefs file instead

Code: Select all

nosound false 
nogui false 
noclipconversion false 
ignoresegv false 
idlewait false 
seriala file 
serialb file 
nonet false 
jit true 
jit68k false 
frameskip 8 
ramsize 134217728 
rom F:\EMULATORS\MACINTOSH\SheepShaver\SheepShaver\macos8.6.rom 
windowmodes 7 
screenmodes 63 
gfxaccel true 
disk F:\EMULATORS\MACINTOSH\SheepShaver\SheepShaver\Sys8.6.HFV 
cdrom e: 
nocdrom false 
bootdrive 0 
bootdriver 0 
pollmedia true 
enableextfs true 
debugextfs false 
extdrives CF
keyboardtype 5 
keycodes true 
mousewheelmode 1 
mousewheellines 3 
dragonfly
Student Driver
Posts: 21
Joined: Sun Mar 06, 2005 9:24 pm

try a process monitoring utility

Post by dragonfly »

This is a tough nut to crack ..

as a long shot I would try using FileMon utility from http://www.sysinternals.com to monitor SheepShaver starting up
to see if there are any file access problems found ..

in FileMon filter ..

put SheepShaver as keyword in the "include" field

in "exclude" field put in background processes to be excluded from the report (like explore) ..
separate keywords with semi-colons ..
you can add into exclude field the unwanted processes that popup in the display window until you only have sheepshaver report.

This just might throw up a clue.
Nothing guaranteed but it sometimes helps to pin down problems.

...

Have you tried the SheepShaver GUI ?

...
Post Reply