[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

kill Limulator competitors ..

From: phila Wed Sep 13 08:40:37 1989
To: celesteb; danbo; greglo; jodys; marcw; mikedr; richab
Subject: RE: Limulator technology: spread it around?
Date: Wed Sep 13 07:31:42 1989

'cause we're big bad microsoft and we LIKE to stomp the daylights out of the little guys.

seriously -- we shouldn't try to crush these guys -- let them upgrade their products to compatible with ours. Give them the info they need. Even say nice things about the good ones. However, I don't want to put any development effort into making it easier for them.

Sender: mikedr Tue Sep 12 20:29:17 1989
To: celesteb; danbo; greglo; jodys; marcw; philba; richab
Subject: RE: Limulator technology: spread it around?
Date: Tue Sep 12 20:26:54 1989

I disagree with Greg. Our goal is not to drive limulator vendors out of business. If someone besides Microsoft is able to delever great functionality to our users, why should we stand in the way of using it? Do you really want to penalize users for using Microsoft software?

Sender: greglo Tue Sep 12 20:22:19 1989
To: celesteb; danbo; greglo; jodys; marcw; mikedr; philba; richab
Subject: RE: Limulator technology: spread it around?
Date: Tue Sep 12 20:20:42 1989

Need a policy on whether we want to allow other people to modify their limulator so that they will work with Win386 just as well as our own EMM386.SYS (i.e. let Win386 take over their open emm handles while we are running, to support ems using memory resident programs). Do we document our interface in the DDK?

One could say that there is no reason that various OEM limulators or 386MAX should not work with us. On the other hand, maybe we want to kill them.

My opinion right now is that there will be no reason for a person not to use EMM386 with Win386 3.0. Sure 386MAX has additional nifty keeno features, like mapping upper memory blocks, but they can't use those features with Win386. All the features they could use with Win386 are already provided by EMS386. So maybe we want to keep thinks simple and tell thm always use EMM386, and throw away the competitors.

http://edge-op.org/iowa/www.iowaconsumercase.org/011607/5000/PX05055.pdf

--

court documents in the case of Comes v Microsoft.

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index