3 ms·
The reason that the first version of Windows NT was called 3.1
- contextfree 5y ago> DoubleSpace contained stolen STAC code is this true? afaik, the lawsuit Stac won was a patent lawsuit over the compression algorithm - I don't think there was actual implementation code involved.
- lproven 5y agoThis is as I understand it. (It's my blog post, BTW.) https://web.archive.org/web/20070509205650/http://www.vaxxine.com/lawyers/articles/stac.html https://web.archive.org/web/20070509205650/http://www.vaxxin... https://www.latimes.com/archives/la-xpm-1994-02-24-fi-26671-story.html https://www.latimes.com/archives/la-xpm-1994-02-24-fi-26671-... https://tedium.co/2018/09/04/disk-compression-stacker-doublespace-history/ https://tedium.co/2018/09/04/disk-compression-stacker-double... https://en.wikipedia.org/wiki/Stac_Electronics#Microsoft_lawsuit https://en.wikipedia.org/wiki/Stac_Electronics#Microsoft_law... MS bullied Central Point Software into providing the backup and antivirus tools, on the basis of CPS being able to sell upgrades and updates. CPS went out of business. https://en.wikipedia.org/wiki/Central_Point_Software https://en.wikipedia.org/wiki/Central_Point_Software MS attempted to bully STAC into providing Stacker for free or cheaply. STAC fought back. Geoff Chappell was involved: https://www.geoffchappell.com/ https://www.geoffchappell.com/ He's the guy that found and published the AARD code MS used to fake Windows 3.1 failing on DR-DOS. https://en.wikipedia.org/wiki/AARD_code https://en.wikipedia.org/wiki/AARD_code As described here: https://www.zapread.com/Post/Detail/7735/aard-code-or-how-bill-gates-finished-off-the-competition/ https://www.zapread.com/Post/Detail/7735/aard-code-or-how-bi... Discussed on HN here: https://news.ycombinator.com/item?id=26526086 https://news.ycombinator.com/item?id=26526086 Especially see this nice little summary: https://news.ycombinator.com/item?id=26529937 https://news.ycombinator.com/item?id=26529937 It would be hard to patent this stuff _that_ narrowly. Various companies sold disk compression; note the whole list here: https://en.wikipedia.org/wiki/Disk_compression#Standalone_software https://en.wikipedia.org/wiki/Disk_compression#Standalone_so... MS saw the code, MS copied it, STAC proved it, MS removed it (MS-DOS 6.21) and then added the functionality back (MS-DOS 6.22) after re-implementing the offending code.
- contextfree 5y agoAll of those links seem to be consistent with my understanding - it was a patent infringement lawsuit and there were no allegations of stolen implementation code?
- lproven 5y agoI think that was simpler the easier thing to convey to code-illiterate lawyers and judges. The quite extensive coverage in the IT press at the time -- pre-WWW -- was that MS demanded the full source from Stac during the "negotiations", and when Stac refused to sign, MS took what it wanted. MS pulled dirty tricks repeatedly in the 1990s. It stole from Stac, it stole from Quicktime. It rewrote Hitachi's license agreement for MS-DOS so that when Hitachi bundled BeOS, it could not make it bootable. It did the same to IBM to make offering a choice of OS/2 difficult to impossible. It lied to Aldus when Aldus started work on a Windows word-processor. It disgracefully pressured AOL to damage Netscape. It lied and covered up efforts to discredit Digital Research. And this stuff needs to be remembered, because it shows the character of the company, which is now giving useless junk out in source code form in its efforts to depict itself as friendly to FOSS. It could not be trusted then, and it can't now.
- glhaynes 5y agoWould love to see supporting evidence for this. That’s a great little tidbit if true.
- lproven 5y agoIf I had some, it wouldn't have been just a blog post. ;-)
- glhaynes 4y agoThank you for writing it up!
- lproven 4y ago:-) It was a pleasure. It worries me that much of the history of our industry is being lost. Not ancient stuff like 1960s mainframes. I mean reasons why X.org is called "X". Or why it matters that you can close a window with Alt-F4 and move it with alt-space, M. Because the result of people forgetting how to use a Win9x clone (by which I mean almost all modern FOSS desktops) is that those desktops are all now less usable for people with low vision, or none, than the same distros were a decade ago. https://scribe.rip/@r.d.t.prater/linux-accessibility-an-unmaintained-mess-8fbf9decaf8a https://scribe.rip/@r.d.t.prater/linux-accessibility-an-unma... And my explanation of what I mean by all modern desktops: https://www.theregister.com/2022/05/17/linux_desktop_feature/ https://www.theregister.com/2022/05/17/linux_desktop_feature...
- paulryanrogers 5y agoThese version as name contortions remind me of the Boeing 373 MAX debacle. All to dodge very deliberate agreement/certification scoping?
- RcouF1uZ4gsC 5y ago>The agreement with Novell only covered “Windows 3.1”. That is why the second, finished, working edition of Windows for Workgroups, a big version with massive changes, was called… Windows for Workgroups 3.11. >And that’s why NT was also called 3.1. Because that way it fell under the Novell agreement. I am calling BS on this story. I was around during when NT 3.1 came out, and even in the the trade magazines there were no mentions of anything like this. It was called NT 3.1 basically to parallel Windows 3.1 In addition, the legal reasoning doesn’t make sense. The law isn’t like source code where clever hacks are just mechanically executed. If you go before a judge and try to tell them that your completely new product is covered by an old agreement because of some clever naming, it is not going to go very well for you. So based on the above, I think this story is wrong.
- rnd0 5y agoI agree. Additionally, if it was true then I'd imagine they'd name Windows95 "windows 3.11/32" or somesuch.
- lproven 5y agoWindows 3.11 was a thing, separate from Windows for Workgroups. https://en.wikipedia.org/wiki/Windows_3.1x#Windows_3.11 https://en.wikipedia.org/wiki/Windows_3.1x#Windows_3.11 But I think this also explains why Windows for Workgroups was also only version 3.1 and 3.11. WfWg 3.11 was a _major_ rewrite, with a whole new 32-bit filesystem (called VFAT and pulled from the WIP Windows Chicago, AKA Windows 95), a 32-bit network stack and more. But they kept the version number. How mysterious, huh?
- lproven 5y agoI wrote it. I also deployed NT 3.1 in production. I was there, too. :-) It was common industry gossip at the time, but no, I can't prove it. I have seen an answer on Quora which said exactly the same thing, for what little it's worth.
- mrlonglong 5y agoSometimes I wish there was a way to vote down articles that appear.