Hello All,
I have an eCS v.12MR system that beeps. On on those sounding beeps that raises the hair on your neck every time your hear it. I have not been able to get the timing down, but the beep happens maybe once every 10 minutes and sometimes shorter... I have checked POPUPLOG.OS2 and nothing recent is listed. I have no idea where else to check or what could be causing the beep...
Any insight would be greatly appreciated.
TIA,
-Todd
I have run into such beeps for a variety of unrelated reasons:
(1) failing hard drive (depends on the system BIOS)
(2) errors not generating the type of failure that would be logged to popuplog.os2 (various *nix ports for instance and certain OS/2 apps, that arent crashing, but handling an error and exiting)
(3) certain programs sending a notification to the system speakers (most notable I have run into are UPS utitilities)
(4) certain IM clients generating notification sounds
(5) sounds->speaker drivers generating such sounds via the mobo speaker
(6) some timed routine that is failing for some reason (eCS clock utility?, eCS scheduler utility?)
(7) certain WPS class issues or extension issues will cause this as well (including various settings on xWorkplace/eWorkplace and/or Styler/2 related to changing the priority of certain WPS threads). There is a setting in one or more of them that actually will MAKE your system beep on a priority change for the threads they utilize. When I enabled that, it drove me crazy until I realized that it was changing thread priority all the time on a regular basis, making my system beep like yours regularly.
Thus, the questions that would follow are:
Have you changed any xWorkplace/eWorkplace/Styler2/eStyler settings? If so, check out
#7.
How many beeps on each occurrence? Long or short beep(s)? Are they exactly ten minutes apart (+/- a few seconds) - if so, definitely see
#6 and #7?
Have you tried disabling anything that fits in category
#6?
Does categories
#3-5 apply?
Have you downloaded and tried the smartmon utility (findable on Hobbes) to ensure it is not an error status being detected by the mobo for a hard drive? (category
#1)
Lastly, and usually not important except as it applies to category
#6 and out of resource issues... what version of REXX are you running (CREXX/OREXX)?
That's all I can think of right now - but I just woke up, so I am sure I missed a lot of possibilities.