Message-Id: <199705231508.LAA26131@delorie.com> Date: Fri, 23 May 1997 10:02:19 -0500 From: "Jonathan E. Brickman" Reply-To: "Jonathan E. Brickman" To: opendos AT delorie DOT com Subject: Re: OpenDOS announcement... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Precedence: bulk > That would be very useful -- a > master list of shortcomings vs. > "the industry-standard DOSes." > I agree with Jonathan that making > OD compatible with and *at least* > as good performance-wise is a top > priority and ought to be taken > care of before folks start coding > up new features. Honestly, I don't really think that full compatibility is necessary, given that the definition of "full compatibility" is not exactly firm. Here are things I consider vital for OpenDOS credibility: 1. Take the "fully compatible" allegation off the Caldera web sites right now. Leave it off. Replace it with a list of specific things that OD will actually do buglessly right now. 2. Fix the installation procedure. 3. Make a list of memory-related configuration solutions. Post it. 4. Make a list of incompatible drivers, driver types, rough guesses at untested driver types, and suggested substitutes. Post it. 5. Don't worry about Windows 3.1x compatibility for now. Get the latest versions of WordPerfect for DOS and Arachne and other vital apps to work well, no matter what it takes. 6. Then work on rewriting source to eliminate the needed hacks et cetera. Until items 1 through 3 above, at a minimum, are completed, I will continue to have strong reason to recommend against use of OpenDOS. Jonathan E. Brickman River City Computing, Inc. (913) 232-6663 http://www.cjnetworks.com/~rivercity brickman AT cjnetworks DOT com It seems to me that men usually think more about carburetors, and women think more about doors. I think the world needs really good carburetors...and really good doors.