Crap!!! It obviously wasn't the Hard Drive, I'm back to the grey boot screen.
I've done NOTHING but restart after doing the clean install!
It's giving the following error, which I'm seeing in Verbose mode (Command+v)
Mez com.apple.launchd[1] (com.apple.nDNSResponder |xxx|) : posix_spawnp("usr/sbin/mDNSResponder", ...): No such file or directory
xxx = incremental value, it adds 1 each time the error cycles, which happens roughly ever 10 seconds).
I actaully remember seeing this last time I booted with Verbose mode (prior to upgrading the HD). I'm not annoyed about buying a new HD, I was going to do it anyway... but I really want Leopard to work.
Imported from the Apple Support Forums via the Wayback Machine 🔗
Erase and install if you want to get pedantic.
0
a brody·
Imported from the Apple Support Forums via the Wayback Machine 🔗
This suggests to me your network hardware is damaged or out of date in its firmware. Especially since it happened before upgrading your hard drive.
0
Mez Hopking·
Imported from the Apple Support Forums via the Wayback Machine 🔗
If I go back to the Tiger install, it boots just fine. Surely if there were probs with it, then Tiger would see the same errors?
0
Mez Hopking·
Imported from the Apple Support Forums via the Wayback Machine 🔗
If that is the case, how can I update / repair the firmware?
0
a brody·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Not necessarily. Each operating system addresses networking slightly different and in better ways. Note for instance Leopard has added searching of network volumes over Spotlight. It might be its persistent indexing may be too much for a poorly constructed router or one that is marginal. And then many routers with out of date firmware can also crash Tiger. I've seen this happen before Leopard even existed. When you upgrade a system with multiple devices, you have to make sure they are all in sync with each other as far as meeting the same specs. If they aren't problems can arise like what you are seeing.
0
a brody·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Contact the vendor who makes that router. Usually there are updates on their website. If they don't provide a Mac compatible updater, ask to have it mailed to them for the fix and tell them you wish them to update it and that other vendors do offer Mac compatible updates.
0
Mez Hopking·
Imported from the Apple Support Forums via the Wayback Machine 🔗
It's an Apple AIrport Extreme N... so that's that ruled out. Any other ideas?
0
a brody·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Not totally ruled out. Check its firmware version is most current.
Check that it is a closed network, and no other machines might be attempting to log on the network. Check that the airport card isn't damaged or not properly installed. If you have a Mac with a built-in airport card, you may have to bring it in for service.
Check that the RAM hasn't gone bad with the hardware test that came with the machine. RAM is totally random in its access and hence why Tiger may not be impacted but Leopard is.
0
Mez Hopking·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Already tried the hardware test, all passed. I'm back to running Tiger now, using the internal Airport, so that's fine.
0
a brody·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Just because all passed doesn't mean the RAM is good. It just means there is nothing detectable. No RAM test in the age of the universe can detect all possible combinations of circuits of bad RAM. Thus completely replacing the RAM with high quality lifetime warranty RAM may solve the problem.
0
Faema1969·
Imported from the Apple Support Forums via the Wayback Machine 🔗
C'mon Brody, you are grasping at straws. This issue is Leopard!
0
a brody·
Imported from the Apple Support Forums via the Wayback Machine 🔗
That's totally illogical. If the issue was Leopard I would have seen it too. You have missed some contributing factor.
0
Allan Eckert·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi Mez Hopking;
The hardware test is not the best way to test RAM. I had bad RAM in my PowerMac that the hardware test said was good every time I tested it. I finally download Rember and it was able to find the bad card. Another one that I have heard is better then the hardware test is Memtest. I would suggest you try them and see how your RAM checks out with them.
Allan
0
Allan Eckert·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi a brody;
I concur. If anyone is grasping at straws it is him and not you.