Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Our application is written in C++ and used on Windows XP. On some client machines with only a C: drive, an error pop ups when the application starts:
There is no disk in the drive. Please insert a disk into drive ‘D’
If they hit ‘Continue’ or insert a CD (even an empty one!) and press ‘Try Again’, everything works fine.
Someone suggested that this might be related to compiling on drive D: (our build machine uses drive D: for compilation). Has anyone encountered this issue?
It would certainly be a good idea to find out what’s trying to access the D drive and fix it. But it’s possible to suppress this behaviour, if desired, with a call to SetErrorMode using the SEM_FAILCRITICALERRORS flag. It may even help you to identify the problem, because the error will be sent directly to the application instead of being handled with a system dialog.