Every ten minutes my G5 iMac beeps twice 'beep beep' 48 minutes, 58 minutes, 08 minutes etc. I can't place what might be causing this. Anyone got any ideas? I could reboot and hope the process finishes but I'd rather figure it out first 
LastLine said:No iCal open.
Nothing on today. Will advise on volume in 4 minutes time.ITASOR said:iCal doesn't need to be open to run alarms and such.
I would suggest opening iCal and looking under today's date to see if anything is there.
Does adjusting the volume affect the volume of the beep?
wasimyaqoob said:I think you need to enter the CODE
4 8 15 16 23 42
and press "Execute"
Lost fans will know![]()
It's an iSight.yankeefan24 said:security update wouldn't do anything
Good luck!
Look in activity monitor to see if any "helpers" are running.
Also, do you have a rev A, B, or C (iSight) iMac? May have something to do with it (though i doubt it)
yellow said:Do the logs say anything about it?
Is it a loud beep (from a speaker) or is it a soft beep from somewhere deep inside?
Does it happen if you log in as another user (create one)?
LOL. My kids have a toy cell phone that beeps periodically (about every 3 minutes) when left on, drives me nuts trying to find the *&%^)*&# thing in the middle of the night, since it tends to be under the sofa or buried in a pile of other toys.blodwyn said:Are you sure it's not a smoke detector beeping because of low battery?
lol sorry I thought I had.yellow said:Never got an answer on any of these..
LOL, that's the first thing I thought of when I saw the thread title.wasimyaqoob said:I think you need to enter the CODE
4 8 15 16 23 42
and press "Execute"
Lost fans will know![]()
Done and triedEricNau said:LOL, that's the first thing I thought of when I saw the thread title.
Try it in Terminal... but really, Don'tLastLine said:Done and triedSafari didn't much respond to it
![]()
LastLine said:Not sure where to look for logs.
Will check out the console next time I get the beeps.yellow said:Any entry in the logs around the time of the beep. Use Console.app if you're not CLI-versed.
And what about logging in as another user (create one if need be)? This will help determine if the problem is system-wide, or relegated to your normal user.