Hi,
will the 6.1 release support internationnal keyboards on text consoles ?
Do we have any idea of the release date ?
Thanks
Arnauld Disableu
In 6.1 this feature has been not implemented yet. Should be done in one of
the next versions (mayby 6.1.1).
“Arnauld Disableu” <arnauld@disableu.net> wrote in message
news:9gt504$blu$1@inn.qnx.com…
Hi,
will the 6.1 release support internationnal keyboards on text consoles ?
Do we have any idea of the release date ?Thanks
Arnauld Disableu
We downloaded the free QNX RTP and have been using it to prototype an
application. If we can get the prototype working satisfactorily, then I
guess we’ll buy the real thing. We have some questions at this point though:
-
What is the difference between the free NC version and the real
commercial version. We have 6.0 beta w/ patch A. Since, I have seen
references to patch B, patch C, and now 6.1. Patch B we downloaded from
the tucows site. We have, however, had no success getting it to install.
And I don’t see patch C or 6.1 available to the public anywhere. -
Timing. We’ve played with other RTOSes such as VxWorks, RTLinux, and
(my favorite) RTAI-Linux. In all of those you can make the timing
resolution much less than 500 micros. In particular it is periodic tasks
that are bugging me. I had heard that there were rumours that this was
discussed on this or another list some time in the past and that RTP
might be lifting that restriction. I want to be able to “reliably” run
periodic tasks at 100 micros. -
- Is anyone else doing Firewire stuff with QNX? I’m curious what
kind of results they’re getting. The driver we’re using (one for a
MindReady card) is chewing up some serious cycles. The bandwidth is not
that high, but it accounts for more than 60% of our app time!
- Is anyone else doing Firewire stuff with QNX? I’m curious what
–
Travis Griggs (a.k.a. Lord of the Fries)
Member: 3rd Boolean State Software Collective
Key Technology
“It had better be a pretty good meeting to be better than no meeting at
all”-- Boyd K. Packer
“Travis Griggs” <tgriggs@keyww.com> wrote in message
news:3B32552D.5090203@keyww.com…
We downloaded the free QNX RTP and have been using it to prototype an
application. If we can get the prototype working satisfactorily, then I
guess we’ll buy the real thing. We have some questions at this point
though:
- What is the difference between the free NC version and the real
commercial version.
None
We have 6.0 beta w/ patch A. Since, I have seen
references to patch B, patch C, and now 6.1. Patch B we downloaded from
the tucows site. We have, however, had no success getting it to install.
And I don’t see patch C or 6.1 available to the public anywhere.
6.1 isn’t out yet.
You can get patch B/C from the package manager.
- Timing. We’ve played with other RTOSes such as VxWorks, RTLinux, and
(my favorite) RTAI-Linux. In all of those you can make the timing
resolution much less than 500 micros. In particular it is periodic tasks
that are bugging me. I had heard that there were rumours that this was
discussed on this or another list some time in the past and that RTP
might be lifting that restriction. I want to be able to “reliably” run
periodic tasks at 100 micros.
Didn’t hear about this for 6.1.
- Is anyone else doing Firewire stuff with QNX? I’m curious what
kind of results they’re getting. The driver we’re using (one for a
MindReady card) is chewing up some serious cycles. The bandwidth is not
that high, but it accounts for more than 60% of our app time!
–
Travis Griggs (a.k.a. Lord of the Fries)
Member: 3rd Boolean State Software Collective
Key Technology
“It had better be a pretty good meeting to be better than no meeting at
all”-- Boyd K. Packer
Mario Charest wrote:
We have 6.0 beta w/ patch A. Since, I have seen
references to patch B, patch C, and now 6.1. Patch B we downloaded from
the tucows site. We have, however, had no success getting it to install.
And I don’t see patch C or 6.1 available to the public anywhere.
6.1 isn’t out yet.You can get patch B/C from the package manager.
I don’t have an external network connection with the QNX machine. I
downloaded the tucows patch B files to a windows box that does, then
ftp’ed them over to the QNX box. I forget what weird incantations I had
to do to get the package manager to see the various files, but even when
it saw them it had missing files (Patch B Essentials, or something like
that). I did manage to use the package manager to install spin… I was
missing something like top, I’m glad to have this.
–
Travis Griggs (a.k.a. Lord of the Fries)
Member: 3rd Boolean State Software Collective
Key Technology
“It had better be a pretty good meeting to be better than no meeting at
all”-- Boyd K. Packer
Hi,
Travis Griggs <tgriggs@keyww.com> wrote in article
<3B326DFC.6060106@keyww.com>…
Mario Charest wrote:
We have 6.0 beta w/ patch A. Since, I have seen
references to patch B, patch C, and now 6.1. Patch B we downloaded
from
the tucows site. We have, however, had no success getting it to
install.
And I don’t see patch C or 6.1 available to the public anywhere.
6.1 isn’t out yet.You can get patch B/C from the package manager.
I don’t have an external network connection with the QNX machine. I
downloaded the tucows patch B files to a windows box that does, then
ftp’ed them over to the QNX box.
You can download patch B/C from QSS WWW Repository
URL: http://packages.qnx.com/repository2/
The files for patch B are:
binutils-core-2.9.1B-x86.qpk
binutils-core-2.9.1B-x86.qpm
binutils-core-2.9.1B.qpk
binutils-core-2.9.1B.qpm
binutils-core_x86-2.9.1B-x86.qpk
binutils-core_x86-2.9.1B-x86.qpm
binutils-core_x86-2.9.1B.qpk
binutils-core_x86-2.9.1B.qpm
cdrom.qrm
content.tgz
ftp.qrm
index
os-core-2.1.1B-x86.qpk
os-core-2.1.1B-x86.qpm
os-core-2.1.1B.qpk
os-core-2.1.1B.qpm
os-dev-2.1.1B.qpk
os-dev-2.1.1B.qpm
os-devdoc-2.1.1B.qpk
os-devdoc-2.1.1B.qpm
os-dev_x86-2.1.1B.qpk
os-dev_x86-2.1.1B.qpm
os-drivers-2.1.1B-x86.qpk
os-drivers-2.1.1B-x86.qpm
os-drivers-2.1.1B.qpk
os-drivers-2.1.1B.qpm
os-rundoc-2.1.1B.qpk
os-rundoc-2.1.1B.qpm
ph-dev-2.0.1B.qpk
ph-dev-2.0.1B.qpm
ph-devdoc-2.0.1B.qpk
ph-devdoc-2.0.1B.qpm
ph-devtools-2.0.1B-x86.qpk
ph-devtools-2.0.1B-x86.qpm
ph-devtools-2.0.1B.qpk
ph-devtools-2.0.1B.qpm
ph-dev_x86-2.0.1B.qpk
ph-dev_x86-2.0.1B.qpm
ph-drivers-2.0.1B-x86.qpk
ph-drivers-2.0.1B-x86.qpm
ph-drivers-2.0.1B.qpk
ph-drivers-2.0.1B.qpm
ph-runtime-2.0.1B-x86.qpk
ph-runtime-2.0.1B-x86.qpm
ph-runtime-2.0.1B.qpk
ph-runtime-2.0.1B.qpm
repository.qrm
bundles-qnx-6.0B-x86.qpk
bundles-qnx-6.0B-x86.qpm
bundles-qnx-dev-6.0B-x86.qpk
bundles-qnx-dev-6.0B-x86.qpm
bundles-qnx-devtools-6.0B-x86.qpk
bundles-qnx-devtools-6.0B-x86.qpm
bundles-rp7-1.0B-x86.qpk
bundles-rp7-1.0B-x86.qpm
The files for patch C are:
bundles-qnx-dev-6.0C-x86.qpk
bundles-qnx-6.0C-x86.qpk
bundles-qnx-6.0C-x86.qpm
ph-runtime-2.0.1C-x86.qpk
bundles-qnx-dev-6.0C-x86.qpm
ph-dev_x86-2.0.1C.qpm
ph-drivers-2.0.1C-x86.qpk
ph-drivers-2.0.1C-x86.qpm
ph-drivers-2.0.1C.qpk
ph-drivers-2.0.1C.qpm
ph-dev_x86-2.0.1C.qpk
ph-runtime-2.0.1C-x86.qpm
ph-runtime-2.0.1C.qpk
ph-runtime-2.0.1C.qpm
Save them in temporary directory on your QNX machine.
In package manager add repository and enter
URL: /path to your temp dir
Repository name: something
I have installed patches B and C in this way.
Regards,
Eduard.