4 ms·
Hmmm ... I had no difficultly imagining that Netware would die a hard death in the early 90s. My memory of the exact details are a bit fuzzy at this remove (I
by hga 16y ago
Hmmm ... I had no difficultly imagining that Netware would die a hard death in the early 90s. My memory of the exact details are a bit fuzzy at this remove (I might be e.g. confounding versions 2 and 3), but its fatal flaw was no memory protection. And as I recall, at least early on, the entire directory structure was in memory (this was an issue for my company in provisioning them for document imaging storage).
So if you wanted to run any 3rd party software on your Netware servers you were making a big bet on both its stability and safety (in not scribbling over the rest of Netware, including most especially whatever memory it was using to keep track of files and directories, no matter whether it had all of the latter in memory or not).
As soon as NT became stable enough (which didn't take very long at all as these things go, that group really had its act together from launch to 3.51 SP1) the value proposition was pretty clear and simple: run Netware for file and print services or run NT for both plus whatever other server software you might want (NDS was never a big issue for the sorts of systems I was involved with so I don't know the story there).
So as I recall the bleeding started before Win2K, although I can see becoming critical with the release of Active Directory.
Of course, all this assumed that Novell wouldn't make the proper strategic decisions in time, but it didn't take too long to realize they just didn't have what it took in that area.
- munchhausen 16y ago> My memory of the exact details are a bit fuzzy at this remove (I might be e.g. confounding versions 2 and 3), but its fatal flaw was no memory protection. You are correct, Netware 3 ran everything in Ring 0, which also made it so fast. Memory protection was added in Netware 4, but you can still opt for running applications in non-protected address space all the way up to Netware 6.5 (latest, and almost certainly the last version).
- hga 16y agoInteresting. Wikipedia claims "In 4.x and earlier versions, NetWare did not support preemption, virtual memory, graphical user interfaces, etc. Processes and services running under the NetWare OS were expected to be cooperative, that is to process a request and return control to the OS in a timely fashion. On the down side, this trust of application processes to manage themselves could lead to a misbehaving application bringing down the server." If true, memory protection without preemptive multitasking is still basically unacceptable (just not something you can base a healthy server ecosystem on; we had enough "fun" of that sort with non-preemptive 16 bit Windows client). The article also notes that TCP/IP was a second class citizen at best until Netware 5.x in October 1998, "during a time when NetWare market share dropped precipitously...." In general it notes Netware's kernel had a big speed advantage which became less important as systems steadily became faster (and I suspect its tunable caching became less useful).