Geek Answers Handbook

"There is no disk in the disk" in an application that does not require it

Our application is written in C ++ and is used in Windows XP. On some client machines with only C: when an application pops up, an error message appears:

There is no disk in the disk. Insert the disc into drive "D"

If they click Continue or insert a CD (even a blank one!) And click Try Again, everything will be fine.

Someone suggested that this could be due to compilation on the D: drive (our compilation machine uses the D: drive to compile). Has anyone encountered this issue?

+4
source share
5 answers

It would be nice to know what to try to access drive D and fix it. But you can suppress this behavior if you call SetErrorMode using the SEM_FAILCRITICALERRORS flag. It may even help you identify the problem, because the error will be sent directly to the application, rather than being handled by the system dialog.

+5
source

Try compiling in C: and see if an error exists. You can use Process Monitor from www.syinternals.com to find out which file / directory the program is trying to access. Hope this helps!

+3
source

It may be old news, but I got the same error that Delphi 2010 is trying to start now. It turns out that when I turned off my mobile phone, which I was charging, the error disappeared.

As I charge my phone all the time on this computer, I wondered why it all happened all of a sudden. The difference this time was that my phone was connected when I rebooted the computer to install some updates.

After disconnecting the phone (after restarting), the error disappeared, and I connected my phone to charging without any incidents.

Hope this helps someone.

+3
source

Try running the program through Dependency Walker and see if there is any link to D: in the binary dependencies. This may give you a hint about which library (if any) is problematic. Or it may give you nothing, but it is free and very quick to do, so I would recommend it.

+2
source

Oh yes, we had errors like these ... unfortunately, I can’t tell you what the fix is, but it was something completely stupid that I remember. I could still find a comment in our CDebugStackWalk class, so maybe this is due to the unfolding of the stack ... somewhere, somehow ...

0
source

More articles:


All Articles