News for hackers. Stuff that matters.
Re:How Novell Netware lost the battle against Windows NT (2013) by andrewstuart on Friday December 30, 2022 @08:40AM (#34184888)
Novell didn’t, or couldn’t, make Netware use task preemption and memory protection.

It’s a startling deficiency that killed its chances of becoming a general purpose server.

Without these things, the Netware server couldn’t be trusted to run independent applications.

I don’t know if this is true but I heard it was Drew Major who made this call, which IMO killed Netware.

Re:How Novell Netware lost the battle against Windows NT (2013) by jacquesm on Friday December 30, 2022 @08:45AM (#34184926)
Desqview had that more or less solved, I wonder why Novell couldn't.
Re:How Novell Netware lost the battle against Windows NT (2013) by mike_hearn on Friday December 30, 2022 @09:01AM (#34185039)
Probably compatibility? Protected memory and pre-emptive multitasking were a notoriously difficult transition. Apple never managed it with classic macOS, and scars from the transition are visible all over the Windows API even decades later.
Re:How Novell Netware lost the battle against Windows NT (2013) by jacquesm on Friday December 30, 2022 @09:42AM (#34185437)
I can see why Apple couldn't do it, the MMU on the Mac wasn't up to the task but on the PC anything post 386 was more than up for it from a technical perspective. Even the 286 machines could do it very well (QnX was originally built on a 16 bit platform).
Re:How Novell Netware lost the battle against Windows NT (2013) by rwmj on Friday December 30, 2022 @10:42AM (#34186029)
Even the awkward segmentation on 8086 was arguably a form of memory protection. Minix on 8086 was surprisingly robust in practice (obviously not in theory) as a rogue 'near' pointer would usually only corrupt the current program.

But on the original topic, yes once you've got a 286+ there's no excuse for your OS not having true memory protection.

Re:How Novell Netware lost the battle against Windows NT (2013) by monocasa on Friday December 30, 2022 @11:59AM (#34186935)
The 68851 was more than up to the task, to say nothing of PowerPC chips.
Re:How Novell Netware lost the battle against Windows NT (2013) by jacquesm on Friday December 30, 2022 @12:03PM (#34186982)
That only really happened from the 68030 onward didn't it? Until the 030 processes needed to be pretty careful not to step on each others address space.
Re:How Novell Netware lost the battle against Windows NT (2013) by monocasa on Friday December 30, 2022 @12:31PM (#34187316)
It started with the 68020 which came out with 68851 support in an Apple product in 1987.

Despite that Mac continued with only partial process protection up until the release of OSX in the early 2000s.

My point is their problem wasn't hardware support, but software compatibility.

Re:How Novell Netware lost the battle against Windows NT (2013) by jacquesm on Friday December 30, 2022 @12:40PM (#34187444)
Hm, ok, I wasn't aware that the 020's already had a full MMU on board, thanks for the correction. Probably they made too many assumptions about being able to mess around in other processes address space to enable it by the time they got it.
Re:How Novell Netware lost the battle against Windows NT (2013) by icedchai on Saturday December 31, 2022 @12:10AM (#34193788)
I think they are incorrect. The original Mac II (68020 machine) didn't ship with a full MMU. It had a socket for the 68851 though, if one wanted to add one. I somehow doubt many people did.

The newer Mac II's (IIx onward) were 68030-based, so they would've had MMUs built in. (They also released the Mac LC later on, which was 68020 based and had no socket for an MMU.)

Re:How Novell Netware lost the battle against Windows NT (2013) by jacquesm on Saturday December 31, 2022 @05:16PM (#34201326)
Did the operating system the machine shipped with know what to do with that MMU or was it ignored if installed and only used by alternative os's?
Re:How Novell Netware lost the battle against Windows NT (2013) by icedchai on Sunday January 01, 2023 @08:28PM (#34213154)
As far as I know, it was ignored until System 7, which added virtual memory support. A/UX (Apple Unix) required it, but that wasn't released until a year or so after the Mac II was initially available.
Re:How Novell Netware lost the battle against Windows NT (2013) by spookthesunset on Friday December 30, 2022 @01:59PM (#34188553)
God I remember those days. The Mac was way late to the party.

Was Win95 preemptive or cooperative? I totally forget. Pretty sure only the NT versions of windows were preemptive.

I recall there was a period of time when you’d run Windows 2000 because it was so much more stable than 98/ME. It worked mostly okay but it didn’t have as good of support for gaming and was pretty late to the party with DirectX support.

Re:How Novell Netware lost the battle against Windows NT (2013) by twoodfin on Friday December 30, 2022 @02:30PM (#34188966)
Win95 was preemptive and with full memory protection.

They obviously had to make compromises for performance and compatibility’s sake that made the long term move to NT essential, but I feel like the Chicago kernel team’s efforts have never (to my knowledge) been well-documented or -appreciated.

Re:How Novell Netware lost the battle against Windows NT (2013) by monocasa on Friday December 30, 2022 @02:47PM (#34189145)
I wouldn't say full memory protection. The shared arena was kind of a "don't touch but the hardware isn't enforcing it" shared 1GB region that all processes had access to.
Re:How Novell Netware lost the battle against Windows NT (2013) by GeekyBear on Friday December 30, 2022 @09:23PM (#34192813)
Definitely not full memory protection. A Win32 program could take down the whole computer.
Re:How Novell Netware lost the battle against Windows NT (2013) by burnte on Friday December 30, 2022 @03:18PM (#34189544)
Win95 was both, it didn't preempt Win12 apps, they'd all run in the same VM space, but 32bit ones could be preempted, but still take down the system. Full protetion eeded the NT kernel.
Re:How Novell Netware lost the battle against Windows NT (2013) by kjs3 on Friday December 30, 2022 @04:33PM (#34190366)
Not that Apple used it, but the even earlier 68010+68451 gave you segmented (not paged) memory protection.
Re:How Novell Netware lost the battle against Windows NT (2013) by Maursault on Friday December 30, 2022 @05:02PM (#34190624)
> software compatibility

A/UX ran with memory protection on the 68020 Mac II in 1988, probably in 1987 in beta also.

Re:How Novell Netware lost the battle against Windows NT (2013) by icedchai on Saturday December 31, 2022 @12:01AM (#34193741)
The Mac II didn't ship with a 68851, however. It was an extra add-on.
Re:How Novell Netware lost the battle against Windows NT (2013) by mrweasel on Friday December 30, 2022 @10:36AM (#34185949)
The topic is briefly touched on in the book: "In search of stupidity". Basically the NetWare kernel wasn't actually developed by Novell, at least not initially, but by a team from a company called Superset. As described you could suggest things to the Superset team, but they wasn't actually someone your could order around, partly because they weren't even employees for many years. This team completely ignore customer demands, and focuses solely on technical improvement that have little real-world tie-in.

The book is "In Search of stupidity" by Merrill R. Chapman, this particular topic is covered on page 173-174.

Re:How Novell Netware lost the battle against Windows NT (2013) by mistrial9 on Friday December 30, 2022 @09:24AM (#34185252)
> genuinely looked back then like Microsoft was going to wipe out everything

except for the thousands of companies, academics and individuals who said NO

Re:How Novell Netware lost the battle against Windows NT (2013) by ghaff on Friday December 30, 2022 @09:37AM (#34185385)
There were some exceptions like Sun but the vast majority of the technology industry absolutely saw Wintel as inevitable whether they liked the idea or not. You may think they were wrong--and they were to a large degree--but it was absolutely the prevailing sentiment at the time.
Re:How Novell Netware lost the battle against Windows NT (2013) by mistrial9 on Friday December 30, 2022 @10:03AM (#34185636)
with all due respect, please re-think your words.. There are millions of active minds, thousands of companies, multiple world markets.. and you reduce the entire globe to "it was thought to be inevitable" ?! do I have to point out the reductio ad absurdum element to that statement? I was there, others here too..
Re:How Novell Netware lost the battle against Windows NT (2013) by browningstreet on Friday December 30, 2022 @10:40AM (#34185991)
In party conversation parlance, I think the sentiment was common. Microsoft was actually subject to a monopoly decree, they invested in Apple to prop up a competitor, they were eating the lunch of workstations, and we were years away from the "Year of the Linux Desktop". Probably many HNers were part of the other side -- running the workstations, installing Linux, excited about Netscape, but Microsoft felt like a Goliath. That they were eventually humbled, now we live with many Goliaths.
Re:How Novell Netware lost the battle against Windows NT (2013) by TheRealDunkirk on Friday December 30, 2022 @10:38AM (#34185971)
It might have been the prevailing sentiment... of all the Microsoft-subsidized trade rags. I just keep thinking how differently "computing" might have evolved in the mid-to-late 90's if other companies had gotten into a spending war with Microsoft for favorable coverage in the press. It's a tradition that Gates continues to this day with his foundation, and which others seem still yet to learn.
Re:How Novell Netware lost the battle against Windows NT (2013) by ghaff on Friday December 30, 2022 @01:14PM (#34187928)
It really didn't have much to do with ad spending. There were a bunch of Unix-oriented trade rags as well.

There was mostly a lot of appetite from both buyers and application vendors to standardize at the operating system level--which Unix in the mid-90s decidedly was not. There was an effort to come up with a multi-vendor Unix, which SCO predictably screwed up in their pre-lawsuit guise. Linux would eventually mature sufficiently and gain business support for this role on servers but that didn't really happen in a major way until the 2000s, accelerated by IBM's endorsement.

Re:How Novell Netware lost the battle against Windows NT (2013) by andrewstuart on Friday December 30, 2022 @07:06PM (#34191716)
Unix looked very much to be on the ropes at the time. It was extremely fragmented and warring with itself. There was no Linux to unify the Unix-like operating systems. Unix was fraught with lawsuits and licensing claims and issues.

I worked in the heart of the corporate world and at this time the sentiment has changed from "you can't get fired buying IBM" to "you can't get fired buying Microsoft".

As @gaff said in this thread said - it has nothing to do with Microsoft ad spend or what the magazines said - it was dead obvious. And were it not for Linux then it would have been a Microsoft world. Remember also it was Microsoft that saved Apple from bankruptcy when jobs returned. I do think that if not Linux then FreePSD would likely have become todays "Linux".

Re:How Novell Netware lost the battle against Windows NT (2013) by ghaff on Friday December 30, 2022 @07:19PM (#34191804)
I did a podcast series on "Was open source inevitable?" a couple years back which ended up more focused on infrastructure and Linux than it probably should have been. [0] But the general conclusion of my guests was that it probably was. (And, yes, some variant of BSD in spite of the legal hangover. Bryan Cantrill argues this specifically.) I do think that absent an open source movement beyond the fringe, Microsoft might have ended up more dominant commercially.

[0] https://bitmason.blogspot.com/2020/06/podcast-was-open-sourc...

Re:How Novell Netware lost the battle against Windows NT (2013) by nl on Friday December 30, 2022 @08:33PM (#34192409)
This is the wrong take. Instead it's the typical low end overtakes the high end that we've seen over and over.

MSDOS on the PC was clearly not suitable for real business apps. Well not for networked ones. Well not for ones that need a server. Well not for GUI apps. Well not for apps that needed more powerful CPUs than those you x86 chips.

Wait.. why are all our customers on Windows NT on Pentiums?

Re:How Novell Netware lost the battle against Windows NT (2013) by ThrowawayR2 on Friday December 30, 2022 @10:05PM (#34193087)
Hard to see how having Novell, Sun Microsystems, HP, IBM, DEC, etc. dipping their hands into our pocketbooks would be any better than Microsoft. None of them would have behaved any better than Microsoft either if they'd been dominant.
Re:How Novell Netware lost the battle against Windows NT (2013) by layer8 on Friday December 30, 2022 @03:39PM (#34189820)
Thousands!
Re:How Novell Netware lost the battle against Windows NT (2013) by efitz on Friday December 30, 2022 @09:48AM (#34185498)
I remember that the beat practice was to reboot your NetWare servers every weekend to work around the leaky NLMs :-)
Re:How Novell Netware lost the battle against Windows NT (2013) by dragonsky on Friday December 30, 2022 @06:50PM (#34191589)
I was running a 2.x server. it was a sad day that I had to reboot and break the 359 day uptime... Amazing system, solid as a rock as long as long as you stuck to file sharing and printer management.
Re:How Novell Netware lost the battle against Windows NT (2013) by nradov on Friday December 30, 2022 @09:51AM (#34185536)
Lack of memory protection and pre-emptive multitasking allowed for faster performance of NetWare's core file and printer sharing services. That was a major selling point back when computers were orders of magnitude slower. But by the time Windows NT launched, even though the file sharing was slower than NetWare it was still good enough for most customers.

One of the major SQL database vendors (maybe Sybase?) actually ported their product to NetWare. But no one bought it due to the problems you stated.

The NetWare development tools were also terrible. Whereas the early Windows NT development tools were actually pretty good. Unlike with NetWare, NT allowed developers to code on a workstation platform and then deploy on a server platform with an identical API which was a huge factor in getting third-party developers onboard.

Re:How Novell Netware lost the battle against Windows NT (2013) by gadders on Friday December 30, 2022 @10:28AM (#34185862)
I think there was also a Lotus Notes server for NLM.
Re:How Novell Netware lost the battle against Windows NT (2013) by mobilio on Friday December 30, 2022 @01:46PM (#34188388)
Also Gupta SQL for NetWare
Re:How Novell Netware lost the battle against Windows NT (2013) by LorenPechtel on Friday December 30, 2022 @07:56PM (#34192047)
Yeah, I made some use of SPX/IPX. Talk about a minefield! System data in user space, if your program crashed just ctrl-alt-del (this was back in the DOS era) because the instant that data block got overwritten the system would crash anyway.

On the other hand why hasn't anyone implemented a recycle bin like they did? (Your whole drive was your recycle bin.) And the users really loved the feature that said "this drawing is locked by <station name>" that I can see no way to implement under any other system.

Re:How Novell Netware lost the battle against Windows NT (2013) by calrain on Friday December 30, 2022 @10:56AM (#34186174)
I started on Netware 2.x but mostly worked with Netware 3.1x.

There was a guy at our office that was extremely proficient with Netware, so much so that if he got physical access to a Netware server, he could press the special 'Admin key sequence' (from memory it was about 4 keys pressed at once on the keyboard) and then he would issue commands to peek into memory and tell you the Admin password. This trick only worked if you had already unlocked the screen console with the Admin account since the server booted, but it showed us very early on how important physical security to even a keyboard was.

I do remember a key fight that happened back then with Netware and Microsoft was how Netware gave you a free 2 user license to a server if that server was only running network services, such as maybe a DHCP server. If you wanted to do file sharing, then you had to buy the appropriate user license.

Microsoft introduced the ability for a Windows NT server to mount a share locally where the contents of that share was data from a Netware server. This way you could get a free 2 user Netware server license, have the NT server use one of those licenses, and then hundreds of people could access the data without Netware being able to technically block it.

I recall (can't find any images on the Internet to back it up) that Microsoft changed the traditional 'hand under a folder' icon for this feature so that if you looked carefully, the hand had it's middle finger extended.

Re:How Novell Netware lost the battle against Windows NT (2013) by mjcl on Friday December 30, 2022 @07:23PM (#34191825)
> special 'Admin key sequence'

R Shift + L Shift + Alt + Esc would trigger the debugger. I would use that to get the console back after btrieve/pervasive.sql ABENDed to unmount volumes before restarting, otherwise NetWare would spend an hour or two running VREPAIR.

Re:How Novell Netware lost the battle against Windows NT (2013) by kQq9oHeAz6wLLS on Friday December 30, 2022 @10:35PM (#34193253)
> showed us very early on how important physical security to even a keyboard was

My HS ran Novell in the 90s, and they learned this lesson after one of my friends (and fellow computer nerd) walked up to one of the 3 severs and typed DISABLE LOGIN (IIRC), thus locking out the math, English, and science teachers.

He spent the rest of the year disallowed from touching any computer in the school, which was interesting for our programming classes. I recall him making life for the librarians difficult by stopping by the library and making them look things up for him.

Re:How Novell Netware lost the battle against Windows NT (2013) by geoffdunbar on Friday December 30, 2022 @11:37AM (#34186643)
I worked at Oracle from 1993-1996, porting the Oracle database to Netware.

> Novell wouldn’t, or couldn’t, make Netware use task preemption and memory protection.

I actually remember being shown a pre-release version that had memory protection, at least. I don't recall if pre-emptive multitasking was included. It was a bit hacky; I think there was a kernel but then most of the OS ran in one process anyways, so perhaps it was a partial step. I think the problem was trying to be backwards compatible while shifting to the new memory model. Their development team was probably pretty small compared to something like Windows NT, so they didn't have the luxury of re-writing everything.

Looking at WikiPedia it is unclear if this upgrade was part of Netware 5 (released in 1998). Your other comment suggests maybe they killed this functionality. I was working for Microsoft by this point anyways. :-)

> There were some third party server applications built for Netware, I think maybe CC:mail server and Lotus Notes, but the memory protection and cooperative multitasking meant they didn’t last long.

We did actually have quite a few customers for the Oracle database on Netware. Mostly companies that were already locked into Netware for other reasons. In retrospect it does seem like madness to run an RDBMS on a server with no pre-emption or memory protection. I think the performance was pretty good, though. :-)

> Also Microsoft was at the height of its powers as a competition killing machine and nothing that stood in its way survived. It really genuinely looked back then like Microsoft was going to wipe out everything and it would be a Microsoft only future. Novell was no exception along with Lotus and Borland and many others.

This 100%. It felt absolutely inevitable that Windows NT was going to completely dominate this space once Microsoft came out with a competitive offering. And we didn't really know that Windows NT was a honest-to-goodness real operating system, instead of something hacked together on top of Windows for Workgroups (and DOS by extension). Of course, no one saw Linux coming at this point.

Re:How Novell Netware lost the battle against Windows NT (2013) by AlbertCory on Friday December 30, 2022 @12:43PM (#34187479)
Did we know each other? (Oracle, 1991-98). I wrote two articles about it on my Substack, https://albertcory50.substack.com).
Re:How Novell Netware lost the battle against Windows NT (2013) by geoffdunbar on Friday December 30, 2022 @02:26PM (#34188903)
I don't remember... but it's long enough ago that that doesn't mean anything. Virtually everyone I knew there left the company around 1996 as the raises weren't keeping up with the market. New hires were making more than everyone else.
Re:How Novell Netware lost the battle against Windows NT (2013) by AlbertCory on Friday December 30, 2022 @03:15PM (#34189502)
if you read my second article: managing then absolutely sucked. You couldn't hire anyone.
Re:How Novell Netware lost the battle against Windows NT (2013) by volkadav on Friday December 30, 2022 @06:04PM (#34191175)
I was a manager there from 2016-2019 and ... it still absolutely sucked. :) Plus ça change, plus c'est la même chose.
Re:How Novell Netware lost the battle against Windows NT (2013) by spamizbad on Friday December 30, 2022 @12:58PM (#34187669)
It seems silly today, but back in the 90s there was a pretty vocal (albeit small) contingent of people who didn’t like protected memory because of its performance impact, software compatibility issues, and reluctance to relearn some performance hacks.

Not just around Netware but on the MacOS side as well.

Re:How Novell Netware lost the battle against Windows NT (2013) by roryirvine on Friday December 30, 2022 @03:14PM (#34189497)
Oh yes - Amiga fans were loudly anti-protected memory, Archimedes / RiscOS users poo-poohed preemptive multi-tasking, and Mac owners claimed that neither was necessary.
Re:How Novell Netware lost the battle against Windows NT (2013) by UniverseHacker on Friday December 30, 2022 @06:49PM (#34191579)
I’m not old enough to remember, but does anyone know if there was ever a vocal anti-OS faction? It would seem logical, since an OS has a lot of overhead vs bare metal apps, and pre task switching OSs don’t offer much that can’t be implemented directly in each program.
Re:How Novell Netware lost the battle against Windows NT (2013) by andrewstuart on Friday December 30, 2022 @07:11PM (#34191742)
No.

The biggest issue for the entire industry at the time was the operating system. Everyone knew we needed real operating systems. Everyone was sick of crashing applications stomping on each other. Servers had just started to become a thing in the corporate world and server applications were just arriving. People were very interested in operating systems and where they were headed.

There wasn't even the concept of "bare metal" at the time. All DOS applications were bare metal. All Windows applications were cooperative multitasking and crashy. People were hungering for better.

Everyone expected that OS/2 was the server operating system that we would all be using. And indeed it probably would have been if Microsoft hadn't killed it. Lots of server applications got ported to OS/2 before Windows killed it stone dead.

Re:How Novell Netware lost the battle against Windows NT (2013) by UniverseHacker on Saturday December 31, 2022 @03:00AM (#34194556)
My question was aimed at much earlier pre-DOS times, wondering if there was resistance to simple non multitasking OSs like DOS vs booting straight into the application. I was around and remember what you are describing.

Edit: for example, when I was in elementary school in the early 90s we had a lab of already antique Apple IIs, with no permanent storage or OS. We would just boot directly into programs on a floppy. Some of the programs themselves had simple features to save and open files.

Re:How Novell Netware lost the battle against Windows NT (2013) by bitwize on Friday December 30, 2022 @08:26PM (#34192346)
There are people in the Amiga fandom who still believe this whole virtual memory fad is going to pass once people realize that AmigaOS EXEC was far more responsive in handling multiple tasks.
Re:How Novell Netware lost the battle against Windows NT (2013) by treeman79 on Friday December 30, 2022 @03:11PM (#34189460)
I don’t fully recall. But I believe passwords for Novell where stored in plaintext. With letters incremented and reversed. So getting admin privileges were crazy easy. All the computer people had admin at my high school. Found out a few years later that lots of grades had been changed for many students. School never caught on.
Re:How Novell Netware lost the battle against Windows NT (2013) by bcrl on Saturday December 31, 2022 @10:07PM (#34203181)
I don't think it was the OS that held NetWare back, rather it was the change in the CPU / memory / network / disk bandwidth balance.

Back when NetWare was being heavily used in the 1980s and early 1990s, 10Mbps ethernet was faster than accessing the local hard disk. ST506 (aka MFM) HDDs only have 5Mbps of bandwidth, and MS-DOS had no build in caching (until later releases -- maybe 5.x? My memory is fuzzy), but Novell NetWare ran in protected mode and had a real disk cache using all available memory on the server.

Once IDE HDDs became popular, the throughput of HDDs quickly began to exceed that of ethernet at the time. Once that happened, there was no benefit to centralizing storage resources on a file server when the local disk was far faster. It also didn't help that Windows NT was difficult to run over a network, but that was just another nail in the coffin.

Re:How Novell Netware lost the battle against Windows NT (2013) by lproven on Tuesday January 03, 2023 @10:21AM (#34232473)
Article author and submitter here.

I think that is a mistaken assumption. You have an effect, and you have a cause, but they are largely unrelated.

No, it didn't have preemption, or memory protection, early on, but that didn't matter because it was a file server and basically only a file server.

The Netware kernel was by and large a single binary running on a single core because that's all CPUs and PCs had then. It only did one job: reading stuff from data, sending it over the network, accepting stuff back and writing it.

It doesn't matter if you don't have memory protection if you only have one task. It doesn't matter if you can't preempt when there is only one thread.

When Netware was at its peak, it was the fastest fileserver there was, by quite a big margin, and that's all that mattered, because the apps executed on the client machines, not on the server.

I put in lots of Netware boxes and all they ran was Netware itself and nothing else. That's what it was for and what it was good at and all that I ever added anywhere was an on-server backup/restore tool, at the most.

Servers were not connected to the internet, and couldn't be, because Netware didn't include or use TCP/IP in the early days. They didn't route anything anywhere. There was nowhere to route it to or from, except other Netware servers on the same LAN.

They didn't have the killer feature you cite because there was no use for it.

I know that there were email servers -- that's where Pegasus got started. I know some people ran databases on it. I dealt with hundreds of clients from dozens of companies at 4-5 different employers and I never saw a single on-server app of any kind. No email, no databases, nothing.

It was a thing but not mainstream.

But when Windows NT came along, suddenly here was an OS that could be a stable file/print server and run apps as well.

You're saying that the world's best-selling bicycle lost out to motorcycles because it didn't have an engine. When it was the best-selling bicycle, motorcycles didn't exist yet. So it's true but it's not the cause. Motorbikes came along and allowed people to do a lot more stuff but bicycles still sell very well... without their engines.

What happened is that at Netware 4.x took over, Internet adoption spread at the same time. Suddenly ordinary small businesses wanted an email server, or a proxy server, and Novell did that -- for a price -- and they wanted it on the same expensive box.

And it wasn't very good at that. Then it became a problem, yes. But NT was doing well by then, it was a bit cheaper, client licenses were a bit cheaper, but more importantly, as others point out, NT didn't enforce client limitations whereas Netware did... and Netware was hard, while NT was easy.

So NT stole Netware's market out from under it.

Around the same time, the poor support for server apps became an issue. As did the difficulty of developing them.

Netware 4 let you push server apps out to a protection ring outside the kernel's Ring 0, but it cost performance. It did support some levels of protection but that was not the key thing.

NT was cheaper, easier, and while slower, ran server apps with aplomb. Even if Netware had been better at it, that wouldn't have saved it. It would still have been harder, meaning it required more skill of admins and developers... and it would still have been more expensive.

So, you're right, it was an issue -- but I think it was not actually a make-it-or-break it issue.

NDS made life hard for small businesses, who didn't want it or need it. An enterprise feature foisted onto SMEs.

And a new competitor, who was better in ways much more important than the ways it was weaker.