• Please review our updated Terms and Rules here

Novell Netware

GeoffB17

Veteran Member
Joined
Jun 8, 2016
Messages
578
Location
Guisborough, England
Any interest here in 'vintage' software?

When I started with computers way back about 1990, we used to install Novell Netware systems as well as do software for them. I certainly remember installing all the software for Novell 2.2, and I think I even did a couple of 3.1 (or was it 3.11) as well. The 2.2 was fun, working your way through a pile of 360k floppies, often going back and forth with the specific disks (OSEXE?) where the installed copy of the OS was being created. And keeping trck that you had the right drivers for the network card you were using.

I kept hold of some of the Btrieve bits, I always longed to do something with Btrieve, but never did.

Why do I mention this?


Just yesterday, got a call from an old client, with a 2.2 network (running a Clipper S87 system that we wrote/installed. The connection to the server had failed.

Oh, I thought, this could be 'interesting'. The server is a somewhat ancient Packard Bell, I think a 386.

Anyway, I went there today, and Oh, as soon as I booted the w/s, I got the logon prompt and everything seemed to be fine. I checked the files, checked other markers, and all AOK. So, what caused the problem, no sign. Maybe just a funny contact on the network cable (co-ax, with the T-pieces on the back of the PCs and 'terminators' at each end of the cable.

Boss on the customer business may be thinking of 'upgrading', I think I should place a claim for the old bits. They should have the full set of disks for 2.2, with manuals etc.

Anyway, this system installed prob early 1990s, server barely touched since, and still chugging. Occasional problems with the wiring, but this does NOT affect the server, and usually a little jiggle of the cable connectors restores the link.

Oh, my older 486sx PX still has the old network card (with the coax connector) in, maybe even the original card drivers are there to as the machine was once connected to a novell network. Long ago (late 90s ?). All I need is a working server to connect to??

Anyone else still interested in this sort of software.

Geoff Barnard
 
Yeah do score the old software if you can GeoffB17
I know of one chap who has netware running on his old PCs.
I had a 10Base2(Co-axe) three system home network for some time. It wasn't netware but tcp/ip though.
 
Last edited:
Back in '93 to '94 I probably installed more Netware 3.11 and 3.12 servers than I care to remember, most of them 486 DX/50's since the higher bus speed paid better dividends... I held a CNE, was qualified to teach the CNE and CNA courses... My specialty was getting Win 3.1 to remote boot over the LAN on diskless workstations.

...and you know what the scariest part of that is?

I probably don't remember a damned thing about it. In '94 I quit in a huff (I do that) and never dealt with Netware any time after that.

Makes me wonder how long it would take for me to pick it up again. I've kind of got the same thing going on with Paradox. I still support an accounting package I wrote in Paradox ages ago, but said "support" typically involves just tweaking DOSBox to run it for the clients on a modern machine... I poked my head into the codebase the other day and just drew a total blank. I apparently don't remember a blasted thing about PAL.
 
I'll a bit of bragging... :) I worked at the time too with NetWare (having originally but my teeth on 3Com gear). We installed a bunch of NetWare on NetFrame 386 towers. They where really much more like minis with redundant everything and $100K price tags. Those were fun...
 
I spent a week in class in the later 80's to become an Novell Authorized Reseller, which I kept until Novell decided to require that resellers had a storefront, and at that time I was working from my house. It was fun while it lasted! I believe I have an old server around here that has Novell 2.2 installed on it, it may even work, hasn't been powered on for decades tho.
 
This is a Micro Five 286 Novell Server of mine:

attachment.php
 
mitsubishi Apricot

mitsubishi Apricot

Back in '93 to '94 I probably installed more Netware 3.11 and 3.12 servers than I care to remember, most of them 486 DX/50's since the higher bus speed paid better dividends... I held a CNE, was qualified to teach the CNE and CNA courses... My specialty was getting Win 3.1 to remote boot over the LAN on diskless workstations.

...and you know what the scariest part of that is?

I probably don't remember a damned thing about it. In '94 I quit in a huff (I do that) and never dealt with Netware any time after that.

Makes me wonder how long it would take for me to pick it up again. I've kind of got the same thing going on with Paradox. I still support an accounting package I wrote in Paradox ages ago, but said "support" typically involves just tweaking DOSBox to run it for the clients on a modern machine... I poked my head into the codebase the other day and just drew a total blank. I apparently don't remember a blasted thing about PAL.

Hi, did any of you guys work on Mitsubishi Apricot's back in the day(1990 ish)? they ran on Netware.
 
I remember learning Novell back in the mid 90's when I was attending TAFE here in Australia (not sure what the US equivalent for TAFE is perhaps a Technical College?). All on a 10base2 network if I recall correctly.

Probably couldn't remember a damn thing if I played around with it now but tempted to at the moment as I'm currently playing around networking on my XT.
 
Netware 286 and 386 work quite well with VMware :) I've created and booted servers and connected via DOS virtual machines... all using IPX protocol. So good way to relive it.
 
I used to have the NETAD title for 3.20 in the mid of the 90's. About 10 years ago I threw away my Netware 3.20 student kit.

At that time, there were many little system houses selling strange self built machines as netware servers. A friend of mine sold servers which did RAID 1 on ESDI harddisk and SCSI harddisk. His argumentation was, that it's two different technologies who can't have the same error. But in case of error who decides if the content of the one or other drive is wrong...?
 
Back
Top