Message-Id: <3.0.6.16.19990309201329.30270018@highfiber.com>
X-Sender: raster AT highfiber DOT com
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (16)
Date: Tue, 09 Mar 1999 20:13:29
To: opendos AT delorie DOT com
From: Charles Dye <raster AT highfiber DOT com>
Subject: Re: dr dos fdisk and ms dos
In-Reply-To: <199903090117.UAA01561@escape.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: opendos AT delorie DOT com
X-Mailing-List: opendos AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

"..." <yesss AT escape DOT com> writes:

><< I've seen at least one instance of DR DOS FDISK 
>creating a partition which MS-DOS could not read. [...] 
> 
><<	DR-DOS 7.02 Key Features:
>	* A genuine 100% compatible DOS >>
>
>		--<http://www.calderathin.com/products/drdos/whatsnew.html>
> 
>Clever. DR DOS 7.02 is genuinely 100% compatible 
>with NovDOS 7, maybe? Apparently not MS DOS. ... 
>99% sadder and 1% wiser, 			--Fisher

That's kind of a foolish claim.  Even MS-DOS isn't always 100%
backward compatible with APIs and data structures of earlier
versions of MS-DOS.  True 100% perfect compatibility would
require nothing short of piracy.

To be fair, I think the problem you're having isn't really with
DR DOS per se (the DR DOS kernel,) but with DRI's FDISK (an
associated utility program.)  If I find some free time this week,
I'll try to recreate the problem, using the DR DOS FDISK program
on both DR DOS 7.02 and MS-DOS 6.22.  If I can duplicate it, I'll
write out a nice detailed bug report for Caldera.  Kinda hate to
do that, because I still haven't *paid* for Caldera's release of
DR DOS, but it's a fairly serious problem.

raster AT highfiber DOT com