28 Jun
2001
28 Jun
'01
12:47 p.m.
In a message dated 6/28/01 7:42:48 PM Eastern Daylight Time,
pechter(a)bg-tc-ppp1667.monmouth.com writes:
<< > Bill Pechter skrev:
Not if you have to use the GUI to admin it and reboot to change
network addresses.
I'd liked a cross between OS/2 and VAX/VMS...
maybe with FreeBSD
thrown in.
Isn't that Windows NT? Always liked OS/2 and always will. IBM was
screwed by M$ who kept
changing Win32 and keeping new apps from running on OS/2.
So what? OS/2 is OS/2 and Windows is Windows. You can't just rely on some
other OS vendor to supply you with the right API and applications.
But M$ promised if you code to Win32S it would be
portable to OS/2,
Win3.1 and Win95/NT and kept changing the DLLs to break it.
.The only problem in OS/2 was if the Workplace Shell threads blocked and
locked up you'd lose the desktop... but all the
server services
like network kept going.
Getting a prompt and login from Telnet was possible on
OS/2 when it
wasn't standard in NT.
The ftp and telnet servers made OS/2 pretty compatible
to
FreeBSD/Linux/Unix in what it could do on a lan. >>
OS/2 v.3 had a single input queue which caused the problem where the desktop
would not respond but the system will still chug along just fine. If you had
a multithreaded foreground app that quit working, sometimes there was no way
to break of it. Supposedly that was fixed in Warp 4 but i've still had it
quit on me. Installing that program called Watchcat has saved me several
times from rebooting.
--
DB Young Team OS/2
old computers, hot rod pinto and more at:
www.nothingtodo.org