[B2-devel] Re: SheepShaver

[Carsten K. <ck...@ku...>]

Howard,

Thank you for your e-mails.

hs> I have seen at least two other people having problems like this on Suse distributions.

This darned, obscure autoconf/automake/m4 system! Are there more than
10 people on this planet who actually know what's going on inside it?

hs> As far is I know there is an issue with the naming of the
hs> floppy devices between suse and, for instance, mandrake linux. 
hs>
hs> Something like using FD0 instead of fd0
hs>
hs> On my machine that leads to unacceptable waiting times before SheepShaver starts.

I don't worry about the floppy and the little delay it creates in the
boot process. Haven't used floppy disks in a year or two anyway.

hs> The gtk 1.2 issue is still open, also on my machine. I
hs> haven't been able to succesfully compile sheepshaver on Suse 9.0 

(repeat rant about auto-*)

hs> Some remarks to you possible explanations below
hs> Here are a few possible explanations:
hs> - The ROM Image on the MacOS8.5 CD is not suitable for SheepShaver

hs> This isn't the case

Thank you for confirming this.

hs> - MacOS8.5 doesn't run under SheepShaver
hs> MacOS 8.5 does run under SheepShaver

Thank you for confirming this. I didn't really expect it but didn't
want to rule it out either.

hs> - The MacOS CD has a physical defect and SheepShaver tries to execute a
hs> program segment located in a defective area

hs> You have to get a new medium

Seems like I have to go shopping on E-Bay...

hs> - SheepShaver works the CD ROM Driver in such an uncommon way that my
hs> PlexWriter crashes

hs> I haven't seen any reports on issues like this.

I'd be surprised, too, as I regularly use it to write CDs

hs> - SheepShaver works the CD ROM Driver in such an uncommon way that a
hs> programming error in the IDE driver shows up

hs> I couldn't tell

hs> - SheepShaver works the CD ROM Driver in such an uncommon way, so that a
hs> difference between a CD Writer and an ordinary CD Drive shows up

hs> I haven't had any problems concerning this

I still can't rule this out. What else would explain that the CD drive
is locked and I can't remoce the MacOS8.5 CD after SheepShaver
crashes?! As far as I know, it is Linux Kernel semantics to free all
resources a process has kept after the process is killed. All files
get closed, etc., so there should be no reason for the device driver
in the kernel to stop me from removing the CD, as it is not mounted or
anything.

I'll try to get another CD and see if the problem persists.

Thank you for your help,

Carsten