how come none of the big news services such as ZDNET and CMPNet have covered
the launch of the QNX RTP?
Looks like slashdot is the only (major) place that it is mentioned.
Does this mean the world doesn;t care about RTP or does it mean that QSSL’s
PR company failed to get the attention of the right people in the media?
Disappointing.
Andrew
Andrew <NOastuart@mira.netspam> wrote:
: how come none of the big news services such as ZDNET and CMPNet have covered
: the launch of the QNX RTP?
We have contacted them so I guess they don’t feel it’s
newsworthy. Maybe if people keeping using and talking
about QNX it will hit their radar.
: Looks like slashdot is the only (major) place that it is mentioned.
: Does this mean the world doesn;t care about RTP or does it mean that QSSL’s
: PR company failed to get the attention of the right people in the media?
: Disappointing.
: Andrew
Other than these newsgroups where can we raise attention - as enthusiastic
users/developers ?
Steve Tomkins wrote:
Andrew <> NOastuart@mira.netspam> > wrote:
: how come none of the big news services such as ZDNET and CMPNet have covered
: the launch of the QNX RTP?We have contacted them so I guess they don’t feel it’s
newsworthy. Maybe if people keeping using and talking
about QNX it will hit their radar.: Looks like slashdot is the only (major) place that it is mentioned.
: Does this mean the world doesn;t care about RTP or does it mean that QSSL’s
: PR company failed to get the attention of the right people in the media?: Disappointing.
: Andrew
Ken Recchia <rectech@nctimes.net> wrote:
Other than these newsgroups where can we raise attention - as enthusiastic
users/developers ?
Contact these big news services as users/developers… 
Chris
Steve Tomkins wrote:
Andrew <> NOastuart@mira.netspam> > wrote:
: how come none of the big news services such as ZDNET and CMPNet have covered
: the launch of the QNX RTP?We have contacted them so I guess they don’t feel it’s
newsworthy. Maybe if people keeping using and talking
about QNX it will hit their radar.: Looks like slashdot is the only (major) place that it is mentioned.
: Does this mean the world doesn;t care about RTP or does it mean that QSSL’s
: PR company failed to get the attention of the right people in the media?: Disappointing.
: Andrew
Previously, Andrew wrote in qdn.public.qnxrtp.advocacy:
how come none of the big news services such as ZDNET and CMPNet have covered
the launch of the QNX RTP?
ZDNet probably won’t cover it until they are forced to, by competition,
because they are so dependent on microsoft for advertising revenue.
[…]
maybe i need to come over to Canada and get a job as your head of RTP
marketing and sort things out
andrew
Other than these newsgroups where can we raise attention - as enthusiastic
users/developers ?
i managed to get Tony at http://www.theregister.co.uk to do a mention,
its a bit sparce, but thats Tony, he`s a Mac user at heart lol.
the reg is probably the most secretly read UK news site that the
large HW and OEM execs read, (had a very interesting chat about
their server logs a while back) intel, AMD, M$ and many more,
be sure that the RTP word is out in this regard.
i feel more work needs to done on the end user side, and thats were
the early takers, or path finders as gary P would call this collective,
it seem like a good idea to get over to theregister message board
(link of its main page, on the right) and start hammering away at the
keyboard there, and other such types of places, its clear that the
top execs are there, at the very least reading, sometimes chatting
under assumed names.
i beleave its always better to have 10 good end users that are willing
and actively going out of their way to find that one place or person
that can turn the tide, than a 1000+ ill tempered advocacy types
bashing away.
it might be a wise plan to search out the multimedia creation, gameing
sites and message boards as i do, keeping in mind that many influential
people read and actively use these places.
i expected a lot more end user talk by now in these places, given the
strenghs of this RealaTime OS being perfect for these types of things,
perhaps their just not understanding yet, perhaps we need to try harder.
the simple truth is this, if you want this RTP to become more than a
world class embedded developers OS, are you prepared to go out of your
way to help/educate the vast potential userbase out there, or are you
just going to sit around being ill tempered ?, i`d assume, if your here
and reading this text, your one of the former, and ready to get doing.
Steve Tomkins wrote:
Andrew <> NOastuart@mira.netspam> > wrote:
: how come none of the big news services such as ZDNET and CMPNet have
: covered the launch of the QNX RTP?We have contacted them so I guess they don’t feel it’s
newsworthy. Maybe if people keeping using and talking
about QNX it will hit their radar.: Looks like slashdot is the only (major) place that it is mentioned.
: Does this mean the world doesn;t care about RTP or does it mean that
: QSSL’s PR company failed to get the attention of the right people in the
: media?: Disappointing.
–
Paul May, Manchester, UK
Phoenix Core
Andrew wrote:
maybe i need to come over to Canada and get a job as your head of RTP
marketing and sort things out
Well … at first at first try to give that OS an IDENTITY
QNXRTP ?? QRTP? QNX6 as reported by uname ? QNX/Neutrino … or QNX ??
Confusing! At the end QSSL has introduced an OS … but not a PRODUCT
with a NAME!
Armin
The name of the product is QNX Reatlime Platform (QNX RTP)
The OS in the QNX RTP is QNX Neutrino.
The GUI for the QNX RTP is Photon.
…
I believe this is explained in the Welcome message when you first boot into
the QNX Realtime Platform, availalbe by clicking on the top right icon of
the Shelf.
-deb
<Armin@Steinhoff_.de> wrote in message
news:39DB7A92.2C8B7A3C@Steinhoff_.de…
Andrew wrote:
maybe i need to come over to Canada and get a job as your head of RTP
marketing and sort things out
Well … at first at first try to give that OS an IDENTITY >
QNXRTP ?? QRTP? QNX6 as reported by uname ? QNX/Neutrino … or QNX ??
Confusing! At the end QSSL has introduced an OS … but not a PRODUCT
with a NAME!Armin
This is sortof like calling SunOS Solaris. Solaris consists of SunOS and CDE.
Debbie Kane wrote:
The name of the product is QNX Reatlime Platform (QNX RTP)
The OS in the QNX RTP is QNX Neutrino.
The GUI for the QNX RTP is Photon.
…
I believe this is explained in the Welcome message when you first boot into
the QNX Realtime Platform, availalbe by clicking on the top right icon of
the Shelf.-deb
Armin@Steinhoff_.de> wrote in message
news:39DB7A92.2C8B7A3C@Steinhoff_.de…
Andrew wrote:maybe i need to come over to Canada and get a job as your head of RTP
marketing and sort things out
Well … at first at first try to give that OS an IDENTITY >
QNXRTP ?? QRTP? QNX6 as reported by uname ? QNX/Neutrino … or QNX ??
Confusing! At the end QSSL has introduced an OS … but not a PRODUCT
with a NAME!Armin
Debbie Kane wrote:
The name of the product is QNX Reatlime Platform (QNX RTP)
I would call it ‘product line’. QNX Realtime Platform isn’t a clear
‘name’ … my
understanding is that the core product of QSSL is a RTOS and not a
platform.
The meaning of ‘platform’ is too diffuse. So it would be nice to have
QNX2,
QNX4 … and Neutrino as the ‘operating environment’ for e.g a ‘Neutrino
RTP’.
The OS in the QNX RTP is QNX Neutrino.
The GUI for the QNX RTP is Photon.
Why not QNX Photon?? However … QSSL should not sell QNX +
‘something_else’.
Regards
Armin
…
I believe this is explained in the Welcome message when you first boot into
the QNX Realtime Platform, availalbe by clicking on the top right icon of
the Shelf.-deb
Armin@Steinhoff_.de> wrote in message
news:39DB7A92.2C8B7A3C@Steinhoff_.de…
Andrew wrote:maybe i need to come over to Canada and get a job as your head of RTP
marketing and sort things out
Well … at first at first try to give that OS an IDENTITY >
QNXRTP ?? QRTP? QNX6 as reported by uname ? QNX/Neutrino … or QNX ??
Confusing! At the end QSSL has introduced an OS … but not a PRODUCT
with a NAME!Armin
“J. Scott Franko” wrote:
This is sortof like calling SunOS Solaris. Solaris consists of SunOS and CDE.
Show my the name SunOS at the SOLARIS page … I see only ‘Solaris
Product Line’,
‘Solaris operating environment’, ‘Solaris 7’, ‘Solaris 8’ and so on …
Regards
Armin
Debbie Kane wrote:
The name of the product is QNX Reatlime Platform (QNX RTP)
The OS in the QNX RTP is QNX Neutrino.
The GUI for the QNX RTP is Photon.
…
I believe this is explained in the Welcome message when you first boot into
the QNX Realtime Platform, availalbe by clicking on the top right icon of
the Shelf.-deb
Armin@Steinhoff_.de> wrote in message
news:39DB7A92.2C8B7A3C@Steinhoff_.de…
Andrew wrote:maybe i need to come over to Canada and get a job as your head of RTP
marketing and sort things out
Well … at first at first try to give that OS an IDENTITY >
QNXRTP ?? QRTP? QNX6 as reported by uname ? QNX/Neutrino … or QNX ??
Confusing! At the end QSSL has introduced an OS … but not a PRODUCT
with a NAME!Armin
If you do a uname -a on solaris it doesn’t return solaris, instead it returns SunOS
or SunOS 5.5. If you do it on QRTP it returns QNX not QRTP. It should return NTO,
but thats a different story.
But what I was pointing out was that QSSL is being like sun. They have this unix
like OS that is the core thing they sell, but want to repackage it as something
else, so they add things like a new gui and call it the “platform”, or the
“operating environment”. Its all pakaging and marketing and targetting. The only
real difference is between QNX and NTO. The rest is packageing and targetting and
marketing.
Armin@Steinhoff_.de wrote:
“J. Scott Franko” wrote:
This is sortof like calling SunOS Solaris. Solaris consists of SunOS and CDE.
Show my the name SunOS at the SOLARIS page … I see only ‘Solaris
Product Line’,
‘Solaris operating environment’, ‘Solaris 7’, ‘Solaris 8’ and so on …Regards
Armin
Debbie Kane wrote:The name of the product is QNX Reatlime Platform (QNX RTP)
The OS in the QNX RTP is QNX Neutrino.
The GUI for the QNX RTP is Photon.
…
I believe this is explained in the Welcome message when you first boot into
the QNX Realtime Platform, availalbe by clicking on the top right icon of
the Shelf.-deb
Armin@Steinhoff_.de> wrote in message
news:39DB7A92.2C8B7A3C@Steinhoff_.de…
Andrew wrote:maybe i need to come over to Canada and get a job as your head of RTP
marketing and sort things out
Well … at first at first try to give that OS an IDENTITY >
QNXRTP ?? QRTP? QNX6 as reported by uname ? QNX/Neutrino … or QNX ??
Confusing! At the end QSSL has introduced an OS … but not a PRODUCT
with a NAME!Armin
In article <39DCBF63.E611F443@Steinhoff_.de>, <Armin@Steinhoff_.de> wrote:
“J. Scott Franko” wrote:
This is sortof like calling SunOS Solaris. Solaris consists of SunOS and CDE.
Show my the name SunOS at the SOLARIS page … I see only ‘Solaris
Product Line’,
‘Solaris operating environment’, ‘Solaris 7’, ‘Solaris 8’ and so on …
Yes, the messaging has been confused. I am more concerned about
the lack of differentiation between QNX demo disk and QNX RTP,
however, or that of QNX 4 products vs. RTP products on the web site.
I expect OEMs to not be too uncomfortable with
QNX RTP = QNX Neutrino + RTP Application Environment
(utils,package manager, etc.)
For you uname freaks:
Solaris:
%uname
SunOS
%uname -a
SunOS solaris4 5.8 Generic i86pc i386 i86pc
And nobody has heartburn over that.
Debbie Kane wrote:
The name of the product is QNX Reatlime Platform (QNX RTP)
The OS in the QNX RTP is QNX Neutrino.
The GUI for the QNX RTP is Photon.
…
I believe this is explained in the Welcome message when you first boot into
the QNX Realtime Platform, availalbe by clicking on the top right icon of
the Shelf.-deb
Armin@Steinhoff_.de> wrote in message
news:39DB7A92.2C8B7A3C@Steinhoff_.de…
Andrew wrote:maybe i need to come over to Canada and get a job as your head of RTP
marketing and sort things out
Well … at first at first try to give that OS an IDENTITY >
QNXRTP ?? QRTP? QNX6 as reported by uname ? QNX/Neutrino … or QNX ??
Confusing! At the end QSSL has introduced an OS … but not a PRODUCT
with a NAME!Armin
Steve Furr email: furr@qnx.com
QNX Software Systems, Ltd.
Steve Furr wrote:
Yes, the messaging has been confused. I am more concerned about
the lack of differentiation between QNX demo disk and QNX RTP,
however, or that of QNX 4 products vs. RTP products on the web site.I expect OEMs to not be too uncomfortable with
QNX RTP = QNX Neutrino + RTP Application Environment
(utils,package manager, etc.)For you uname freaks:
Solaris:
%uname
SunOS
%uname -a
SunOS solaris4 5.8 Generic i86pc i386 i86pc
solaris4 is the name of the machine is the above example, not the name of the OS or
the platform, or the environment, etc…
Its SunOS v5.8. I haven’t got a machine up and running with my newly purchased copy
of Solaris 8, so I did a uname -a on a machine at work and it comes out:
% uname -a
SunOS x.y.com 5.5 Generic_103094-20 i86pc i386 i86pc
the name of our machine in is x, in the y.com domain, and the OS is SunOS v5.5 (the
names have been changed to protect the innocent).
And nobody has heartburn over that.
But I do have heartburn over uname -a showing QNX for both QNX and NTO. Of course,
I’ve got antacids, and it is somewhat trivial, but I think some people might like to
call upon this info from within code to see which OS they are running in (I think its
been mentioned before). I suppose you could figure it out with the header files
#define’s, though.
Hi Scott,
“J. Scott Franko” wrote:
If you do a uname -a on solaris it doesn’t return solaris, instead it returns SunOS
or SunOS 5.5. If you do it on QRTP it returns QNX not QRTP. It should return NTO,
but thats a different story.
Yes … that’s a different story which has nothing to do with marketing
…
But what I was pointing out was that QSSL is being like sun. They have this unix
like OS that is the core thing they sell, but want to repackage it as something
else, so they add things like a new gui and call it the “platform”, or the
“operating environment”.
I like ‘operating environment’ more … it’s much clearer.
Its all pakaging and marketing and targetting.
Yes … and it is VERY important for a bussiness success.
The only real difference is between QNX and NTO.
No … currently we have to differenciate between:
QNX4, NTO 2.1 and QRTP 2.0 (not to mention that Augusta stuff)
QNX4 is completely different from the NTO product line.
NTO 2.1 comes with Photon 1.14 …
QRTP 2.0 uses Photon 2.0.
That means a PhAB application of NTO 2.1 is incompatible
with a PhAB application of QRTP 2.0.
NTO 2.1 supports x86, MIPS, PPC, H4 a.s.o …
QRTP 2.0 supports x86.
In the moment I feel like sitting on three different chairs
The rest is packageing and targetting and marketing.
Don’t underestimate that ‘rest’ !
Regards
Armin
Armin@Steinhoff_.de wrote:
“J. Scott Franko” wrote:
This is sortof like calling SunOS Solaris. Solaris consists of SunOS and CDE.
Show my the name SunOS at the SOLARIS page … I see only ‘Solaris
Product Line’,
‘Solaris operating environment’, ‘Solaris 7’, ‘Solaris 8’ and so on …Regards
Armin
Debbie Kane wrote:The name of the product is QNX Reatlime Platform (QNX RTP)
The OS in the QNX RTP is QNX Neutrino.
The GUI for the QNX RTP is Photon.
…
I believe this is explained in the Welcome message when you first boot into
the QNX Realtime Platform, availalbe by clicking on the top right icon of
the Shelf.-deb
Armin@Steinhoff_.de> wrote in message
news:39DB7A92.2C8B7A3C@Steinhoff_.de…
Andrew wrote:maybe i need to come over to Canada and get a job as your head of RTP
marketing and sort things out
Well … at first at first try to give that OS an IDENTITY >
QNXRTP ?? QRTP? QNX6 as reported by uname ? QNX/Neutrino … or QNX ??
Confusing! At the end QSSL has introduced an OS … but not a PRODUCT
with a NAME!Armin
Hi Steve,
Steve Furr wrote:
In article <39DCBF63.E611F443@Steinhoff_.de>, <Armin@Steinhoff_.de> wrote:
“J. Scott Franko” wrote:This is sortof like calling SunOS Solaris. Solaris consists of SunOS and CDE.
Show my the name SunOS at the SOLARIS page … I see only ‘Solaris
Product Line’,
‘Solaris operating environment’, ‘Solaris 7’, ‘Solaris 8’ and so on …
Yes, the messaging has been confused. I am more concerned about
the lack of differentiation between QNX demo disk and QNX RTP,
however, or that of QNX 4 products vs. RTP products on the web site.
Yes … that problem has its root from the abuse of ‘QNX’ as a prefix
for everything included in different product lines …
I expect OEMs to not be too uncomfortable with
QNX RTP = QNX Neutrino + RTP Application Environment (utils,package manager, etc.)
^^^^^^^
that is not a NAME … it sounds like QNX ‘something else’
For you uname freaks:
Solaris:
%uname
SunOS
%uname -a
SunOS solaris4 5.8 Generic i86pc i386 i86pcAnd nobody has heartburn over that.
)
Regards
Armin
Armin@Steinhoff_.de wrote:
Hi Scott,
“J. Scott Franko” wrote:
If you do a uname -a on solaris it doesn’t return solaris, instead it returns SunOS
or SunOS 5.5. If you do it on QRTP it returns QNX not QRTP. It should return NTO,
but thats a different story.Yes … that’s a different story which has nothing to do with marketing
…But what I was pointing out was that QSSL is being like sun. They have this unix
like OS that is the core thing they sell, but want to repackage it as something
else, so they add things like a new gui and call it the “platform”, or the
“operating environment”.I like ‘operating environment’ more … it’s much clearer.
Its all pakaging and marketing and targetting.
Yes … and it is VERY important for a bussiness success.
I agree, but that has nothing to do with helping a developer or manager understand the
jumble.
The only real difference is between QNX and NTO.
No … currently we have to differenciate between:
QNX4, NTO 2.1 and QRTP 2.0 (not to mention that Augusta stuff)QNX4 is completely different from the NTO product line.
NTO 2.1 comes with Photon 1.14 …
QRTP 2.0 uses Photon 2.0.
That means a PhAB application of NTO 2.1 is incompatible
with a PhAB application of QRTP 2.0.
NTO 2.1 supports x86, MIPS, PPC, H4 a.s.o …
QRTP 2.0 supports x86.In the moment I feel like sitting on three different chairs >
I’m sure it feels crazy to be supporting all that! ;O)
But really, when all this beta stuff finishes up, are you really going to try to market
all these different combinations? A really simplified message is that there are two
different RTOS’s, QNX and NTO, two different and incompatable version of the GUI, 1.x,
and 2.x, and targets for many machines available as build options in qcc -V (which may
only work for NTO).
Is the only reason that QRTP only support x86 because the other targets were just not
packaged with it? Could one easily add target support in the future (at the QSSL level?
AT the developer level?)? Will the GUI eventually settle out so that Photon 2.0 is
supported on QNX4, and NTO2? Will QRTP keep up with the current NTO?
Right now I can see putting up with the craziness because you guys are in the beta phase
of trying to broaden your market. But when the dust settles, there should be the legacy
QNX, the more modern NTO, the most current version of Photon that runs on both, and the
targets (which may only work with NTO).
If you are not going to have the latest version of photon running on both QNX and NTO,
then change the name to Photon QNX v1.x and Photon NTO v1.x and move on from there. They
do seem to be two different products (in terms of looks) differentiated by only a version
number, which make them seem like the same product.
The rest is packageing and targetting and marketing.
Don’t underestimate that ‘rest’ !
Regards
Armin
http://www.steinhoff.de
Armin@Steinhoff_.de wrote:“J. Scott Franko” wrote:
This is sortof like calling SunOS Solaris. Solaris consists of SunOS and CDE.
Show my the name SunOS at the SOLARIS page … I see only ‘Solaris
Product Line’,
‘Solaris operating environment’, ‘Solaris 7’, ‘Solaris 8’ and so on …Regards
Armin
Debbie Kane wrote:The name of the product is QNX Reatlime Platform (QNX RTP)
The OS in the QNX RTP is QNX Neutrino.
The GUI for the QNX RTP is Photon.
…
I believe this is explained in the Welcome message when you first boot into
the QNX Realtime Platform, availalbe by clicking on the top right icon of
the Shelf.-deb
Armin@Steinhoff_.de> wrote in message
news:39DB7A92.2C8B7A3C@Steinhoff_.de…
Andrew wrote:maybe i need to come over to Canada and get a job as your head of RTP
marketing and sort things out
Well … at first at first try to give that OS an IDENTITY >
QNXRTP ?? QRTP? QNX6 as reported by uname ? QNX/Neutrino … or QNX ??
Confusing! At the end QSSL has introduced an OS … but not a PRODUCT
with a NAME!Armin
Armin@steinhoff_.de wrote:
Debbie Kane wrote:
The name of the product is QNX Realtme Platform (QNX RTP)
my understanding is that the core product of QSSL is a RTOS and not a
platform.
And you are correct. The platform consists of the core product, plus
a bunch of other stuff that is not part of the core product. The core
product in the platform is the Neutrino 2.1 RTOS, and one of the
major pieces of the `stuff’ is the Photon 2.0 GUI.
As far as the word platform goes, I much prefer it over operating environment.
Operating environment only implies that the computer will operate', whereas RTP also includes full development tools. Now you may still argue that platform’ doesn’t explain itself well enough, but I would argue that
operating environment does not adequately cover everything that’s in here.
Saying development environment doesn’t get you off the hook either, because
it might imply that RTP is not something for Joe User, and we hope that with
the help of some of our new friends, it will become that.
So it’s a platform. I we get to define what that actually means, so much the
better. As far as I know, there is nothing comparable out there to take the
cue from anyway.
Armin@steinhoff_.de wrote:
Oh yeah… and stop using that Augusta name… it was a code word
just like Memphis and Chicago. It doesn’t count.