What Happened to 3Com?
dfarq.homeip.net
dfarq.homeip.net
They were high-quality cards and the lifetime warranty proved to be very popular.
That sounds like a stupid scam unless you’re super confident in your product.
Outside that, I think I missed everything though I have memories of another company that merged into 3x in, xircom? Before they were acquired again.
For those with textual proclivities: https://archive.computerhistory.org/resources/text/Oral_Hist...
Metcalfe has a reputation for being brash and outspoken and it clearly shows in the interview. I think it served him well in business and later in life as a pundit. I remember looking forward to his columns in InfoWorld, though I didn't necessarily give much stock to his predictions.
He talks a little bit about the downfall of 3Com in the interview, though he begs-off of talking about things that happened there after he left.
I very much enjoyed the trivia and minutiae about the creation of Ethernet and the Digital / Intel / Xerox relationship that ultimately resulted in it being standardized.
Basically, it was a long listen but there was some good stuff in there.
That is a remarkable decision.
I was on the Macintosh network os client team. For whatever reason (maybe he was annoyed that Apple copied so much from Xerox) Metcalfe didn't like Macs. In this era Macs used Apple's proprietary AppleTalk/LocalTalk network. We did a demo for 3Com execs using a large external monitor connected via a single black coax cable that looked just like thin-ethernet. He got excited for a moment and came right over to look at the Mac and was very disappointed to see the cable attached to a display! (3Com was working on Ethernet cards for Mac at the time but they weren't ready at the time of this demo.)
For those too young to remember: there was an SF Bay Area baseball park known as Candlestick Park that was briefly branded "3Com Park" -- to the great annoyance of SF Giants fans. During one interview he as asked if in the early days of 3Com he would have done anything differently. He said, "I would have named the company 'Candlestick'!"
Every year that I worked at 3Com, we proclaimed it was "the Year of the Network!" It became a running industry joke.
But of course, Metcalfe's Law contains some fundamental truths: https://en.wikipedia.org/wiki/Metcalfe's_law
Proclaim the Year of the Network some time in 1993 or 1994, and you're golden.
(It was the 1980's version of the Linux Desktop joke)
An amusing example of his punditry:
"I predict the Internet, which only just recently got this section here in InfoWorld, will soon go spectacularly supernova and in 1996 catastrophically collapse."
Keep in mind he co-invented Ethernet, so he knew what he was talking about!
Here's hoping we'll be able to look back with equal amusement at the AI doom predictions.
https://www.elon.edu/u/imagining/expert_predictions/from-the...
Ron Crane which was 3com's 4th employee and designed the 3C100, 3com's first ethernet product. Many years later he hired me for my first real job of out school and brought me to the bay area. I then got to work side by side with him and David Boggs (https://en.wikipedia.org/wiki/David_Boggs). At the time I never realized how special working with these two were...wasn't every company in the bay area like this?
I stayed in tough with Ron Crane until his death in 2017. He was both brilliant and incredibly sweet. He was so proud to take me behind the scenes at the Computer History Museum to show some work he'd been going.
I know Ron has writen about 3com...but this story captures the Ron I know: https://www.theregister.com/on-prem/2013/05/28/how-god-and-u...
One day, Ron (a hardware engineer from Xerox) gave a talk about the theoretical performance of an Ethernet file transfer. He calculated the end-to-end latency and data-rate including disk latency, network latency, the number of clock cycles necessary to send and receive the data, etc.
He had (overhead projector) slides that showed all his assumptions and calculations. Finally he displayed a slide with a graph showing this theoretical maximum, the actual performance of the 3Com network stack, and (IIRC) the Novell stack. As I recall, actual performance was about an order-of-magnitude lower than the theoretical max.
His point wasn't that our software division should be able to achieve the theoretical max. It was that if we (for example) got halfway there, we would know that Novell would never ship software that was twice as fast as ours.
He was very nice and scholarly about it and did not mean offense. I and many others weren't offended. But a surprising number of people were.
I'm sorry to hear that he passed.
ep0: 3c509 in test mode. Erase pencil mark! This means that someone has
scribbled with pencil in the test area on the card. Erase the pencil
mark and reboot. (This is not a joke).
It's the E1 pad between the barcode and the empty BIOS socket: https://en.wikipedia.org/wiki/3Com_3c509#/media/File:3Com_3C...Details (pg 88): https://www.ardent-tool.com/NIC/3c5x9b_Technical_Reference.p...
----------------------------------------
It is the user’s responsibility (with help from the configuration program) to avoid configuring the boot PROM on the adapter in such a way that the system is not able to boot. If this does occur, you can manually jump the Test Via using a #2 pencil. The Test Via forces the adapter into test mode, which disables the boot PROM so that the adapter configuration program can be run. You must cover the designated area thoroughly with the pencil mark.
Test mode forces the adapter not to perform the Automatic Initialization sequence, which means the EEPROM is not read and the adapter is left in the following configuration:
■ Address Configuration register = 0000h
■ Resource Configuration register = 0000h
■ Product ID register = 0000h
Test mode also shortens the ID sequence to 8 bytes (first is still FFh and last is 69h) and forces it to the active state (that is, the adapter is active and will respond to I/O cycles at base address 0200h even without going through the ID sequence).
After you are done, thoroughly erase the pencil mark.
----------------------------------------
I was only a consultant at 3Com during this time, so I may have some of the details wrong, but 3Com essentially bet the success of its software division on the partnership. We built a product called 3+Open that was based on OS/2 Lan Manager. The product flopped. But unfortunately 3Com had agreed to multi-million-dollar, fixed annual license payments to Microsoft for OS/2. (Which may have been the right choice had the product been successful.)
To get out of the license payments, 3Com gave all its LAN software IP to Microsoft and exited that business. Microsoft used that technology in Windows NT Lan Manager and essentially destroyed Novell.
If you want details, the Bill Gates Biography "Hard Drive: Bill Gates and the Making of the Microsoft Empire" tells the story of that failed partnership.
For Microsoft it sounds like it "failed successfully".
MS realy is the trojan horse. Because probabilities multiply into less probable outcomes but result is again and again the same.
Source: me, LAN guy since 1990 and NT admin since 1993.
But the stocks jiggled and the buyout plan was postponed when valuations became uneven, and it never happened.
Standard wisdom was to use an Intel EtherExpress Pro card for a long time after onboard Ethernet was available. Lots of server hardware had unused builtin NICs until they got decent.
https://news.ycombinator.com/item?id=42746741
tldr:
"The RealTek 8139 PCI NIC redefines the meaning of 'low end.' This is probably the worst PCI ethernet controller ever made...8139 supports bus-master DMA, but it has a terrible interface that nullifies any performance gains that bus-master DMA usually offers.
For transmission, the chip offers a series of four TX descriptor registers. Each transmit frame must be in a contiguous buffer, aligned on a longword (32-bit) boundary. This means we almost always have to do mbuf copies in order to transmit a frame, except in the unlikely case where a) the packet fits into a single mbuf, and b) the packet is 32-bit aligned within the mbuf's data area. The presence of only four descriptor registers means that we can never have more than four packets queued for transmission at any one time.
Reception is not much better. The driver has to allocate a single large buffer area (up to 64K in size) into which the chip will DMA received frames. Because we don't know where within this region received packets will begin or end, we have no choice but to copy data from the buffer area into mbufs in order to pass the packets up to the higher protocol levels.
It's impossible given this rotten design to really achieve decent performance at 100Mbps, unless you happen to have a 400Mhz PII or some equally overmuscled CPU to drive it."
tldr tldr: it didnt matter past 2001 since slowest low end CPUs were cheap enough to nullify all the potential gains from smart good 100Mbit NICs
I can't quite remember if the 3c509, 595 or 905 was the fastest and best. I think 905. I created a boot disc for these and a few other NICs that featured on Novell's Cool Solutions.
Nowadays I have QSFP28+ to fiddle with.
It was fast, but not noticeably faster than any other cards my friends had. Except I spent way too much on mine.
(Small text changes, and a CTA at the bottom)
https://web.archive.org/web/20220302141059/https://dfarq.hom...
They split off their Palm (PalmPilot) division in 2000 to focus on Network equipment. The the .com bust happened.
Palm/Handspring/Treo could have been the iPhone, if they'd been better managed.
iPhone wasn't just a form factor, the software traces back to NeXTSTEP 1989.
Fact of the matter is nothing could have been the iPhone, everything sucked in 2007.
Apple had the wind in its back with the iPod and Mac OS X Tiger.
The Intel transition was complete.
Apple was firing on all cylinders, what a time to be in your early 20s.
Even Android did a 180 once the writing was on the wall, it originally resembled BlackBerry OS.
>The first thing that happened was 3Com walked away from its enterprise networking equipment business. Admittedly Cisco was hard to compete with. But 3Com was the only brand succeeding at doing it.
I can't really agree with that because 3com never had a serious router product line. They had LAN switching equipment and NICs. There was nothing like a whole product line of routers that could take a full BGP table in the 1999-2000-2001 era, and certainly nothing like medium to large carrier routers. I'm talking about around the same era when the Juniper M40 was released to compete with Cisco in that market. Or a Cisco 12008. Anything broadly along those lines. 3Com was far behind in advanced IP routing and things that would serve as like a metro aggregation router or core router.
I remember when USRobotics was giving away free 56Kbps modems to BBSes if the SYSOP listed that they had a USRobotics modem and kept the BBS up for 24 hours a day.
Someone is still making a NIC chip, they're just selling it to the motherboard OEM, instead of selling an add-in board to the customer (or selling a chip to the add-in maker). In a way, this is more sales, because desktops tend to come with a wired nic and a wireless nic, and so do good laptops.