8 ms·
DOS Ain't Done Til Lotus Won't Run? (2005)
- mmastrac 11y agoWhile this article is dated, a more appropriate reference would be the Windows/DR-DOS kerfuffle: https://en.wikipedia.org/wiki/AARD_code https://en.wikipedia.org/wiki/AARD_code
- berkeleynerd 11y agoThis. It's damning. I was an attentive nerd when this and the Stacker scandal went down and I was outraged. I've been a staunch open source advocate ever since. Microsoft's willingness to sabotage competitor's software is an established fact. "The AARD code was a segment of code in a beta release of Microsoft Windows 3.1 that would determine whether Windows was running on MS-DOS or PC DOS, rather than a competing workalike such as DR-DOS, and would result in a cryptic error message in the latter case." "The rationale for the AARD code came to light when internal memos were released during the United States v. Microsoft antitrust case in 1999. Internal memos released by Microsoft revealed that the specific focus of these tests was DR-DOS. At one point, Microsoft CEO Bill Gates sent a memo to a number of employees, reading "You never sent me a response on the question of what things an app would do that would make it run with MSDOS and not run with DR-DOS. Is there feature [sic] they have that might get in our way?"
- yuhong 11y agoYea, there was a reason why I mentioned DR-DOS when I was discussing the OS/2 2.0 fiasco.
- delonia 11y agoThe author of that article says "I know from personal experience that today [2005] Microsoft takes application compatibility very seriously". And if you want to install Windows on a computer that already has a Linux distribution installed (dual-boot), then Windows will replace the existing boot manager, making it really difficult to boot Linux. That thing used to happen then, and it still happens now (2015).
- cwyers 11y agoThat's not the same thing as application compatibility.
- toast0 11y agoYes, it's annoying, but it's not app compat. And dual-boot is pretty far outside the mainstream, I don't blame them for not building out other boot loader detection and integration. Other bootloaders change frequently, and windows install discs come out maybe every two years. It's better to have consistent behavior (windows install WILL wipe your MBR) than sometimes it works and sometimes it doesn't, and when it doesn't work everyone says it worked for me, etc.
- anonbanker 11y agoit's so far out the mainstream, that people have been doing it regularly for 20 years now. Grub is old enough to attend Junior High. Lilo would be in grad school. they both have windows compatability. Microsoft not reciprocating is evidence of their intent.
- TodPunk 11y ago"People" in this instance is a handful of special edge cases compared to the majority of computer users, even if we're only looking at people that build their own computer, or hell, even just looking at only linux users. Dual booting is a minority. Yes, you CAN do it. Linux has made it easy. Great! But not many DO. Nobody gives hell to every other OS manufacturer that will clobber our current bootloader configs. That means more than OSX, btw.
- eropple 11y agoFreeBSD used to (maybe still does?) clobber the boot loader too. Do they also have mustachios that they evilly twirl?
- krylon 11y agoOn the other hand, Windows runs on 85 - 90 percent of desktop machines, whereas FreeBSD's market share on the desktop is probably below 1%. (This is not a judgement on FreeBSD's quality as a desktop system, I have used it myself for about two years and was very happy with it. But compared to Windows, its market share on the desktop is tiny.) For better or worse, there is a difference between a system used by a tiny minority of people (again: on the desktop) and a system that practically has a monopoly on the (corporate) desktop and that is developed and sold by a company that has a history of anti-competitive behavior. (And to be fair, I get the impression that things have begun to change at Microsoft since Nadella became CEO. But that still does not erase history.)
- digi_owl 11y agoUgh, first time i have really experienced what others have complained about. the text really needs more contrast.
- wnevets 11y agoNo one is going to let facts get in their way of an anti-microsoft circle jerk.
- pjc50 11y agoSee also the "Halloween Memos": http://www.groklaw.net/articlebasic.php?story=20070127202224445 http://www.groklaw.net/articlebasic.php?story=20070127202224...
- digi_owl 11y agoDeity i miss Gorklaw.
- chris_wot 11y agoOh man, Andrew Orlowski? I remember that IE7 story, it was absolutely a beat-up and it just confirmed for me he wasn't much of a reporter!
- shubhamjain 11y agoI recall story of leaked Win2k source code which was filled with profanity and ugly hacks. Surprising fact was how much effort was put in to make software suites work with windows [1]. Although these are ugly hacks but it is a general reminder that people who will buy the software won't see why some obscure bad pointer in MS Office is causing this but something that used to work perfectly fine in previous Windows doesn't work in the current. [1]: http://www.kuro5hin.org/story/2004/2/15/71552/7795 http://www.kuro5hin.org/story/2004/2/15/71552/7795
- anonbanker 11y agothat source code is still available in torrent form. I have a copy somewhere.
- mrspeaker 11y agoIt's so strange you mentioned the Win2K source leak - I was just thinking about this yesterday. I remember at the time there was warnings about it on Slashdot along the lines of "Don't download/read the source code, else you'll be 'tainted' and won't be able to commit code to Open Source projects!" Has it been long enough that I dare peek at it now? ;)
- Analemma_ 11y agoYou're probably fine, unless you ever want to commit to ReactOS. From what I've heard, they're very serious about not letting anyone with exposure to Microsoft's code touch the project, because the clean-room implementation requirements are so strict.
- MichaelGG 11y agoI never contributed to Mono because they didn't allow it if you had MS source code access. That was probably prudent, though should be OK now I'd guess.
- stephengillie 11y agoWhat's funny is Microsoft had some of the same ideology. The belief was nobody could look at Open Source code, or they risked applying the GPL to, like, Windows Vista. The fear was real, if unrealistic.
- deleted 11y ago[deleted]
- rilindo 11y agoI been around IT long enough to know that this statement: "DOS ain't done till Lotus won't run" Was never a common saying. It is actually: "DOS ain't done till Lotus runs" I am not sure how it devolved to the current usage. I suspect it is probably started after the Microsoft-DOJ trials.
- pohl 11y agoI've been in computing since the TRS-80 Model I, and I have only ever heard the "won't run" variant.
- vram22 11y agoThe test could work both ways, if you really think about it: 1. I vaguely remember hearing stuff like that long ago - e.g. "Lotus 1-2-3 used such low-level features of the OS (MS-DOS) and the hardware (PC) - for performance, that it would not work on PC clones that are close but not 100% compatible. 2. It could also have meant: MS-DOS clones and PC clones were different enough (even if just slightly, but in crucial ways) that Lotus would not work on clones.
- fineman 11y agoThat's wrong. I started in that era and the saying was "till Lotus won't run" even back when it was fresh. Microsoft also put misleading error messages in Win3.1 to sabotage DRI's DR DOS product. There are email snippets of the execs planning their strategy. It's their standard operating procedure. They fixed around SimCity because it didn't compete with any of their offerings.
- deleted 11y ago[deleted]
- WorldWideWayne 11y agoLooking at the submitter's background I don't see any professional experience with Microsoft tech. Maybe someone can explain it to me - I don't understand why a guy has avoided Microsoft for his entire career feels the need to dredge up a 10 year old article that talks about events from over 30 years ago. Too much pro-Microsoft news for you? Honestly - what's your interest here?
- mindcrime 11y agoI don't understand why a guy has avoided Microsoft for his entire career feels the need to dredge up a 10 year old article that talks about events from over 30 years ago. Too much pro-Microsoft news for you? Honestly - what's your interest here? A comment[1] somebody made yesterday on the "Twitter apologizes" story reminded me of this. I think it's an important story regardless of your opinion on Microsoft specifically, exactly because it highlights the risk inherent in building something on top of a platform you don't control. I wanted to highlight that that particular bit of wisdom isn't exactly something new. Looking at the submitter's background I don't see any professional experience with Microsoft tech. FWIW, I have spent plenty of time working with Windows and DOS in my life, I just don't highlight it, because it isn't really relevant to what I do now. I also don't mention OS/2, AS/400, RPG, Visual Basic and a laundry list of other things I've worked with that now seem more or less irrelevant. [1]: https://news.ycombinator.com/item?id=10427499 https://news.ycombinator.com/item?id=10427499
- mgkimsal 11y agoyou should highlight some grails. :)
- crgt 11y agoThis quote was mentioned in the recent discussion of Twitter's outreach to developers. I believe the intent of this submission was to share a slice of relevant history with those in the community too young to have lived through it.
- mindcrime 11y ago
- GPGPU 11y agoHowever, post-Jobs Apple is most definitely "OS X Ain't Don't 'til Microsoft Office Won't Run" See: http://www.pcworld.com/article/2988941/software-productivity/office-2016-for-mac-users-plagued-by-crashes-after-upgrading-to-os-x-el-capitan.html http://www.pcworld.com/article/2988941/software-productivity... (It's been fixed over the past few days, with patches from both Microsoft and Apple.)
- protomyth 11y agoI remember the phrase from back in the day, but never really paid attention to it. I do remember testing new PCs with Lotus 1-2-3 and Flight Simulator to prove they were actual compatibles that were going to work with all the software.
- mmahemoff 11y agoThe obligatory Joel post ... "Jon Ross, who wrote the original version of SimCity for Windows 3.x, told me that he accidentally left a bug in SimCity where he read memory that he had just freed. Yep. It worked fine on Windows 3.x, because the memory never went anywhere. Here's the amazing part: On beta versions of Windows 95, SimCity wasn't working in testing. Microsoft tracked down the bug and added specific code to Windows 95 that looks for SimCity. If it finds SimCity running, it runs the memory allocator in a special mode that doesn't free memory right away. That's the kind of obsession with backward compatibility that made people willing to upgrade to Windows 95." http://www.joelonsoftware.com/articles/fog0000000054.html http://www.joelonsoftware.com/articles/fog0000000054.html
- rbanffy 11y agoChanging Windows to work with legacy software is easy to do when you are the unchallenged market leader. That wasn't the case when Lotus running on DOS was something Microsoft (and Lotus) would care about. In that era, Microsoft faced competition from multiple directions. I wouldn't be surprised if there was a decision to sabotage Lotus 123 on some version of DOS, specially if that sabotage could drive the move to Windows and Excel. In all fairness, that Microsoft (they seem to have somewhat improved, as their power diminished) was known for not playing fair (something later demonstrated in court): http://www.theregister.co.uk/1999/11/05/how_ms_played_the_incompatibility/ http://www.theregister.co.uk/1999/11/05/how_ms_played_the_in... So, forgive me if I take this piece of history with a grain of salt. I started in this business at a time Microsoft made a BASIC interpreter and little more and I have observed a lot myself.
- digi_owl 11y agoI think what MS did to take on Lotus was to outdo them by being able to read the file formats perfectly. I seem to recall that after the MS Office file formats was documented as part of a MS-EU settlment, Joel pointed out how the Excel format carried at least two ways to do dates. One of them a replica of how Lotus 123 did it.
- bluedino 11y agoRetrospect is fun; When Transmeta unveiled their new CPU, it was the first time in a long time that a company that was not Intel finally admitted that if you're a CPU, and you want a zillion people to buy you, you gotta run x86 code. This after Hitachi, Motorola, IBM, MIPS, National Semiconductor, and who knows how many other companies deceived themselves into thinking that they had the right to invent a new instruction set. Then along came ARM.
- oblio 11y agoYou mean: > Then along came smartphones. Wasn't ARM a relative minor player before smartphones took over?
- robterrell 11y agoARM is not an overnight success. It's older than Transmeta. ARM is from the 1990's -- it was the chip that powered the Newton.
- dalke 11y agoIf this were true, then it should be easy to reproduce. It's not like the software has disappeared. Which versions of DOS broke compatibility with which versions of Lotus?
- JadeNB 11y agoIs the "Well Known Microsoft Blogger" maybe Raymond Chen (http://blogs.msdn.com/b/oldnewthing http://blogs.msdn.com/b/oldnewthing)? I can't seem to get to the archives on that site, so I don't know how long it's been around, but he published a compilation in 2007, so might already have been blogging in 2005.