From: Ronald P. R. <ron...@xs...> - 2009-10-25 12:40:16
|
Those are the builds I compared. Your 2009-07-26 build does not have the problem, your 2009-08-23 build does have the problem. There are now a couple of different reports from this (or at least a very similar) problem on PPC and one on Intel. SheepShaver either quits or freezes, always just after the MacOS welcome screen appears and before one can see extensions loading. Disabling extensions at startup does not help. On my PowerBook G4 it is a freeze. The PB has a fresh and updated Leopard installation with no additional software but the Developer Tools. You have seen the report of this (or a similar) problem an Intel machine in Emaculation.com forum. Ronald. Op 24 okt 2009, om 01:50 heeft Michael Schmitt het volgende geschreven: > Compare the 2009-07-26 build to the 2009-08-23 build, posted here: <http://www.emaculation.com/forum/viewtopic.php?p=30713#30713 >> > > That build contains the precise timing changes. > > Since I created both builds similarly, it should help isolate the > issue. > > Note that I tested that build on PPC and it worked for me. > > > On Oct 23, 2009, at 4:16 PM, Ronald P. Regensburg wrote: > >> There is a problem with recent builds of SheepShaver MacOSX on PPC >> Macs. >> >> SheepShaver launches normally and the virtual machine begins to >> startup normally. But then SheepShaver freezes at the MacOS welcome >> screen before extensions start loading. The same when trying to >> startup with extensions disabled. The message that extension are >> disabled appears in the welcome screen, but that is as far as it >> gets. >> SheepShaver does not react to anything anymore, it uses more than 90% >> of CPU time and the OSX side shows the spinning beachball. There are >> no unusual messages in Console. >> >> The problem must have started with a change in August. >> >> A 2009-07-14 build does not have the problem. >> >> The 2009-07-26 build that Michael Schmitt posted here: >> <http://www.emaculation.com/forum/viewtopic.php?p=30434#30434> >> also does not have the problem. That build already contains the >> memory >> allocation error fix, although that fix was not yet committed to CVS >> then. If the fix was applied as it was used for this build, that >> excludes this fix as the cause of the problem. >> >> A 2009-08-23 build and all later builds have the problem on PPC Macs. >> Could the "precise timer" patch be the cause of the problem? >> >> If I know which files are involved with that patch, I can try to >> build >> with earlier versions of those files. >> >> Ronald. > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > basilisk-devel mailing list > bas...@li... > https://lists.sourceforge.net/lists/listinfo/basilisk-devel > |