Installer error with XPFb16 |
August, 16, 2002 9:12 PM |
Tony.Scaminaci |
Swapped out the XLR8 card today for a Sonnet Crescendo G4/450 card. After getting the card stable in OS 9, I tried installing 10.1 but I'm now getting installer errors. The first attempt was without verbose mode, and everything was going great until the MacOS X screen came up and then disappeared into the blue screen of death with a spinning beach ball in the upper left-hand corner (no, the Radeon 7000 card is NOT installed). This was not a hard freeze as with the XLR8 card since the beach ball continued spinning for over 15 minutes before I rebooted. The second attempt was with verbose mode turned on and this is when I noticed the following message: The installer has unexpectedly quite (error 1). So, I rebooted and started over again with verbose mode on as well as extended debugging mode turned on. This time I got the same message but with an error code 0. Again, this is very different from the freezes with the XLR8 card. It would get all the way into the installation process and then randomly freeze. The Sonnet G4 card is not getting out of the inital boot phase. Throttle is turned on as high as possible. Ryan, I've emailed you the log file. Tony |
. |
RE: Installer error with XPFb16 |
August, 19, 2002 3:26 PM |
Tony.Scaminaci |
. |
Never did figure out the cause of this problem but I finally got X installed on the 9500 by running XPF under a minimal 9.1 install rather than 9.2.2. You know, while the XLR8 card was freezing all the time, the Sonnet card exhibits strange one-time behavior that sometimes never repeats again. After I did a test install using 9.1, I erased the destination drive and retried a new install under 9.2.2 and it worked perfectly. Who knows what caused it, but at least it's installed and working now. I'm happy. Tony |
. |
RE: Installer error with XPFb16 |
August, 19, 2002 2:04 PM |
OSXGuru |
. |
Hmm. I have not had a lot of luck figuring out what these "Installer unexpectedly quit" errors are caused by. My working theory is that it either relates to RAM troubles (you'll love to hear that :-), or problems with the CD. But I really don't know exactly why this sometimes happens. (Unfortunately, it has never happened to me--it would be easier to fix that way). |
|
|