Re:Windows Server 2016: End of One Era, Start of Another
by jasode on Thursday September 29, 2016 @10:50AM
(#12605691)
>Netware's difficulties in stably running multiple apps (it was a rock-solid platform for file and print but less stable as an app. server)
Thank you for that reminder. The NLM platform was a fragile architecture.[1] In contrast, both IBM OS/2 and Windows NT of that time period had superior architecture (memory protection, separation of kernel-vs-user address space) for complex applications.
And to add to the other commenter about ease of dev tools -- it definitely was easier to use Visual Basic 3.0 and deploy the app on NT rather than use Netware's NLM SDK that required the C programming language. Even though VB was marketed as a tool for desktop apps, it didn't stop Microsoft shops from deploying VB apps on the server side.
Re:Windows Server 2016: End of One Era, Start of Another
by mjcl on Thursday September 29, 2016 @01:45PM
(#12607243)
Ugh, I remember having to use esc+alt+shift+shift debugger to try and get the server back long enough to down it. And praying that VREPAIR didn't run on restart.
Thank you for that reminder. The NLM platform was a fragile architecture.[1] In contrast, both IBM OS/2 and Windows NT of that time period had superior architecture (memory protection, separation of kernel-vs-user address space) for complex applications.
And to add to the other commenter about ease of dev tools -- it definitely was easier to use Visual Basic 3.0 and deploy the app on NT rather than use Netware's NLM SDK that required the C programming language. Even though VB was marketed as a tool for desktop apps, it didn't stop Microsoft shops from deploying VB apps on the server side.
[1]https://en.wikipedia.org/wiki/NetWare_Loadable_Module#Progra...