AARD code

An example of the error messages the AARD would produce.

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. This XOR-encrypted, self-modifying, and deliberately obfuscated machine code used a variety of undocumented DOS structures and functions to perform its work, and appeared in the installer, WIN.COM and several other executables in the OS.

The AARD code was originally discovered by Geoff Chappell on 17 April 1992 and then further analyzed and documented in a joint effort with Andrew Schulman.[1][2][3][4] The name was derived from Microsoft programmer Aaron R. Reynolds (1955–2008),[5] who used "AARD" to sign his work; "AARD" was found in the machine code of the installer.[6][7] Microsoft disabled the AARD code for the final release of Windows 3.1, but did not remove it, so that it could have become reactivated later by the change of a single byte in an installed system, thereby constituting a "smoking gun".[4][8]

DR-DOS publisher Digital Research released a patch to enable the AARD tests to pass on its operating system in 1992.[9][10]

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.[11][12] 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?"[10][13] Microsoft Senior Vice President Brad Silverberg later sent another memo, stating: "What the [user] is supposed to do is feel uncomfortable, and when he has bugs, suspect that the problem is DR-DOS and then go out to buy MS-DOS."[10][13]

Following the purchase of DR-DOS by Novell and its renaming to "Novell DOS", Microsoft Co-President Jim Allchin stated in a memo, "If you're going to kill someone there isn't much reason to get all worked up about it and angry. Any discussions beforehand are a waste of time. We need to smile at Novell while we pull the trigger."[10][13]

What had been DR-DOS changed hands again. The new owner, Caldera, Inc., began a lawsuit against Microsoft over the AARD code, Caldera v. Microsoft,[10][14][15][16] which was later settled.[13][17] It was believed that the settlement ran in the order of $150 million,[18] but was revealed in November 2009 with the release of the Settlement Agreement to be $280 million.[19]

See also

References

  1. Chappell, Geoff (2011-11-24) [1999-09-03, 1992-04-17]. "Record of AARD Research". Archived from the original on 2016-11-25. Retrieved 2016-11-25. (Web article published by Geoff Chappell on 3 September 1999 about an e-mail sent to Andrew Schulman on 17 April 1992.)
  2. Chappell, Geoff (2011-11-24) [1999-05-08]. "First Public AARD Details". Archived from the original on 2013-04-02.
  3. Schulman, Andrew (September 1993). "Examining the Windows AARD Detection Code - A serious message--and the code that produced it". Dr. Dobbs Journal. Archived from the original on 10 December 2005. Retrieved 2013-10-05.
  4. 1 2 Schulman, Andrew; Brown, Ralf; Maxey, David; Michels, Raymond J.; Kyle, Jim (1994). Undocumented DOS - A programmer's guide to reserved MS-DOS functions and data structures - expanded to include MS-DOS 6, Novell DOS and Windows 3.1 (2 ed.). Addison Wesley. ISBN 0-201-63287-X. ISBN 978-0-201-63287-3.
  5. "Aaron R. Reynolds". Legacy. Obituary. Seattle Times. Aug 4, 2008. Archived from the original on 4 March 2016.
  6. Dellert, Brian (1998-10-21). "Microsoft Plays Hardball". Eat the State!. 3 (7). Archived from the original on 2008-04-20. Retrieved 2008-08-21.
  7. Pournelle, Jerry (2000-04-01). "The Microsoft Monopoly Debates". Archived from the original on 2008-08-29. Retrieved 2008-08-21.
  8. wired.com: "How a Crypto ‘Backdoor’ Pitted the Tech World Against the NSA" (Zetter) 2013-09-24
  9. Paul, Matthias (2000-09-18). "25 years of DR DOS history - Digital Research DOS history". FreeDOS.org. Archived from the original on 2016-11-25. Retrieved 2013-10-05. See footnote #19 (BDOS 1067h "DR DOS 6.0 Windows 3.1 update, April 1992"; 1992-03, 1992-04-07: "This public DR DOS 6.0 update only includes patches addressing full Windows 3.1 compatibility. There should have been a full "business update" for registered users, shipping a little bit later."), #27 (BDOS 1072h "Novell DOS 7 Panther/Smirnoff BETA 3", 1993-09: "This issue does not have workarounds for Windows 3.1 AARD code."), #29 (BDOS 1072h "Novell DOS 7 German release"; 1994-02-22: "This issue is known to have workarounds for Windows 3.1 AARD code. This should also apply to the earlier English issue.")
  10. 1 2 3 4 5 Susman, Stephen D.; Eskridge III, Charles R.; Southwick, James T.; Susman, Harry P.; Folse III, Parker C.; Palumbo, Ralph H.; Harris, Matt; McCune, Phil; Engel, Lynn M.; Hill, Stephen J.; Tibbitts, Ryan E. (April 1999). "In the United States District Court - District of Utah, Central Division - Caldera, Inc. vs. Microsoft Corporation - Consolidated statement of facts in support of its responses to motions for summary judgement by Microsoft Corporation - Case No. 2:96CV 0645B" (Court document). Caldera Inc. Archived from the original on 3 October 2013. Retrieved 2013-05-12.
  11. Lea, Graham (1999-11-05). "How MS played the incompatibility card against DR-DOS - Real bear-traps, and spurious errors". The Register. Archived from the original on 2016-11-25. Retrieved 2013-09-26.
  12. Bridis, Ted (1998-08-28). "Windows Warning Resurfaces in Suit". Associated Press. Archived from the original on 2016-11-25. Retrieved 2016-11-25.
  13. 1 2 3 4 Goodin, Dan (1999-04-28). "Microsoft emails focus on DR-DOS threat". CNET News. Retrieved 2008-08-21.
  14. Susman, Stephen D.; Eskridge III, Charles R.; Susman, Harry P.; Southwick, James T.; Folse III, Parker C.; Borchers, Timothy K.; Palumbo, Ralph H.; Harris, Matthew R.; Engel, Lynn M.; McCune, Philip S.; Locker, Lawrence C.; Wheeler, Max D.; Hill, Stephen J.; Tibbitts, Ryan E. (May 1999). "In the United States District Court - District of Utah, Central Division - Caldera, Inc. vs. Microsoft Corporation - Case No. 2:96CV 0645B - Caldera, Inc.'s Memorandum in opposition to defendant's motion for partial Summary Judgment on plaintiff's "Technological Tying" claim" (Court document). Caldera Inc. Archived from the original on 3 October 2013. Retrieved 2013-10-05.
  15. Ball, Lyle (1999-04-28). "Caldera submits evidence to counter Microsoft's motions for partial summary judgment" (Press release). Caldera, Inc. Archived from the original on 3 October 2013. Retrieved 2013-10-05.
  16. Wheeler, Max D.; Hill, Stephen J.; Tibbitts, Ryan E.; Susman, Stephen D.; Eskridge III, Charles R.; Paterson, Thomas W.; Dow, Stuart J.; Palumbo, Ralph H.; Folse III, Parker C.; Borchers, Timothy K. "In the United States District Court - District of Utah, Central Division - Caldera, Inc. vs. Microsoft Corporation - Case No. 2:96CV 0645B - First amended complaint and jury demand" (Court document). Tech Law Journal. Archived from the original on 2016-11-25.
  17. Lea, Graham (2000-01-13). "Caldera vs Microsoft - the settlement". BBC News. Archived from the original on 2008-10-05. Retrieved 2008-08-21.
  18. Wilcox, Joe (2000-01-11). "Caldera settlement shows a new side of Microsoft". cnet. Archived from the original on 2016-11-25. Retrieved 2009-01-19.
  19. "Exhibits to Microsoft's Cross Motion for Summary Judgment in Novell WordPerfect Case". Groklaw. 2009-11-23. Retrieved 2011-10-22.

Further reading

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.