QNX4 Updates System Updated!

Hi R B,

Thanks for the help.

The only ALSA executables I have are aplay/arecord, mpg123, and the deva-*
drivers.

Do I need to download something else from the ALSA site, and if so, will the
current stuff compile and run under QNX4?

I should say that I am simultaneously brand-new to QNX and audio
programming. I don’t even know if the machine I have is configured to run
Photon…no one uses it here.

For me, getting arecord to work is just a necessary first step. After that,
I need to write custom code to do recording as part of a much larger
program/project.

Thanks,
Mark

“R B Adler” <no@mail.com> wrote in message news:8tvekv$fhq$1@inn.qnx.com

Mark,

I use a few different things. One I use is an app that I got from QNX. I
don’t remember where or who I got it from, but it’s very useful (although
I
don’t use a mouse in QNX, and the whole thing is graphical, so I have to
use
the TAB key a lot and see what it does).

Another thing I use is an application that I wrote to change the mixers.
I
set it up to use the ALSA controls for the mixer and set whichever
channels
I want. If you have no ALSA experience, it’s not too difficult to figure
out. I might be able to share some of my stuff with you to get you
started.
I typically disable most of the channels, enable the ones I want to listen
to or record from, set the levels, and that’s about it. arecord works
from
there.

If you need help with ALSA stuff, just respond and I’ll see what I can do.

R B Adler


“Mark Johnson” <> nooz@my-deja.com> > wrote in message
news:8tv1so$3aa$> 1@inn.qnx.com> …
Hi RB,

Thanks for the help. I think I am getting close.

I have tried what you suggested (arecord -w -M -t10 test.wav) with an SB
64
card (ES1373 chipset, audiopci driver) , and I get a wav file containing
exactly 10 seconds of silence. I have used mic input and line input…in
both cases, silence.

I don’t know anything about setting the proper mixer values…can you
clue
me in? What command-line program can I use to do that?

Thanks,
Mark

“R B Adler” <> no@mail.com> > wrote in message
news:8tuv9s$128$> 1@inn.qnx.com> …
Mark,
I’ve used arecord before, and this is what I’ve found:

  • As you probably know, you need to set the proper mixer values for
    recording, so if you use a mic, you have to have that as the selected
    record
    input.
  • I like to use the M option (the m option can be used too). It’s
    important
    to specify the quality of the recording, or it doesn’t know how to
    react.
  • The ‘t’ flag doesn’t have a space after it (at least in my
    experience,
    I
    didn’t put one in and it worked fine).

I would run “arecord -w -M -t10 test.wav” and it would just use
whichever
mixer setting is selected for recording.

Hope this helps,
R B Adler

“Mark Johnson” <> nooz@my-deja.com> > wrote in message
news:8tsif8$spc$> 1@inn.qnx.com> …
Ok, I now have a suitable sound card working with aplay under QNX4.
It
is
a
SoundBlaster Live! Value, model# CT4830 with the EMU10K1 chip set.

Playback works fine with aplay, though I haven’t comprehensively
tested
this
with many file types.

However, I can’t record anything. I’m hoping that I am just missing
some
option on arecord.

If I try “arecord -w -t 10 test.wav” (attempting to record a 10
second
WAV
file) and then speak into the microphone, it will print out two
informative
status lines, create a “test.wav” file 44 bytes long, and then do
nothing.
It will not stop after 10 seconds.

When I hit CNTL-C, it prints

Got a signal: 2
Got a signal: 15

and then it just sits… Sometimes it eventually returns me to
the
command prompt, and sometimes is freezes the entire machine.

Any tips?

TIA,
Mark





\

joe@qnx.com wrote:

123

def


Joe Bishop (joe@qnx.com)

I am having the same problem! My guess is the BIOS or the JumpTec hardware
itself, I am pretty sure I created a working boot disk several months ago
with an earlier board. Like you I am able to get the QNX install disk to
boot and I am even able to make a copy of it ON the JumpTec machine and boot
that successfully but the boot disks made as specified in the QNX tech notes
do not work. Any idea what the difference is between the loader on the QNX
install disk and the other ones?

Thanks for any light you can throw on this.

“Chris Travis” <ctravis@qnx.com> wrote in message
news:8nbhs9$ilo$1@nntp.qnx.com

In qdn.public.qnx4 James Gober <> jgober@goisi.com> > wrote:

Hello James,

Does the boot floppy work on the machine which you created it on?

Chris

: We are trying to install QNX4 on a new embedded system. The hardware is
a
: JumpTEC embedded board (133MHz Pentium) with an attached Mitsumi floppy
: drive. The BIOS is Phoenix BIOS 4.0 Release 6.0. We can successfully
boot
: via floppy into DOS so we believe the hardware is running properly.

: We created a QNX boot floppy via the instructions posted in the QNX
: knowledge base. (How to create a licensed QNX boot floppy.) When we try
to
: boot off of this floppy, the QNX loader loads and we get the dots on the
: screen. The dots continue to print forever and nothing else happens. The
: loader does not seem to be loading the boot image from the floppy
(.boot). I
: have reviewed the BIOS setup and cannot find anything that looks
suspicious.

: We have been working on this problem since Friday (including over the
: weekend) and urgently need help. We have an impending demo deadline.

: James Gober
: > jgober@goisi.com
\

Did you ever find a solution for this?
I had a problem similar to this, and I found
I had to both limit the .boot file size AND
use dinit -O when making the boot floppy (i.e.
use the old loader). I still have no idea why.
I recently posted a question about that…

Rich B.



James Gober wrote:

We are trying to install QNX4 on a new embedded system. The hardware is a
JumpTEC embedded board (133MHz Pentium) with an attached Mitsumi floppy
drive. The BIOS is Phoenix BIOS 4.0 Release 6.0. We can successfully boot
via floppy into DOS so we believe the hardware is running properly.

We created a QNX boot floppy via the instructions posted in the QNX
knowledge base. (How to create a licensed QNX boot floppy.) When we try to
boot off of this floppy, the QNX loader loads and we get the dots on the
screen. The dots continue to print forever and nothing else happens. The
loader does not seem to be loading the boot image from the floppy (.boot). I
have reviewed the BIOS setup and cannot find anything that looks suspicious.

We have been working on this problem since Friday (including over the
weekend) and urgently need help. We have an impending demo deadline.

James Gober
jgober@goisi.com


Richard Bonomo
UW Space Astronomy Laboratory
ph: (608) 263-4683 telefacsimile: (608) 263-0361
SAL-related email: bonomo@sal.wisc.edu
all other email: bonomo@ece.wisc.edu
web page URL: http://www.cae.wisc.edu/~bonomo


Try setting the TCP_NODELAY socket option to see if the delays stop
The NODELAY test might give a hint as to where the problem is located.

Thanks hw

Check this link out.
For the driver info.
http://qdn.qnx.com/support/docs/photon114/run_inst/utils/pppcl.html

Thanks hw

Dmitry Kabakov <dmitrykabakov@mail.ru> wrote in message
news:9c1iia$jdr$1@inn.qnx.com

Hi!
Where is gr.phi?
Help me.

A response to a very old message, but I hope no one minds.

Previously, Mario Charest wrote in comp.os.qnx, qdn.public.qnx4, qdn.public.qnx4.devtools, qdn.public.qnx4.photon:

There is none.

I have heard you can use the QNX4.24 version on QNX4.25 but I’m not 100%
sure.
Hopefully someone from QSSL will confirm

“Vlastislav sebesta” <> elsys@sky.cz> > wrote in message
news:8skmtr$gli$> 1@inn.qnx.com> …
Hi!
Which utility shall we use in QNX 4.25 instead of Csc in QNX 4.24 ?
Thank you !

The 4.24 Csc works just fine in 4.25 for me. I don’t know of anything
that would prevent it from working; there is nothing very magic about
how it works.

I’m not sure why it was dropped from distribution (no one around who
understood it and was willing to accept ownership maybe?). Under some
circumstances it can still give a performance benefit, even with the
presence of 100Mb networks. However the biggest benefit was seen on
slow networks.


William A. (Bill) Flowers Phone: +1-727-669-9999
Insight Control Systems Fax: +1-727-669-8999

On Thu, 14 Jun 2001 20:56:50 GMT, Alex Cellarius <acellarius@systems104.co.za> wrote:

Is there an already ported version of MC available with a more recent version
than the 4.1.3 I see on /usr/free?
That one works under 4.25, but it’s dropping an accented a (à) character
in places where blanks should be.

The problem seems to be related to the line characters.
If one selects +| etc characters (-a option), it works fine.

Anyone else see this & have a fix?

Remove -Q switch from "Dev.ansi -Q " in sysinit.#, set TERM to qansi-m.

David


Alex Cellarius wrote:

On Thu, 14 Jun 2001 20:56:50 GMT, Alex Cellarius <> acellarius@systems104.co.za> > wrote:
Is there an already ported version of MC available with a more recent version
than the 4.1.3 I see on /usr/free?
That one works under 4.25, but it’s dropping an accented a (à) character
in places where blanks should be.

The problem seems to be related to the line characters.
If one selects +| etc characters (-a option), it works fine.

Anyone else see this & have a fix?

“David V.” wrote:

Remove -Q switch from "Dev.ansi -Q " in sysinit.#, set TERM to qansi-m.
I use mc 4.1.36
David

Alex Cellarius wrote:

On Thu, 14 Jun 2001 20:56:50 GMT, Alex Cellarius <> acellarius@systems104.co.za> > wrote:
Is there an already ported version of MC available with a more recent version
than the 4.1.3 I see on /usr/free?
That one works under 4.25, but it’s dropping an accented a (à) character
in places where blanks should be.

The problem seems to be related to the line characters.
If one selects +| etc characters (-a option), it works fine.

Anyone else see this & have a fix?

On Tue, 19 Jun 2001 10:30:00 +0200, “David V.” <davidv@elisra.com> wrote:

Remove -Q switch from "Dev.ansi -Q " in sysinit.#, set TERM to qansi-m.

Thanks-will give it a try.

On Tue, 19 Jun 2001 12:08:15 GMT, Alex Cellarius <acellarius@systems104.co.za> wrote:

On Tue, 19 Jun 2001 10:30:00 +0200, “David V.” <> davidv@elisra.com> > wrote:
Remove -Q switch from "Dev.ansi -Q " in sysinit.#, set TERM to qansi-m.

Thanks-will give it a try.

Tried it without any luck.
The initial screen looks ok, but as soon as the cursor is moved, the a accent character
is inserted in front of the size column of where the selection line was previously.
Once the menus are displayed it gets worse, especially when the menus are open
and one moves horizontally from 1 main option to the next. Then the screen gets
really messed up with the à character.

Guess I will stick with -ac option-it’s functional.

Hi Erick,

You can start the driver manually just fine (the drivers are started in the
/etc/config/sysinit file). This computer had been working for several weeks
with 2 network cards installed before we tried adding the PCI analog input
card.

For some reason, the person installing the new card tried running the nettrap
utility even though the NIC drivers were already running. This is when we
discovered the PCI analog input card was confusing the nettrap utility and
causing the computer to lock up.

I guess we do not need to run nettrap, but it sure is a nice utility to use
when you have multiple NICs in one computer. Let me know if you have anymore
questions.

Thanks,
Tony



---------- Forwarded message ----------
Date: Tue, 25 Sep 2001 17:05:14 +0000 (GMT)
From: Hardware Support Account <hw@qnx.com>
To: qdn.public.qnx4@qnx.iaware.org
Newsgroups: qdn.public.qnx4
Subject: Re: nettrap locking up computer

Hi Tony,

What happens if you just run the driver manually? Do you have to run nettrap?

Erick.



Hardware Support Account <hw@qnx.com> wrote:

Hi Tony,

Not sure off the top of my head, however I will see what the network
guys think.

E.



Tony Williams <> tony@ctcqnx4.ctc.cummins.com> > wrote:
I’ve ran into a situation where the nettrap utility locks up (must hit the
power switch to recover) the computer. I tried running nettrap with the
verbose option and the last message echoed to the screen before it locks up
was “Looking for DEC FDDI Card.”

This computer has 2 PCI CNet ethernet cards (21143 chipset) and nettrap is
able to see them fine. The nettrap utility gives it’s recommendation on how
to start the driver for the CNet cards before the computer locks up. Also
installed in this computer is a PCI analog input card (Datel PCI-4163).

I’ve found that when I remove the Datel card, nettrap works fine and does not
lock up the computer.

Does anyone have any comments about what might be happening here? Why would a
PCI card that is not a NIC cause problems for nettrap?

Thanks,
Tony Williams


qdn.public.qnx4 mailing list
qdn.public.qnx4@qnx.iaware.org
http://qnx.iaware.org/mailman/listinfo/qdn.public.qnx4

Tony Williams <> tony@ctcqnx4.ctc.cummins.com> > wrote:
I’ve ran into a situation where the nettrap utility locks up (must hit the
power switch to recover) the computer. I tried running nettrap with the
verbose option and the last message echoed to the screen before it locks up
was “Looking for DEC FDDI Card.”

This is not entirely surprising.

What nettrap does, is it wanders along hitting the ioports that cards
use with the appropriate bits that would ask it to report its identity.
(It probes.) If you happen to have some other card at those ioports which
gets these bits… and does something… then it is quite easy to lock up
a machine with nettrap.

For this reason, I generally recommend that you run “nettrap -v” to find
out what you have, and from then on just run the drivers explicitly rather
than running nettrap each time.

Thanks for the information David. We only use the nettrap utility to find out
what we have and then start the driver explicitly in the sysinit file as you
suggested. We have not used the verbose option with nettrap in the past
because we only wanted to see the information concerning what was found during
the probe and not everthing it was probing for.

Sounds like the answer to my question is either use the -e option to ignore IO
ports the Datel card is using or don’t run the nettrap utility if a Datel card
is installed in the computer. Thanks again for the info.

-Tony


This computer has 2 PCI CNet ethernet cards (21143 chipset) and nettrap is
able to see them fine. The nettrap utility gives it’s recommendation on how
to start the driver for the CNet cards before the computer locks up. Also
installed in this computer is a PCI analog input card (Datel PCI-4163).

I’ve found that when I remove the Datel card, nettrap works fine and does not
lock up the computer.

nettrap probably tickles the Datel card in a bad way while looking for
the FDDI card. Or, if you really want to use nettrap, figure out what
ioports your Datel card is using, and use the nettrap -e option to tell
it to not scan those ports.

Does anyone have any comments about what might be happening here? Why would a
PCI card that is not a NIC cause problems for nettrap?

Because it is “probed” and this causes it to start doing something.

-David

QNX Training Services
dagibbs@qnx.com

Thanks for the info Mario. Anybody know where the telnetd source is for QNX4
then? I would like to see telnetd not allow connection to accounts that are
setup without passwords.

Thanks,
Tony


---------- Forwarded message ----------
Date: Thu, 29 Nov 2001 08:24:54 -0500
From: Mario Charest <mcharest@clipzinformatic.com>
To: qdn.public.qnx4@qnx.iaware.org
Newsgroups: qdn.public.qnx4
Subject: Re: telnet daemon


“Tony Williams” <tony@ctcqnx4.ctc.cummins.com> wrote in message
news:mailman.1006983377.19382.qdn.public.qnx4@qnx.iaware.org

Seems the source in the CVS link below is incomplete. The Makefile
includes
recurses.mk and the file is not in that directory. Anybody know where I
can
find the recurses.mk file?

These are sources for QNX6 and not QNX4. recurses.mk is include
with QNX6.

Thanks,
Tony

---------- Forwarded message ----------
Date: Wed, 14 Nov 2001 03:24:31 +0600
From: ian zagorskih <> ianzag@novosoft-us.com
To: > qdn.public.qnx4@qnx.iaware.org
Newsgroups: qdn.public.qnx4
Subject: Re: telnet daemon


“Tony Williams” <> tony@ctcqnx4.ctc.cummins.com> > wrote in message
news:> mailman.1005683895.12200.qdn.public.qnx4@qnx.iaware.org> …
Is anyone aware of a telnet server that will only allow access to those
accounts that have passwords? We have a ported ftp server already that
operates this way and I’m looking for a telnet server with similar
functionality. Any comments would be appreciated.


at > http://cvs.qnx.com/cgi-bin/cvsweb.cgi/services/telnetd/ > you can find
telnetd source code. i believe it’s easy to add this little features.

Thanks,
Tony Williams


// wbr

“Tony Williams” <tony@ctcqnx4.ctc.cummins.com> wrote in message
news:mailman.1007042178.23606.qdn.public.qnx4@qnx.iaware.org

Thanks for the info Mario. Anybody know where the telnetd source is for
QNX4
then?

They are not available.

I would like to see telnetd not allow connection to accounts that are
setup without passwords.

I think you can create wrappers for that. I don’t really know about
that though.

Most telnetd source that you can find on the net should compile
on QNX4.

Thanks,
Tony


---------- Forwarded message ----------
Date: Thu, 29 Nov 2001 08:24:54 -0500
From: Mario Charest <> mcharest@clipzinformatic.com
To: > qdn.public.qnx4@qnx.iaware.org
Newsgroups: qdn.public.qnx4
Subject: Re: telnet daemon


“Tony Williams” <> tony@ctcqnx4.ctc.cummins.com> > wrote in message
news:> mailman.1006983377.19382.qdn.public.qnx4@qnx.iaware.org> …
Seems the source in the CVS link below is incomplete. The Makefile
includes
recurses.mk and the file is not in that directory. Anybody know where I
can
find the recurses.mk file?


These are sources for QNX6 and not QNX4. recurses.mk is include
with QNX6.

Thanks,
Tony

---------- Forwarded message ----------
Date: Wed, 14 Nov 2001 03:24:31 +0600
From: ian zagorskih <> ianzag@novosoft-us.com
To: > qdn.public.qnx4@qnx.iaware.org
Newsgroups: qdn.public.qnx4
Subject: Re: telnet daemon


“Tony Williams” <> tony@ctcqnx4.ctc.cummins.com> > wrote in message
news:> mailman.1005683895.12200.qdn.public.qnx4@qnx.iaware.org> …
Is anyone aware of a telnet server that will only allow access to
those
accounts that have passwords? We have a ported ftp server already
that
operates this way and I’m looking for a telnet server with similar
functionality. Any comments would be appreciated.


at > http://cvs.qnx.com/cgi-bin/cvsweb.cgi/services/telnetd/ > you can find
telnetd source code. i believe it’s easy to add this little features.

Thanks,
Tony Williams


// wbr

Mario Charest <mcharest@clipzinformatic.com> wrote:

I think you can create wrappers for that. I don’t really know about
that though.

I don’t think wrappers will work in this case because wrappers wraps
telnetd and they won’t know what username someone will input to
the telnetd prompt (wrapper happens before telnetd).
wrappers will work if you want to limit based on source IP address.
wrappers can recoginze the IP address where user’s connection comes from
and then decide whether to refuse the connection or spawn the telnetd.

Most telnetd source that you can find on the net should compile
on QNX4.

that’s interesting. If most telnetd source from the net would compile on qnx4,
why wouldn’t this qnx6 source work? the telnetd sources from the net
are for other Unix. I heard qnx6 is more compatible with other Unix
than qnx4 is. so are you implying qnx4 is more compatible to other Unix
than to qnx6?

frank

<fliu@bb.vipstage.com> wrote in message news:9ub2qd$qsr$1@inn.qnx.com

Mario Charest <> mcharest@clipzinformatic.com> > wrote:
I think you can create wrappers for that. I don’t really know about
that though.

I don’t think wrappers will work in this case because wrappers wraps
telnetd and they won’t know what username someone will input to
the telnetd prompt (wrapper happens before telnetd).
wrappers will work if you want to limit based on source IP address.
wrappers can recoginze the IP address where user’s connection comes from
and then decide whether to refuse the connection or spawn the telnetd.

Most telnetd source that you can find on the net should compile
on QNX4.

that’s interesting. If most telnetd source from the net would compile on
qnx4,
why wouldn’t this qnx6 source work?

Because the qnx6 package assumes it’s compile on QNX6, hence the
requirement for recurse.mk.

the telnetd sources from the net
are for other Unix. I heard qnx6 is more compatible with other Unix
than qnx4 is. so are you implying qnx4 is more compatible to other Unix
than to qnx6?

Not at all. I’m just saying version you might find on internet are
probably less OS dependant then the QNX6 version is.

frank

Hi, everybody,

I am running a QNX 4.25 on an IBM PC and have some trouble with /dos/c.

The /dos/c is mounted automatically when the system is installed and
partition of /dev/hd0.0t6 is adopted for this /dos/c. Whenever I access
/dos/c, the dos file system terminates. Meanwhile /dos/b is mounted for
floppy and works fine.

I would appreciate if someone can give me some suggestion.

Best regards,

Alex Wu