1987 Networking: ELS NetWare 286 Level I 2.0a

A rare find recently turned up: NetWare from 1987, specifically the low-end ELS variant of NetWare 286 version 2.0a (ELS may be claimed to mean Entry Level System or maybe Entry Level Server, but at least originally it stood for Entry Level Solution). NetWare v2.0 was released in 1985, followed by v2.0a in 1986. In November 1987, NetWare v2.1 was to become available, but in September of that year Novell released the low-end ELS product with support for 4 users (really 4 concurrent connections) and without some of the perks of Advanced NetWare. The ELS package was based on the about-to-be obsoleted v2.0a version of NetWare 286.

Screenshot of non-dedicated ELS NetWare 2.0a booting up.
Is it DOS? Is it NetWare? It’s both!

The original ELS I product was later updated with NetWare v2.12 as its basis. In early 1988, Novell added an ELS II package with support for 8 users. The ELS II variant was initially based on NetWare v2.1 and later updated to v2.11, v2.12, and finally v2.15. In 1991, Novell consolidated all the low-end versions into NetWare 2.2 (sold alongside NetWare 3.11 and released more or less at the same time as 3.11).

A print ad for ELS (Entry Level Solution) NetWare, published in PC Magazine in December 1987. "To get the power of NetWare, you'll have to pay a small price", $595. Via Google Books.
A NetWare ELS print ad (PC Magazine, December 1987)

For whatever reason, even though NetWare versions for PCs existed since the early 1980s, it is nearly impossible to find any NetWare server software from before 1990; presumably in large part because NetWare actually sold in rather small numbers before 1990 and with funny stuff like hardware locks in the early versions, the software wasn’t very useful once the hardware died. Whatever the reason, NetWare from 1987 is exceedingly rare, and in fact any PC networking software from 1987 or earlier is surprisingly difficult to find.

Continue reading
Posted in 286, 3Com, Kryoflux, NetWare, Networking | 29 Comments

Another Strange 286 Board

The OS/2 Museum sometimes seems to have a knack for acquiring hardware so obscure that it cannot be even identified. One of the more recent arrivals was a seemingly typical Baby AT 286 board with an 8 MHz CPU. The board was in remarkably good condition for its age, having been produced in 1986; the date code on the PCB could be read as 15-98 or as 86-51, but there’s no question which of the two interpretations is correct. A significant contributing factor to the good shape of the board was no doubt the fact that it uses a CR2032 lithium coin battery and not one of those horrible leaky NiMh rechargeables.

A Maxware/Fujitech Baby AT 286 motherboard.
A Baby-AT 286 clone board of ostensibly Japanese manufacture

The board claims to have been made in Japan by a company named Fujitech, or maybe Maxware. Interestingly, a very similar Fujitech XT board was seen with a sticker on it referencing Octek, a Taiwanese company. This would not be the first board supposedly Made in Japan that was really manufactured in Taiwan or China, but at least this “AT-BABY” uses almost exclusively Japanese components, whether it was actually assembled in Japan or not.

Continue reading
Posted in 286, PC hardware, PC history | 27 Comments

More Fun with ISA DMA

A reader comment on a previous post on ISA DMA pointed out that UMBPCI (or rather the DMACHK utility distributed with it) does something unusual with regard to ISA DMA. There was a suspicion of somehow accomplishing the mythical memory-to-memory DMA transfers; that proved to be unfounded, at least in the UMBPCI case, but what the utility does is nevertheless quite interesting.

Dual NEC D8237AC-% DMA controllers in a PC/AT clone board.
Classic cascaded 8237A DMA controller chips in a PC/AT clone

First some background about what DMACHK does and why it exists in the first place. UMBs are generally prone to causing difficulty with DMA, and UMBPCI is no exception. The way UMBPCI works is that it enables memory between 640KB to 1MB for use with UMBs. Such memory is normally only intended for ROM shadowing and in some chipsets, it is not accessible via DMA (whereas EMM386/QEMM/386MAX use paging to remap normal memory into the UMB range, causing physical addresses to differ from linear ones).

Continue reading
Posted in PC architecture, PC hardware, Software Hacks | 8 Comments

MS OS/2 SDK Document Dump

The Microsoft OS/2 1.0 SDK library section got a big fat update. Over the holidays I managed to finalize and upload about 25 PDFs, some of which have been lying on my NAS in 98% completed state for almost 10 years, and some of which have been only scanned a few months ago. I may still have one or two ring binders lying around and those will be added when I find them and scan them.

It’s thousands of pages of Microsoft documentation from 1987 and early 1988. Some of the documents ought to be interesting for DOS programmers since they include retail MASM 5.0 and MS C 5.0 documentation. There are also pre-release versions of the MS C/MASM 5.0 documentation from May 1987. There are separate “diff” addenda documenting the OS/2 specific features of the tools pertaining to the beta compilers shipped with the MS OS/2 SDK. And there is actual pre-release OS/2 programming documentation from April 1987, right after OS/2 was publicly announced.

Posted in Documentation, Microsoft, OS/2 | Leave a comment

The Cape Cod Disaster

Here’s a motherboard Intel very quickly wanted to forget about:

Intel Desktop Board CC820 with CPU and SDRAM, early 2000
Intel CC820 Desktop Board (early 2000)

It’s the Intel CC820—or Cape Cod—desktop board, a product that was late to market (not unusual) and within a few months, the subject of a recall (quite unusual). As the CC820 designation suggests, the board was built on the ill-fated Intel 820 ‘Camino’ chipset.

The Camino chipset was supposed to be released roughly in mid-1999 as a replacement of the workhorse 440BX chipset for mainstream desktops. At the same time, Intel changed how it segmented the market. The 440BX supported up to two processors, while the 820 didn’t (though the 820DP variant did); the 820 chipset was targeted for typical desktops, while the Intel 840 chipset was meant for high-end workstations with two processors. Note that the Intel 810 chipset was meant for “value” PCs, and played that role quite successfully.

The 440BX chipset was limited to 100 MHz FSB; the 820 supported 100 and 133 MHz FSB for the then-new Coppermine Pentium III processors. The 440BX chipset was limited to ATA-33, while the 820 supported ATA-66. The 440BX only supported AGP 2x, while the 820 provided AGP 4x capability.

But that wasn’t all. The 820 chipset also supported RDRAM, or Rambus DRAM. And therein lay the problem.

Continue reading
Posted in Bugs, Intel, PC hardware, PC history, Pentium III, RDRAM | 45 Comments

DOS Wireless Networking, Continued

As I recently mentioned, wireless networking is extra difficult when the access point reboots itself at the slightest hint of heavier traffic. The faulty TP-Link router was temporarily replaced with a Netgear WG602 of similar vintage. The Netgear has been solid and has no trouble transferring tens of megabytes without a glitch.

I should note that although the TP-Link turned out to be bad, it has nicer diagnostics than the Netgear and it is slightly more tweakable. But a working AP wins out any day.

Agere ORiNOCO wireless PC Card in an IBM ThinkPad 760XL
Agere ORiNOCO wireless PC Card in a ThinkPad 760XL

The next project was getting IBM’s TCP/IP 2.1 working wirelessly. The protocol stack is almost completely dynamically loadable and unloadable, and comes with a decent NFS client. I had previously got IBM TCP/IP going in a DOS VM without much difficulty, but convincing it to work with a Cisco Aironet 350 turned out to be surprisingly tricky.

Continue reading
Posted in DOS, Networking, NFS, TCP/IP, Wireless | 3 Comments

The Danger of Datasheets

A few days age I came across an article about the 8237 DMA controller in an old German computing magazine (DOS Extra, issue 1 ’87/88, page 123, Schnelle Speicherverwaltung mit dem DMA-Controller, or Fast memory management with the DMA controller). While skimming through the article, I began to suspect that the although the author did a good job reading the 8237 datasheet, he had only a rather vague idea of how the controller was actually wired up in the IBM PC.

On closer reading of the article, my suspicion was confirmed. While there is some PC-centric information in the article (which I/O ports the 8237 is mapped at, or the fact that the DMA controller is used for memory refresh in the IBM PC), absolutely crucial IBM-specific information is missing.

Continue reading
Posted in Corrections, PC hardware, PC press | 29 Comments

Power Trouble

This will not come as a surprise to anyone who is deeply familiar with PC hardware; the other 99% please bear with me.

A good quality and compatible power supply is crucial to the healthy operation of a PC. The catch is that whether a PSU (Power Supply Unit) is actually compatible and truly good quality may not be very apparent. Even worse, when there are problems, the symptoms may be extremely non-obvious and tend toward “analog” failures—sometimes things work, sometimes they don’t, seemingly with no rhyme or reason.

Probably my favorite retro mainboard is an Alaris Cougar, a VL-bus OEM board manufactured by IBM, also known as IBM Cobalt-AT. The board has an onboard 100 MHz IBM BL3 processor (a triple-clocked Blue Lightning 486DLC, i.e. IBM’s rocket-boosted 386), separate Socket 2 for a 5 Volt 486 SX/DX/DX2 or Pentium Overdrive, a blazingly fast Adaptec VLB IDE controller, and MR BIOS which POSTs about hundred times faster than conventional BIOS implementations (well, not really but it often feels that way, because it is easily 10 times faster).

The board is from 1993 or 1994 and of course it uses the Baby AT form factor, with a classic AT P8/P9 power connector (ever plugged those in backwards? I have…). AT power supplies are getting harder to find and their on/off switches are not suitable for bench operation. An ATX PSU with a switch on the back, combined with a simple ATX to AT adapter, does a better and usually quieter job. Except not always.

Continue reading
Posted in PC hardware, PC history | 13 Comments

Wireless Networking in DOS

Wireless networking has a long history, longer than most people realize. NCR’s WaveLAN was available in 1990 and of course supported DOS. But WaveLAN was only the precursor to IEEE 802.11 and it is completely incompatible with IEEE-standard networking equipment.

The IEEE 802.11b standard came out in 1999, specified a 11 Mbps signaling rate, and it’s about the oldest not totally obsolete wireless networking standard. The trouble is that IEEE 802.11b equipment appeared when DOS was almost gone from home and corporate PCs, although it still survived as a “pre-boot” environment for running Norton Ghost, Partition Magic, Drive Image, and similar products. The upshot is that until the early 2000s, there was demand for DOS networking drivers for then-current hardware.

My need was seemingly simple: I set up an old ThinkPad 760XL (166 MHz Pentium MMX) running DOS for my son to play 1990s games on, especially but not exclusively Sierra and LucasArts adventures; for that purpose, the laptop is quite suitable, it has a decent ESS sound chip and a CD-ROM. Moving data to the laptop on a CF card with a PCMCIA adapter is not difficult, but it gets old; it would be really handy to have the laptop on the network, accessing the home NAS via either SMB or NFS.

IBM ThinkPad 760XL with Cisco Aironet PCM350 WiFi PC Card.
Vintage Wireless, circa 2000

The laptop is of course old enough that it has no built-in Ethernet or WiFi, although it has two PCMCIA/CardBus (at least I believe they’re also functional as CardBus) slots. But the laptop is portable, and it’s in a corner of the house where there’s no Ethernet socket nearby. So WiFi would be really great. But is it even possible to get a DOS laptop on a WiFi network in 2019?

The short answer is “yes, but”. The long answer follows.

Continue reading
Posted in DOS, Networking, Wireless | 20 Comments

More on NX Insanity

This article was supposed to be published about two years ago but got forgotten and ignored until now. It’s not the only such article. Perhaps it will start a new “better published late than never” series.

After looking more closely into the nonsense surrounding the implementation and usage of the NX feature, I ended up with more questions than answers. And it’s definitely not the fault of AMD, the people who first defined and implemented NX.

A big contributor is Microsoft, too. The code to detect and enable NX in Windows 10 (analyzing the original 10240 build here) is, to put it mildly, weird. That is very much at odds with Server 2003 (WRK) which has completely straightforward code to detect and, if present and requested, enable NX.

First let’s consider 64-bit Windows 10 10240 because it’s simpler. Given that NX was introduced in and defined as a non-optional part of the AMD64 architecture, a 64-bit OS should be able to query bit 20 (NX) in CPUID leaf 80000001h, register EDX. But that’s not what Windows 10 does. Continue reading

Posted in AMD, Bugs, Intel, Microsoft | 13 Comments