Version 2.2.2 fixes the Jaguar Classic problem |
September, 12, 2002 12:26 AM |
OSXGuru |
Version 2.2.2 of XPostFacto is out, and it fixes the Jaguar Classic problem (which had affected those with G4 upgrade cards). For the technically-minded among you, here's how I found the problem. (Well, I'll leave out all the false starts and red herrings :-) I did a "strings TruBlueEnvironment | grep cpu" command in the terminal to see if anything interesting might show up. Out popped the following strings: cpu-version IODeviceTree:/cpus Well, it seemed possible that Classic might be looking at the "cpus" node in the device-tree to get the cpu-version. The problem is that on the older machines, there is no "cpus" node. So I modified the ApplePowerSurgePE kernel extension to make one, and put the "PowerPC,60?" node underneath it. Reboot Mac OS X, launch Classic, and behold the happy Mac. It's always nice to see a smiling face :-) |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
October, 09, 2002 2:53 PM |
tpzahm |
. |
Finally got around to a clean install of both OS 9.1 and Jaguar. Amazingly, everything works now! |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
October, 05, 2002 5:03 PM |
hermane |
. |
After a week of operating with the "split" XPF 2.2.1 bootx/XPF 2.2.2 extensions configuration, everything seems to be stable and repeatable. OSX 10.2.1 boots and runs Classic every time. I've tried doubling the XPF memory allocation but the "Unexpected fatal error" still occurs. Thanks again for the fine effort and assistance Ryan! |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
October, 04, 2002 12:40 AM |
paul_findley |
. |
Here is the last post with commas, since line feeds seem to get killed: It seems the ideal freebie solution for Sonnet and Classic is XpostFacto, followed by Sonnet X tuneup (free) (for Sonnet cards, esp, the 800MHz) , followed by XpostFacto to reinstall extensions (to re-enable classic, which Sonnet kills) . |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
October, 04, 2002 12:38 AM |
paul_findley |
. |
I t seems the ideal freebie solution for Sonnet and Classic is XpostFacto Sonnet X tuneup (free) (for Sonnet cards, esp, the 800MHz) XpostFacto reinstall extensions (to re-enable classic, which Sonnet kills) |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
October, 01, 2002 10:27 PM |
howgil |
. |
For anyone interested, I tried the Sonnet OS X installer, and was not able to get it to work. Wasted $30. I had no trouble installing 10.2 using XPF, and if I was a little more alert, I would have realized that reinstalling the extensions had fixed my Classic problem, which may have been caused by the Sonnet OS X tune up. The Sonnet G4 800 is a great piece of hardware, but IMHO their software isn't so hot. Many thanks to Ryan Rempel for great software. |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
October, 01, 2002 10:10 PM |
howgil |
. |
Disregard previous post. I've discovered that Classic was actually starting successfully, it just loads so fast with the G4 800, that I thought it was quiting before it was completely loaded. The Sonnet G4 800 is really FAST! |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
October, 01, 2002 10:01 PM |
OSXGuru |
. |
If you are getting as far as loading extensions in Classic, then the problem isn't the same as the one which was fixed in 2.2.2. (I suppose that I should have said that version 2.2.2 fixes a Jaguar Classic problem). I guess that one question would be whether there might be an extension that loads near the end that might cause a problem. Or perhaps a startup item? Also, you could look in the system.log and see if there are any error messages (and check the console.log as well). |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
October, 01, 2002 9:50 PM |
howgil |
. |
I've got a 7300 upgraded with a Sonnet G4 800. I have 10.2.1 running flawlessly, but I can't get Classic (clean install of 9.1) to run. I've used XPF to install extensions from both 9 and X, but no joy. Classic starts to launch, but quits shortly after the extensions have loaded. |
. |
RE: Unexpected fatal error |
September, 30, 2002 12:30 AM |
OSXGuru |
. |
That makes sense--it is the extensions that solve the Classic problem, and the extensions don't get reinstalled automatically, so you would now be operating with the extensions from 2.2.2 and the BootX from 2.2.1. BootX does get reinstalled automatically if there is a new version. Though I may need to reconsider that given cases like yours. In your case, you won't want to use 2.2.2 to boot your machine, as it would install the version of BootX that is problematic for you. The "Can not continue to operate this application because unexpected fatal error occured" doesn't exactly sound reassuring! I'm not generating that message explicitly, but it may be a MacApp thing (or a Mac OS thing). I'll look into it. One thing you might try doing is increasing the memory allocation for XPostFacto--let me know if that helps, and I can increase the default settings. |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 29, 2002 10:56 PM |
hermane |
. |
Ryan- Thanks for the expedient suggestions, tried both, and neither changed the sequence described earlier. BUT, I did a little more experimenting and found something that DOES seem to work based on your hint about BootX. After installing 2.2.2, I went back to 2.2.1 and checked only BootX for reinstallation under the 'Advanced' menu. The machine boots normally AND launches Classic successfully. Seems to be repeatable after a reboot to OS9 or OSX2. I assume that if the 'Extensions' reinstall is not checked, the 2.2.2 version is left intact, which is probably what fixed the 'Classic Boot' issue??? I'll advise if this fix holds...Thanks again. By the way, I've been ignoring an allert box that pops up on every XPF boot that says "Can not continue to operate this application because unexpected fatal error occured (OK)". I just hit the OK button, and things appear to proceed normally. |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 29, 2002 9:28 PM |
OSXGuru |
. |
There was a new version of BootX with version 2.2.2, and it sounds as though it is causing your problem for some reason. However, there weren't any changes in BootX that ought to have this effect. So it may relate to something in the installation process for BootX rather than the contents as such. Here are a couple of things you could try. You could try using XPostFacto 2.2.2 again. The BootX from 2.2.2 will get installed again, but if there was a glitch in the installation process last time, perhaps that glitch won't show up again this time. You could try setting the "output-device" in the Open Firmware menu of XPostFacto to your monitor, and then hold down command-v as you restart. This will have two effects. First, it will initialize your display a little earlier in the boot process than otherwise, which might change things a little. Second, you may get an error message on the screen, rather than a blank monitor. Let me know how it goes. |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 29, 2002 8:49 PM |
hermane |
. |
Had been flawlessly using 10.1.5 with XPF 2.2.1 on my 9600 and decided it was time to install 10.2. No problem with the install using XPF 2.2.1 but soon encountered the "Classic Boot problem". Downloaded and installed XPF 2.2.2. Unfortunately, I'm now unable to get 10.2 to boot - appears that the display card is never activated, or possibly activated and then deactivated. Upon boot with XPF 2.2.1, my monitor power LED usually flashed from yellow to green for about a second, then back to yellow for a second, then back to steady green while the boot progressed normally. With XPF 2.2.2, I just hang at a yellow LED after the first green blink. Rebooting causes the same sequence. I'm running a 9600 with a Sonnet 450/G4 processor upgrade and an ATI Nexus 128 (32MB) display card. If I revert back to XPF 2.2.1 and reinstall BootX and extensions, booting proceeds normally - just no Classic. This feels like a display card issue. Anybody encountered a similar situation? Thanks for the effort and fine work Ryan - I've really been pleased at how well things have worked with this 'unsupported' hardware/software configuration over the past year. |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 27, 2002 3:32 PM |
OSXGuru |
. |
Yes, it does sound like the "Install Extensions" procedure didn't work for some reason (you did the correct thing, though). You could try rebooting into Mac OS 9 and using XPostFacto to install extensions from there--it is a different technique, so it may not be subject to the same problem. BTW, you won't be able to enable your L2 cache with a Classic application, since Classic applications cannot talk to the hardware directly. You'll need a Mac OS X specific utility, such as the PowerLogix Cache Control software, or my L2CacheConfig. |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 23, 2002 8:01 AM |
miwine |
. |
OK, an hour's wait seemed to have cured my bootup problems, and now OSX runs nicely. But still no 9.1. Suggestions appreciated... |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 20, 2002 5:31 AM |
miwine |
. |
...and now something far worse: after trying to reinstall the extensions and rebooting, I get a circle with a slash through it instead of the gray apple on the startup screen...the equivalent, I presume, of the flashing question mark in OS 9. Help (whimper)... |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 20, 2002 5:22 AM |
miwine |
. |
Whoops...typo below: I did use 2.2.2, not 2.2...sorry. |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 20, 2002 5:20 AM |
miwine |
. |
Ryan, first of all, terrific work. Having said that I, too, haven't been able to start Classic after installing XPF 2.2 on a PowerMac 7500 upgraded with an XLR8 ZIF carrier and an OWC 450mhz G4 chip. Console produces the error message: mach_error (os/kern) no space available Jan 14 23:52:17 localhost Classic[410]: *** The BlueBox just crashed! *** Jan 14 23:52:17 localhost Classic[410]: ERROR = SystemCrash(9) Jan 14 23:52:17 localhost WindowServer[241]: CGXPostEventByConnection: invalid connection I ran terminal per yr instructions and found neither cpus@0 or PowerPC,60? So I guess the install didn't take. Did I miss something? My install consisted of opening XPF 2.2 in OSX, going to File and selecting "install extensions." After a proper amount of time (couple of minutes) I got no prompt saying installation had finished so I quit XPF, rebooted into X and tried to start Classic, unsuccessfully. Advice, please...I can't set my L2 cache for the G4 processor, AFAIK, unless I can get into Classic! |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 19, 2002 10:11 PM |
OSXGuru |
. |
info716: That does sound like the problem which XPostFacto 2.2.2 is supposed to fix. I'm assuming that you did install the extensions from 2.2.2 (that is what fixes the problem). If so, perhaps you could run this command in the terminal and post the results. The command is: ioreg -p IODeviceTree This will show whether the fix in 2.2.2 is doing what it is supposed to be doing. (You should see a "cpus@0" node near the end, with a PowerPC,60? node just after it). Tom: Perhaps you could try the same thing, just to make sure that the fix is in (so to speak). |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 18, 2002 7:49 PM |
tpzahm |
. |
Another update on the Classic Crash situation -- I put things back to rights (everybody with his proper MacOSROM file), and nothing changes! Still get the "...Finder has unexpectedly quit" message when the Classic startup thermometer is at about 4/5. Any thought, Oh Guru? Expectently, Tom Zahm |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 18, 2002 8:54 AM |
tpzahm |
. |
Two notes: (1) re: info716's error message -- That's the same one I was getting when I was using an OS9Helper-patched 9.2 (2) I did a clean install of 9.0 + 9.1 update onto a freshly erased partition. Same 1-second-and-out routine. Then I tried something recommended elsewhere: I copied MacOSOM from /System/Library/CoreServices/Classic Startup/Contents/Resources of my 10.1 partition to both the 10.2 partition and to the System Folder of my newly-installed 9.1. This time OS9 (Classic) would nearly complete booting when a "Finder has unexpectedly quit." message appeared. |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 16, 2002 2:56 PM |
info716 |
. |
I'm still not able to launch Classic in Jaguar, while using XPF 2.2.2. Umax S900, Sonnet Crescendo G4-350 Mhz, 352Mb RAM This I found in the log: mach_error (os/kern) no space available Sep 16 21:28:38 woodstox Classic[592]: *** The BlueBox just crashed! *** Sep 16 21:28:38 woodstox Classic[592]: ERROR = SystemCrash(9) Sep 16 21:28:38 woodstox WindowServer[434]: CGXPostEventByConnection: invalid connection |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 16, 2002 3:36 AM |
mjoecups358 |
. |
2.2.2 fixed classic for me... Why are you people so obsessed with 9.2.2? Who cares? 9.1 works fine and there is no screwing around or patching, I get enough of that on the OSX side (hehe). |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 15, 2002 1:24 PM |
tpzahm |
. |
I tried no extensions, apple-only extensions, and 9.2.2 base, and it didn't work. Tom Zahm |
. |
RE: Version 2.2.2 fixes the Jaguar Classic problem |
September, 14, 2002 5:07 PM |
speedy |
. |
I just tried booting 9.2.2 that was patched with Ben's 1.0b6. It works just fine. Maybe there are some 3rd party extensions that are causing the conflict? |