4 ms·
If anyone wants an insider's view, here's a Usenet post from one of the early Microsoft employees, Gordon Letwin: http://gunkies.org/wiki/Gordon_Letwin_OS/2_u
by melling 13y ago
If anyone wants an insider's view, here's a Usenet post from one of the early Microsoft employees, Gordon Letwin:
http://gunkies.org/wiki/Gordon_Letwin_OS/2_usenet_post http://gunkies.org/wiki/Gordon_Letwin_OS/2_usenet_post
Somewhere in the Usenet archive is Gordon trolling the OS/2 users for weeks (or months?) on end. I can't remember the exact details, but he had a bet with several people that Windows would have multitasking, or that OS/2 wouldn't have some sort of multitasking before Windows. The bet was to fly the winner to any city of their choice and buy them dinner.
The discussions were quite heated and it was particulary memorable because he was one of the first 12 employees at Microsoft.
http://en.wikipedia.org/wiki/Gordon_Letwin http://en.wikipedia.org/wiki/Gordon_Letwin
- deleted 13y ago[deleted]
- twoodfin 13y agoLetwin was also the guy for OS/2 on the Microsoft side while the alliance lasted. His Inside OS/2 is a detailed account of trying to squeeze a real multitasking, protected memory OS into a '286: http://www.amazon.com/Inside-OS-2-Gordon-Letwin/dp/1556151179 http://www.amazon.com/Inside-OS-2-Gordon-Letwin/dp/155615117... The cover photo is also classic.
- jonah 13y ago"Foreword by Bill Gates"
- adamnemecek 13y agoThe photo should be in a National Geographic captioned "A Unix beard in his natural habitat".
- sliverstorm 13y agoIn its natural habitat. A Unix beard is genderless; it merely seems to exhibit a preference for male hosts.
- peatmoss 13y agoI thought Unix greybeards were like Tolkien's dwarves in exhibiting little sex-based dimorphism.
- yuhong 13y agoAs I mentioned in a comment on a os2museum blog post, keep in mind Letwin left in 1993, before MS did many of the unethical attacks against OS/2 that is not mentioned in this article.
- wglb 13y agoHowever, I got the impression he was asked to leave as a result of his confrontational behavior.
- npsimons 13y agoSo, did Letwin ever pay up?
- melling 13y agoI think Letwin turned out to be right. I can't find the Usenet thread. It was from the early 1990's.
- npsimons 13y agoWas he though? This is someone speaking from the outside, with fuzzy memories of release dates, but I'm pretty sure Windows (excepting NT) didn't have preemptive multitasking until 2000, and I think OS/2 was out before NT. I still have fond memories from the late 90's of a friend who adminned Windows and had a CD for when someone would set the password on the screensaver on the Windows boxes: the CD had an autorun that would pluck the password out of the registry and put it in the clipboard so you could paste it into the password box (no memory protection). That and the memory shotgunner: a program that would write random data to random memory addresses. No Windows machine would stay up for more than about 5 minutes running that, while Linux would kill the program and merrily continue on its way. Or the packet of doom to lock up Windows remotely.
- dmethvin 13y agoWin95 had preemptive multitasking. Win 3.1 had cooperative multitasking. The "multiuser" aspect of Win95 wasn't secure at all, it was more for letting multiple users have separated settings (e.g., browser bookmarks). However, even that often failed because software would assume a single user and store all the settings in a common location. Since there was no real security in FAT32 filesystems that was pretty easy to do.
- npsimons 13y agoI may be splitting hairs at this point, but I think we're both partly right; according to Wikipedia (https://en.wikipedia.org/wiki/Preemption_%28computing%29 https://en.wikipedia.org/wiki/Preemption_%28computing%29), Windows 95, 98 and ME had preemptive multitasking for 32 bit programs, but not 16 bit (which would have been the majority at the time of release of Win95). My confusion may come from remembering running multiple DOS and Windows programs at the same time in OS/2 with nary a hiccup and being able to tweak settings (such as RAM allotments).