Because RTP won’t work with my S3 card, I use phindows to communicate
with it. This is proving to be quite effective. I am impressed.
I notice that even when I am not doing anything other than simply
staring at the Photon display - no apps running on my account - the CPU
usage is typically hovering at around 70%. Why is that? A pidin shows
only a couple of READY tasks (one generally being for the pterm).
RTP is running on a PII-233 MMX CPU with 64M memory.
Is there a sac type utility on the horizon? And an equivalent to the sin
info output of QNX4 with the same type of information (specifically
memory available/total memory)?
Overall, for me the RTP is shaping up very well. Like all the others I
have a steep learning curve to climb. Should be fun - since there’s
bugger all easy to get at documentation! 
I can’t print what’s there
out yet as I haven’t figured out how to set up for my Laserjet yet…
Thanks,
Geoff Roberts.
How do you you use phindows with QRTP? Do you have to start phrelay by
hand? How do you automate it for startup? This was in inetd.conf or
something like that in QNX4. Where is it configured in NTO? Does it work
with the Tiny Stack? If not, can someone give step by step to get the Big
Stack working on startup?
Scott
Geoff Roberts wrote:
Because RTP won’t work with my S3 card, I use phindows to communicate
with it. This is proving to be quite effective. I am impressed.
I notice that even when I am not doing anything other than simply
staring at the Photon display - no apps running on my account - the CPU
usage is typically hovering at around 70%. Why is that? A pidin shows
only a couple of READY tasks (one generally being for the pterm).
RTP is running on a PII-233 MMX CPU with 64M memory.
Is there a sac type utility on the horizon? And an equivalent to the sin
info output of QNX4 with the same type of information (specifically
memory available/total memory)?
Overall, for me the RTP is shaping up very well. Like all the others I
have a steep learning curve to climb. Should be fun - since there’s
bugger all easy to get at documentation! > > I can’t print what’s there
out yet as I haven’t figured out how to set up for my Laserjet yet…
Thanks,
Geoff Roberts.
Just start inetd and it should be working.
You can have inetd started automaticaly by create executable
script /etc/rc.d/rc.local
“J. Scott Franko” <jsfranko@switch.com> wrote in message
news:39E1E378.F69800AA@switch.com…
How do you you use phindows with QRTP? Do you have to start phrelay by
hand? How do you automate it for startup? This was in inetd.conf or
something like that in QNX4. Where is it configured in NTO? Does it work
with the Tiny Stack? If not, can someone give step by step to get the Big
Stack working on startup?
Scott
Geoff Roberts wrote:
Because RTP won’t work with my S3 card, I use phindows to communicate
with it. This is proving to be quite effective. I am impressed.
I notice that even when I am not doing anything other than simply
staring at the Photon display - no apps running on my account - the CPU
usage is typically hovering at around 70%. Why is that? A pidin shows
only a couple of READY tasks (one generally being for the pterm).
RTP is running on a PII-233 MMX CPU with 64M memory.
Is there a sac type utility on the horizon? And an equivalent to the sin
info output of QNX4 with the same type of information (specifically
memory available/total memory)?
Overall, for me the RTP is shaping up very well. Like all the others I
have a steep learning curve to climb. Should be fun - since there’s
bugger all easy to get at documentation! > > I can’t print what’s there
out yet as I haven’t figured out how to set up for my Laserjet yet…
Thanks,
Geoff Roberts.
Not that the phrelay that comes with the pre-release has a problem
with terminal.
“Mario Charest” <mcz@videotron.ca> wrote in message
news:8rsv2m$f39$1@inn.qnx.com…
Just start inetd and it should be working.
You can have inetd started automaticaly by create executable
script /etc/rc.d/rc.local
“J. Scott Franko” <> jsfranko@switch.com> > wrote in message
news:> 39E1E378.F69800AA@switch.com> …
How do you you use phindows with QRTP? Do you have to start phrelay by
hand? How do you automate it for startup? This was in inetd.conf or
something like that in QNX4. Where is it configured in NTO? Does it
work
with the Tiny Stack? If not, can someone give step by step to get the
Big
Stack working on startup?
Scott
Geoff Roberts wrote:
Because RTP won’t work with my S3 card, I use phindows to communicate
with it. This is proving to be quite effective. I am impressed.
I notice that even when I am not doing anything other than simply
staring at the Photon display - no apps running on my account - the
CPU
usage is typically hovering at around 70%. Why is that? A pidin shows
only a couple of READY tasks (one generally being for the pterm).
RTP is running on a PII-233 MMX CPU with 64M memory.
Is there a sac type utility on the horizon? And an equivalent to the
sin
info output of QNX4 with the same type of information (specifically
memory available/total memory)?
Overall, for me the RTP is shaping up very well. Like all the others I
have a steep learning curve to climb. Should be fun - since there’s
bugger all easy to get at documentation! > > I can’t print what’s
there
out yet as I haven’t figured out how to set up for my Laserjet yet…
Thanks,
Geoff Roberts.
Previously, J. Scott Franko wrote in qdn.public.qnxrtp.os:
How do you you use phindows with QRTP? Do you have to start phrelay by
hand? How do you automate it for startup? This was in inetd.conf or
something like that in QNX4. Where is it configured in NTO? Does it work
with the Tiny Stack? If not, can someone give step by step to get the Big
Stack working on startup?
Scott
Geoff Roberts wrote:
Because RTP won’t work with my S3 card, I use phindows to communicate
with it. This is proving to be quite effective. I am impressed.
I notice that even when I am not doing anything other than simply
staring at the Photon display - no apps running on my account - the CPU
usage is typically hovering at around 70%. Why is that? A pidin shows
only a couple of READY tasks (one generally being for the pterm).
RTP is running on a PII-233 MMX CPU with 64M memory.
Is there a sac type utility on the horizon? And an equivalent to the sin
info output of QNX4 with the same type of information (specifically
memory available/total memory)?
Overall, for me the RTP is shaping up very well. Like all the others I
have a steep learning curve to climb. Should be fun - since there’s
bugger all easy to get at documentation! > > I can’t print what’s there
out yet as I haven’t figured out how to set up for my Laserjet yet…
Thanks,
Geoff Roberts.
It’s exactly the same. inetd.conf and services are correctly initialized in OEM release to listent for a phindows request of connection on tcpip.
Just start phindows and give the correct tcpip address.
Alain.