QNX RTOS v4 Knowledge Base
QNX RTOS v4 Knowledge Base
| Title |
Phindows Configuration Issues |
| Ref. No. |
QNX.000009514 |
| Category(ies) |
Configuration |
| Issue |
1: Where does Phindows store its configuration information?
2: Updating my Photon from 1.12 to 1.13 has changed the way my application looks under Phindows. It no longer looks like a native W95 application.
3: How do I specify a dialup script option so that I can automate the job of dialing out and logging in to a remote QNX site?
4: Getting a grey screen on the Phindows display when trying to make the session extend across multiple screens; the Phindows session is an extension to a Photon session on a qnx server.
5: Every phindows pterm needs a pseudo tty (pty), but Dev.pty only allows up to 16 pty's. How do I get more?
|
| Solution |
Issue 1: Where does Phindows store its configuration information?
We use the standard Microsoft API to register this information, and let the OS place the information. The answer will therefore depend on what type and what version of MS OS you use to run Phindows. For W95, windowsphindows.ini and windowssystemphindows.ini are possible candidates. Under NT, the information is stored in the Registry database.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 2: Updating my Photon from 1.12 to 1.13 has changed the way my application looks under Phindows. It no longer looks like a native W95 application.
We've included a widow manager which has the code fixes for 1.13 but still has the 1.12 window frame. It's called pwm.112 in /qnx4/photon/bin.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 3: How do I specify a dialup script option so that I can automate the job of dialing out and logging in to a remote QNX site?
You could use a batch file to echo 'at' commands to the serial port, then lauch phindows to get things started, but you still need to login.
By far the "easiest" way to automate this sort of thing is to use PPP on the serial port, take advantage of the Win95/NT dial-up networking support to dial and login, and use
Phindows with the -t option instead of -m.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 4: Getting a grey screen on the Phindows display when trying to make the session extend across multiple screens; the Phindows session is an extension to a Photon session on a qnx server.
Make sure you have the 'Multi Monitor Placement' item in the PWM config menu enabled on the Photon side.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Issue 5: Every phindows pterm needs a pseudo tty (pty), but Dev.pty only allows up to 16 pty's. How do I get more?
Start more Dev.pty processes and specify different names, e.g.:
Dev.pty -n16 &
Dev.pty -n16 -N/dev/ptyq,/dev/ttyq &
Dev.pty -n16 -N/dev/ptyr,/dev/ttyr &
...
Dev.pty also has a -l option that makes the commands shorter:
Dev.pty -n16 &
Dev.pty -n16 -l q &
Dev.pty -n16 -l r &
...
Software that looks for a free terminal will find the next one in the group. you don't need to worry about what name it has. Also make sure you start Dev with lots of device slots.
|
|
