Trying to install Darwin on 8500 |
December, 04, 2002 10:53 AM |
k97jazz |
Hello all, A while ago I had installed 10.1 on my 8500 (not G3/G4, still 200 604e) without any problems using XPostFacto. It was painless. Yesterday I decided to try my hand at Darwin, but I'm running into problems. First I tried installing Darwin 6.0.2 using XPostFact 2.2.4, but upon reboot, the machine would hang at the start of the command prompt (I could see the cursor block and that was it). Then I told myself 6 probably wouldn't install since it was basically for Jaguar. (Any chance I should be able to install this?) So I tried installing the final version of 1.4. This time, no problem with the install. However, upon rebooting, the OS will not load any of the XPostFacto extenstions (com.macsales.* failed to load). Eventually it says it can't load the SCSI driver and therefore won't mount my drive. Any thoughts on this? Thanks! -Matt |
. |
RE: Trying to install Darwin on 8500 |
December, 13, 2002 8:07 PM |
joevt |
. |
The error messages might be in the system.log file. Use Sherlock in OS 9 to find it on the OS X volume and use a text editor like BBEdit to look at it. The first line in the log after a restart occurs should contain "syslogd: restart". The second line should contain "standard timeslicing quantum" though sometimes the log doesn't start recording until much later after that line. Does Darwin 1.4 give you a command prompt? If so, then you can try the "kextstat" command to get info on your loaded extensions and "kextload -entZ" command to test the extensions that weren't loaded. |
. |
RE: Trying to install Darwin on 8500 |
December, 10, 2002 8:17 PM |
OSXGuru |
. |
You're right about Darwin 6.0.2--it just won't run on the 604e. Theoretically, I'd like to fix this, but haven't figured out how yet. It's odd that Darwin 1.4 would install OK, but then not boot properly--I'm not sure what the reason is. Some of the XPostFacto extensions are only meant for certain versions of Darwin, so it is normal for some of them not to load (but not all of them). If you can write down some of the error messages, that might help. Are you using an ordinary internal SCSI drive, or something else? |
|
|