Is anyone else having problems with large pterm windows under Phindows?
I am finding that using pterm windows with more than about 58 rows of text
don’t work well at all under Phindows. For example they don’t redraw
themselves properly if you change consoles.
Here is our setup:
QNX6 side:
Version: 6.2.1
Photon native graphics resolution on console:1024x768x32 (tnt driver)
Windows side:
WindowsXP
Phindows 2.00
Resolution 1280x1024x32
Phindows maximised
To reproduce the problem, create a couple of large pterm windows on virtual
console 1 (say 60 rows x 80 cols, pterm14 font). Make sure they overlap a
little bit. Run some commands in both windows to fill them up with text.
Now change to virtual console 2 and start the help viewer. Maximise it.
Now change back and forth between consoles 1 and 2 repeatedly (ctrl-alt-1,
ctrl-alt-2 etc). Before long you will see obvious screen corruption.
This doesn’t happen if the pterm windows are under about 55 rows in size. It
also doesn’t happen on the VGA console, so it seems to be a phrelay/Phindows
problem.
Anyone else seen this?
Rob Rutherford
Ruzz Technology
“Garry Turcotte” <garry@qnx.com> wrote in message
news:b6f3fr$eh5$1@nntp.qnx.com…
Replied via email
Please post here. I’ve been very annoyed by this problem for some time now.
Thanks,
Marty Doane
Robert Rutherford wrote:
Is anyone else having problems with large pterm windows under Phindows?
I am finding that using pterm windows with more than about 58 rows of
text
don’t work well at all under Phindows. For example they don’t redraw
themselves properly if you change consoles.
Here is our setup:
QNX6 side:
Version: 6.2.1
Photon native graphics resolution on console:1024x768x32 (tnt driver)
Windows side:
WindowsXP
Phindows 2.00
Resolution 1280x1024x32
Phindows maximised
To reproduce the problem, create a couple of large pterm windows on
virtual
console 1 (say 60 rows x 80 cols, pterm14 font). Make sure they overlap
a
little bit. Run some commands in both windows to fill them up with text.
Now change to virtual console 2 and start the help viewer. Maximise it.
Now change back and forth between consoles 1 and 2 repeatedly
(ctrl-alt-1,
ctrl-alt-2 etc). Before long you will see obvious screen corruption.
This doesn’t happen if the pterm windows are under about 55 rows in
size. It
also doesn’t happen on the VGA console, so it seems to be a
phrelay/Phindows
problem.
Anyone else seen this?
Rob Rutherford
Ruzz Technology
Marty Doane wrote:
“Garry Turcotte” <> garry@qnx.com> > wrote in message
news:b6f3fr$eh5$> 1@nntp.qnx.com> …
Replied via email
Please post here. I’ve been very annoyed by this problem for some time now.
Thanks,
Marty Doane
I sent him a new phrelay to see if it’s a problem
I fixed two months ago. I’ll send it to you to try
and you can follow-up to the group with the results…
“Garry Turcotte” <garry@qnx.com> wrote in message
news:b6f6la$gc2$1@nntp.qnx.com…
I sent him a new phrelay to see if it’s a problem
I fixed two months ago. I’ll send it to you to try
and you can follow-up to the group with the results…
I tried the new phrelay that Garry sent me and I can confirm that I am
experiencing the known bug that he mentioned.
I understand the fix requires a new phrelay and new Phindows.
Thanks for your help Garry.
Rob Rutherford
“Garry Turcotte” <garry@qnx.com> wrote in message
news:b6f6la$gc2$1@nntp.qnx.com…
Marty Doane wrote:
“Garry Turcotte” <> garry@qnx.com> > wrote in message
news:b6f3fr$eh5$> 1@nntp.qnx.com> …
Replied via email
Please post here. I’ve been very annoyed by this problem for some time
now.
Thanks,
Marty Doane
I sent him a new phrelay to see if it’s a problem
I fixed two months ago. I’ll send it to you to try
and you can follow-up to the group with the results…
The first phrelay sent confirmed the source of the problem to Garry.
An experimental phrelay and phindows.exe fixed the problem.
–
Marty Doane
Siemens Dematic