Hi,
I was very happy to see QNX 6.1 install very smoothly on my Thinkpad A22m.
Wow sound, cdrom, ethernet, accelerated and overlay video just all worked.
Mpegs with the Media Player , the G2 realplayer and shockwave support for
Voyager all work great. All those developement tools should keep about
anyone busy. Great job on a really nice OS. My only complaint is really
picky… I have a 15" LCD with my Thinkpad and can do 1400x1050 with 16 bit
color. The driver options for the ATI Mobility M3 with photon only have
1600x1200 and 1280x1024 then smaller. 1280x1024 accelerated with overlay
support still is really nice.
My only other observations are all those sudo UNIX command line tools. It
is VERY confusing for a long time UNIX user. What is with pidin and pidin
in? Why did QNX not implement ps and uname like the rest of the UNIX-like
world (even MacOS X and BeOS have ps)?
Pat
Patrick Berge <pberge@stny.rr.com> wrote:
Hi,
I was very happy to see QNX 6.1 install very smoothly on my Thinkpad A22m.
Wow sound, cdrom, ethernet, accelerated and overlay video just all worked.
Mpegs with the Media Player , the G2 realplayer and shockwave support for
Voyager all work great. All those developement tools should keep about
anyone busy. Great job on a really nice OS. My only complaint is really
picky… I have a 15" LCD with my Thinkpad and can do 1400x1050 with 16 bit
color. The driver options for the ATI Mobility M3 with photon only have
1600x1200 and 1280x1024 then smaller. 1280x1024 accelerated with overlay
support still is really nice.
My only other observations are all those sudo UNIX command line tools. It
is VERY confusing for a long time UNIX user. What is with pidin and pidin
in? Why did QNX not implement ps and uname like the rest of the UNIX-like
world (even MacOS X and BeOS have ps)?
???
cburgess:/home/cburgess >which ps
/bin/ps
cburgess:/home/cburgess >which uname
/bin/uname
cburgess:/home/cburgess >uname -a
QNX cburgess 6.1.0 2001/08/23-19:38:50edt x86pc x86
cburgess:/home/cburgess >ps
PID TTY TIME CMD
344997912 ? 00:00:00 pterm
345002011 ? 00:00:00 /bin/sh
532508 ? 00:00:20 pwm
345042978 ? 00:00:00 elm
345104423 ? 00:00:00 pterm
345108520 ? 00:00:00 /bin/sh
345124905 ? 00:00:01 tin
345129002 ? 00:00:00 pterm
345133099 ? 00:00:00 /bin/sh
345272364 ? 00:00:00 sh
345272365 ? 00:00:00 vi
345276462 ? 00:00:00 pterm
345280559 ? 00:00:00 /bin/sh
345399344 ? 00:00:00 script
345403441 ? 00:00:00 script
345403442 ? 00:00:00 /bin/sh
345497651 ? 00:00:00 ps
cburgess:/home/cburgess >
–
cburgess@qnx.com
Colin Burgess <cburgess@qnx.com> wrote:
Patrick Berge <> pberge@stny.rr.com> > wrote:
Hi,
I was very happy to see QNX 6.1 install very smoothly on my Thinkpad A22m.
Wow sound, cdrom, ethernet, accelerated and overlay video just all worked.
Mpegs with the Media Player , the G2 realplayer and shockwave support for
Voyager all work great. All those developement tools should keep about
anyone busy. Great job on a really nice OS.
BTW - Thanks for nice comments! :v)
My only complaint is really
picky… I have a 15" LCD with my Thinkpad and can do 1400x1050 with 16 bit
color. The driver options for the ATI Mobility M3 with photon only have
1600x1200 and 1280x1024 then smaller. 1280x1024 accelerated with overlay
support still is really nice.
My only other observations are all those sudo UNIX command line tools. It
is VERY confusing for a long time UNIX user. What is with pidin and pidin
in? Why did QNX not implement ps and uname like the rest of the UNIX-like
world (even MacOS X and BeOS have ps)?
???
cburgess:/home/cburgess >which ps
/bin/ps
cburgess:/home/cburgess >which uname
/bin/uname
cburgess:/home/cburgess >uname -a
QNX cburgess 6.1.0 2001/08/23-19:38:50edt x86pc x86
cburgess:/home/cburgess >ps
PID TTY TIME CMD
344997912 ? 00:00:00 pterm
345002011 ? 00:00:00 /bin/sh
532508 ? 00:00:20 pwm
345042978 ? 00:00:00 elm
345104423 ? 00:00:00 pterm
345108520 ? 00:00:00 /bin/sh
345124905 ? 00:00:01 tin
345129002 ? 00:00:00 pterm
345133099 ? 00:00:00 /bin/sh
345272364 ? 00:00:00 sh
345272365 ? 00:00:00 vi
345276462 ? 00:00:00 pterm
345280559 ? 00:00:00 /bin/sh
345399344 ? 00:00:00 script
345403441 ? 00:00:00 script
345403442 ? 00:00:00 /bin/sh
345497651 ? 00:00:00 ps
cburgess:/home/cburgess
–
cburgess@qnx.com
–
cburgess@qnx.com
Colin,
Wow do I look dumb! I was reading the FAQs/documenation and jumped to a
conclusion. Doh I should have just tried ps. Anyway I thought it is still
odd to have a redundant command like pidin? As you can see am new to
QNX… I should mess around with it a little more before asking simple
questions. Sorry.
Pat
Colin Burgess wrote:
Patrick Berge <> pberge@stny.rr.com> > wrote:
My only other observations are all those sudo UNIX command line tools.
It
is VERY confusing for a long time UNIX user. What is with pidin and
pidin in? Why did QNX not implement ps and uname like the rest of the
UNIX-like world (even MacOS X and BeOS have ps)?
???
cburgess:/home/cburgess >which ps
/bin/ps
cburgess:/home/cburgess >which uname
/bin/uname
cburgess:/home/cburgess >uname -a
QNX cburgess 6.1.0 2001/08/23-19:38:50edt x86pc x86
cburgess:/home/cburgess >ps
PID TTY TIME CMD
344997912 ? 00:00:00 pterm
345002011 ? 00:00:00 /bin/sh
532508 ? 00:00:20 pwm
345042978 ? 00:00:00 elm
345104423 ? 00:00:00 pterm
345108520 ? 00:00:00 /bin/sh
345124905 ? 00:00:01 tin
345129002 ? 00:00:00 pterm
345133099 ? 00:00:00 /bin/sh
345272364 ? 00:00:00 sh
345272365 ? 00:00:00 vi
345276462 ? 00:00:00 pterm
345280559 ? 00:00:00 /bin/sh
345399344 ? 00:00:00 script
345403441 ? 00:00:00 script
345403442 ? 00:00:00 /bin/sh
345497651 ? 00:00:00 ps
Patrick Berge <pberge@stny.rr.com> wrote:
Colin,
Wow do I look dumb! I was reading the FAQs/documenation and jumped to a
conclusion. Doh I should have just tried ps. Anyway I thought it is still
odd to have a redundant command like pidin? As you can see am new to
QNX… I should mess around with it a little more before asking simple
questions. Sorry.
Don’t worry. QNX has always had a QNX specific process info command. In
QNX2 it was tsk, in QNX4 it was sin, and in QNX6 it is pidin.
Those in the know will remember the hours of fun trying to find new
easter eggs (tsk tsk, sin toomuch, pidin english, pidin toomuch, pidin pie)
Pat
Colin Burgess wrote:
Patrick Berge <> pberge@stny.rr.com> > wrote:
My only other observations are all those sudo UNIX command line tools.
It
is VERY confusing for a long time UNIX user. What is with pidin and
pidin in? Why did QNX not implement ps and uname like the rest of the
UNIX-like world (even MacOS X and BeOS have ps)?
???
cburgess:/home/cburgess >which ps
/bin/ps
cburgess:/home/cburgess >which uname
/bin/uname
cburgess:/home/cburgess >uname -a
QNX cburgess 6.1.0 2001/08/23-19:38:50edt x86pc x86
cburgess:/home/cburgess >ps
PID TTY TIME CMD
344997912 ? 00:00:00 pterm
345002011 ? 00:00:00 /bin/sh
532508 ? 00:00:20 pwm
345042978 ? 00:00:00 elm
345104423 ? 00:00:00 pterm
345108520 ? 00:00:00 /bin/sh
345124905 ? 00:00:01 tin
345129002 ? 00:00:00 pterm
345133099 ? 00:00:00 /bin/sh
345272364 ? 00:00:00 sh
345272365 ? 00:00:00 vi
345276462 ? 00:00:00 pterm
345280559 ? 00:00:00 /bin/sh
345399344 ? 00:00:00 script
345403441 ? 00:00:00 script
345403442 ? 00:00:00 /bin/sh
345497651 ? 00:00:00 ps
–
cburgess@qnx.com
“Colin Burgess” <cburgess@qnx.com> wrote in message
news:9q7eh1$cf6$1@nntp.qnx.com…
Those in the know will remember the hours of fun trying to find new
easter eggs (tsk tsk, sin toomuch, pidin english, pidin toomuch, pidin
pie)
Oh Boy!
I knew about “tsk tsk” and “sin toomuch” but I haven’t taken the time to
“strings pidin” yet.
Oops! Was I supposed to say that?
Bill Caroselli
PS. Just tried them. Pretty lame. Just like their supposed to be. Q4’s
sin toomuch was much better. And Oh, you forgot, “pidin sin”.
Colin Burgess <cburgess@qnx.com> wrote:
Patrick Berge <> pberge@stny.rr.com> > wrote:
Colin,
Wow do I look dumb! I was reading the FAQs/documenation and jumped to a
conclusion. Doh I should have just tried ps. Anyway I thought it is still
odd to have a redundant command like pidin? As you can see am new to
QNX… I should mess around with it a little more before asking simple
questions. Sorry.
Don’t worry. QNX has always had a QNX specific process info command. In
QNX2 it was tsk, in QNX4 it was sin, and in QNX6 it is pidin.
Those in the know will remember the hours of fun trying to find new
easter eggs (tsk tsk, sin toomuch, pidin english, pidin toomuch, pidin pie)
pidin tsk 
E.
Pat
Colin Burgess wrote:
Patrick Berge <> pberge@stny.rr.com> > wrote:
My only other observations are all those sudo UNIX command line tools.
It
is VERY confusing for a long time UNIX user. What is with pidin and
pidin in? Why did QNX not implement ps and uname like the rest of the
UNIX-like world (even MacOS X and BeOS have ps)?
???
cburgess:/home/cburgess >which ps
/bin/ps
cburgess:/home/cburgess >which uname
/bin/uname
cburgess:/home/cburgess >uname -a
QNX cburgess 6.1.0 2001/08/23-19:38:50edt x86pc x86
cburgess:/home/cburgess >ps
PID TTY TIME CMD
344997912 ? 00:00:00 pterm
345002011 ? 00:00:00 /bin/sh
532508 ? 00:00:20 pwm
345042978 ? 00:00:00 elm
345104423 ? 00:00:00 pterm
345108520 ? 00:00:00 /bin/sh
345124905 ? 00:00:01 tin
345129002 ? 00:00:00 pterm
345133099 ? 00:00:00 /bin/sh
345272364 ? 00:00:00 sh
345272365 ? 00:00:00 vi
345276462 ? 00:00:00 pterm
345280559 ? 00:00:00 /bin/sh
345399344 ? 00:00:00 script
345403441 ? 00:00:00 script
345403442 ? 00:00:00 /bin/sh
345497651 ? 00:00:00 ps
cburgess@qnx.com
Previously, Patrick Berge wrote in qdn.public.qnxrtp.newuser:
Anyway I thought it is still
odd to have a redundant command like pidin?
The intersection of the two is not equal to the union.
Not being a Unix OS/kernel, QNX has other pid/tid level
information that is useful. For example, ps will not
tell you that a thread is SEND, RECEIVE, or REPLY blocked,
a very useful thing to know in QNX.
Mitchell Schoenbrun --------- maschoen@pobox.com
Colin,
OK? And I though BeOS had cute little messages hidden in the OS…just
look at the bad http address you get with Net Positive.
Do you have any input about a 1400x1050 resolution for ATI Rage128?
And this one will get your attention… What revisions of the Walnut board
or 405GP are needed for QNX realtime platform? And do I get all the same
software as the X86 platform or just a small subset? I am involved in
405GP development/testing at work.
Pat
Patrick Berge <pberge@stny.rr.com> wrote:
Colin,
OK? And I though BeOS had cute little messages hidden in the OS…just
look at the bad http address you get with Net Positive.
Do you have any input about a 1400x1050 resolution for ATI Rage128?
And this one will get your attention… What revisions of the Walnut board
or 405GP are needed for QNX realtime platform? And do I get all the same
software as the X86 platform or just a small subset? I am involved in
405GP development/testing at work.
Sorry Pat, I’m really not a hardware guy. Someone else will have to step
in here, although this is probably not the best newsgroup to attract
the attention of the hardware gurus…
–
cburgess@qnx.com
Patrick Berge <pberge@stny.rr.com> wrote:
Colin,
OK? And I though BeOS had cute little messages hidden in the OS…just
look at the bad http address you get with Net Positive.
Do you have any input about a 1400x1050 resolution for ATI Rage128?
The driver for the Rage128 uses a direct modeswitcher so you can manually
try other resolutions. There are some limitations on direct modeswitchers -
for example X and Y resolutions may have to be divisible by 8 or 16.
1400x1050 won’t work, but you could try something closes to that - 1376x1048
for example. You’ll have to manually edit your
/etc/system/config/graphics-modes
io-graphics -g1376x1048x16 -dldevg-ati_rage128.so -I0 -d…
And this one will get your attention… What revisions of the Walnut board
or 405GP are needed for QNX realtime platform? And do I get all the same
software as the X86 platform or just a small subset? I am involved in
405GP development/testing at work.
I have done Walnut testing with Revision D, we are currently in the process of
obtaining Revision E board to do further testing. If you install the PPC runtimes
you will be able to see what is currently available on PPC for QNX 6.1.
Regards,
Joe
Patrick Berge <pberge@stny.rr.com> wrote:
Colin,
OK? And I though BeOS had cute little messages hidden in the OS…just
look at the bad http address you get with Net Positive.
Do you have any input about a 1400x1050 resolution for ATI Rage128?
The driver for the Rage128 uses a direct modeswitcher so you can manually
try other resolutions. There are some limitations on direct modeswitchers -
for example X and Y resolutions may have to be divisible by 8 or 16.
1400x1050 won’t work, but you could try something closes to that - 1376x1048
for example. You will have to manually edit your /etc/system/config/graphics-modes
file and make the top line:
io-graphics -g1376x1048x16 -dldevg-ati_rage128.so -I0 -d…
E.
And this one will get your attention… What revisions of the Walnut board
or 405GP are needed for QNX realtime platform? And do I get all the same
software as the X86 platform or just a small subset? I am involved in
405GP development/testing at work.
Pat
Hardware Support Account wrote:
The driver for the Rage128 uses a direct modeswitcher so you can manually
try other resolutions. There are some limitations on direct modeswitchers
- for example X and Y resolutions may have to be divisible by 8 or 16.
1400x1050 won’t work, but you could try something closes to that -
1376x1048
for example. You will have to manually edit your
/etc/system/config/graphics-modes file and make the top line:
io-graphics -g1376x1048x16 -dldevg-ati_rage128.so -I0 -d…
Now that is very cool so I could try 1400x1048x16 right? since both
resolutions are divisible by 8. That’s only 2 pixes in the X lost.
Pat
Hi Patrick,
Yes, that should work, give it a try
E.
Patrick Berge <pberge@stny.rr.com> wrote:
Hardware Support Account wrote:
The driver for the Rage128 uses a direct modeswitcher so you can manually
try other resolutions. There are some limitations on direct modeswitchers
- for example X and Y resolutions may have to be divisible by 8 or 16.
1400x1050 won’t work, but you could try something closes to that -
1376x1048
for example. You will have to manually edit your
/etc/system/config/graphics-modes file and make the top line:
io-graphics -g1376x1048x16 -dldevg-ati_rage128.so -I0 -d…
Now that is very cool so I could try 1400x1048x16 right? since both
resolutions are divisible by 8. That’s only 2 pixes in the X lost.
Pat