• Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.

No Ethernet with Kanga after update to 9.2???

hilga007

6502
Hey there!

I am selling my Kanga on here and decided to test everything out. I am having a heck of a time getting it to browse the Internet! TCP/IP control panel is enabled, and everything seems ready to go, except for the fact that its just not working and I have no idea why.

There is no "activity light" on my router, which indicates its coming from the Kanga's end.

I had to use OldWorldSupport (OS 9 Helper from macsales.com) to bring this laptop up to that level, as it natively only supports up to 9.1. Does anyone know of anything in regard to this? Otherwise I will have to just reinstall 9.1...

 
The Kanga is a funny machine. It's more like a 3400 with a G3 upgrade than the later G3 Powerbooks. If you're selling anyway, I'd just roll it back to 9.1 where at least everything works and let the buyer worry about reconfiguring it for 9.2.2.

 
The Kanga is a funny machine. It's more like a 3400 with a G3 upgrade than the later G3 Powerbooks. If you're selling anyway, I'd just roll it back to 9.1 where at least everything works and let the buyer worry about reconfiguring it for 9.2.2.
yeah do a roll back and see what happens.
 
have you tried to delete the pref file for TCP/IP. have you tried to wiggle the cable around a bit wile its connected to the port and on the router( just wondering) have you tried to use a different cable ( i know it sounds stupid)

that is if you already haven't tried al of those above.

 
Yup, thanks for the advice, but I've done every piece of troubleshooting I can, and narrowed it down to perhaps a driver issue for 9.2.2. I will be reinstalling 9.1 shortly.

 
Yup, thanks for the advice, but I've done every piece of troubleshooting I can, and narrowed it down to perhaps a driver issue for 9.2.2. I will be reinstalling 9.1 shortly.
cool let us know what happends
 
Restoring to 9.1 seems to have solved the problem, so it must be an issue with the "OldWorldSupport" and some drivers there...

 
Back
Top