Q64026: CodeView Crashes in DOS on "Drive Not Ready" Error

Article: Q64026
Product(s): See article
Version(s): 3.00
Operating System(s): MS-DOS
Keyword(s): ENDUSER | buglist3.00 | mspl13_basic
Last Modified: 25-JUL-1990

CodeView version 3.00 may hang after encountering a "Drive Not Ready"
error. This error may occur if a file is opened on Drive A and a disk
is not in the drive.

To reproduce this problem, compile the following program with CodeView
options (cl /Zi /Od):

   main () {
     FILE *fp;
     fp = fopen("a:\readme.doc","r");
   }

If you run the program in CodeView version 3.00 without a disk in
Drive A and press F5 to run the program, the following error will
appear:

   Not ready reading drive A
   Abort, Retry, Fail?

Regardless of what is typed, the machine will hang and you must do a
cold reboot to remedy the crash.

Note: CodeView versions 2.20 and 2.30 do not hang the machine if the
above steps are executed. The fopen() just returns a NULL. OS/2 also
handles the error correctly in versions 2.20, 2.30, and 3.00 of
CodeView.

Microsoft has confirmed this to be a problem with CodeView version
3.00. We are researching this problem and will post new information
here as it becomes available.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1986-2002.