From Techrights

Revision as of 17:07, 16 January 2009 by Schestowitz (Talk | contribs)
Jump to: navigation, search


display alien Dos message function

if(!Verify_DOS() DisplayAlienDosMessage();


near DisplayAlienDosMessage(void)
print(9,TAB,"WARNING: Microsoft QuickPascal has been tested for use");
print(lO,TAB,"only with the MS-DOS and PC-DOS operating systems.");
print(12,TAB,"Your use of this product with another operating system");
print(13,TAB,"may void valuable warranty protection provided by");
print(14,TAB,"Microsoft on QuickPascal.");
print(16,TAB,"...Press any key to continue");

feel uncomfortable using DR-DOS

To: davidcol Subject: RE: message Date: Mon, 10 Feb 92 08:51:10 PST

what the guy is supposed to do is feel uncomfortable, and when he has bugs, suspect that the problem is dr-dos and then go out and buy ms-dos, or decide not to take the risk for the other machines he has to buy for in the office.


From bradsi; Mon Feb 10 10:50:05 1992 To: steveb Subject: Re: the message Date: Mon, 10 Feb 92 10:50:05 PST

i am saying that we should either:
b) put a kind gentle message in setup. like an incompatible tsr message, but not everytime the user starts windows .. the most sensible thing from a development standpoint is to continue to build dependencies on msdos into windows.

aard: how to explain the encrypted code ..

From: darbyw To: Bradsi Cc: darbyw Subject: FW: DOS Practices Date: Wednedsday, September 01, 1993 8:55 AM

Thanks,Brad, I don't think this addresses the issue of our encrypting the code .. how do I explain that. I've got everything else programmed in my response.


From: bradsi


.. we do not test on other systems nor can we verify the stability of windows running on anything other than msdos ..

'You never sent me a response on what things an app would do that would make it run with MS-DOS and not run with DR-DOS'
"the approach that ralph and I have discussed is to use a vxd to 'extend' dos by patching it .. We would not patch unknown OSs"

purpose of the AARD code

January 12 2007

RONALD ALEPIN, recalled as a witness, having been previously duly sworn, testified as follows:



Q. When we broke yesterday we were discussing the AARD code. And yesterday morning Mr. Holley asked you if there was a malfunction in the AARD code. Do you recall that question?

A. I recall a question concerning malfunctioning and the AARD code.

Q. And your response was no, there was no malfunction; right?

A. That's correct.

Q. And you testified that there wasn't a real error. It was a false error; right?

A. That's correct.

Q. Okay. By false error, do you mean that it was not true?

A. Yes.

Q. Now, have you seen evidence in the record that leads you to believe that Microsoft knew that the AARD code was not a true error?

A. Yes.

Q. What did you see?

A. Well, there is a discussion of -- in the record concerning what the purpose was for the code. It was to detect a non-Microsoft operating system, and that in and of itself is -- was not an error. And the purpose for installing the code was not to detect errors, but to detect a different operating system ...

== explanation for the AARD Code ..

From aaronr Mon Aug 2 11:35:34 1993 X-MSMail-Message-ID: 15DF233B X-MSMail-Conversation: 15DF233B X-MSMail-WiseRemark: Microsoft Mail - 3.0.729 From Aaron Reynolds <> To: bradsi Date: Mon, 2 Aug 93 11:32:50 PDT Subject: AARD drivel

Microsoft does not test windows on anything other than Microsoft's MS-DOS .. In order to be fair and up front with our windows users it might be a good idea to disclose to them in a timely fashion, before they might encounter some possibly data corrupting problem, that they were running the windows product on a non-Microsoft MS-DOS on which Microsoft had not done any testing
Mr. Schulman goes on at length about how this code is "obfuscated and encrypted" and that this is somehow an indicating of malicious intent .. That is likely to be targeted by the "work a likes", which defeats the code's purpose to disclose to the user that windows is being run on a DOS that Microsoft has not tested on
All we were interested in doing was disclosing to users in a timely fashion that they were running the windows 3.10 product on something on which Microsoft had not done any testing

You never sent me a response on the question of what things an app [application] would do that would make it run with MSDOS and not run with DR-DOS," BG circa 1989 ..

those rabid DR-dogs ..

From: tomle Fri Sep 28 06:40:31 1990 To: bradsi; ericst; markche; mikedr; philba Cc: tomle Subject: What would you be doing now

If you were one of those those rabid DR-dogsin the UK what would you be doing about now. .. If I were DR development, I would be hard at work on a release 5.1 that would match everything we have in Dos 5.0 plus .. Our official strategy implies we top them with Dos 5, which we will do, and then we're in the drivers seat ..

comes v Microsoft

problems with rom-DRDOS 6.0 and win ..

From: bradsi Sun Jan 12 16:04:17 1992 Subject: Re: FW: problems with rom-DRDOS 6.0 and win ..

ok, post a nice SOL msg. bottom line is that he needs msdos- something that is compatible with windows

comes v microsoft

MS on attacking the counterfeiting of MS-DOS ..

From: Jeff Alder Date: September 4, 1991


In order to attack the counterfeiting of MS-DOS and increase the penetration in the naked PC market. THIN-DOS will be introduced in early November ..



A competitive defense against DR_DOS provided by 2-3 year license agreements

A substantial decrease in the profit incentive and oppurtunities for counterfeiters

comes v microsoft


"You never sent me a response on the question of what things an [application] would do that would make it run with MS-DOS and not run with DR-DOS," Bill Gates wrote in 1988. His earlier email? "I am not looking for something they cant get around. I am looking for something their current binary fails on."

Curiously enough PLEX0874_0001.PDF don't contain that quote ?

I do believe they moved the entire directory up a few IP addresses so as they could lose it. I forget which one, but if you go to one of their websites and enter ../districts/fourth/MicrosoftTrial/Plaintiff/ you'll get the contents.

Personal tools
Search entire domain