Forums Bug Reports Pc speaker

mIRC does not play beeps with the pc speaker when i turn that feature on..

"Use pc speaker

Makes mIRC play beeps through your pc speaker.

"

it just plays it on my normal soundcard

Many motherboards with an onboard soundcard don't use the PC speaker at all, they play the sounds meant for the PC speaker through the soundcard (yes, even during boot). Are you sure this isn't the case for yours?

i am sure, and i have used different pcspeaker.exe to test my pcspeaker, and surely the sound comes from the pc speaker, also talked to others, and they could not get it to work, did it work for you?

I can't test it, as my motherboard is one of those.

After testing a bit more, it seems the "Use pc speaker" doesn't make any difference here with respect to the sound produced: it still produces the Windows "Default Beep" sound (Control Panel > Sounds) and not the PC speaker beep.

from memory the pc speaker can be beeped though manipulation of a port in the pc, but i dont think when u beep the speaker in mirc its doing this, rather its some command to the os to do it, and if the os isnt going to do it, it wont do it. So the exe u used might have bypassed the OS all togther maybe.

whatever the "os command" is, mIRC should figure that out and do the right thing, or this is a feature that not will work on any of the new motherboards i guess...

so in my opinion its a bug...

If an app tells the OS (via its API) to play something via the PC Speaker, and it does something different, that's not a bug in the app.

If the OS tells the hardware to play something via the PC Speaker and it doesn't, it's not a bug in the OS.

If the hardware you bought doesn't do what you want it to, then it's probably your fault <evil grin>

Anyway. A couple of things: Beep() is the windows API call to use the PC Speaker; I'd assume (with a large amount of confidence) that's what mIRC uses.
At a command prompt, does "echo ^G" (that's ctrl-g) give a PC speaker beep or not?

the ^G in dos beeps my pc speaker...

OK, as I understand it, that is what the API call Beep() should do, too.

Odd.

This may not work in mIRC, but I remember that a way to produce a beep in some DOS languages was by outputting a certain character to the screen. I think it may have been chr 8.

Just a possible suggestion .

Ctrl-8 doesn't work, but Ctrl-G does (as was mentioned). The trick would be sending that to the command prompt from mIRC. Although Ctrl-G looks like ^G at the command prompt, you can't just send ^G because it won't work, so using the /run command to open CMD and send ^G won't work. And I'm unsure how you send a control+character in the /run command.

I think he actually said chr 8 not ctrl-8, but he was really thinking of chr7 which is ctrl-g anyway.

ps: this is a /run of it chr7 // ctrl-g

//run -n cmd /c echo $chr(7)

Ah, I misread that and I didn't think about getting a $chr value for Ctrl-G.