• 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.

Details: some elbow-grease req'd to add NIC to SE FDHD

Here we go. My epic SE restore saga - final chapter only.

'Epic' means long-winded. But this is why we're all here, right? Sharing what it takes to keep getting the most out of our legacy Macs?

This Cabletron Ethernet NIC is split between a PDS board parallel to the logic board and a magnetics board that mounts parallel to the back of the chassis above the expansion porthole. It offers 10BaseT and AUI connections, and this one has a 64KB buffer. It does not seem to autonegotiate, and so I connect it through a managed switch with a port forced to 10Mbps+half .

First, the main board. Note the orange Sprague axial cap at lower right of the NIC, a little out of kilter..

View attachment 85454

Another perspective. This all fits perfectly fine.. well, almost...

View attachment 85455

The only clearance problem with the main board is that once returned to the chassis, the floor of the I/O bay can (and did) pinch that cap on the NIC, just a little. Fortunately, there is enough slack in the cap's axial leads to just roll the cap outboard a couple of millimeters. But some precautionary insulation, heavy vinyl electrical tape, will pad the chassis' edge - in case I ever slide the logic board out again and forget to watch the clearance on that cap:

View attachment 85456

If I ever do this again, I will get in there with a Dremel and round the sharp edges off of the frame there.

Now, the NIC's I/O panel, with the SE I/O brace attached. Again, this was in fine shape and while not exactly a bargain, I knew it would work when I saw it. (And, it worked.)

Note more of that vinyl tape on the back. More later on that.

View attachment 85457

View attachment 85458

Now, the I/O board was the whole problem. When I first tried to anchor it in the I/O bracket back onto the SE chassis, the I/O board could not clear the internal hard drive. The HDD connectors were nearly in contact with the back of the chassis (when the unit was sealed up).

The only way to make this NIC work and keep the internal HDD .. was to modify the HDD tray. The tray was a clamshell with a top and bottom half. I removed the tray, drilled new holes, and advanced the HDD as far forward in the tray as possible (forward -> towards the user). The limit to this move was the CRT. I did not want to abandon the "lid" (top half) the HDD tray as it shields the HDD from the CRT's EMI. But I also did not want the tray lid to be in contact with the back of the CRT: one good knock and it might fracture the tube. Which would be bad.

The original HDD that was in the tray was anchored to the tray with side screws; IIRC it was an ancient Conner. It wouldn't spin up and had to be replaced. The tray is wider than the HDD and had "dimples" to narrow it down where the side screws met the HDD. The dimples did not extend far enough forward, so I drilled the new holes in the floor of the tray, then covered the floor of the tray first in Kapton tape, for its forever-adhesion, and then added a second layer of vinyl tape for durability. With the HDD screwed down firmly on top of it, the vinyl can never curl up anyway... I'd have preferred an air gap between the HDD and the tray floor for thermal, but hopefully the tray itself can conduct enough heat away to let things live, even through the tapes.

The front of the tray lid was angled to avoid the CRT. I softened the angle - raised its lower edge further from the tray floor - to buy more space to push the HDD forward inside the tray. I applied ample Kapton to the lip of the lid as well as the back of the CRT in case there was any electrical potential between it and the back of the CRT, as well as to soften the impact should any outside jolt ever shake them into each other.

These photos show my first attempt, where the gap between the tray and CRT was there - but too small, paper-thin, to be acceptable. I made a refinement and opened up a 2.5mm gap between the two, which should prevent any physical contact.. but yes, still narrow.

View attachment 85460

View attachment 85461

I repeat, it's not that way now. There's a true gap between them, now.

So how did this help the NIC I/O board clearance? By advancing the HDD within the tray, I gained about 2cm more behind the HDD. Which was enough - but with only about 2mm to spare for expansion and vibration. Now, you see why the earlier NIC I/O board photo showed tape on the back. There's still a close call between the NIC I/O board and the HDD power plug. And those resistors' solder nibs, on the underside of the I/O board, were pointy and sharp. I trimmed them almost flat and then gobbed a little extra solder on them to be certain I had not broken the joints, but also to have nice, dull, round little lumps under the tape that will never perforate the tape.

If anyone knows of a modern, lower-profile HDD power plug, ideally based on a right-angle header.. I believe I've seen them. I should go search for one.

View attachment 85462

And that was about it! I spent time double-checking the mechanicals before I powered it up. Everything still works. Fetched a file or two and called it a night.

I am VERY OPEN to (constructive..) criticisms here. I worry a little about thermal issues in this, namely the HDD now belly-flat on its tray as well as so cozy with the CRT. I did replace the chassis fan with a new, efficient, quiet, modern, look-alike fan. I do hope I have taken adequate precautions.

Epilogue

If I haven't turned into a fire hazard, it's a SE with no new-fangled replacement subsystems, two SuperDrives, an 80MB Apple-branded HDD, 4MB RAM, 10Mbps link, all external I/O working, and a clean case. This was the first system I tried to restore and I have learned the ropes with it. And it is my "Way-back Machine". I sort of thrill a little every time I turn it on and hear the 1984-version chime.. which, when the Macs first appeared on the scene, I associated with Apple bringing 32-bit computing and graphical UI into the everyday person's home. To me, it was like having a little Xerox workstation (like we used in college) in your house.
 
I'm pretty sure they do make right angle headers. Problem is that the Molex plug design was designed for low cost, and so low cost it became, and this has lead to a fire hazard in more modern PCs. If I'm not seriously mistaken, it was, or still is a concern with certain Molex to SATA adapters. Even the Molex plug on the built-in harness for my main PC's CD-ROM drive can be described as "mildly concerning" with lots of wobble on the pins.

Does your router not like your half-duplex 10Mbps connection? I've never had to actually use a 10Mbps switch for old macs yet.
 
Here we go. My epic SE restore saga - final chapter only.

'Epic' means long-winded. But this is why we're all here, right? Sharing what it takes to keep getting the most out of our legacy Macs?

This Cabletron Ethernet NIC is split between a PDS board parallel to the logic board and a magnetics board that mounts parallel to the back of the chassis above the expansion porthole. It offers 10BaseT and AUI connections, and this one has a 64KB buffer. It does not seem to autonegotiate, and so I connect it through a managed switch with a port forced to 10Mbps+half .

Does your router not like your half-duplex 10Mbps connection? I've never had to actually use a 10Mbps switch for old macs yet.

Interested to hear what router you use. Pretty sure I’ve had to do with all mine.
 
In the past, I've used some D-Link router, a Linksys WRT54g (extremely popular 10-15 years ago), and am currently using some cheapo ZyXel DSL modem/router. Never had an issue with a number of different NICs. Only the Asante MC3NB, but that's an easy fix where you swap out a resistor.

I think most likely you're going to run into those kinds of issues with off-brand, less common NICs. Shiva, Dayna, SONIC, ... I steer away from those and prefer common marques, like Farallon or Asante which use National Semiconductor DP839XX chipsets. Not only are they detected right out of the gate by System 7's Installer, or NSI software, but they also work with A/UX if you're into that.

Of course that also depends on your system. The SE has a number of different choices, or had, but also if you're using something like a SCSI Ethernet adapter then yeah of course it's going to be off the beaten path.

There is no auto-negotiation with 10Mbps Ethernet devices like these. That's only a thing with 10/100 or 10/100/1000Mbps stuff.
 
The workshop's upstream connection for this SE is on a leaf switch, a Netgear GS308E using a 1m CAT6 patch cable.

From what little I know about autonegotiation - I may be wrong - it is possible for a downstream port that operates only at 10/full and does not autonegotiate to force a fully-compliant negotiating upstream host port to assume that the downstream is 10/half. The result is unpredictable; if luck prevails and there is very little traffic, it can 'work'. If the downstream transmits often enough, errors ensue, and the link may either just be useless, or be declared officially down by either party.

I can set up an experiment and try a few key configuratiuons. I think the GS308E has a stats page where I can watch for FCS errors accumulating. The SE Cabletron driver provides a Control Panel that logs vital stats. I may try that sometime this weekend.
 
Of course that also depends on your system. The SE has a number of different choices, or had, but also if you're using something like a SCSI Ethernet adapter then yeah of course it's going to be off the beaten path.

There is no auto-negotiation with 10Mbps Ethernet devices like these. That's only a thing with 10/100 or 10/100/1000Mbps stuff.

Yeah, the Asante EN/SC has been a featured player in my setups for many many years.
 
From what little I know about autonegotiation - I may be wrong - it is possible for a downstream port that operates only at 10/full and does not autonegotiate to force a fully-compliant negotiating upstream host port to assume that the downstream is 10/half. The result is unpredictable; if luck prevails and there is very little traffic, it can 'work'. If the downstream transmits often enough, errors ensue, and the link may either just be useless, or be declared officially down by either party.

Yes. This is especially a problem with earlier NICs, because it relies on a fairly rigorous implementation of part of the standard that some older NICs were a little bit wobbly on.

I've only actually had one NIC where this was a problem, and it was an ancient one; I'm always surprised how many people seem to hit this problem, but it is a real technical problem not just a collective neurosis. :-)
 
Summary:

All but one of my legacy Mac NICs can link to an auto port. Thanks for the feedback, all - it is nice to go full duplex!

Details:

My NuBus test systems are both undergoing restoration, so I cannot test my NuBus NIC.



The Cabletron SE will form a link with an auto port on the GS308E. The GS308E status indicators show 10M, as expected. There are very few collisions (only one after hundreds of thousands of packets).



An Asanté MCLC LC PDS (with FPU socket; I added an FPU) (c)1993 will not form a link on an auto port. It will link on any fixed 10M port, full or half duplex. The card is in perfect condition. There is a socketed chip, likely a ROM (can't tell because I don't want to destroy the paper label that covers the stamping), so perhaps there is a ROM update for it. The buffer RAM is 256Kb=32KB and there are four extra pads; I wonder if it can be expanded to a 64KB buffer? There's a jumper as well, J2; it may be for link integrity.

IMG_0335.jpeg




A DaynaPORT E/LC SE PDS (with pads for an unstuffed FPU) will form a link on an auto port on the GS308E. It is built around the NS SONIC chip. I'd put a socket on the FPU pads, but this is used in an LC475 with an FPU'd '040, and so the empty pads are best.



The NuBus NIC is an Asanté MCNB Revision A. It is built around the NS ST-NIC and I expect it will form a link on an auto port. It is rather similar to the SE PDS, similar enough that I think the SE PDS jumper is to en/disable link integrity checking; the NuBus has a jumper with silkscreen text that explains it. This too has a 256Kb buffer RAM with extra pads and this one I might try to replace with a larger RAM, but there's no guarantee the ROM detects the RAM size dynamically. This is intended for a IIcx that, if I can stabilize it, may become the one old Mac I keep.
 
If you check with Glenn Anderson on Tinker Different, he's done reverse engineering of the Asante cards, and could probably tell you what to do about your LC card. He's the guy who figured out that you can change R28 on a MC3NB from 36K ohms to 220K-ish ohms to delay the link detection circuit.
 
One of my IIcx's was in its happy-chime mood today (that one is very sensitive to flexing of the logic board.. re-solder party, soon) and I determined that the Asanté MCNB Revision A will not link with an auto port. It will link 10M full, though, so again - something was gained.

So, nice tip, @Mk.558 - I will review Tinker Different for any tips on modding this revision of the MCNB.

FWIW: the eight-bit wide static RAMs of that era appear to have followed a common pinout. Replacing these 32kilobit RAMs with larger ones is electrically possible, but I have had trouble finding parts. Some of the overseas salvage yards have them in DIP, not SOJ packaging and I could probably just bend the pins.. but.. another day. These work fine without extra buffering.
 
What does it look like?

850zpfqn.png


If it looks like that, then just replace the resistor marked, to 220K or something around there ohms. 270K could probably work too.
 
Mine's different. Although the 26LS32 is still there, I think the ST-NIC handles the support provided by outboard logic in the Tinker Different schematics.

IMG_0336.jpeg
 
Back
Top