06-09-2014 06:42 PM
My program goes through a fairly long initialization process. While the program is initializing hardware (an oscilloscope and a picoammeter) it beeps twice. I figure that there is some sort of non-critical error occurring. I figure that I could use divide and conquer to find where the error is occurring but I was wondering if there is some way to "capture" a beep and turn it into an error message.
Solved! Go to Solution.
06-09-2014 06:51 PM
06-09-2014 08:02 PM
Huge question! does the computer "Beep" or does one of the instruments in the system "Beep?"
06-10-2014 12:36 AM
@oyester wrote:
My program goes through a fairly long initialization process. While the program is initializing hardware (an oscilloscope and a picoammeter) it beeps twice. I figure that there is some sort of non-critical error occurring. I figure that I could use divide and conquer to find where the error is occurring but I was wondering if there is some way to "capture" a beep and turn it into an error message.
but your hardware is working alright?
06-10-2014 12:52 AM
Hey,
maybe the Windows Event Viewer is a good starting point to track down the "beeps".
More information about the Event Viewer here.
01-15-2015 05:52 PM
It's very embarrassing to say this. I checked with my supervisor, and , when certain hardware has been found, a beep notifies us. So actually, if I didn't hear two beeps, something would be wrong. No I didn't write this. The previous guy, who is now my supervisor, wrote it.
01-15-2015 06:29 PM
Thank you for being courageous enough to post the findings here. It takes a lot of guts to admit something like that, and maybe it will help someone else out on down the road. 🙂