So I guess 8.5 is the lowest, since currently no old-world ROM is supported on the windows version.Jack Hair wrote:Guess not, i installed of an OS 8.5 ISO and updated to 8.6.Marc wrote:I think the lowest we can boot in Windows is OS 8.6
Visual C++ Runtime Library hates SheepShaver. (Windows)
Moderators: Cat_7, Ronald P. Regensburg, ClockWise
- PPC_Digger
- Forum All-Star
- Posts: 1050
- Joined: Thu Jul 22, 2004 9:02 am
- Location: Israel
-
- Tinkerer
- Posts: 61
- Joined: Fri Sep 12, 2003 4:16 am
-
- Tinkerer
- Posts: 61
- Joined: Fri Sep 12, 2003 4:16 am
During one of my installations (I think it was 8.5), The OS ran some kind of first-run config utility. It asked me what my time zone is, my name, company name, etc. At one point it wanted to setup (or check) my network connection. This caused it to hang indefinetly.
Perhaps anything that attempts to connect to the internet or network crashes?
Also, accessing the "Monitors and Sound" control panel in 8.5 caused a quit without error message. I have not yet tried this in OS 8.6.
Perhaps anything that attempts to connect to the internet or network crashes?
Also, accessing the "Monitors and Sound" control panel in 8.5 caused a quit without error message. I have not yet tried this in OS 8.6.
it did it to me to when i clicked to finalized the setup process it also hangedrobotintestines wrote:During one of my installations (I think it was 8.5), The OS ran some kind of first-run config utility. It asked me what my time zone is, my name, company name, etc. At one point it wanted to setup (or check) my network connection. This caused it to hang indefinetly.
Unrelated to the post above me, but, I've noticed that SheepShaver won't work for me when jit is enabled If I try to use jit normally, it hangs during boot.. But it -will- work when I disable extensions (Mind you, no text is visible. Anywhere, as in, it works, but no text), or turn jit off. Is this inherent in SheepShaver's code? Or is it a problem of incompatability with my CPU, or, what? Just trying to pin-point exactly what's causing this behaviour.
EDIT: If you skip loading modules, you don't get the run-time errors.
EDIT: If you skip loading modules, you don't get the run-time errors.
sure! here it is:
extfs g:\
rom MacOSROM1
disk os8.6.hfv
cdrom n:\
windowmodes 3
screenmodes 63
seriala COM1
serialb COM2
bootdrive 0
bootdriver 0
ramsize 67108864
frameskip 0
gfxaccel true
nocdrom false
nonet false
nosound false
nogui false
noclipconversion false
ignoresegv true
jit true
jit68k false
keyboardtype 5
keycodes false
mousewheelmode 1
mousewheellines 3
ignoresegv true
idlewait true
keycodes false
mousewheelmode 1
mousewheellines 3
enableextfs false
debugextfs false
extdrives CDEFGHIJKLMNOPQRSTUVWXYZ
pollmedia true
btw: "extfs"? what does it mean?
extfs g:\
rom MacOSROM1
disk os8.6.hfv
cdrom n:\
windowmodes 3
screenmodes 63
seriala COM1
serialb COM2
bootdrive 0
bootdriver 0
ramsize 67108864
frameskip 0
gfxaccel true
nocdrom false
nonet false
nosound false
nogui false
noclipconversion false
ignoresegv true
jit true
jit68k false
keyboardtype 5
keycodes false
mousewheelmode 1
mousewheellines 3
ignoresegv true
idlewait true
keycodes false
mousewheelmode 1
mousewheellines 3
enableextfs false
debugextfs false
extdrives CDEFGHIJKLMNOPQRSTUVWXYZ
pollmedia true
btw: "extfs"? what does it mean?