A while ago, the question of antique NetWare OS/2 requesters came up. The oldest known surviving NetWare OS/2 Requester is version 1.2, which is designed to work with OS/2 1.2. There are clear mentions of older requesters supporting OS/2 1.1 and possibly even 1.0, but nothing seems to have survived.
Except something did survive, in an archive called REL102.ZIP–not a terribly obvious name. Said archive contains the “OS/2 Requester Developer’s Release” from April 6, 1988 (a bit over 31 years old as of this writing). This was clearly not the first such release, and the oldest files are from February 1988. Given its vintage, it’s obvious that the Requester was designed to work with OS/2 1.0.
There are several device drivers and a number of OS/2 utilities (SLIST, ATTACH, MAP, etc.); a notable omission is LOGIN (although LOGOUT is included), possibly because LOGIN.EXE normally lives on a NetWare file server.
The documentation is extremely sparse, containing only a brief READ.ME file. There is no
information about installing and configuring the Requester. Fortunately, the documentation for NetWare OS/2 Requester version 1.1 yielded a few good hints.
It is notable that this pre-release Requester includes network drivers which are modular
(separate .SYS driver for each supported network card) but do not use ODI, or at least there is no separate LSL (Link Support Layer). The drivers are at least somewhat configurable using a NWREQ.CFG file (later called NET.CFG), which makes them a precursor to (or an early version of) ODI, which was officially introduced in 1989 with NetWare 386.
There was only one hitch, there was no driver for the network hardware emulated by VirtualBox. And because the driver model was not like any released version of the NetWare Requester for OS/2, the chances of finding a driver for AMD PCnet or NE2100 (leave alone Intel E1000) were zero.
So I sat down and wrote emulation of the venerable (or infamous?) 3Com EtherLink 3C501. For a while I was stumped by the fact that soon after Novell’s OS/2 E3C501.SYS driver loads, it just sits in a loop, not making any progress. After some head scratching I realized that this must have been an intentional stall inserted to make debugging easier (the machine stops when the NIC driver and IPX.SYS are loaded but before network traffic starts, so it’s possible to set breakpoints in interesting places). That sort of functionality (for lack of a better word) reflects the state of the preview OS/2 Requester. It is easy to patch out the loop in the driver, or attach a debugger and skip past it (“ew cs:ip 9090” in the VirtualBox VM debugger, writing two NOP instructions at the current code location to overwrite the “jmp $” instruction).
As shown above, the Novell drivers call themselves “Alpha”, which is accurate.
Does It Work?
Yes, it really does! Mostly. At boot-up, the OS/2 machine finds the nearest NetWare file
server (NetWare version 2.1 or later required, tested with 2.12, 2.15, and 3.12 servers)
and automatically maps the L: drive to SYS:LOGIN, standard for NetWare OS/2 requesters.
What does not work is logging in, because there’s no LOGIN executable for OS/2 (or rather none that would run with this pre-release Requester). It is possible that the problem was that NetWare servers then available had no support for OS/2 clients and no ability to handle OS/2 login scripts. Maybe.
Whatever the reason for the missing LOGIN, the ATTACH command works well enough, and allows accessing file servers and mapping network drives. File sharing works very well even in this early version of the OS/2 Requester, both in OS/2 sessions and in the DOS box.
Basic OS/2 utilities like ATTACH, MAP, SLIST, or WHOAMI work well. There is not much
and none of the later utilities from the version 1.2 NetWare OS/2 Requester or later work due to changes to NWCALLS.DLL.
NetWare utilities in the DOS box do not work and produce odd errors. IPX support appears to exist in the DOS box but isn’t fully functional. Whether it should be working is entirely unclear from the tiny amount of available documentation.
Both OS/2 sessions and the DOS box can receive messages, such those produced by the BROADCAST or SEND commands on the server console, or notifications from a server going down.
How Does It Work?
It appears that the early NetWare OS/2 Requester works very much like old NetWare DOS shells. That’s even reflected in naming, the NWREQ.SYS driver creates a device named NWSHELL$, and the background process NWDAEMON.EXE calls itself the “shell daemon”.
Precisely how the requester works is unclear. OS/2 1.0 did not have an architected mechanism for redirectors to hook into the file operations. On DOS, NetWare shells hooked INT 21h, but on OS/2 the mechanism had to be different. Whatever it was, it was likely similar to what the early versions of the Microsoft LAN Manager workstation and the IBM LAN Server requester used.
Starting with OS/2 1.2, all major OS/2 networking clients (NetWare, LAN Manager/LAN Server) used installable file systems (IFSs) to add network drives, but on OS/2 1.0 and 1.1 it had to be done differently.
In 1988-1989, a networked OS/2 workstation was probably very much a rarity. For that reason alone, reviving the ancient NetWare OS/2 Requester was quite satisfying.
Thinking about it, your emulated 3C501 is probably better than the real one.
For fun, look for old posts by Donald J. Becker on Usenet on the 3C501.
I thought of mentioning Donald Becker’s warnings, but in the end forgot about it. I’m sure what he said was justified in the early 1990s, but of course at that point the 3C501 was a 10-year old design, which wasn’t particularly advanced even when it was new.
Yes, the emulated one is definitely better — the host side can hold incoming packets for a while, so dropped packets aren’t an issue.
From an ancient version of Linux’s Ethernet HOWTO, dated 1993 [ http://linux-distributions.org/docs/howto/Ethernet-HOWTO.txt ]:
“(I have a standing offer: I’ll pay $2 for each 3c501 shipped to me postpaid, but only if you include the BNC ‘T’ connector and the jumpers. $2.50 if you just send the ‘T’, jumpers, and address PROM and promise to destroy the board. -djb)” (Donald Becker)
Donald Becker reeeeally didn’t like those cards 🙂 I am now beginning to wonder if part of the problem was that the 3C501 worked okay in a network consisting of 3C501 cards, which would have been quite common in the early and mid-1980s. In the late 1980s, there was an explosion of PC Ethernet adapters, many of them 16-bit, all of them with bigger buffers or even bus-mastering. LANs were no doubt much bigger, too, and PCs were much faster, capable of generating a lot more traffic. That is quite possibly where the EtherLink could no longer keep up.
And TCP/IP is quite sensitive to packet loss, even 1-2% packet loss has a huge impact on bandwidth.
I just picked up a lot of old 3.5 disks today, one is labeled ‘netware requester for os/2 v1.1 public-2 copyright 1987. Is this of any interest to anyone?
Also in the batch is
Netware requstor for os/2 v1.1 SYSTEM c1987
Netware gateway v2.15 c 1987
Els level ii lan-drv-els c1987
Netware 286 v2.15 lan_drv_180 c1987
Yes, the disks are definitely of interest, especially the OS/2 related ones! So far I have not seen anything of Novell’s requester for OS/2 1.1, but I know it existed.
I need a few days a to give then a slight clean before I attempt to even read them. I uploaded a photo of the discs here https://www.facebook.com/photo/?fbid=10223875975519827&set=pcb.10223876000240445. Where should I then upload the files, in the case that they are readable? thx RM
Only yesterday I discovered this. That may or may not be the same files. Actually the SYSTEM disk could very well be different. BTW the NetWare OS/2 1.1 Requester is from 1989, not 1987 as the copyright on the disks suggests.
As for upload, anything like file.io or mega.co.nz should work. If the files are too big, I’ll tell you how to upload to the OS/2 Museum FTP. But let’s see if the disks a readable first.
@Rm
The diskettes you have might just contain another very interesting and rare thing – the “Netware for Macintosh” product. My information is that the 3.5 inch version of this product for Netware 2.15 came on two diskettes called “GATEWAY” and “LAN_DRV_180”, and you might have just that.
I’ve just started clearing my loft and have a boxful of Netware disks and a box of OS/2 disks too and another crate of disks too (I might still have some pre release stuff too I think but haven’t examined them yet). I must have put them up there at least 20 years ago so they may not be readable even if I can find suitable hardware and software especially as it gets very hot up there in the summer.
I came across 2 5.25″ disks, original Novell P/N 127-010622-001 labelled NETWARE REQUESTER FOR OS/2 (Developers Software) v1.00 DISKETTE 1 and DISKETTE 2
copyright date is 1987
I also have 2 5.25 disks handwritten labelled OS/2 v1.2 REQ Latest 7/6/90 on Novell Labels which I think came from Novell UK
If I remember correctly the OS2 utilities on the server needed to be installed in subdirectories named OS2 under SYS:LOGIN and SYS:PUBLIC. These needed to be on every Netware Server if you had more than one as if your OS/2 Workstation connected to a server without rather than the one you wanted (the workstation would attach to the first server to respond) you would get the DOS login which would not work.
I have 3 original 3.5″ diskettes P/N 127-011608-001 Rev A Netware Requester for OS/2 v1.1 -SYSTEM, PUBLIC-1 and PUBLIC2 as well.
I also found 2 sets of 3.5″ floppy disks copyright Novell 1983-1992 but from IBM and licenced – property of IBM with IBM retaining title
these are 136-001734-001 rev A Workstation Services REQUESTER
136-001735-001 rev A Workstation Utilities-1 OS2UTIL-1
136-001736-001 rev A Workstation Utilities-2 OS2UTIL-2
also I found 2 of the 4 disk 3.5″ disk boxed sets (132-011969-010 A) for the requester and utilities for OS/2 v1.2 which I think were used for a v3.10a server.
I also found a LAN_DRV_180 Diask and a Macintosh System Tools-1 disk!
Do you have any way to read those floppies? Maybe they’re no longer readable, but then again they might be fine. Sounds like you have some quite interesting stuff there, like the ancient OS/2 Requesters. I don’t suppose you also have NetWare 3.0 or 3.1? I’ve never been able to find anything older than 3.11.
I have some of the Macintosh disks too (both the NetWare and the Mac side), but don’t know enough to do anything useful with them.
I have 2 sets of 3.1 0n 3.5″ but no original system-1 disks – all have of the system-1 disk is one copy which is labelled “original sent for 3.11 upgrade”. I’ve got a USB floppy disk reader somewhere when I can find it. I think they are rare as they were sent off for upgrade to 3.11. 3.10 wasn’t that different from 3.11 and not available for long. I’ve got some NetWare 2 stuff I’m trying to catalog I think there may be 2.11, 2.12 and 2.15 but I can’t remember if they needed hardware dongles/cards for copy protection – which I don’t have. I did have old documentation which has now gone. Early Novell 286 software was serialised to cards, or disk controllers in Novells own servers. I’ve also got some Netware interface Tools (NIT Libraries) 5.25″disks for developers. They are for Lattice c v3.0 Borland Turbo C v1.5 and Microsoft C 4.o. I also have later versions of these.
2.12 was the first NetWare without hardware copy protection. Although I doubt the protection would be that hard to defeat with modern tools. NW 2.15 is not that hard to find but I’m not sure I’ve seen a complete 2.12 or 2.11 set.
If people had to sent 3.1 disks back for upgrades, yeah that would explain why it’s so rare (as in no longer exists). Even so, archiving what’s left would be great.
Oh and one word of advice: If the floppy drive starts making weird noises, like scraping or scratching, stop immediately and try to clean the heads, or at least try reading some disk you don’t care about, before trying to read the next valuable floppy.
I’d be able/willing to archive floppies with a Kryoflux, if we could get them shipped to Germany. But not now as I’ll be gone for most of August.