4 ms·
Lack of memory protection and pre-emptive multitasking allowed for faster performance of NetWare's core file and printer sharing services. Everything ran close
by nradov 4y ago
Lack of memory protection and pre-emptive multitasking allowed for faster performance of NetWare's core file and printer sharing services. Everything ran close to the metal with minimal OS overhead and few context switches. 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.
- gadders 4y agoI think there was also a Lotus Notes server for NLM.
- mobilio 4y agoAlso Gupta SQL for NetWare
- LorenPechtel 4y agoYeah, 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.