just wondering if anyone has experienced the same thing that is happening to me and if anyone knows if there's a simple remedy?
basically i'm coding a small MFC application, and everytime i run the app in 'debug' mode... when the program starts up i get an error message box that says 'There is no disk in the drive. Please insert a disk into drive \Device\Harddisk1\DR1.'.... so i hit cancel and it reappears about 4 times... so i press 'cancel' each time... and then the program runs fine.... so i don't really think much about it....
so i build a release version of the app and i run it.... no problems at first, and then i open up a child window and 'BLAM!' i get an application error... it says 'The exception Priveleged instruction. (0xc0000096) occurred in the application at location 0x0012fc88. click ok to terminate etc. etc.'
so i dug around on google and priveleged instruction seems to be linked with accessing ports, or devices... so i figured the two were related... so i run the release again and choose debug.... step through for ages and then eventually i trigger another message that appears and says 'there is no disk in the drive. please insert a disk into drive \Device\Harddisk1\DR1.' same as the one i get in the debug build... so i'm 99% convinced that they are linked...
so has anyone had the same problem or recognise this? i can't think what could possiblly be causing this so any ideas would be really appreciated!!
Don't know what the problem is, but there are a few standard solutions that seem to work for most unexpected problems:
a) Go "rebuild all"
b) Find out what's wrong
c) Delete your code and do it all over again
d) Kill MFC and use normal Windows API. I'm a MFC hater ;)
e) Reinstall your compiler
f) Reinstall windows
g) Reinstall windows, reinstall your compiler, kill MFC and redo your code
h) Format your harddrive and reinstall Windows
i) Buy a new harddrive
j) Buy a new motherboard
k) Buy a new computer
l) All of the above
m) Options (a) and (b), and possibly (c) (least recommended)
hehe... not the most useful reply i've ever had... but pretty funny nonetheless. unfortunately... none of the [sensible] suggestions seem to work... and i put a breakpoint at the very very start of the 'initinstance' call for the application... and guess what? the problem still happens... anyone else got some tips?
nope, nevermind.... its weird.. if irun the debug version through MSDEV i get the error.... if i just run the debug version directly... no error... but the release version still crashes.... i dunno.
Sorry, no clue. Are you accessing files? And could you post some code?