X-Apparently-From: Message-ID: <000401c03dea$c62c0870$a28a1004@dbcooper> From: "Patrick Moran" To: References: <20000918 DOT 151710 DOT -577105 DOT 1 DOT domanspc AT juno DOT com> Subject: Re: DRDOS FDISK Date: Fri, 6 Oct 2000 17:15:14 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Reply-To: opendos AT delorie DOT com > When MSDOS ran into this ID on any DRdos versions it would trash your > system to some extent and would not let your windows programs run > properly, > if at all. That was part of the lawsuit, if memory serves me right. This was not the case. It was when you loaded DRDOS EMM386 that caused the problem. When windoze would load, it owuld chack some portion of EMM386 loaded in meory and then refuse to load windoze. Caldera did win that lawsuit (settled out of court) and cost Gates' a pretty penny. At that time it was something like 10% of what MS stock was worth. I have the details of it that Caldera posted on it's site and some other refernces as to what it cost MS. I may even have the complete lawsuit somewhere around here as I believe I downloaded it a long time ago. However, it would not surprize me any if the ID in the boot sector did have some adverse effect with MS crap for software. However, this still has nothing to do with FDISK and my original question. This is strictly a format problem. Thus far, I have not seen a real FDISK problem, other than the DOS 3.3 to DOS 5+ problems which occured with all version of DOS in that era. Pat _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com