probably not an issue, but coincidental because something very similar just occured here at work...
have you checked to see if your path environment includes the a:\ drive everytime it seeks to launch an executable file???
...ahh..never mind..that probably is not it..i just checked on my pc here at work.... purposely changed my path variable to look to the a drive first... didnt light up at all....
what about a setting within your bios?? did you recently make any changes to it??
other than that..im going to have to do some research on this..i just genuinely dont know... if anyone else has the answer.....chime in please...
Try Setting the Service called Shell Hardware Detection to Automatic. I had the same thing happening to me, after enabling that service it stopped doing it.
Also Hi EP and people. I found this place again while looking through a oooollllllldddd backup. I have filled over 10TB and was looking at my collection of antiques. Any bids on the 500Mhz Win 95 fix?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.