Look also at http://www.be.com - they posted an article comparing
feature sets of different internet applicances, using different OSes
(including iOpener, based on QNX4) with BeIA solution. They of course
call QNX4 just ‘QNX’ and since most people think that QNX RTP is ‘QNX’
it might really damage perception of system. ‘Oh, it does not support
Macromedia, Java, RealPlayer, any streaming media, what a poor
I think QSSL should let Be know that they should not use name ‘QNX’ in
such indiscriminate manner. They do discriminate between versions of
WinCE after all. They could include Audrey into comparision too, or QSSL
could make their own comparision and publish it
And QSSL should try to deliver the message to public that QNXRTP is ‘New
QNX’. That is very tough task in practice and perhaps a better approach
would be to have a distinctive name. Now, ‘Realtime Platform’ in NOT a
name, it is ‘distribution type’ at best. And ‘QNXRTP’ in not a name
either because people don’t like names consisting of 6 consonants
(remember, PCMCIA = People Can’t Memorize Computer Industry Acronyms).
I’ve told that already, but will repeat - ‘QNX Neutrino’ is a much
better name and we still can have ‘QNX Neutrino OEM’ and ‘QNX Neutrino
RTP’, which would clear most of confusion. This naming scheme should be
applied consistently and pervasively.
Zeljko Fucek wrote:
I think that the current QSSL’s OS naming convention seems to be very
confusing for anyone having the first contact with different QNX OS
flavours. Now, it is just “QNX” on Tucows…
Unless, it is deliberately done so: “QNX” is here to stay purely from the
historical reasons, and it will (hopefully) successfully represent future
“Debbie Kane” <> firstname.lastname@example.org> > wrote in message
news:8t4p3q$ao$> email@example.com> …
If you’re writing or porting an application for the QNX
realtime platform (RTP), here’s your chance to distribute it
to the worldwide community of RTP users.
Starting immediately, Tucows – the largest distributor of
software on the Internet – is taking submissions for their
new library of QNX RTP software.
Once the library is up and running, all RTP applications
accepted by Tucows will be distributed across the Tucows
network, which totals over 4000 service providers worldwide.
Just imagine… once your software is accepted, it will
be immediately accessible to every RTP user and developer.
There’s no better way to target the fast-growing QNX RTP
community – over 350,000 downloads at last count!
What kind of software can you submit?
You can submit freeware, shareware, adware, demoware,
and so on. Tucows can also provide an e-commerce solution
if you’d like to distribute a commercial version of your
Submitting is easy
To submit your application, visit the Tucows submit
center at > http://submit.tucows.com> , click on QNX, and fill
in the information requested.
Within days, Tucows will review your submission and
inform you whether it has been accepted.
Get in on the ground floor
The fact that Tucows is already building a QNX library –
just weeks after the RTP launch – is a testament to how
quickly the QNX realtime platform is gaining momentum. Now’s
the time to establish your application as a standard among
RTP users. So submit as soon as possible!
The best of luck with your submission and thanks again
for choosing the QNX realtime platform.