I have acquired an old Dell 316SX PC with an old style ethernet card. It has both a coax connector and a DB connector. What adapter can I use to plug it into a modern switch?
CentreCOM? Make sure it will use the right language. Is it a British or American version Dell?Yup, I would just look for a 10BaseT/100BaseT card if you can find one that works. Alternately, the second connector might work with one of these: https://www.ebay.com/itm/145845921676
Actually I believe the MAU connector was intended to let you connect to 10BASE5 thick ethernet. My first real job was with the Dutch (ex-) monopolist phone company doing IT support in an office building back in 1992. The LAN was used to reach file servers and print using Novel Netware and to connect to the FIVE DIFFENT KINDS of mainframes and mini computers the company used. (Unisys Mapper, IBM AS/400, DEC VAX, Tandem NonStop, am I forgetting one...?)Back in the day NICs tended to come with BNC and a connector to attach a MAU for those of us who thought that running your network over phone wiring would ever be a thing.
If you are daring enough and lucky enough, you might combine one of these with one of these. Or a similar solution, assuming your OS of choice will support them.For those of you in need of an even bigger shot of nostalgia, see my Ars FP feature from 2011:
Speed matters: How Ethernet went from 3Mbps to 100Gbps… and beyond
Too bad I it doesn't cover NBASE-T, though. That's 2.5 and 5 Gbps Ethernet over UTP and automatic switching between 100 Mbps - 10 Gbps as supported by the NICs and the cabling.
And sadly, the original 10 Mbps Ethernet is in decline, with new 10 Gbps hardware no longer supporting 10 Mbps, but only 100 Mbps and up. That's fine for NICs in computers, but how am I going to connect my 30-year-old Amigas to the internet or my Synology NAS if my switch can't do 10 Mbps half duplex??
Systems from those days can't even handle one clock cycle's worth of data from a modern system.All I need is 640kb Ethernet god damnit.
That first link won't load for me. But I do in fact have an Avaya Silver PCMCIA 802.11b card much like the one you link to from back in the day, and there are actually Amiga drivers for it so I can use that card with my Amiga 1200. However, I can't do WPA with it so that leaves WEP which is no good. And nothing like this for my Amiga 3000.
No, in the absence of autonegotiation you still get the right speed, and half duplex by default.My vote is MAU to get to RJ45/10baseT, you'll probably need a managed switch to force the port down to 10/half but it should work.
That serial I/O card looks to be an HWIC-2T (High speed WAN Interface Card, 2 port/Terminal) for a Cisco 1600/1700/1800/2600/2700/2800/3600/3700/3800 series unit. The difference being- those are specialized high-speed serial and not run of the mill RS232 115k baud maxed normal serial interfaces. Think V.35, DSU/CSU, DCE at max 2.048Mbps. When the opportunity arose, we yanked these for the Ethernet WAN cards when we could.I did my networking degree in the late 2010s and we were still hooking up our lab routers & switches with serial links.
![]()
It was a link to a PDF about the AMPHUS (FORMERLY VADEM) VG-469 ISA to PCMCIA card.That first link won't load for me. But I do in fact have an Avaya Silver PCMCIA 802.11b card much like the one you link to from back in the day, and there are actually Amiga drivers for it so I can use that card with my Amiga 1200. However, I can't do WPA with it so that leaves WEP which is no good. And nothing like this for my Amiga 3000.
It's really great to be able to mount my NAS over SMB on these machines, it makes exchanging data between those and the modern world a breeze. (Slow breeze, but still.) Obviously when I get a faster switch that doesn't do 10 Mbps I'll hook up my current 10/100/1000 switch with the Amigas on it up to the new one to solve the problem. Still sad to see the original 10 Mbps Ethernet disappear.
We still have a couple of T1s in our main data center and at some BFE branches.I did my networking degree in the late 2010s and we were still hooking up our lab routers & switches with serial links.
![]()
Pretty sure you're right that the AUI connector (which you plugged your MAU into) was originally designed for thicknet (which used vampire taps that couldn't be integrated directly into cards), but it was universal enough that it got used for pretty much every physical media type for 10Mbps ethernet.Actually I believe the MAU connector was intended to let you connect to 10BASE5 thick ethernet.
The actual product for that Amphus chip is something like this.
Weird that it took a week before someone mentioned the 3c509.I had one of these
Held on to it when I was doing some networking classes so people could actually see 'em. Thanks for jogging some memories!
Yeah, I actually have experience with the old AT 3COM cards. This PC does have Windows 3.X installed, so there's also the Windows drivers approach.Pretty sure you're right that the AUI connector (which you plugged your MAU into) was originally designed for thicknet (which used vampire taps that couldn't be integrated directly into cards), but it was universal enough that it got used for pretty much every physical media type for 10Mbps ethernet.
AUI's descendants are still with us today, in the form of SPF and similar more compact transceivers.
The actual product for that Amphus chip is something like this.
Trying to find a single one of that chip (which is probably out of production now, with any Amphus has in stock being made over a decade ago), then designing a new PCB around it, just to use a PCMCIA NIC in an ISA slot, would require more than just daring. It'd probably be more accurate to call it insanity.
Weird that it took a week before someone mentioned the 3c509.
@AndrewZ, the safest choice is definitely a 3Com card, as they were the business standard back in the ISA days and supported by almost everything that supports ethernet in any way. In addition to the venerable 3c509 (you'll need to get a later version to get one with a 8p8c connector for 10BASE-T), there's also the 3c515 (fast ethernet; the ISA slot can't run it at full speed, but it's more compatible today since 10BASE-T support is disappearing).
Could be worse, it could've had a token ring card.
Token ring wasn't terrible as long as someone didn't take the terminator out. Or twist it juuuuust enough so it looked like it was in but it wasn't.That’s one network technology I’m thankful I never had to deal with.
Although when I was in college, the Mass Comm department was stuck in the basement of the library tower building.
One night when we were trying to hack together some manner of radio transmitter antenna we found in a closet, a token ring cable end popped out from behind the ceiling tile we moved.
Yes, it was horror movie level scary!![]()
Carrier pigeons. Station wagons for big files.I don't trust that new fangled Ethernet. I'll stick with ARCnet.
RFC1149: IPoAC.Carrier pigeons. Station wagons for big files.
I don't trust that new fangled Ethernet. I'll stick with ARCnet.
Now I'm wondering what the 802.3at equivalent for RFC1149 would look like.
For those of you in need of an even bigger shot of nostalgia, see my Ars FP feature from 2011:
Speed matters: How Ethernet went from 3Mbps to 100Gbps… and beyond
Too bad I it doesn't cover NBASE-T, though. That's 2.5 and 5 Gbps Ethernet over UTP and automatic switching between 100 Mbps - 10 Gbps as supported by the NICs and the cabling.
And sadly, the original 10 Mbps Ethernet is in decline, with new 10 Gbps hardware no longer supporting 10 Mbps, but only 100 Mbps and up. That's fine for NICs in computers, but how am I going to connect my 30-year-old Amigas to the internet or my Synology NAS if my switch can't do 10 Mbps half duplex??
Feeding tubes that activate when the pigeon lands and inserts its beak into the socket after removal of the datagram. Of course physical material would need to be provided, unlike PoE. The real problem would be waste control and management during "recharging" sessions (which would occur in "fast charge" mode between send/receive activities and "deep charge" mode for several hours at night). Not to mention the inability to transfer data at night without specialized equipment (night owls) which will be costlier.Now I'm wondering what the 802.3at equivalent for RFC1149 would look like.
I hear big things are gonna happen with Apple Talk. Might check it out.I don't trust that new fangled Ethernet. I'll stick with ARCnet.
Just imagine Cook turning and saying "one more thing, Apple Talk II", and it's like a 100Gb protocol that works on alarm pair (two wires) cabling up to a kilometer, with speed reductions scaling smoothly with distance down to gigabit at 20km, and a Cat6 pair can reach 500Gb, and you can bond the pairs in bigger cables so you can get 200Gb using common household phone cables, or 2Tbps with Cat6. It has zero patents involved that aren't owned by Apple, and it will only work with MacOS until the new patents expire, and will only work with Apple Silicon devices from the M5 onward using a dedicated port that nothing else uses. There is also a wireless version of course, but simple physics of signals limits it to 100Gbps at up to 300 meters.I hear big things are gonna happen with Apple Talk. Might check it out.
Keep dreaming. The only thing that Apple hates more than wires on their devices is buttons on those devices. The future is wireless!Just imagine Cook turning and saying "one more thing, Apple Talk II", and it's like a 100Gb protocol that works on alarm pair (two wires) cabling up to a kilometer,