From Techrights

Revision as of 14:58, 16 January 2009 by Xyoperr (Talk | contribs)
Jump to: navigation, search


comes: SCP Microsoft 86-dos license agreement ..

This license agreement is made and entered into this 6th day of January, 1981, by and between SEATTLE COMPUTER PRODUCTS INC, a Washington Corporation (hereinafter referred to as SCP), and MICROSOFT, a Washington general partnership (hereinafter referred to as MS)

WHEREAS, MS desires to obtain non-exclusive rights to market the product defined in Paragraph 1, below ..


The product is a single-user disk operating system with utilities for the 8086 microprocessor which has the name "86-DOS" ..


(a) 86-DOS OBJECT CODE TO END USERS: This License Agreement conveys to MS the right to distribute 86-DOS in object code form only to an unlimited number of end users ..

(b) 86-DOS OBJECT CODE TO OEMS (NO PER COPY ROYALTY) .. a royalty of $10,000

(c) 86-DOS OBJECT CODE TO OEMS (WITH PER COPY ROYALTY) .. an initial fee of $1,000 plus a royalty of $25 for each copy of 86-DOS licensed ..

(d) 86-DOS OBJECT SOURCE CODE .. a royalty of $5,000



MS will pay SCP $10,000 upon signing of this agreement Payment of the initial fee described in Paragaph 2(c), above and royalties called for under this Agreement shall be due within 45 days of the date MS invoices their customer for the product for which the initial fee or royalty is due ..

(c) Nothing in this License Agreement shall require MS to identify its customers to SCP ..


> Was that a DOS microsoft bought out and buried? Cos I thought MSDOS was based on QDOS which was a ripoff of CP/M?

86-DOS was a renamed QDOS and yes it was a 'ripoff' of CP/M although not enough of one for Gary Kildall to garner any comfort ...

comes: not letting the big manufacturers off the per system hook ..

From jaramybu Wed Jun 22 13:55:35 1988

To: richardF cc: Joachimk

Revenue for our divisions is not the main issue. If we start letting the big manufacturers off the per system hook, our 100& goal for DOS penetration depends on our success with a larger number of smaller accounts, and threatens our dominance ...

resistance from WIN customers ..

From: D-OEM From: Joachim Date: July 5 - 1988 RE: DOS 4 0 - US Sales Policy


Do not confuse the customer with Windows talk. We will try to "upgrade" NON-WIN customers in Q3 FY89 when WIN3.0 is real. Sell what you have. If there is resistance from WIN customers to take the shell for their 286 and 386 machines. I want to know about it. We might consider to sweeten the deal. But remember, IBM compatibility will mean to carry the shell.


MS is planning to implement an upgrade for MS - packaged goods customers only. This will be done in a low key fashion through advertising and fulfillment with proof of purchase requirements. This is done on a limited basis only and should NOT concern our OEMs. The price for the upgrade package will be approximately $60.

have bambi refuse to run on this alien OS

From: chuckst Sun Sep 29 17:16:46 1991 To: mikedr; philba; scottq Subject: Bambi on DR-DOS 6.0 Date: Sun Sep 29 17:16:39 1991

I tracked down a serious incompatibility with DR-DOS 6 - They don't use the 'normal' device driver interface for > 32M partitions. Instead of setting the regular START SECTOR field to 0ffffh and then using a brand new 32-bit field the way MS-DOS has always done, they simply extend the start sector field by 16 bits. .. I've patched a version of Bambi to work with DRD6, and it seems to run Win 3.1 without difficulty. This same problem may have caused other problems with Win 3.1 and the swapfile under DRD6.
It is possible to make Bambi work, assuming we can come up with a reasonably safe method for detecting DRD6. .. What do you think? Should we test further with the patched Bambi to see if there are any more incompatibilities?

From: philba Mon Sep 30 08:15:02 1991 To: bradsi Cc: davidcol Subject: Bambi on DR-DOS 6.0 Date: Sat, 28 Sep 91 07:57:50 PDT

hey, hey, hey ....
my proposal is to have bambi refuse to run on this alien OS, comments?

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 ...

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

Personal tools
Search entire domain