Not really an expansion card but a full blown EISA motherboard featuring an i80486 and an i80860 socket directly on board – thus the ingenious name Hauppauge 4860. The i860 can work in parallel to the i486, both sharing the on-board RAM which can be freely partitioned. But theoretically the i860 could also run completely alone… at least Hauppauge mentions this in the manual, announcing a UNIX version for this option (of course that never shipped).
This board is quite a huge beast, full size AT that is. For its time it was regarded as high-quality but besides 1 ASIC and 2 Intel chip set ICs there are a lot of logic ICs and PALs.
I’d say it’s a ‘IC graveyard’ and one of the most exciting 80486 boards ever made.
(And a real diva when it comes to add cards :-/ More on this further down)
These are the main specs:
- 80486 socket (does not run stable with DX/2), 25 or 33MHz
- 80860 socket (same clock speed as 486)
- Weitek 4167 (aka Abacus) mem-mapped FPU socket
- Intel “485TurboCache Module” socket
- 7-8 EISA Slots (depending on revision)
- Intel EISA chip set consisting of 82358-33 EISA Bus Controller and 82357 Integrated System Peripheral
- On-board Serial/Parallel and PS/2 mouse support
- 8 SIMM sockets for up to 64MB (Fast Page Mode,parity – No chance with EDO or non-parity)
- Award “486 Modular BIOS v4.10” / BIOS level 1.01 -obviously specifically tailored to the 486/860 needs.
Because there are so many things on this manly mainboard, I will go into further detail based on quadrants:
Well, that’s where all the mojo sits, right. The two processors side by side – ahhh – what a macho view! 😉 Mind the single oscillator: This means both CPUs run at the same speed, which is a bit of a pity, as the i860 was/is available at clock speeds up to 40MHz. Because Intel never really crossed the 33MHz external clock (the 50MHz 486 was quickly replaced by clock doubling versions due to heat issues) for their 486 processor, this is the highest common denominator.
That said, the Hauppauge 4860 does not support DX/2 processors… believe me I tried them all (even up to 5×86 w/ voltage regulator).Yes, it’s running fine one day while failing to boot the next day. So be sporting about it, an AMD 5×86/133 will easily outperform the i860/33 and who would like to put him ashame like this?
Ok, next to the two brains you can easily spot the 8 SIMM slots. It’s not easy to satisfy the RAM specs here: PS/2 SIMMs, optimally 60ns, Fast Page Mode (FPM) with parity – only up to 8MB per SIMM will be addressed. I had to learn that it is not so easy anymore to find those SIMMs today :-/
At the rightmost edge of the board you can see the classic AT-style power connectors… with an additional connector for 5V. Yup, it’s a server board, having all RAM- & EISA-slots populated, this beast can slurp quite some juice. Ok, it still would be nothing compared to todays insane 1000W power supplies feeding quad-core CPUs and dual graphic-cards.
At the lower edge you can spot quite some logic ICs. That’s a part of the memory interface – yeah, no stinkin’ ASIC, just TTL logic and many GALs.
While or two processors still peeking over the right edge, you can easily spot even 2 more sockets on this board. The square one on the left is meant for a Weitek 4167 (also known as “Abacus”) while the two pin-rows in the middle of the picture are planned for an “Intel 485TurboCache” (yes, that’s 485) module.
Honestly, I have no idea why Hauppauge added the Weitek 4167. As it was just about a bit faster than the inbuilt FPU of the 486/33 (~10% overall), it had no chance against the i860 – both needed programs which were specifically made for them, so compatibility wasn’t an argument for both. I guess it was added on the board just because they could… which is the right spirit!
The socket for the “485 TurboCache” was a good idea – which seems to went wrong in the case of this board. The module generally is nothing more than an i82485 cache controller with 64 or 128k SRAM. After years of searching I found two different models, both not working with the 4860. This seems to be a known issue to Hauppauge as you can find complaints in old (’92) newsgroup posts and Hauppauge itself suggesting not using this module.
This is the most modern part of the board (as by 1992 standards). It’s actually using ASCIs and not only 80’s-style PLDs. In the top-left corner you’ll spot the Samsung 82C452, which is controlling the 2 serial and 1 parallel port(s) on the board.
Next to it is all the Keyboard/BIOS stuff – one fine thing to mention: Hauppauge used an external battery for the settings/clock. Thanks to god they didn’t use some of those nasty Dallas SRAM/Clock chips. After 10 years the internal battery get weak and there’s no way the replace just that (well, there are ways, but that’s really the last resort).
Now it’s getting serious: ASICs, made by Intel… a chip set! Woohoo! Namely the 82350 Intel chip set (Click here for a lenghty article I wrote about this chip set).
This chip set comprises the 82358-33 EISA Bus Controller (EBC) and the 82357 Integrated System Peripheral (ISP). Together these two devices implement a functional interface to the EISA bus, and provide most of the standard peripheral functions necessary to implement a minimum EISA solution. In a simple sentence: The EISA interface.
That said, there’s a catch: The 4860 being an early EISA board, does not feature the more ‘modern’ 82358DT EBC you’ll find on most EISA boards. This might be the reason why some EISA cards refrain from working with this board. I found a snippet saying “The 82358DT is a superset of the original 82358 and includes a mode compatible with the 82359 Buffered Bus“. The 82359 DRAM controller is obviously missing (probably not a available at that time) and the RAM controller is implemented in lots’o’GALs.
Across the bottom of the picture there’s another slot, looking a bit like EISA… but it’s not! That’s the Hauppauge 64bit Framebuffer Expansion Bus. Hauppauge sold a graphics card basically containing 4MB of VRAM which could be directly accessed by the i860 at very high speed. That made the board a graphics-accelerator like for example the SPEA Fire.
Not much is known about this framebuffer card. Still, I was able to find a blurry press photograph in an 1992 computer magazine. Obviously it’s mainly buffers, GALs, VRAM and 3 RAMDACs for R, G and B… I do have an AutoCAD ADI driver, but I guess you won’t get this board anywhere on the planet anymore 🙁
Here’s a better photograph I just dragged out of the web:
Welcome to the end of our tour… the boring part – at least at the first look. 8 EISA slots and some buffers. Nothing exciting, really.
If you take a close look, you’ll see the sticker between slot 6 & 7 (counting from the bottom). This sticker tells you that this board is a “rev D2”:
I don’t have that much documents to figure out the tiny little differences to older versions, but the big one is slot #2. In previous revisions, that slot was ISA… a heritage to this fact is, that on REV D2, this slot is a “non EISA bus master slot” – which is also true for slot #7 (inline with the Frambuffer-Card slot).
The reason for this is (my assumption, though) that the 82357 (ISP) integrates seven 32-bit DMA channels, of which 6 routed to the EISA slots and one used for the Framebuffer.
That’s it for now. I will add new findings as I proceed with my fiddlings.
Thanks for joining the tour, don’t forget to buy a T-shirt in the merchandise shop at the exit…
For the whole enchilada, get the 4860 Manual here. That’s real men reading stuff… i860 source code samples included.
This is the official tools and driver disk and here’s a (yet) small archive containing the ADI drivers for the Framebuffer card and the i860 APX specifically tailored to the Hauppauge 4860 (i.e. won’t run on any other i860 system).
Another nice find: The presentation held at Hot Chips Conference 1990. It gives some more insight into the board design and ideas behind it.
I found a short article in one of my old (German) computer magazines (“MC”, 1992). Here it is for your amusement/riddling:
11 thoughts on “Hauppauge 4860”
Cit. “Because Intel never crossed the 33MHz (external) clock for their 486 processor”….
Intel crossed externally the 33MHz frequency with its beast…80486DX 50.
You’re absolutely right. No idea what made me writing this…
I do remember when the 50MHz model came out. It ran hot as hell and was one of the first Intel CPUs requiring active cooling.
Also, 50MHz made board designs incredibly difficult (read: expensive) when they had VLB or PCI buses, which were created for 33, max. 40MHz (VLB) bus clock. Problems were solved by adding wait-states when accessing the bus, making such systems slower than their 33MHz rivals.
Intel did come out with a 486DX 50 Mhz. I use to be a tech at shop and we had built a Netware 3 server with one. It was nothing but problems but I think it was more timing issues than thermal. I also remember it had major issues with the Adaptec dual SCSI EISE adapter. (It was an EISA motherboard). The server would crash because of a hardware error. Disabling one of the channels reduced the frequencies of crashes and replacing it with EISA SCSI cards stopped that particular problem. But the board had other problems and made it unreliable and to solve those all we did was replace the CPU with a 486DX2 66 Mhz,
Thanks for commenting. Yes, those timing issues are due to the fact that a 50MHz CPU/RAM-bus clock was really high-end back in those days and a motherboard had to be designed very carefully to cope with that ‘insane speed'(tm)… EISA clocking hadn’t had issues because 50MHz can be divided by 6 to reach a perfect 8.33MHz bus-clock.
The dual channel EISA SCSI controller sounds like an Adaptec 2742T or some high-end beasts with i960 controllers onto it… I have quite some EISA boards having issues with those – most of them older than the SCSI controllers. I assume in the end of the EISA era they “stretched” the specs to the max.
Probably the most fun box I ever had under my desk. And Hauppauge packaged it in a case that was built like a tank. If I recall correctly, it even had hinges on the side panels. We must have had 6 or 8 of these boxes in our group at the time. They were being used to develop code for our Intel i860 Hypercubes. We thought we were really screaming at 66 MFLOP! (our boards were 33MHz versions) I believe the 486 was only a fraction of a MFLOP. The Portland Group Fortran vectorized our kernel close enough to the theoretical maximum that I we didn’t need to hand tweak anything. (not that I remember, anyway…) Fun times.
Hey John! Wow, sounds amazing, thanks for sharing! Of course neither photos nor code survived, right?
I might have a glossy somewhere of our Hypercube, but not the Hauppauge. The code was all proprietary. We were doing Computational Electromagnetics for the government.
I owned one of these ages ago, it ran the first version of Linux which I downloaded on 5″ floppies. It was a very fast machine for it’s time and I think I had 8 or 16 MB installed. I can’t remember what it cost but it was not cheap, getting a i860 was the hardest part.
I was working for a startup at the time and they had a 3D graphics chip they were trying to sell one of the major graphics companies… I wrote the OS for the i860 and the 3D geometry code which ran on the i860 for the 486 host.. it was very cool.
It was totally worth it as it landed me a good paying job in computer graphics for almost 20 years… I retired at 48.
Thanks „Guy“ for sharing this history treasure… I’d love to see that OSes code or even run it on my 4860, but that is probably all gone and dusted. Sigh.
It’s been gone for years, but I have been searching eBay for a 4860 motherboard to work on.. still searching.
Yes, it exists in Greece and works just fine! Send me an email at email@example.com