Define slow. Provide numbers.
Out of the box (so to speak) QNX6 is slower than QNX4. But there are many
things that can be doen to tweak it. The problem is that QSSL has provided
a system that will work on (almost) any hardware configuration. As such it
includes many generalities.
Here are some things to look for:
- to speed up the boot process, check each command line that utimately get
loaded and build a custom boot image that loads those exact commands. That
will save QNX from having to determine your hardware when it starts up.
- Put it on it’s own file system, not hosted on the Windows file system.
- When you have upgraded to all of the exact software that you intend to
use, get rid of the package file system and store all of the files you need
Other issues that you can not help for now are caused by the gcc compiler.
Compared to the Watcom compiler for QNX4 it is slow, fat and ugly. And it
produces code that is slow fat and ugly. I am hopful that the compiler will
get upgraded sometime soon.
On the plus side, QNX6 does embed quite nicely. By generating a system that
does exactly what you need it to do and nothing else, I’m sure you’ll find
that it is plenty fast enough and compact enough.
If I can be of any help in customizing you OS please let me know.
Bill Caroselli – 1(530) 510-7292
“Jeff Anderson” <firstname.lastname@example.org> wrote in message
I just finally got qnx installed on my good ole testing machine - pentium
100, 32 Mb RAM, 700MB HDD, CD etc. Two problems - everything is
slow. is this just how it is or am i missing something. secondly, i am
experimenting with qnx as a possible OS for a pc104 based car computer. i
want to be able to do gs displays and maybe a little fuel injection work
later. So how is it that i scale all this down so it fits on a flash card
and runs quickly? I dont really know that much at all about architecture
embedded os’s, but any pointers in the right direction would be much