←back to thread

304 points mooreds | 1 comments | | HN request time: 0.229s | source
Show context
Animats ◴[] No.42167811[source]
Because, when they did it right, in Windows NT 3.51, the users with legacy 16 bit applications screamed. There was a 16-bit DOS compatibility box, but it wasn't bug-compatible with DOS.

Microsoft underestimated the inertia of the applications market. NT 3.51 was fine if you used it as a pure 32-bit operating system. You could even configure it without DOS compatibility. Few did.

replies(3): >>42167845 #>>42168418 #>>42171920 #
badsectoracula ◴[] No.42168418[source]
> when they did it right, in Windows NT 3.51, the users with legacy 16 bit applications screamed

I mean, i don't think there is anything "right" involved from the users' perspective when all they get is the programs they want to use their computer with becoming broken :-P.

In general people do not use computers for the sake of their noise nor OSes for the sake of clicking around (subjectively) pretty bitmaps, they use computers and OSes to run the programs they want, anything beneath the programs are a means not an end.

(and often the programs themselves aren't an end either - though exceptions, like entertainment software/games, do exist - but a means too, after all people don't use -say- Word to click on the (subjectively again) pretty icons, they use it to write documents)

replies(2): >>42168537 #>>42169526 #
1. Animats ◴[] No.42169526[source]
That may have been Dave Cutler's doing. Cutler came from DEC and did the OS for the VAX. (Not UNIX, DEC's own OS). When DEC went from 16 to 32 bits, the VAX was made hardware-capable of booting up in PDP-11 mode. Nobody used that feature, because the result was an overpriced PDP-11. So it seemed reasonable to think that, once the 386 was out, everybody would run 32-bit software on new hardware.

That did not happen. 16-bit applications hung on for a decade.