neverending beep

Sometimes, e.g. when trying to delete more characters than written
within a Photon shell, the loudspeaker starts to beep and never quits.
How can I quiet this “#¤”# %"# beep? :-/
QNX 6.1.0.

/ Tom

Kevin Stallard wrote:

Just tried it…it worked…

But how does linking /dev/null to /dev/con1 do this? I’d be interested in
knowing.

/dev/null doesn’t respond to the ASCII bell character (7?), by making a
noise whereas /dev/con does.

Rennie

Kevin Stallard wrote:

I’m still confused…

ln -sP is the command used.

So in effect we;re making /dev/null /dev/con1, superseeding devc? But how
is this related to pterm…I mean I thought pterm used pty’s (e.g.
dev/ptyp0 ) not /dev/con. I still don’t understand the plumbing…

I’m not sure what the reasoning is behind why pterm writes to /dev/con1
but I would guess that rather than manhandle the pc hardware itself,
pterm uses devc-con since it already has the code to twiddle the speaker
(i.e. if there were a /dev/pcspkr, I bet pterm would use that instead).

Rennie

…and x86.

Hi Tom,

ln -sP /dev/null /dev/con1

Complete thread you could read there

From: Mujtaba Ali <mujtaba@bitsmart.com>
Newsgroups: qdn.public.qnxrtp.newuser
Subject: Muting PC Speaker and packages.qnx.com
Date: Mon, 15 Oct 2001 01:18:03 -0400
Organization: QNX Developers Network (inn.qnx.com)
Xref: inn.qnx.com qdn.public.qnxrtp.newuser:3125

Eduard.
ed1k at ukr dot net

Tomas Högström <tomas@scandicraft.se> wrote in article <3CEA2E24.32722D4D@scandicraft.se>…

Sometimes, e.g. when trying to delete more characters than written
within a Photon shell, the loudspeaker starts to beep and never quits.
How can I quiet this “#¤”# %"# beep? :-/
QNX 6.1.0.

/ Tom

Just tried it…it worked…

But how does linking /dev/null to /dev/con1 do this? I’d be interested in
knowing.

Kevin

“ed1k” <ed1k@spamerstrap.com> wrote in message
news:01c200cc$9531ea40$106fa8c0@ED1K…

Hi Tom,

ln -sP /dev/null /dev/con1

Complete thread you could read there

From: Mujtaba Ali <> mujtaba@bitsmart.com
Newsgroups: qdn.public.qnxrtp.newuser
Subject: Muting PC Speaker and packages.qnx.com
Date: Mon, 15 Oct 2001 01:18:03 -0400
Organization: QNX Developers Network (inn.qnx.com)
Xref: inn.qnx.com qdn.public.qnxrtp.newuser:3125

Eduard.
ed1k at ukr dot net

Tomas Högström <> tomas@scandicraft.se> > wrote in article
3CEA2E24.32722D4D@scandicraft.se> >…
Sometimes, e.g. when trying to delete more characters than written
within a Photon shell, the loudspeaker starts to beep and never quits.
How can I quiet this “#¤”# %"# beep? :-/
QNX 6.1.0.

/ Tom

I’m still confused…

ln -sP is the command used.

So in effect we;re making /dev/null /dev/con1, superseeding devc? But how
is this related to pterm…I mean I thought pterm used pty’s (e.g.
dev/ptyp0 ) not /dev/con. I still don’t understand the plumbing…

Thanks,

Kevin


“Rennie Allen” <rallen@csical.com> wrote in message
news:3CEA0879.6030908@csical.com

Kevin Stallard wrote:
Just tried it…it worked…

But how does linking /dev/null to /dev/con1 do this? I’d be interested
in
knowing.

/dev/null doesn’t respond to the ASCII bell character (7?), by making a
noise whereas /dev/con does.

Rennie
\

O, I understand now

Kevin

“Rennie Allen” <rallen@csical.com> wrote in message
news:3CEA20B2.4070709@csical.com

Kevin Stallard wrote:
I’m still confused…

ln -sP is the command used.

So in effect we;re making /dev/null /dev/con1, superseeding devc? But
how
is this related to pterm…I mean I thought pterm used pty’s (e.g.
dev/ptyp0 ) not /dev/con. I still don’t understand the plumbing…


I’m not sure what the reasoning is behind why pterm writes to /dev/con1
but I would guess that rather than manhandle the pc hardware itself,
pterm uses devc-con since it already has the code to twiddle the speaker
(i.e. if there were a /dev/pcspkr, I bet pterm would use that instead).

Rennie

Rennie Allen <rallen@csical.com> wrote in article <3CEA20B2.4070709@csical.com>…

(i.e. if there were a /dev/pcspkr, I bet pterm would use that instead).

I’m already thinking about month or two for this driver. I’m willing to write this resource
manager. Are there any ideas about interface of this driver. Should it be just beeping when someone
write ‘bell’ to /dev/pcspkr and devctl interface for tone/durations settings? In this case,
devc-con and Photon might use this device in very easy way just by redirect ‘bell’ to this device.
But for my applications it would be better just write tone (Hz) in this file and speaker then will
generate the tone, and zero or close it to turn it off. Is any plan concerning this matter at QSSL?
I can write the commercial one if you will pay me a penny :wink:

P.S. Also I’m thinking on /dev/rtc/…

Eduard.
ed1k at ukr dot net

“ed1k” <ed1k@spamerstrap.com> wrote in message
news:01c20250$8f86a380$106fa8c0@ED1K…

I can write the commercial one if you will pay me a penny > :wink:

Eduard.

A penny? Really?

I don’t even need it but at that price it’s a bargain. Where do I mail my
penny?
(Oh wait! My cost just jumped to almost 40 cents. Talk about inflation.)

Never mind.

Bill Caroselli (Q-TPS) <QTPS@EarthLink.net> wrote in article <acj504$301$1@inn.qnx.com>…

“ed1k” <> ed1k@spamerstrap.com> > wrote in message
news:01c20250$8f86a380$106fa8c0@ED1K…

I can write the commercial one if you will pay me a penny > :wink:

Eduard.

A penny? Really?

I don’t even need it but at that price it’s a bargain. Where do I mail my
penny?
(Oh wait! My cost just jumped to almost 40 cents. Talk about inflation.)

Never mind.

Bill, you’re very serious man :wink:
I wonder only a thing why QSSL did not write that driver? It’s easy, I believe. And it is not worst
thing (the driver) in embedded apps. Why I should work directly with hardware timer if I want to
pipe by speaker? Embedded apps are not always with SoundBlaster. Also I could just slay that driver
to be pleased by silence at desktop.

P.S. I can tell you my bank’s account only via private mail :wink:

Eduard.
ed1k at ukr dot net

I agree. It should be there. I assume that you are looking for the QNX4
sound() function done as a resource manager and with support for duration.

It shouldn’t be hard to write. But obviously some routine must work
directly with the HW timers.

For the record, most of our customers have us disconnect the damn speaker
more often than not. Then they wonder why the system never notified them
when something went wrong.

“ed1k” <ed1k@spamerstrap.com> wrote in message
news:01c2027a$d0c48180$106fa8c0@ED1K…

Bill Caroselli (Q-TPS) <> QTPS@EarthLink.net> > wrote in article
acj504$301$> 1@inn.qnx.com> >…

“ed1k” <> ed1k@spamerstrap.com> > wrote in message
news:01c20250$8f86a380$106fa8c0@ED1K…

I can write the commercial one if you will pay me a penny > :wink:

Eduard.

A penny? Really?

I don’t even need it but at that price it’s a bargain. Where do I mail
my
penny?
(Oh wait! My cost just jumped to almost 40 cents. Talk about
inflation.)

Never mind.


Bill, you’re very serious man > :wink:
I wonder only a thing why QSSL did not write that driver? It’s easy, I
believe. And it is not worst
thing (the driver) in embedded apps. Why I should work directly with
hardware timer if I want to
pipe by speaker? Embedded apps are not always with SoundBlaster. Also I
could just slay that driver
to be pleased by silence at desktop.

P.S. I can tell you my bank’s account only via private mail > :wink:

Eduard.
ed1k at ukr dot net

Do we really consider this an acceptable solution?

“ed1k” <ed1k@spamerstrap.com> wrote in message
news:01c200cc$9531ea40$106fa8c0@ED1K…

Hi Tom,

ln -sP /dev/null /dev/con1

Complete thread you could read there

From: Mujtaba Ali <> mujtaba@bitsmart.com
Newsgroups: qdn.public.qnxrtp.newuser
Subject: Muting PC Speaker and packages.qnx.com
Date: Mon, 15 Oct 2001 01:18:03 -0400
Organization: QNX Developers Network (inn.qnx.com)
Xref: inn.qnx.com qdn.public.qnxrtp.newuser:3125

Eduard.
ed1k at ukr dot net

Tomas Högström <> tomas@scandicraft.se> > wrote in article
3CEA2E24.32722D4D@scandicraft.se> >…
Sometimes, e.g. when trying to delete more characters than written
within a Photon shell, the loudspeaker starts to beep and never quits.
How can I quiet this “#¤”# %"# beep? :-/
QNX 6.1.0.

/ Tom