|
From: Matthias S. <th...@sp...> - 2004-12-16 15:29:58
|
Tomek Jerzykowski wrote : > Are you absolutely sure that you are using the newest code from CVS? I used > to have such problems with SheepShaver, not Basilisk some time ago, but it > has already been fixed (x86_64). Maybe only in SheepShaver code? 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? Here's the first paragraph of the doc/index.html file in the SheepShaver CVS tree : "SheepShaver is a MacOS run-time environment for Linux that allows you to run MacOS applications at native speed inside the Linux multitasking environment on PowerPC-based Linux systems. This means that both Linux and MacOS applications can run at the same time and data can be exchanged between them." Does SheepShaver run on x86 and x86-64? How does it position itself compared to BasiliskII, pretty much like VMWare (-> BasiliskII) and Wine (-> SheepShaver)? I'm a bit confused. Back on topic, I recall having seen posts about x86_64 fixes for SheepShaver, as well as builds that supposedly fixed the "black screen" some people were seeing. 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. Backports of the asm fixes to BasiliskII for testing would also be very welcome :-) Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora Core release 3 (Heidelberg) - Linux kernel 2.6.9-1.681_FC3.r300 Load : 0.63 0.86 0.84 |