My problem is desesperetingly simple, when I try to launch the latest builds of Basilisk or SheepShaver (in Windows), they just won't start.
When I start them, nothing shows up, the process appears in the taskmgr for a short time (less than half a second for 128 MB of RAM, like 15 seconds for 512 MB of RAM, there you can see it just tries to fill the RAM up to about 200 MB and then rolls back) and thats all.
Nothing in stderr.txt or stdout.txt
Whats wrong?
Just can't start 2.3 (nor the new Basilisk)
Moderators: Cat_7, Ronald P. Regensburg, ClockWise
Ok, here's the cfg file for SheepShaver, as generated by the GUI (and based on my old cfg file)
and here it is for Basilisk
Code: Select all
disk mac hd.hfv
disk apps.hfv
disk Apps.dsk
cdrom d:
cdrom e:
cdrom f:
extfs
screen win/640/480
windowmodes 3
screenmodes 63
seriala FILE
serialb FILE
rom C:\Documents and Settings\Principal\Bureau\Mac emulators\SheepShaver\macos8.6.rom
bootdrive 0
bootdriver 0
ramsize 536870912
frameskip 1
gfxaccel true
nocdrom false
nonet false
nosound false
nogui false
noclipconversion false
ignoresegv true
jit true
jit68k false
keyboardtype 5
keycodes true
mousewheelmode 1
mousewheellines 3
ignoresegv true
idlewait true
keycodes true
mousewheelmode 1
mousewheellines 3
enableextfs true
debugextfs false
extdrives CFJ
pollmedia true
etherpermanentaddress true
ethermulticastmode 0
routerenabled true
ftp_port_list 21
tcp_port
portfile0 C:\B2TEMP0.OUT
portfile1 C:\B2TEMP1.OUT
and here it is for Basilisk
Code: Select all
disk MacOS7.5.3.hfv
disk C:\Documents and Settings\Principal\Bureau\Mac emulators\Mini vMac\Apps.dsk
cdrom F:\
extfs
screen win/640/480
seriala FILE
serialb FILE
udptunnel false
udpport 6066
rom C:\Documents and Settings\Principal\Bureau\Mac emulators\BasiliskII\ROM's\Quadra 650 (1993-7.0.1).ROM
bootdrive 0
bootdriver 0
ramsize 33554432
frameskip 0
modelid 24
cpu 68040
fpu true
nocdrom true
nosound false
noclipconversion false
nogui false
jit true
jitfpu true
jitdebug false
jitcachesize 8192
jitlazyflush true
jitinline true
keyboardtype 5
keycodes false
mousewheelmode 1
mousewheellines 3
ignoresegv false
enableextfs true
debugextfs false
extdrives #C
pollmedia true
etherpermanentaddress true
ethermulticastmode 2
routerenabled true
ftp_port_list 21
tcp_port
portfile0 C:\B2TEMP0.OUT
portfile1 C:\B2TEMP1.OUT
Do you have the new build in the same directory the old one was in?
Why don't you install all the new stuff in C:\SheepShaver? It make life a bit easier in respect to paths etc. And keeps stuff separated.
I would suggest you try to keep things as simple as possible for starting SheepShaver.
You can rename the current config file so a new one gets generated when you start the GUI and set only the bare neccessities:
So only 1 HD-image, one CD-Rom, the rom file and the rest to default values.
You could then start with a new HD-image and install the OS cleanly.
You should also try to zap Pram from the GUI's file menu. (or delete the file SheepShaver_nvram.dat)
Cat_7
Why don't you install all the new stuff in C:\SheepShaver? It make life a bit easier in respect to paths etc. And keeps stuff separated.
I would suggest you try to keep things as simple as possible for starting SheepShaver.
You can rename the current config file so a new one gets generated when you start the GUI and set only the bare neccessities:
So only 1 HD-image, one CD-Rom, the rom file and the rest to default values.
You could then start with a new HD-image and install the OS cleanly.
You should also try to zap Pram from the GUI's file menu. (or delete the file SheepShaver_nvram.dat)
Cat_7