Honest opinions requested

I’m a relative newbie in QNX. I used QNX on a project a couple years back
and since then I have been using VxWorks, so the sum of QNX knowledge that I
possessed before (could have tattoed it on an ant’s butt), is basically
gone. I’m now looking to use RTP/Neutrino on a new project and I have two
questions:

  1. How embeddable is it with respect to running from flash/prom/eprom? The
    last project that I used QNX with, we booted from PCMCIA flash disk
    (emulating IDE). So that was no biggie. Burning it on a PROM was a little
    more intense, so we didn’t pursue it. On my new project, we really like to
    boot this system from PROM (space-based hardware, especially flash, gets
    chomped on by ionizing radiation), and we need it to boot quick.

  2. Finding newbie type of information online is frustrating, as attested by
    the flaming threads I’ve read in several groups. I’d like to buy a book on
    Neutrino and the one recommended on the QNX website is one by Krten. Is
    this a good book? Are there any better or supplemental books out there?

Thanks,
John

John Bowen wrote:

I’m a relative newbie in QNX. I used QNX on a project a couple years back
and since then I have been using VxWorks, so the sum of QNX knowledge that I
possessed before (could have tattoed it on an ant’s butt), is basically
gone. I’m now looking to use RTP/Neutrino on a new project and I have two
questions:

  1. How embeddable is it with respect to running from flash/prom/eprom? The
    last project that I used QNX with, we booted from PCMCIA flash disk
    (emulating IDE). So that was no biggie. Burning it on a PROM was a little
    more intense, so we didn’t pursue it. On my new project, we really like to
    boot this system from PROM (space-based hardware, especially flash, gets
    chomped on by ionizing radiation), and we need it to boot quick.

It is very embeddable. Better than QNX4 was. I’d suggest however to go
with PowerPC architecture, which means buying QNX4-hosted development
environment. You can do that stuff with x86 hardware too (I’ve seen a
little cute Pentium board booting Neutrino in 1 sec from power on) but
chances are you’ll have to arrange custom engineering work with QSSL
since x86 hardware sort of assumes presense of BIOS (and so does
‘regular’ Neutrino on x86). Intel has product to allow BIOS-less boot on
some of their PCI chipsets, you might want to look at it.

  1. Finding newbie type of information online is frustrating, as attested by
    the flaming threads I’ve read in several groups. I’d like to buy a book on
    Neutrino and the one recommended on the QNX website is one by Krten. Is
    this a good book? Are there any better or supplemental books out there?

Online docs are reasonably good although sometime little vague. Rob’s
book can help to understand some concepts but it can’t replace docs. Any
good generic book about modern OS design would be a good background
reading too. As for “newbie issue”, I’d suggest to get your hands on
system, play with it and cease to be a newbie as fast as you can :wink:

good luck,

  • igor

I have never tried using it in an embedded situation so I don’t know
about that.

Rob Krten’s book is very good and addresses many areas thoroughly. For
me it did not have enough low level data about the whole QNX system, but
it is a book primarily on Neutrino and programming with it rather than
using it :slight_smile:.

I have had some very helpful and very fast answers from both QNX and the
various newsgroups, but sometimes you get nothing. There is some useful
information on the web sites qnx.com and qnxstart.com

Best of luck for the new year !

Simon

In article <92deo0$cq1$1@inn.qnx.com>, John Bowen
<John.Bowen@grc.nasa.gov> writes

I’m a relative newbie in QNX. I used QNX on a project a couple years back
and since then I have been using VxWorks, so the sum of QNX knowledge that I
possessed before (could have tattoed it on an ant’s butt), is basically
gone. I’m now looking to use RTP/Neutrino on a new project and I have two
questions:

  1. How embeddable is it with respect to running from flash/prom/eprom? The
    last project that I used QNX with, we booted from PCMCIA flash disk
    (emulating IDE). So that was no biggie. Burning it on a PROM was a little
    more intense, so we didn’t pursue it. On my new project, we really like to
    boot this system from PROM (space-based hardware, especially flash, gets
    chomped on by ionizing radiation), and we need it to boot quick.

  2. Finding newbie type of information online is frustrating, as attested by
    the flaming threads I’ve read in several groups. I’d like to buy a book on
    Neutrino and the one recommended on the QNX website is one by Krten. Is
    this a good book? Are there any better or supplemental books out there?

Thanks,
John
\


Simon Wakley
Visit our web site at <<www.cameracontrol.com>>

“Igor Kovalenko” <Igor.Kovalenko@motorola.com> wrote in message
news:3A4A48CE.8FC3AFE3@motorola.com

John Bowen wrote:

I’m a relative newbie in QNX. I used QNX on a project a couple years
back
and since then I have been using VxWorks, so the sum of QNX knowledge
that I
possessed before (could have tattoed it on an ant’s butt), is basically
gone. I’m now looking to use RTP/Neutrino on a new project and I have
two
questions:

  1. How embeddable is it with respect to running from flash/prom/eprom?
    The
    last project that I used QNX with, we booted from PCMCIA flash disk
    (emulating IDE). So that was no biggie. Burning it on a PROM was a
    little
    more intense, so we didn’t pursue it. On my new project, we really like
    to
    boot this system from PROM (space-based hardware, especially flash, gets
    chomped on by ionizing radiation), and we need it to boot quick.


    It is very embeddable. Better than QNX4 was. I’d suggest however to go
    with PowerPC architecture, which means buying QNX4-hosted development
    environment. You can do that stuff with x86 hardware too (I’ve seen a
    little cute Pentium board booting Neutrino in 1 sec from power on) but
    chances are you’ll have to arrange custom engineering work with QSSL
    since x86 hardware sort of assumes presense of BIOS (and so does
    ‘regular’ Neutrino on x86). Intel has product to allow BIOS-less boot on
    some of their PCI chipsets, you might want to look at it.

I was considering a VME based PPC for one of the processors. My concept is

a distributed control system with a master (VME) and several slaves (maybe
PC/104 or EBX) communicating via ethernet. The slaves network boot from the
master using bootp. I’m glad to see it’s possible.

  1. Finding newbie type of information online is frustrating, as attested
    by
    the flaming threads I’ve read in several groups. I’d like to buy a book
    on
    Neutrino and the one recommended on the QNX website is one by Krten. Is
    this a good book? Are there any better or supplemental books out there?


    Any ideas where to find information like what should be contained in the

“System Administration Guide - Work in progress version” on the website? I
have to admit, I’ve been playing with it on a PC/104 system for a few days,
and the TBD’s were killing me in there.

Online docs are reasonably good although sometime little vague. Rob’s
book can help to understand some concepts but it can’t replace docs. Any
good generic book about modern OS design would be a good background
reading too. As for “newbie issue”, I’d suggest to get your hands on
system, play with it and cease to be a newbie as fast as you can > :wink:

good luck,

  • igor
    Thanks for your reply.

John

It’s very embeddable as Igor said. I’ve done an X86 implementation without a
BIOS, and it’s a piece of cake. The steps involved, for any architecture, are:

  1. Configure your chipset so you can access memory, I/O, and so on
  2. For X86, switch to protected mode
  3. Copy the startup image to RAM and verify the checksums
  4. Jump into the startup image

This can be made more or less complicated depending on whether or not you have
a linearly mapped ROM, or windowed ROM, and so on, but that’s the jist of it-
it’s very easy, and doesn’t use any BIOS calls whatsoever. You are of course
free to add as much hardware checking and diagnostics as you feel up to. You
simply stuff the data about how much RAM and what devices you’ve got into the
system page using the provided routines (you get source code for all of it with
the developer’s kit) and when you jump into the image it “just deals with it”.
Very, very cool. My 486/33 boot image, which contains the kernel, a couple of
shared objects, serial driver, the command shell and two or three utilities
(pidin, ls, and so on) takes up ~388K in a FLASH device, including the reset
vector code.

The best info source I’ve found is the System Architecture guide. It gives you
a pretty good idea of how the O.S. is put together, and Rob’s book is extremely
helpful for some of the higher level concepts of resource managers and
multi-threading in general. There is no substitute for installing the RtP and
playing with it, however, so read up then play on. You won’t be disappointed.

-Warren “I wouldn’t get on a Microschlock powered spacecraft” Peece



“John Bowen” <John.Bowen@grc.nasa.gov> wrote in message
news:92deo0$cq1$1@inn.qnx.com
| I’m a relative newbie in QNX. I used QNX on a project a couple years back
| and since then I have been using VxWorks, so the sum of QNX knowledge that I
| possessed before (could have tattoed it on an ant’s butt), is basically
| gone. I’m now looking to use RTP/Neutrino on a new project and I have two
| questions:
|
| 1. How embeddable is it with respect to running from flash/prom/eprom? The
| last project that I used QNX with, we booted from PCMCIA flash disk
| (emulating IDE). So that was no biggie. Burning it on a PROM was a little
| more intense, so we didn’t pursue it. On my new project, we really like to
| boot this system from PROM (space-based hardware, especially flash, gets
| chomped on by ionizing radiation), and we need it to boot quick.
|
| 2. Finding newbie type of information online is frustrating, as attested by
| the flaming threads I’ve read in several groups. I’d like to buy a book on
| Neutrino and the one recommended on the QNX website is one by Krten. Is
| this a good book? Are there any better or supplemental books out there?
|
| Thanks,
| John
|
|
|

Just to scare you a little, I know of several NT based systems used on the
Internation Space Station…

“Warren Peece” <warren@nospam.com> wrote in message
news:92djkh$fg2$1@inn.qnx.com

It’s very embeddable as Igor said. I’ve done an X86 implementation
without a
BIOS, and it’s a piece of cake. The steps involved, for any architecture,
are:

  1. Configure your chipset so you can access memory, I/O, and so on
  2. For X86, switch to protected mode
  3. Copy the startup image to RAM and verify the checksums
  4. Jump into the startup image

This can be made more or less complicated depending on whether or not you
have
a linearly mapped ROM, or windowed ROM, and so on, but that’s the jist of
it-
it’s very easy, and doesn’t use any BIOS calls whatsoever. You are of
course
free to add as much hardware checking and diagnostics as you feel up to.
You
simply stuff the data about how much RAM and what devices you’ve got into
the
system page using the provided routines (you get source code for all of it
with
the developer’s kit) and when you jump into the image it “just deals with
it”.
Very, very cool. My 486/33 boot image, which contains the kernel, a
couple of
shared objects, serial driver, the command shell and two or three
utilities
(pidin, ls, and so on) takes up ~388K in a FLASH device, including the
reset
vector code.

The best info source I’ve found is the System Architecture guide. It
gives you
a pretty good idea of how the O.S. is put together, and Rob’s book is
extremely
helpful for some of the higher level concepts of resource managers and
multi-threading in general. There is no substitute for installing the RtP
and
playing with it, however, so read up then play on. You won’t be
disappointed.

-Warren “I wouldn’t get on a Microschlock powered spacecraft” Peece



“John Bowen” <> John.Bowen@grc.nasa.gov> > wrote in message
news:92deo0$cq1$> 1@inn.qnx.com> …
| I’m a relative newbie in QNX. I used QNX on a project a couple years
back
| and since then I have been using VxWorks, so the sum of QNX knowledge
that I
| possessed before (could have tattoed it on an ant’s butt), is basically
| gone. I’m now looking to use RTP/Neutrino on a new project and I have
two
| questions:
|
| 1. How embeddable is it with respect to running from flash/prom/eprom?
The
| last project that I used QNX with, we booted from PCMCIA flash disk
| (emulating IDE). So that was no biggie. Burning it on a PROM was a
little
| more intense, so we didn’t pursue it. On my new project, we really like
to
| boot this system from PROM (space-based hardware, especially flash, gets
| chomped on by ionizing radiation), and we need it to boot quick.
|
| 2. Finding newbie type of information online is frustrating, as attested
by
| the flaming threads I’ve read in several groups. I’d like to buy a book
on
| Neutrino and the one recommended on the QNX website is one by Krten. Is
| this a good book? Are there any better or supplemental books out there?
|
| Thanks,
| John
|
|
|

“John Bowen” <John.Bowen@grc.nasa.gov> wrote in message
news:92dk1g$fhf$1@inn.qnx.com
| Just to scare you a little, I know of several NT based systems used on the
| Internation Space Station…

I’ll begin preparations for having it crash in my back yard… :slight_smile:

-Warren

Warren Peece wrote:

It’s very embeddable as Igor said. I’ve done an X86 implementation without a
BIOS, and it’s a piece of cake. The steps involved, for any architecture, are:

  1. Configure your chipset so you can access memory, I/O, and so on
  2. For X86, switch to protected mode
  3. Copy the startup image to RAM and verify the checksums
  4. Jump into the startup image

This can be made more or less complicated depending on whether or not you have
a linearly mapped ROM, or windowed ROM, and so on, but that’s the jist of it-
it’s very easy, and doesn’t use any BIOS calls whatsoever.

You make it sound real simple Warren, but it might not be all that piece
of cake it you have to deal with PCI devices. Worse yet if you have
chain of different bridges with multiply PCI buses. And then there is
USB… Go cook that cake then tell us :slight_smile:

  • igor

“Igor Kovalenko” <Igor.Kovalenko@motorola.com> wrote in message
news:3A4A56C8.CD7055C2@motorola.com
| Warren Peece wrote:
| >
| > It’s very embeddable as Igor said. I’ve done an X86 implementation without
a
| > BIOS, and it’s a piece of cake. The steps involved, for any architecture,
are:
| >
| > 1) Configure your chipset so you can access memory, I/O, and so on
| > 2) For X86, switch to protected mode
| > 3) Copy the startup image to RAM and verify the checksums
| > 4) Jump into the startup image
| >
| > This can be made more or less complicated depending on whether or not you
have
| > a linearly mapped ROM, or windowed ROM, and so on, but that’s the jist of
it-
| > it’s very easy, and doesn’t use any BIOS calls whatsoever.
|
| You make it sound real simple Warren, but it might not be all that piece
| of cake it you have to deal with PCI devices. Worse yet if you have
| chain of different bridges with multiply PCI buses. And then there is
| USB… Go cook that cake then tell us :slight_smile:
|
| - igor

True, it can get more complicated. However I was assuming that an embedded
device would be small (I wasn’t thinking VME at all), and any PCI devices would
be “well known” by the programmer and therefor fairly easily configured. We’re
putting together an AMD SC520 based box now, which will have PCI devices on it,
so I’ll be able to speak to the configuration with more authority in the near
future. Do you not have those very same issues with PPC hardware?

USB is a whole new upside-down layer cake, and I’d tend to shy away from it
until it gets a bit more support from the QNX folks. I can’t see it being a
show-stopper, although I admit it would be a lot easier if someone else did all
of the coding for you. You bake the cake, I’ll bring the frosting!

-Warren “have your cake, and eat it too” Peece

Warren Peece wrote:

True, it can get more complicated. However I was assuming that an embedded
device would be small (I wasn’t thinking VME at all), and any PCI devices would
be “well known” by the programmer and therefor fairly easily configured. We’re
putting together an AMD SC520 based box now, which will have PCI devices on it,
so I’ll be able to speak to the configuration with more authority in the near
future. Do you not have those very same issues with PPC hardware?

You do. However, it is ‘normal’ for PPC to not have BIOS so QSSL did a
lot of work to support specific PPC reference boards. For example they
have customized startup-xxx and pci-xxx for many different
chipsets/boards. With x86 you’d have to do that yourself or pay them for
custom work since it is failry ‘uncommon’.

USB is a whole new upside-down layer cake, and I’d tend to shy away from it
until it gets a bit more support from the QNX folks. I can’t see it being a
show-stopper, although I admit it would be a lot easier if someone else did all
of the coding for you. You bake the cake, I’ll bring the frosting!

-Warren “have your cake, and eat it too” Peece

Bon appetite.

  • igor

Previously, John Bowen wrote in qdn.public.qnxrtp.os:

  1. How embeddable is it with respect to running from flash/prom/eprom?

Very.

  1. Finding newbie type of information online is frustrating, as attested by
    the flaming threads I’ve read in several groups. I’d like to buy a book on
    Neutrino and the one recommended on the QNX website is one by Krten. Is
    this a good book? Are there any better or supplemental books out there?

I’ve read Roberts book and I can recommend it. I don’t think that there are
any other 3rd party books out yet. The Neutrino 2.0 documentation is also
worth looking at.


Mitchell Schoenbrun --------- maschoen@pobox.com

John Bowen (John.Bowen@grc.nasa.gov) wrote:
: I’m a relative newbie in QNX. I used QNX on a project a couple years back
: and since then I have been using VxWorks, so the sum of QNX knowledge that I
: possessed before (could have tattoed it on an ant’s butt), is basically
: gone. I’m now looking to use RTP/Neutrino on a new project and I have two
: questions:

: 1. How embeddable is it with respect to running from flash/prom/eprom? The
: last project that I used QNX with, we booted from PCMCIA flash disk
: (emulating IDE). So that was no biggie. Burning it on a PROM was a little
: more intense, so we didn’t pursue it. On my new project, we really like to
: boot this system from PROM (space-based hardware, especially flash, gets
: chomped on by ionizing radiation), and we need it to boot quick.

: 2. Finding newbie type of information online is frustrating, as attested by
: the flaming threads I’ve read in several groups. I’d like to buy a book on
: Neutrino and the one recommended on the QNX website is one by Krten. Is
: this a good book? Are there any better or supplemental books out there?

My book is both the best and the worst out there :slight_smile:
Seriously though, my book, as mentioned in other posts, won’t help you too
much with newbie types of questions. It was written pre-QRTP, so addresses
more of the “programming” types of questions – threads, message passing,
resource managers, etc. It doesn’t address any of the installation or embedding
questions that you might have. You can take a look at the table of contents
at www.parse.com, and there’s also a sample chapter online there to give you
a feel for the style.

Cheers,
-RK

Robert Krten, PARSE Software Devices; email my initials at parse dot com
Consulting, Systems Architecture / Design, Drivers, Training, QNX 4 & Neutrino
Check out our new QNX 4 and Neutrino (QRTP) books at http://www.parse.com/
Wanted PDP-8/9/10/11/12 Systems/documentation/spare parts! Will trade books!

I neglected to mention that we already own a 4.24 license with Watcom 10.6.
Can somebody explain to me why I would junk it and go to RTP? Granted,
Watcom as an IDE is concerned, well um…sucks, but it’s way easier than
using GNU. Is the only advantage of RTP that it is free, or am I just
missing something?

call me cynical, but it appears as far as RTOS’s are concerned, nothing is
free…

John

“John Bowen” <John.Bowen@grc.nasa.gov> wrote in message
news:92deo0$cq1$1@inn.qnx.com

I’m a relative newbie in QNX. I used QNX on a project a couple years back
and since then I have been using VxWorks, so the sum of QNX knowledge that
I
possessed before (could have tattoed it on an ant’s butt), is basically
gone. I’m now looking to use RTP/Neutrino on a new project and I have two
questions:

  1. How embeddable is it with respect to running from flash/prom/eprom?
    The
    last project that I used QNX with, we booted from PCMCIA flash disk
    (emulating IDE). So that was no biggie. Burning it on a PROM was a
    little
    more intense, so we didn’t pursue it. On my new project, we really like
    to
    boot this system from PROM (space-based hardware, especially flash, gets
    chomped on by ionizing radiation), and we need it to boot quick.

  2. Finding newbie type of information online is frustrating, as attested
    by
    the flaming threads I’ve read in several groups. I’d like to buy a book
    on
    Neutrino and the one recommended on the QNX website is one by Krten. Is
    this a good book? Are there any better or supplemental books out there?

Thanks,
John

“John Bowen” <John.Bowen@grc.nasa.gov> wrote in message
news:92irdm$epj$1@inn.qnx.com

I neglected to mention that we already own a 4.24 license with Watcom
10.6.
Can somebody explain to me why I would junk it and go to RTP? Granted,
Watcom as an IDE is concerned, well um…sucks, but it’s way easier than
using GNU. Is the only advantage of RTP that it is free, or am I just
missing something?

You had mentioned that you wanted to use a PPC. QNX4 only supports x86; if
you want PPC you have to go to RtP. Besides that, there are many reasons
to go to RtP (true .dll’s, pthreads, routable deterministic network,
per-connection QoS for network, etc, etc).

As far as IDE, there are some very nice (free) IDE’s available for unix
platforms.

call me cynical, but it appears as far as RTOS’s are concerned, nothing is
free…

RtP is definately not free. It is free for non-commercial use. Even though
Nasa is a government agency, I am sure that (except for purposes of
evaluation) your use of RtP would qualify as commercial use, under the RtP
license…

“John Bowen” <John.Bowen@grc.nasa.gov> wrote in message
news:92irdm$epj$1@inn.qnx.com
| I neglected to mention that we already own a 4.24 license with Watcom 10.6.
| Can somebody explain to me why I would junk it and go to RTP? Granted,
| Watcom as an IDE is concerned, well um…sucks, but it’s way easier than
| using GNU. Is the only advantage of RTP that it is free, or am I just
| missing something?
|
| call me cynical, but it appears as far as RTOS’s are concerned, nothing is
| free…
|
| John

To add to the aforementioned list of advantages of QNX6 (RtP) over QNX4 (please
forgive me if I duplicate a few):

SMP capable, published network and soon to be disk driver interfaces, soon to
be >4G memory capable (get on it, guys! :wink:, better GUI (QNX4 will not support
Photon 2.X), more hardware and software support due to the new architecture and
the fact that it’s free so a zillion people will be porting stuff, more
attention from QNX staff as QNX4 goes into “support” mode, routable native
network protocol…

I bet there’s more. Basically you need to look at it this way, you should be
making the move to QNX6 unless you have overwhelming circumstances requiring
you to stick with QNX4. Just like making the switch from WordImperfect to
MicroSchlock Turd, there’s going to be a learning curve that makes people want
to stick with what they know. Both options have their advantages and
disadvantages, but not quite being up to speed with one is not the most solid
reason in the world to stick with the other.

In case those reasons aren’t enough for you, I’ll try a different tact…

Isn’t NASA supposed to be forward-thinking? Embrace change! Abandon stagnated
viewpoints! Don’t become like people in the concrete industry who are mixed up
and set in their ways!

-Warren “give 'em both barrels” Peece

John Bowen wrote:

I neglected to mention that we already own a 4.24 license with Watcom 10.6.
Can somebody explain to me why I would junk it and go to RTP? Granted,
Watcom as an IDE is concerned, well um…sucks, but it’s way easier than
using GNU. Is the only advantage of RTP that it is free, or am I just
missing something?

THREAD support … SMP … 99.5% compatibility to
the GNU environment.
QNX RTP + a stable working Xphoton (or XFree86)
open up the door to the huge
world of X apps

call me cynical, but it appears as far as RTOS’s are concerned, nothing is
free…

It’s only ‘free’ as long as you think your time
and work have no value :slight_smile:

Armin

“Warren Peece” <warren@nospam.com> wrote in message
news:92jgl9$pef$1@inn.qnx.com

“John Bowen” <> John.Bowen@grc.nasa.gov> > wrote in message
news:92irdm$epj$> 1@inn.qnx.com> …
| I neglected to mention that we already own a 4.24 license with Watcom
10.6.
| Can somebody explain to me why I would junk it and go to RTP? Granted,
| Watcom as an IDE is concerned, well um…sucks, but it’s way easier than
| using GNU. Is the only advantage of RTP that it is free, or am I just
| missing something?
|
| call me cynical, but it appears as far as RTOS’s are concerned, nothing
is
| free…
|
| John

To add to the aforementioned list of advantages of QNX6 (RtP) over QNX4
(please
forgive me if I duplicate a few):

SMP capable, published network and soon to be disk driver interfaces, soon
to
be >4G memory capable (get on it, guys! > :wink:> , better GUI (QNX4 will not
support
Photon 2.X), more hardware and software support due to the new
architecture and
the fact that it’s free so a zillion people will be porting stuff, more
attention from QNX staff as QNX4 goes into “support” mode, routable native
network protocol…

I bet there’s more. Basically you need to look at it this way, you should
be
making the move to QNX6 unless you have overwhelming circumstances
requiring
you to stick with QNX4. Just like making the switch from WordImperfect to
MicroSchlock Turd, there’s going to be a learning curve that makes people
want
to stick with what they know. Both options have their advantages and
disadvantages, but not quite being up to speed with one is not the most
solid
reason in the world to stick with the other.

I don’t doubt that RTP is a good OS. From what I’ve seen it’s exactly as

advertised. But I’m really hesitant about dropping money on compilers and
IDEs. When the latest ANSI C++ standard was issued (exceptions, RTTI and
such) a dozen companies claimed compliance, but of course after thousands of
dollars and countless lives lost, we abandoned them and licked our wounds.
Needless to say, I am always skeptical now.

In case those reasons aren’t enough for you, I’ll try a different tact…

Isn’t NASA supposed to be forward-thinking? Embrace change! Abandon
stagnated
viewpoints! Don’t become like people in the concrete industry who are
mixed up
and set in their ways!

Man, you don’t want to get me started on what a screwed up place NASA is. I

could go on a rant that might last for days…

-Warren “give 'em both barrels” Peece

John,

Any ideas where to find information like what should be
contained in the
“System Administration Guide - Work in progress version”
on the website? I
have to admit, I’ve been playing with it on a PC/104
system for a few days,
and the TBD’s were killing me in there.

Have I included headings or comments to eventually cover the
info you are looking for? If not, let me know what questions
you thought should be answered and I’ll do my best to
include the info.

Regards,
Dave.


Dave Whelan, Technical Writer
QNX Software Systems Ltd.

Hello John,

John Bowen wrote:

[ clip …]

I don’t doubt that RTP is a good OS. From what I’ve seen it’s exactly as
advertised. But I’m really hesitant about dropping money on compilers and
IDEs.

I don’t see any problems with the GNU compilers
… you can absolutely flawless recompile huge
software packages like XFree86 and others. And
regarding IDEs, the door is open for ports of
different open source IDEs like GDE (done), vdk
builder (done), SourceNavigator (done from others)
and e.g. KDEvelop a.s.o … and if the base
libraries are available it is really just a
recompile!

That’s exactly our experiences …

When the latest ANSI C++ standard was issued (exceptions, RTTI and
such) a dozen companies claimed compliance, but of course after thousands of
dollars and countless lives lost, we abandoned them and licked our wounds.
Needless to say, I am always skeptical now.

I don’t believe that this is an issue for QNX RTP.

Armin

I agree with (I think) John. I haven’t yet seen a GNU C++ compiler that did
everything right. I.E. exceptions, RTTI and such.

Armin Steinhoff <A-Steinhoff@web_.de> wrote in message
news:3A539392.A7844567@web_.de…

Hello John,

John Bowen wrote:

[ clip …]

I don’t doubt that RTP is a good OS. From what I’ve seen it’s exactly
as
advertised. But I’m really hesitant about dropping money on compilers
and
IDEs.

I don’t see any problems with the GNU compilers
… you can absolutely flawless recompile huge
software packages like XFree86 and others. And
regarding IDEs, the door is open for ports of
different open source IDEs like GDE (done), vdk
builder (done), SourceNavigator (done from others)
and e.g. KDEvelop a.s.o … and if the base
libraries are available it is really just a
recompile!

That’s exactly our experiences …

When the latest ANSI C++ standard was issued (exceptions, RTTI and
such) a dozen companies claimed compliance, but of course after
thousands of
dollars and countless lives lost, we abandoned them and licked our
wounds.
Needless to say, I am always skeptical now.

I don’t believe that this is an issue for QNX RTP.

Armin