Greeetings:
I am setting up a replacement CPU for our target system. As far as I can see
I am copying all required files to the target CPU using the manufacturer
instructions and our previous configuration as guides. The system we are
replacing is a Ziatech stand alone CPU which we have used for appr. 3 years
in this product (Ziatech has obsoleted this CPU). The new CPU is a
Versalogic PC 104 + stand alone with a DiskOnChip (DOC) storage device. The
DOC is from all appearances an exact simulation of a hard disk storage
device.
After I set up QNX: when we use Vedit the navigation and control keys do not
work. We get graphics characters displayed on the screen instead of the
cursor moving as directed (Up-Arrow, Down-Arrow, Left-Arrow, Right-Arrow,
Alt, etc.)
This very well may have been an existing problem even with the previous CPU
because we never used Vedit on the target then (Primarily because that
configuration used Flash for the disk device and editing files was not fun.)
Now however, editing is moot as the DOC acts just like a disk drive…
I know I’v seen something similiar to this in the pastjust can’t recall the
cause/fix…
Any hints?
Regards,
Ray L.
P.S.
I installed QNX 4.24 then updated to 4.25, then 4.25D.
I have not upgraded Vedit to v5.05 or Vedit Plus (yet).
Ray,
You didn’t specify if you are doing this on a console (vga+kbd), serial
terminal, or telnet? Below are console and telnet - serial gets rather
complicated.
Pick an emulation - QNX or QANSI
Console:
key: 'stty ’ Look at the protocol= value
0 = QNX 1=QANSI
stty protocol=1 will change it…
Telnet:
Make sure (1) your terminal emulator is running in QNX or QANSI
mode. I’ve had limited success with other emulations but have gotten
away with vt100 as long as it is not the windoze terminal emulator.
Make sure you are in 8-bit mode for QNX.
ALL:
key: 'export ’ Look at the TERM= value
it should be ‘qnx’ or ‘qansi’ – note case
export TERM=qnx or qansi to set if necessary
ls /usr/lib/terminfo/q
make sure you have a ‘qnx’ or ‘qansi’ terminal definition.
You can copy from another system or use tic to compile
the source file but you will get a lot more than you need.
Happy hunting,
Jay
Ray LaBrecque wrote in message <9qq45d$k3h$1@inn.qnx.com>…
Greeetings:
I am setting up a replacement CPU for our target system. As far as I can
see
I am copying all required files to the target CPU using the manufacturer
instructions and our previous configuration as guides. The system we are
replacing is a Ziatech stand alone CPU which we have used for appr. 3 years
in this product (Ziatech has obsoleted this CPU). The new CPU is a
Versalogic PC 104 + stand alone with a DiskOnChip (DOC) storage device. The
DOC is from all appearances an exact simulation of a hard disk storage
device.
After I set up QNX: when we use Vedit the navigation and control keys do
not
work. We get graphics characters displayed on the screen instead of the
cursor moving as directed (Up-Arrow, Down-Arrow, Left-Arrow, Right-Arrow,
Alt, etc.)
This very well may have been an existing problem even with the previous CPU
because we never used Vedit on the target then (Primarily because that
configuration used Flash for the disk device and editing files was not
fun.)
Now however, editing is moot as the DOC acts just like a disk drive…
I know I’v seen something similiar to this in the pastjust can’t recall the
cause/fix…
Any hints?
Regards,
Ray L.
P.S.
I installed QNX 4.24 then updated to 4.25, then 4.25D.
I have not upgraded Vedit to v5.05 or Vedit Plus (yet).
\
Jay:
This was all with con1
But: I fixed it.
The doc2000 boot image provided by QNX’s knowledge base had the TERM var set
to a Qansi, Vedit expects it to be set to qnx.
Just wish the Photon (separate article) install problem was this simple!!!
Thanx anyway y’all
Ray L.
“Jay Hogg” <Jay.Hogg@t-netix.com.r-e-m-o-v-e> wrote in message
news:9qs4u8$qis$1@inn.qnx.com…
Ray,
You didn’t specify if you are doing this on a console (vga+kbd), serial
terminal, or telnet? Below are console and telnet - serial gets rather
complicated.
Pick an emulation - QNX or QANSI
Console:
key: 'stty ’ Look at the protocol= value
0 = QNX 1=QANSI
stty protocol=1 will change it…
Telnet:
Make sure (1) your terminal emulator is running in QNX or QANSI
mode. I’ve had limited success with other emulations but have gotten
away with vt100 as long as it is not the windoze terminal emulator.
Make sure you are in 8-bit mode for QNX.
ALL:
key: 'export ’ Look at the TERM= value
it should be ‘qnx’ or ‘qansi’ – note case
export TERM=qnx or qansi to set if necessary
ls /usr/lib/terminfo/q
make sure you have a ‘qnx’ or ‘qansi’ terminal definition.
You can copy from another system or use tic to compile
the source file but you will get a lot more than you need.
Happy hunting,
Jay
Ray LaBrecque wrote in message <9qq45d$k3h$> 1@inn.qnx.com> >…
Greeetings:
I am setting up a replacement CPU for our target system. As far as I can
see
I am copying all required files to the target CPU using the manufacturer
instructions and our previous configuration as guides. The system we are
replacing is a Ziatech stand alone CPU which we have used for appr. 3
years
in this product (Ziatech has obsoleted this CPU). The new CPU is a
Versalogic PC 104 + stand alone with a DiskOnChip (DOC) storage device.
The
DOC is from all appearances an exact simulation of a hard disk storage
device.
After I set up QNX: when we use Vedit the navigation and control keys do
not
work. We get graphics characters displayed on the screen instead of the
cursor moving as directed (Up-Arrow, Down-Arrow, Left-Arrow, Right-Arrow,
Alt, etc.)
This very well may have been an existing problem even with the previous
CPU
because we never used Vedit on the target then (Primarily because that
configuration used Flash for the disk device and editing files was not
fun.)
Now however, editing is moot as the DOC acts just like a disk drive…
I know I’v seen something similiar to this in the pastjust can’t recall
the
cause/fix…
Any hints?
Regards,
Ray L.
P.S.
I installed QNX 4.24 then updated to 4.25, then 4.25D.
I have not upgraded Vedit to v5.05 or Vedit Plus (yet).
\
Jay:
This was all with con1
But: I fixed it.
The doc2000 boot image provided by QNX’s knowledge base had the TERM var set
to a Qansi, Vedit expects it to be set to qnx.
Just wish the Photon (separate article) install problem was this simple!!!
Thanx anyway y’all
Ray L.
“Jay Hogg” <Jay.Hogg@t-netix.com.r-e-m-o-v-e> wrote in message
news:9qs4u8$qis$1@inn.qnx.com…
Ray,
You didn’t specify if you are doing this on a console (vga+kbd), serial
terminal, or telnet? Below are console and telnet - serial gets rather
complicated.
Pick an emulation - QNX or QANSI
Console:
key: 'stty ’ Look at the protocol= value
0 = QNX 1=QANSI
stty protocol=1 will change it…
Telnet:
Make sure (1) your terminal emulator is running in QNX or QANSI
mode. I’ve had limited success with other emulations but have gotten
away with vt100 as long as it is not the windoze terminal emulator.
Make sure you are in 8-bit mode for QNX.
ALL:
key: 'export ’ Look at the TERM= value
it should be ‘qnx’ or ‘qansi’ – note case
export TERM=qnx or qansi to set if necessary
ls /usr/lib/terminfo/q
make sure you have a ‘qnx’ or ‘qansi’ terminal definition.
You can copy from another system or use tic to compile
the source file but you will get a lot more than you need.
Happy hunting,
Jay
Ray LaBrecque wrote in message <9qq45d$k3h$> 1@inn.qnx.com> >…
Greeetings:
I am setting up a replacement CPU for our target system. As far as I can
see
I am copying all required files to the target CPU using the manufacturer
instructions and our previous configuration as guides. The system we are
replacing is a Ziatech stand alone CPU which we have used for appr. 3
years
in this product (Ziatech has obsoleted this CPU). The new CPU is a
Versalogic PC 104 + stand alone with a DiskOnChip (DOC) storage device.
The
DOC is from all appearances an exact simulation of a hard disk storage
device.
After I set up QNX: when we use Vedit the navigation and control keys do
not
work. We get graphics characters displayed on the screen instead of the
cursor moving as directed (Up-Arrow, Down-Arrow, Left-Arrow, Right-Arrow,
Alt, etc.)
This very well may have been an existing problem even with the previous
CPU
because we never used Vedit on the target then (Primarily because that
configuration used Flash for the disk device and editing files was not
fun.)
Now however, editing is moot as the DOC acts just like a disk drive…
I know I’v seen something similiar to this in the pastjust can’t recall
the
cause/fix…
Any hints?
Regards,
Ray L.
P.S.
I installed QNX 4.24 then updated to 4.25, then 4.25D.
I have not upgraded Vedit to v5.05 or Vedit Plus (yet).
\