Thread
Asanté EN/SC-10T on PowerBook 1400cs/166 with Mac OS 7.6.1?
With no wep2 being wired would bypass security setup issues.
Most of the SCSI Ethernet boxes need a power cord which most people have lost.
That would be my first guess.
Asante has legacy drivers on their website still. It says Mac OS 7 or the like which is the wrong wording but it's there.
Most of the SCSI Ethernet boxes need a power cord which most people have lost.
That would be my first guess.
Asante has legacy drivers on their website still. It says Mac OS 7 or the like which is the wrong wording but it's there.
You can get the En/sc to work but it's tricky. First get the driver off the asante page on archive.org, as asante has gotten rid of the link for the download.
Second... Hook it up, boot the machine with the power and ethernet cable, scsi cable connected already.
Boot with extensions off - hit down shift as it boots. Otherwise it could freeze or crash. Install the driver... After you install the driver, it won't be unstable anymore and won't crash / freeze.
Reboot.
Configure tcp/ip settings.
connect to something.
Done!
Second... Hook it up, boot the machine with the power and ethernet cable, scsi cable connected already.
Boot with extensions off - hit down shift as it boots. Otherwise it could freeze or crash. Install the driver... After you install the driver, it won't be unstable anymore and won't crash / freeze.
Reboot.
Configure tcp/ip settings.
connect to something.
Done!
Does this combo work? I can't get it to work for me.
Yes there's a reason.
The installer won't allow the install without it. I guess it does a quick hardware check to see what type of en/sc is connected. Perhaps there is a slight difference and it configures settings slightly differently or something depending upon which type you have? In any case, it absolutely refuses to install without the hardware being plugged in and recognized by the installer.
And I'm guessing it's unstable and freezes before the driver is installed because apple didn't predict ethernet via a scsi port. I could be wrong here but I think the scsi proocol has a type flag or something that identifies the kind of item it is - ex: scanner, cd-rom drive, hard drive, etc... And there is a "unknown" option that is there for anything that doesn't fit... I'm guessing that the en/sc is set as an "unknown" device, and the mac's additional extensions (maybe tcp/ip or opentransport) don't know what to do with it so it freezes. Just a guess of course. You'd probably have a better idea than I as of why that is so.
The installer won't allow the install without it. I guess it does a quick hardware check to see what type of en/sc is connected. Perhaps there is a slight difference and it configures settings slightly differently or something depending upon which type you have? In any case, it absolutely refuses to install without the hardware being plugged in and recognized by the installer.
And I'm guessing it's unstable and freezes before the driver is installed because apple didn't predict ethernet via a scsi port. I could be wrong here but I think the scsi proocol has a type flag or something that identifies the kind of item it is - ex: scanner, cd-rom drive, hard drive, etc... And there is a "unknown" option that is there for anything that doesn't fit... I'm guessing that the en/sc is set as an "unknown" device, and the mac's additional extensions (maybe tcp/ip or opentransport) don't know what to do with it so it freezes. Just a guess of course. You'd probably have a better idea than I as of why that is so.
why wouldnt you install the driver before you hook it up so it wouldnt freeze the machine? any special reason for that step?
Yes, that's possible. FTP can be a real pain in the you know what to get working if there is a firewall in the way. Try using netscape instead and visit http://www.google.com and see what you get. The rendering probably won't be perfect as it's an old browser - but if the bridge is working you should get something.
I already have the drivers installed, so perhaps the problem lies with me using Fetch 3.0.1?
