Re: [B2-devel] Can't run BasiliskII on Fedora Core 3 x86

[Gwenole B. <gb...@di...>]

jeudi 16 d=E9cembre 2004, =E0 04:29  pm, Matthias Saou a =E9crit :

> Hmmm, I've got a stupid question, then. When I looked at SheepShaver, =
I
> understood that it was only relevant on ppc machines. Was I wrong?=20
> Here's
> the first paragraph of the doc/index.html file in the SheepShaver CVS=20=

> tree
> :

Unfortunately, the documention in the CVS tree is somewhat old vs.=20
Christian's site:
<http://www.uni-mainz.de/~bauec002/SheepShaver.html>

> Does SheepShaver run on x86 and x86-64?

Yes, and it runs up to MacOS 9.0.4.

> How does it position itself compared to BasiliskII, pretty much like=20=

> VMWare (-> BasiliskII) and Wine
> (-> SheepShaver)?

SheepShaver has almost the same foundations as Basilisk II thus sharing=20=

a lot of code. Both run-time patch MacOS with driver hooks to native=20
code and high level replacements. i.e. they don't emulate real=20
hardware, but a virtual hardware good enough run those OSes.

> This "black screen" seems to be what I'm getting
> with older BasiliskII releases, so if anyone has more info on that
> particular problem and how to work around it, I'd really appreciate =
it.

Sometimes, people reported they got it fixed by nuking/zap their XPRAM=20=

file (~/.basilisk_ii_xpram).

> Backports of the asm fixes to BasiliskII for testing would also be =
very
> welcome :-)

The problem is I don't see any use of explicit suffixes to push/pop in=20=

Basilisk II code. Well, people probably remember that I didn't see them=20=

in SheepShaver initially either. ;-) On the other hand, new binutils=20
have better checks for it but this is what I now use too. So, I still=20
don't get it.=