QNX6 vs WinCE?

It seems newsagent who posted this at openqnx knows a little bit more than
Cybermetrix’s press-release says. I have failed to find the following
statement in their press-release: “Using Linux will provide CyberMetrix with
a marketing advantage over QNX thanks to Linux’s popularity in recent
years.” Check for yourself http://www.cybermetrix.com/press_releases.htm.

Anyway, what’s openqnx’s point? Blackmail QSSL? I dont think they going to
chase after every fish of that size.

“Jutta Steinhoff” <j-steinhoff@web.de> wrote in message
news:3F113CF8.AD3197E@web.de

qnxstart_@yahoo.nospam.com > wrote:

Ian Zagorskih <> ianzag@megasignal.com> > wrote:
no surprise, people come, people go:

http://www.openqnx.com/Article151.html

Sorry, but i cannot access > www.openqnx.com> . For my memory it always
was so
(request timed out). I guess server is busy while servicing millions
of
requests from QNX userland and i’m just unlucky > :slight_smile:


no, openqnx server is not reliable.
no, it probably needs to wait for a few more years before achieving the
qnxstart momentum.


For all who don’t get access to the given link:


Cybermetrix to migrate CyFlex to Linux
Posted by: newsagent on Jul 11, 2003 - 05:39 AM

Cybermetrix’ CyFlex is a world-class, highly flexible test system
currently in use at major engineering facilities in the U.S. and around
the world. See our past news item for details about CyFlex. Cybermetrix
recently struck a deal with Concurrent Engineering FL to port its
flagship CyFlex product to RedHawk Linux real-time operating system. The
new product is targeted for release in the 4th quarter of this calendar
year.

Christine Mullholand, CEO of Cybermetrix, said “Using Concurrent’s
RedHawk Linux as a highly deterministic platform for CyFlex will ensure
our customers continue to enjoy reliable, well-supported, and high
performance test and measurement systems - with theadded benefits of
Concurrent’s tools, applications and worldwide support.”

Concurrent takes Redhat and then tweaks it for realtime operation and
calls it Redhawk and packages it with their hardware. Using Linux will
provide CyberMetrix with a marketing advantage over QNX thanks to
Linux’s popularity in recent years.

I was already wondering about that Linux vs QNX statement in the press
release, but you see, you can’t double check often enough…

BTW, when reading twice, that sentence is not a quote, it’s the
personal interpretation from Newsagent. It’s written so irritating
that it sounds like a quote of the press release…


Dmitri Poustovalov wrote:

It seems newsagent who posted this at openqnx knows a little bit more than
Cybermetrix’s press-release says. I have failed to find the following
statement in their press-release: “Using Linux will provide CyberMetrix with
a marketing advantage over QNX thanks to Linux’s popularity in recent
years.” Check for yourself > http://www.cybermetrix.com/press_releases.htm> .

Anyway, what’s openqnx’s point? Blackmail QSSL? I dont think they going to
chase after every fish of that size.

“Jutta Steinhoff” <> j-steinhoff@web.de> > wrote in message
news:> 3F113CF8.AD3197E@web.de> …


qnxstart_@yahoo.nospam.com > wrote:

Ian Zagorskih <> ianzag@megasignal.com> > wrote:
no surprise, people come, people go:

http://www.openqnx.com/Article151.html

Sorry, but i cannot access > www.openqnx.com> . For my memory it always
was so
(request timed out). I guess server is busy while servicing millions
of requests from QNX userland and i’m just unlucky > :slight_smile:


no, openqnx server is not reliable.
no, it probably needs to wait for a few more years before achieving the
qnxstart momentum.


For all who don’t get access to the given link:


Cybermetrix to migrate CyFlex to Linux
Posted by: newsagent on Jul 11, 2003 - 05:39 AM

Cybermetrix’ CyFlex is a world-class, highly flexible test system
currently in use at major engineering facilities in the U.S. and around
the world. See our past news item for details about CyFlex. Cybermetrix
recently struck a deal with Concurrent Engineering FL to port its
flagship CyFlex product to RedHawk Linux real-time operating system. The
new product is targeted for release in the 4th quarter of this calendar
year.

Christine Mullholand, CEO of Cybermetrix, said “Using Concurrent’s
RedHawk Linux as a highly deterministic platform for CyFlex will ensure
our customers continue to enjoy reliable, well-supported, and high
performance test and measurement systems - with theadded benefits of
Concurrent’s tools, applications and worldwide support.”

Concurrent takes Redhat and then tweaks it for realtime operation and
calls it Redhawk and packages it with their hardware. Using Linux will
provide CyberMetrix with a marketing advantage over QNX thanks to
Linux’s popularity in recent years.

Dmitri Poustovalov wrote:

It seems newsagent who posted this at openqnx knows a little bit more than
Cybermetrix’s press-release says. I have failed to find the following
statement in their press-release: “Using Linux will provide CyberMetrix with
a marketing advantage over QNX thanks to Linux’s popularity in recent
years.”

This statement is NOT part of the quote of the Cybermetrics press
release. Please read this ‘openqnx’ posting more carefully …

Armin


Check for yourself > http://www.cybermetrix.com/press_releases.htm> .

Anyway, what’s openqnx’s point? Blackmail QSSL? I dont think they going to
chase after every fish of that size.

“Jutta Steinhoff” <> j-steinhoff@web.de> > wrote in message
news:> 3F113CF8.AD3197E@web.de> …


qnxstart_@yahoo.nospam.com > wrote:

Ian Zagorskih <> ianzag@megasignal.com> > wrote:

no surprise, people come, people go:

http://www.openqnx.com/Article151.html

Sorry, but i cannot access > www.openqnx.com> . For my memory it always

was so

(request timed out). I guess server is busy while servicing millions

of

requests from QNX userland and i’m just unlucky > :slight_smile:


no, openqnx server is not reliable.
no, it probably needs to wait for a few more years before achieving the
qnxstart momentum.


For all who don’t get access to the given link:


Cybermetrix to migrate CyFlex to Linux
Posted by: newsagent on Jul 11, 2003 - 05:39 AM

Cybermetrix’ CyFlex is a world-class, highly flexible test system
currently in use at major engineering facilities in the U.S. and around
the world. See our past news item for details about CyFlex. Cybermetrix
recently struck a deal with Concurrent Engineering FL to port its
flagship CyFlex product to RedHawk Linux real-time operating system. The
new product is targeted for release in the 4th quarter of this calendar
year.

Christine Mullholand, CEO of Cybermetrix, said “Using Concurrent’s
RedHawk Linux as a highly deterministic platform for CyFlex will ensure
our customers continue to enjoy reliable, well-supported, and high
performance test and measurement systems - with theadded benefits of
Concurrent’s tools, applications and worldwide support.”

Concurrent takes Redhat and then tweaks it for realtime operation and
calls it Redhawk and packages it with their hardware. Using Linux will
provide CyberMetrix with a marketing advantage over QNX thanks to
Linux’s popularity in recent years.

camz@passageway.com wrote:

Armin Steinhoff <> a-steinhoff@web.de> > wrote:

You have to buy a development seat before you can buy runtimes. But you only
have to buy development seat ONCE.


That’s OK for me. But tell me why should an END-USER buy a C/C++
development seat if he want to programm with a Soft-PLC??


Armin, you are not understand how this works, it’s really simple.
QNX doesn’t sell to end users. The sell to developers,

Yes … I’m the DEVELOPER and I’m not an OEM or VAR.

OEMs, and VARs.
Let me make this perfectly clear, if you design and code a system for
a customer… YOU are the OEM, YOU need the development seat not
the end-user, YOU can buy runtimes at reasonable prices and then
re-sell them to your customers.

Just to make it simple and clear: I’m not the OEM and I’m not interested
to sell QNX.

The only thing you can’t do is, hand your software to the end-user and
tell them to contact QSS for a run-time.

And what happens then? Forgett it :slight_smile:

As you know … you have to give warranty for the products you have
sold. There are also important legal aspects if one of these products
could be the cause of damages … I’m not in the position to handle all
warranty and legal issues in place of QSSL, because I have to provide
the real QNX runtime software and not only stickers.


QSS doesn’t warranty their OS for any particular application, nor should
they.

They have to give at least the warrenty that their system works as
documented …

If you build the system, you are responsible for providing a warranty
at your discretion.

Again: I’m not in the position to handle all warranty and legal issues
of their OS in place of QSSL.

[clip ]

Armin, perhaps you should CALL a sales rep and actually talk to them next time.

There are other alternatives :slight_smile:

Armin

Armin Steinhoff <a-steinhoff@web.de> wrote:

You have to buy a development seat before you can buy runtimes. But you only
have to buy development seat ONCE.

That’s OK for me. But tell me why should an END-USER buy a C/C++
development seat if he want to programm with a Soft-PLC??

Armin, you are not understand how this works, it’s really simple.
QNX doesn’t sell to end users. The sell to developers, OEMs, and VARs.
Let me make this perfectly clear, if you design and code a system for
a customer… YOU are the OEM, YOU need the development seat not
the end-user, YOU can buy runtimes at reasonable prices and then
re-sell them to your customers.

The only thing you can’t do is, hand your software to the end-user and
tell them to contact QSS for a run-time.

As you know … you have to give warranty for the products you have
sold. There are also important legal aspects if one of these products
could be the cause of damages … I’m not in the position to handle all
warranty and legal issues in place of QSSL, because I have to provide
the real QNX runtime software and not only stickers.

QSS doesn’t warranty their OS for any particular application, nor should
they. If you build the system, you are responsible for providing a warranty
at your discretion. This is no different than any other OS vendor, including
Microsoft.

and a single quantity
basic OS runtime is about few hundreds dollars.

Single quantities of the OS + network (no photon) are approximately $120 US.

The annual charge to keep you going between versions is about $5K.

Actually, a 1-year support contract for PE is approximately $1200 US.

Not at all … a M$Windows based SCADA system + M$S runtime is targeting
the same market as similar QNX based SCADA solutions.

Microsoft is MORE expensive. A qnx runtime with OS, network, and photon
is less than $200 US (probably less than $150 US), whereas Windows 2000 or
Windows XP is about $350-$400 US for the same runtime. If you sell a SCADA
system that runs on windows, you have to buy a windows license too, although
the price of the windows OS is often part of the cost of purchasing the PC
itself. You are still paying for it though.

No … the customers are comparing e.g. M$s based SCADA solutions with
QNX based SCADA solutions.

If you are talking about runtime costs, QNX is cheaper, and most SCADA
systems for Windows will easily cost you $5000 - $24000 US for the software
alone, the runtime cost of QNX or Windows is easily in the noise.

The nature of SCADA systems has changed over the years too, they used to be
very realtime and mission critical, i.e. they did the C in SCADA. Now
though (since they all run on windows, and windows likes to crash) they
relegate the relatime, mission-critical stuff to RTUs and PLCs and the
SCADA system typically only does the S. In they heyday of SCADA with QNX
systems like RealFlex) the SCADA system was doing S and C, and realtime
was a requirement, reliability was crucial, they couldn’t run on windows.
The SCADA world just ain’t like that anymore.

Well, a salesman would much rather sell PE for $9K than RT for couple
hundred bucks, right? Remember however that salesmen are just like those
folks in the car dealerships. They DO negotiate and one should not be afraid
to push them.

Actually QSS is more consistent now than they ever were in QNX4. The prices
and discounts are pretty much fixed for lower volumes. The negotiating still
occurs for large quantities and can range from $0 per unit (with a one-time,
all up-front fee) to the >$100 US, all depending on volume forecasts.

Armin, perhaps you should CALL a sales rep and actually talk to them next time.

Cheers,
Camz.


Martin Zimmerman camz@passageway.com
Camz Software Enterprises www.passageway.com/camz/qnx/
QNX Programming & Consulting www.qnxzone.com

Armin (& others) -

Just so you know, we are listening to what you’re saying. We are
considering the merits of offering an installable x86 runtime product that
would facilitate the business of independent software vendors such as
yourself, and offer another option to VARs who might prefer to include
installable QNX-branded product as part of their package as an option to
developing their own OS install on media. I can’t promise what the result
will be, but if you have any information that might contribute to our
decision or would just like an update on the status of this, send me an
email.

  • Eric

“Armin Steinhoff” <a-steinhoff@web.de> wrote in message
news:bg8akd$nir$1@inn.qnx.com

camz@passageway.com > wrote:
Armin Steinhoff <> a-steinhoff@web.de> > wrote:

You have to buy a development seat before you can buy runtimes. But you
only
have to buy development seat ONCE.


That’s OK for me. But tell me why should an END-USER buy a C/C++
development seat if he want to programm with a Soft-PLC??


Armin, you are not understand how this works, it’s really simple.
QNX doesn’t sell to end users. The sell to developers,

Yes … I’m the DEVELOPER and I’m not an OEM or VAR.

OEMs, and VARs.
Let me make this perfectly clear, if you design and code a system for
a customer… YOU are the OEM, YOU need the development seat not
the end-user, YOU can buy runtimes at reasonable prices and then
re-sell them to your customers.

Just to make it simple and clear: I’m not the OEM and I’m not interested
to sell QNX.

The only thing you can’t do is, hand your software to the end-user and
tell them to contact QSS for a run-time.

And what happens then? Forgett it > :slight_smile:

As you know … you have to give warranty for the products you have
sold. There are also important legal aspects if one of these products
could be the cause of damages … I’m not in the position to handle all
warranty and legal issues in place of QSSL, because I have to provide
the real QNX runtime software and not only stickers.


QSS doesn’t warranty their OS for any particular application, nor should
they.

They have to give at least the warrenty that their system works as
documented …

If you build the system, you are responsible for providing a warranty
at your discretion.

Again: I’m not in the position to handle all warranty and legal issues
of their OS in place of QSSL.

[clip ]

Armin, perhaps you should CALL a sales rep and actually talk to them
next time.

There are other alternatives > :slight_smile:

Armin

Armin Steinhoff <a-steinhoff@web.de> wrote:

Yes … I’m the DEVELOPER and I’m not an OEM or VAR.

So there is no issue with you buying qnx runtimes and then offering them
to your customers (aside from not being able to easily package that up
for them to install).

Just to make it simple and clear: I’m not the OEM and I’m not interested
to sell QNX.

Ah, now we get to the crux of it. You don’t have any problem purchasing
the runtimes, your problem is that you don’t want to do it. That is a
very different problem. In this case, the requirement for your customer
to buy a development seat is not QSS’s “fault”, it is yours for refusing
to sell the runtime licensing along with your product.

They have to give at least the warrenty that their system works as
documented …

Actually, they don’t. And to be quite honest, you probably don’t list off
to your customers what the OS does since its an enabling layer that technically
does not do anything until you actually want to run an app.

Again: I’m not in the position to handle all warranty and legal issues
of their OS in place of QSSL.

Again, this is a restriction that YOU have placed on yourself. In all
honesty though, this “requirement” is not unique to you, or QNX. You’d have
the same issue with any other OS, so it’s harldy fair to complain that it
is QSS’s fault that you would need to deal with it and are not prepared and/or
are unwilling to do so. Sounds like you want to be in the business of
writing software, but not in the business of selling it, and just hoping
that someone will magically pay you.

There are other alternatives > :slight_smile:

Sure, you could use Linux, have all the same issues, and not have anyone
to complain to. (you certainly wouldn’t have any hope in hell of providing
any sort of warranty for the OS, let alone any app developed on it).

Cheers,
Camz.


Martin Zimmerman camz@passageway.com
Camz Software Enterprises www.passageway.com/camz/qnx/
QNX Programming & Consulting www.qnxzone.com

Armin,

You still didn’t answer the question:

WHY CAN"T YOU PUT A QNX RUNTIME ON A CD WITH YOUR SOFTWARE AND DELIVER THE
CD TO YOUR CUSTOMER??? You can do it…really! and the runtime only costs a
150 bucks US.

Kevin

“Armin Steinhoff” <a-steinhoff@web.de> wrote in message
news:bg8akd$nir$1@inn.qnx.com

camz@passageway.com > wrote:
Armin Steinhoff <> a-steinhoff@web.de> > wrote:

You have to buy a development seat before you can buy runtimes. But you
only
have to buy development seat ONCE.


That’s OK for me. But tell me why should an END-USER buy a C/C++
development seat if he want to programm with a Soft-PLC??


Armin, you are not understand how this works, it’s really simple.
QNX doesn’t sell to end users. The sell to developers,

Yes … I’m the DEVELOPER and I’m not an OEM or VAR.

OEMs, and VARs.
Let me make this perfectly clear, if you design and code a system for
a customer… YOU are the OEM, YOU need the development seat not
the end-user, YOU can buy runtimes at reasonable prices and then
re-sell them to your customers.

Just to make it simple and clear: I’m not the OEM and I’m not interested
to sell QNX.

The only thing you can’t do is, hand your software to the end-user and
tell them to contact QSS for a run-time.

And what happens then? Forgett it > :slight_smile:

As you know … you have to give warranty for the products you have
sold. There are also important legal aspects if one of these products
could be the cause of damages … I’m not in the position to handle all
warranty and legal issues in place of QSSL, because I have to provide
the real QNX runtime software and not only stickers.


QSS doesn’t warranty their OS for any particular application, nor should
they.

They have to give at least the warrenty that their system works as
documented …

If you build the system, you are responsible for providing a warranty
at your discretion.

Again: I’m not in the position to handle all warranty and legal issues
of their OS in place of QSSL.

[clip ]

Armin, perhaps you should CALL a sales rep and actually talk to them
next time.

There are other alternatives > :slight_smile:

Armin

Eric,

nice to hear that you are listening, may be you should better discuss
with your boss. He got already an email from me 6 weeks ago…

An installable x86 runtime product is exactly what is needed, but I’m
used that no answer in NA means NO!

BTW, we thought the first commercially available graphical programming
tool with IEC61499 processing could make QNX very attractive as target
system for the new realtime demands from SoftPLC users because of the
QNX6 runtime prices would be acceptable for that market now.

OK, that market seems to be uninteresting for QSSL.


Just for clearification and as answer for all following postings with
ideas how 3rd party products should be bundled with QNX in order to
bypass the current license policy from QSSL:

when Armin talks about end-users, so he has non C-developers in mind!
Most of them are VARs. Notice, in industrial automation a VAR is
sometimes also end-user when using the own machines or test equipments
in the own facilities, too.

As told again and again, who don’t write an application with C will need
QNX only as target system. So he don’t need a QNX C-development
system … even when C-programmers can’t imagine :wink:

Why should 3rd parties resell (box shift) QNX Runtime licenses for
unknown hardware and system configurations? How to install a sheet of
paper + sticker?
It’s up to the user to integrate what he will need and to buy legally
all hardware and software components… and he will get warrenty for
each product from the vendor.

The problem is that it’s not possible to buy legally QNX Runtime
Licenses incl. original CD with RT modules as separate PRODUCT !
It’s just a question of license policy. It’s possible for other OSes
which are used e.g. with SoftPLCs, it’s not an exotic idea :wink:

  • Jutta



    Eric Johnson wrote:

Armin (& others) -

Just so you know, we are listening to what you’re saying. We are
considering the merits of offering an installable x86 runtime product that
would facilitate the business of independent software vendors such as
yourself, and offer another option to VARs who might prefer to include
installable QNX-branded product as part of their package as an option to
developing their own OS install on media. I can’t promise what the result
will be, but if you have any information that might contribute to our
decision or would just like an update on the status of this, send me an
email.

  • Eric

“Armin Steinhoff” <> a-steinhoff@web.de> > wrote in message
news:bg8akd$nir$> 1@inn.qnx.com> …
camz@passageway.com > wrote:
Armin Steinhoff <> a-steinhoff@web.de> > wrote:

You have to buy a development seat before you can buy runtimes.
But you only have to buy development seat ONCE.


That’s OK for me. But tell me why should an END-USER buy a C/C++
development seat if he want to programm with a Soft-PLC??


Armin, you are not understand how this works, it’s really simple.
QNX doesn’t sell to end users. The sell to developers,

Yes … I’m the DEVELOPER and I’m not an OEM or VAR.

OEMs, and VARs.
Let me make this perfectly clear, if you design and code a system for
a customer… YOU are the OEM, YOU need the development seat not
the end-user, YOU can buy runtimes at reasonable prices and then
re-sell them to your customers.

Just to make it simple and clear: I’m not the OEM and I’m not interested
to sell QNX.

The only thing you can’t do is, hand your software to the end-user and
tell them to contact QSS for a run-time.

And what happens then? Forgett it > :slight_smile:

As you know … you have to give warranty for the products you have
sold. There are also important legal aspects if one of these products
could be the cause of damages … I’m not in the position to handle all
warranty and legal issues in place of QSSL, because I have to provide
the real QNX runtime software and not only stickers.


QSS doesn’t warranty their OS for any particular application, nor should
they.

They have to give at least the warrenty that their system works as
documented …

If you build the system, you are responsible for providing a warranty
at your discretion.

Again: I’m not in the position to handle all warranty and legal issues
of their OS in place of QSSL.

[clip ]

Armin, perhaps you should CALL a sales rep and actually talk to them
next time.

There are other alternatives > :slight_smile:

Armin

Camz, I can’t follow you.

The only I understand is that you are not familiar with non
C-development systems …

Armin Steinhoff <> a-steinhoff@web.de> > wrote:
Yes … I’m the DEVELOPER and I’m not an OEM or VAR.

So there is no issue with you buying qnx runtimes and then offering them
to your customers (aside from not being able to easily package that up
for them to install).

Just to make it simple and clear: I’m not the OEM and I’m not interested
to sell QNX.

Ah, now we get to the crux of it. You don’t have any problem purchasing
the runtimes, your problem is that you don’t want to do it. That is a
very different problem. In this case, the requirement for your customer
to buy a development seat is not QSS’s “fault”, it is yours for refusing
to sell the runtime licensing along with your product.

They have to give at least the warrenty that their system works as
documented …

Actually, they don’t. And to be quite honest, you probably don’t list off
to your customers what the OS does since its an enabling layer that technically
does not do anything until you actually want to run an app.

Again: I’m not in the position to handle all warranty and legal issues
of their OS in place of QSSL.

Again, this is a restriction that YOU have placed on yourself. In all
honesty though, this “requirement” is not unique to you, or QNX. You’d have
the same issue with any other OS, so it’s harldy fair to complain that it
is QSS’s fault that you would need to deal with it and are not prepared and/or
are unwilling to do so. Sounds like you want to be in the business of
writing software, but not in the business of selling it, and just hoping
that someone will magically pay you.

There are other alternatives > :slight_smile:

Sure, you could use Linux, have all the same issues, and not have anyone
to complain to. (you certainly wouldn’t have any hope in hell of providing
any sort of warranty for the OS, let alone any app developed on it).

Cheers,
Camz.


Martin Zimmerman > camz@passageway.com
Camz Software Enterprises > www.passageway.com/camz/qnx/
QNX Programming & Consulting > www.qnxzone.com

Eric Johnson wrote:

Armin (& others) -

Just so you know, we are listening to what you’re saying. We are
considering the merits of offering an installable x86 runtime product that
would facilitate the business of independent software vendors such as
yourself, and offer another option to VARs who might prefer to include
installable QNX-branded product as part of their package as an option to
developing their own OS install on media. I can’t promise what the result
will be, but if you have any information that might contribute to our
decision or would just like an update on the status of this, send me an
email.

Eric,

Just so you know. This is something that we would buy if it wasn’t too
much extra.

Right now (we are in exactly the same business as Armin) we write our
own installer, since there isn’t an easy to use existing installer
available with the runtime. Maintaining and enhancing our installer costs
us money, and we’d rather not do it, and we’d pay something to not have
to, but we wouldn’t pay too much. I’m just pulling a figure out of thin
air here, but I’d guess that we wouldn’t be willing to pay more than about
$10-$15 above the baseline QNX6 runtime cost for an installer (which is
really what we’re talking here). I would think that if we can afford to
make our own installer for less than around $15 dollars per runtime with
our volumes, that QSS could actually make money charging an extra $10-$15
per runtime at the aggregate volumes of all users like us.

Basically the momentics installer, with a stripped down .qpr to install a
basic OS only, and provided on CD would be great.

  1. Buy QNX runtimes
  2. Make CD with your software and QNX Runtime installer
  3. Give CD to customer.
  4. Include QNX Runtime in purchase price and a bit more for your troubles
    in regards to the installer.


    “Jutta Steinhoff” <j-steinhoff@web.de> wrote in message
    news:3F28567C.D8982821@web.de

Camz, I can’t follow you.

The only I understand is that you are not familiar with non
C-development systems …

Armin Steinhoff <> a-steinhoff@web.de> > wrote:
Yes … I’m the DEVELOPER and I’m not an OEM or VAR.

So there is no issue with you buying qnx runtimes and then offering them
to your customers (aside from not being able to easily package that up
for them to install).

Just to make it simple and clear: I’m not the OEM and I’m not
interested
to sell QNX.

Ah, now we get to the crux of it. You don’t have any problem purchasing
the runtimes, your problem is that you don’t want to do it. That is a
very different problem. In this case, the requirement for your customer
to buy a development seat is not QSS’s “fault”, it is yours for refusing
to sell the runtime licensing along with your product.

They have to give at least the warrenty that their system works as
documented …

Actually, they don’t. And to be quite honest, you probably don’t list
off
to your customers what the OS does since its an enabling layer that
technically
does not do anything until you actually want to run an app.

Again: I’m not in the position to handle all warranty and legal issues
of their OS in place of QSSL.

Again, this is a restriction that YOU have placed on yourself. In all
honesty though, this “requirement” is not unique to you, or QNX. You’d
have
the same issue with any other OS, so it’s harldy fair to complain that
it
is QSS’s fault that you would need to deal with it and are not prepared
and/or
are unwilling to do so. Sounds like you want to be in the business of
writing software, but not in the business of selling it, and just hoping
that someone will magically pay you.

There are other alternatives > :slight_smile:

Sure, you could use Linux, have all the same issues, and not have anyone
to complain to. (you certainly wouldn’t have any hope in hell of
providing
any sort of warranty for the OS, let alone any app developed on it).

Cheers,
Camz.


Martin Zimmerman > camz@passageway.com
Camz Software Enterprises > www.passageway.com/camz/qnx/
QNX Programming & Consulting > www.qnxzone.com

Kevin,

  1. please read carefully all legal stuff from QSSL

  2. please stop your advice when you don’t understand the topic

  3. notice, industrial users (VARs, OEMs, not hobbyists or freaks!)
    want original software products and no second hand copies from
    whatever source when they need a separate (un-bundled) Runtime
    license for a Target system.

  • Jutta


    Kevin Stallard wrote:
  1. Buy QNX runtimes
  2. Make CD with your software and QNX Runtime installer
  3. Give CD to customer.
  4. Include QNX Runtime in purchase price and a bit more for your troubles
    in regards to the installer.

“Jutta Steinhoff” <> j-steinhoff@web.de> > wrote in message
news:> 3F28567C.D8982821@web.de> …

Camz, I can’t follow you.

The only I understand is that you are not familiar with non
C-development systems …

Armin Steinhoff <> a-steinhoff@web.de> > wrote:
Yes … I’m the DEVELOPER and I’m not an OEM or VAR.

So there is no issue with you buying qnx runtimes and then offering them
to your customers (aside from not being able to easily package that up
for them to install).

Just to make it simple and clear: I’m not the OEM and I’m not
interested
to sell QNX.

Ah, now we get to the crux of it. You don’t have any problem purchasing
the runtimes, your problem is that you don’t want to do it. That is a
very different problem. In this case, the requirement for your customer
to buy a development seat is not QSS’s “fault”, it is yours for refusing
to sell the runtime licensing along with your product.

They have to give at least the warrenty that their system works as
documented …

Actually, they don’t. And to be quite honest, you probably don’t list
off
to your customers what the OS does since its an enabling layer that
technically
does not do anything until you actually want to run an app.

Again: I’m not in the position to handle all warranty and legal issues
of their OS in place of QSSL.

Again, this is a restriction that YOU have placed on yourself. In all
honesty though, this “requirement” is not unique to you, or QNX. You’d
have
the same issue with any other OS, so it’s harldy fair to complain that
it
is QSS’s fault that you would need to deal with it and are not prepared
and/or
are unwilling to do so. Sounds like you want to be in the business of
writing software, but not in the business of selling it, and just hoping
that someone will magically pay you.

There are other alternatives > :slight_smile:

Sure, you could use Linux, have all the same issues, and not have anyone
to complain to. (you certainly wouldn’t have any hope in hell of
providing
any sort of warranty for the OS, let alone any app developed on it).

Cheers,
Camz.


Martin Zimmerman > camz@passageway.com
Camz Software Enterprises > www.passageway.com/camz/qnx/
QNX Programming & Consulting > www.qnxzone.com

Rennie Allen wrote:

Eric Johnson wrote:


Armin (& others) -


Just so you know, we are listening to what you’re saying. We are
considering the merits of offering an installable x86 runtime product that
would facilitate the business of independent software vendors such as
yourself, and offer another option to VARs who might prefer to include
installable QNX-branded product as part of their package as an option to
developing their own OS install on media. I can’t promise what the result
will be, but if you have any information that might contribute to our
decision or would just like an update on the status of this, send me an
email.


Eric,

Just so you know. This is something that we would buy if it wasn’t too
much extra.

Right now (we are in exactly the same business as Armin) we write our
own installer, since there isn’t an easy to use existing installer
available with the runtime. Maintaining and enhancing our installer costs
us money, and we’d rather not do it, and we’d pay something to not have
to, but we wouldn’t pay too much. I’m just pulling a figure out of thin
air here, but I’d guess that we wouldn’t be willing to pay more than about
$10-$15 above the baseline QNX6 runtime cost for an installer (which is
really what we’re talking here). I would think that if we can afford to
make our own installer for less than around $15 dollars per runtime with
our volumes, that QSS could actually make money charging an extra $10-$15
per runtime at the aggregate volumes of all users like us.

Basically the momentics installer, with a stripped down .qpr to install a
basic OS only, and provided on CD would be great.

Yes … and it would also make sure that the installation procedure
for QNX6 has always an acceptable and controlled QUALITY.

Live could be so easy for an QNX6 user:

  1. buy an nice JAVA based application from IBM, a SCADA or a SoftPLC
  2. buy a QNX runtime in a hard box with a QNX6 CD
  3. simply install both
  4. if neccessary strip down the runtime with an OS configurator
    (QNX is modular and flexible …isn’t it?)

That’s all … no inquisitory questions from QSSL, no shocking offerings
about not needed development systems … just business as usual :slight_smile:

And of course a satisfied QNX customer …

Armin

Armin Steinhoff wrote:

Rennie Allen wrote:
Eric Johnson wrote:


Armin (& others) -


Just so you know, we are listening to what you’re saying. We are
considering the merits of offering an installable x86 runtime product that
would facilitate the business of independent software vendors such as
yourself, and offer another option to VARs who might prefer to include
installable QNX-branded product as part of their package as an option to
developing their own OS install on media. I can’t promise what the result
will be, but if you have any information that might contribute to our
decision or would just like an update on the status of this, send me an
email.


Eric,

Just so you know. This is something that we would buy if it wasn’t too
much extra.

Right now (we are in exactly the same business as Armin) we write our
own installer, since there isn’t an easy to use existing installer
available with the runtime. Maintaining and enhancing our installer costs
us money, and we’d rather not do it, and we’d pay something to not have
to, but we wouldn’t pay too much. I’m just pulling a figure out of thin
air here, but I’d guess that we wouldn’t be willing to pay more than about
$10-$15 above the baseline QNX6 runtime cost for an installer (which is
really what we’re talking here). I would think that if we can afford to
make our own installer for less than around $15 dollars per runtime with
our volumes, that QSS could actually make money charging an extra $10-$15
per runtime at the aggregate volumes of all users like us.

Basically the momentics installer, with a stripped down .qpr to install a
basic OS only, and provided on CD would be great.

Yes … and it would also make sure that the installation procedure
for QNX6 has always an acceptable and controlled QUALITY.

Live could be so easy for an QNX6 user:

  1. buy an nice JAVA based application from IBM, a SCADA or a SoftPLC
  2. buy a QNX runtime in a hard box with a QNX6 CD
  3. simply install both
  4. if neccessary strip down the runtime with an OS configurator
    (QNX is modular and flexible …isn’t it?)

That’s all … no inquisitory questions from QSSL, no shocking offerings
about not needed development systems … just business as usual > :slight_smile:

And of course a satisfied QNX customer …

Armin

I’m sure at least some people run more than one program on their
machines, and do not want a license with each one. If the product needs
a license or not, depending if it is the first one installed, this could
get confusing.

I don’t remember ever buying a Microsoft OS, only a box with it already
installed and paid for. Is there a process where a box seller could
deliver a legal QNX runtime box?

John Halpenny

Phone: (613) 996-9321

Whats so funny is that you guys are straining at the most solvable problem I
have ever seen.

Thanks for the laughs…it’s been amusing watch you two go round and round
and round when the problem can be very simply solved and you can look good
to your customers to boot.

Imagine you don’t want to make an install CD for your customer, but you are
willing to port your app to a different OS. And an OS that has NO warranty
to boot…

Priceless

Kevin

“Jutta Steinhoff” <j-steinhoff@web.de> wrote in message
news:3F28DFC3.F5001AAB@web.de

Kevin,

  1. please read carefully all legal stuff from QSSL

  2. please stop your advice when you don’t understand the topic

  3. notice, industrial users (VARs, OEMs, not hobbyists or freaks!)
    want original software products and no second hand copies from
    whatever source when they need a separate (un-bundled) Runtime
    license for a Target system.

  • Jutta


    Kevin Stallard wrote:
  1. Buy QNX runtimes
  2. Make CD with your software and QNX Runtime installer
  3. Give CD to customer.
  4. Include QNX Runtime in purchase price and a bit more for your
    troubles
    in regards to the installer.

“Jutta Steinhoff” <> j-steinhoff@web.de> > wrote in message
news:> 3F28567C.D8982821@web.de> …

Camz, I can’t follow you.

The only I understand is that you are not familiar with non
C-development systems …

Armin Steinhoff <> a-steinhoff@web.de> > wrote:
Yes … I’m the DEVELOPER and I’m not an OEM or VAR.

So there is no issue with you buying qnx runtimes and then offering
them
to your customers (aside from not being able to easily package that
up
for them to install).

Just to make it simple and clear: I’m not the OEM and I’m not
interested
to sell QNX.

Ah, now we get to the crux of it. You don’t have any problem
purchasing
the runtimes, your problem is that you don’t want to do it. That is
a
very different problem. In this case, the requirement for your
customer
to buy a development seat is not QSS’s “fault”, it is yours for
refusing
to sell the runtime licensing along with your product.

They have to give at least the warrenty that their system works as
documented …

Actually, they don’t. And to be quite honest, you probably don’t
list
off
to your customers what the OS does since its an enabling layer that
technically
does not do anything until you actually want to run an app.

Again: I’m not in the position to handle all warranty and legal
issues
of their OS in place of QSSL.

Again, this is a restriction that YOU have placed on yourself. In
all
honesty though, this “requirement” is not unique to you, or QNX.
You’d
have
the same issue with any other OS, so it’s harldy fair to complain
that
it
is QSS’s fault that you would need to deal with it and are not
prepared
and/or
are unwilling to do so. Sounds like you want to be in the business
of
writing software, but not in the business of selling it, and just
hoping
that someone will magically pay you.

There are other alternatives > :slight_smile:

Sure, you could use Linux, have all the same issues, and not have
anyone
to complain to. (you certainly wouldn’t have any hope in hell of
providing
any sort of warranty for the OS, let alone any app developed on it).

Cheers,
Camz.


Martin Zimmerman > camz@passageway.com
Camz Software Enterprises > www.passageway.com/camz/qnx/
QNX Programming & Consulting > www.qnxzone.com

I would love QSSL to sell runtimes only too. But there is a very practicle
problem.

If someone buys something, they have right to expact a certain amoutn of
support. So if I were to write a super-automated grmip frizzle and tell my
potnetial customers all they need is a runnning QNX system to install my
product, they may think that they can go out and spend $15 to buy a QNX
runtime system. Now, when they get their CD, just imagine if it didn’t
install right out of the box!?!?!?!? So they try to call QSSL for help? If
QSSL has to answer the phone just once they already lost money on the deal.
I wouldn’t blame QSSL for not fielding those calls.

On the other hand, if I could buy say 20 indivudual runtimes, I could tell
people that they could buy their PC from me with a ligimate copy of QNX
installed. Then I would be responsible to the support on those 20
individual systems. If I am charging enough for my grimp frizzles, then
that is a responsibility that I may be willing to accept.

If my grimp frizzles start selling like hotcakes then I might but 100 copies
the next time, then 500, then who knows!

BTW, I wouldn’t expact QSSL to sell as few as 20 copies for $15. But I
would say that $499 for 1 copy is reasonable. But 10 or more copies and the
price drops to $249 (hell, even I can afford $2490 for somethins tha I can
resell). Say 50 copies drops to $199, etc., etc.

QSSL, I have services that I can sell if the runtime only cost me $249!!!

Now let’s consider the alternative. I start selling my grimp frizzles and
tell people that they need a running QNX system. It’s not too hard to
figure out that they can down load the NC version for free. Then they can
buy my CD adn install it on their system and have a fully functional system.
THEY may be violating the QSSL Non-Comercial terms of the EULA. But that’s
not for me to determine. If they send me a check I’m going to send them a
GF CD. If don’t ask, don’t tell works in the military, then it works for me
too.

BTW, Grimp Frizzles CDs are on sale now for only $79 US. Get yours while
supplies last!


“Rennie Allen” <rallen@csical.com> wrote in message
news:bg9pns$8p1$1@tiger.openqnx.com

Just so you know. This is something that we would buy if it wasn’t too
much extra.

Right now (we are in exactly the same business as Armin) we write our
own installer, since there isn’t an easy to use existing installer
available with the runtime. Maintaining and enhancing our installer costs
us money, and we’d rather not do it, and we’d pay something to not have
to, but we wouldn’t pay too much. I’m just pulling a figure out of thin
air here, but I’d guess that we wouldn’t be willing to pay more than about
$10-$15 above the baseline QNX6 runtime cost for an installer (which is
really what we’re talking here). I would think that if we can afford to
make our own installer for less than around $15 dollars per runtime with
our volumes, that QSS could actually make money charging an extra $10-$15
per runtime at the aggregate volumes of all users like us.

Basically the momentics installer, with a stripped down .qpr to install a
basic OS only, and provided on CD would be great.

Bill,

if anyone wants to use QNX NC runtime and development systems illegal,
why should he buy a pre-installed system from you and even pay for it?

Also, NC is different from SE and PE, so you can’t be sure that a
NC application will run on a commercial runtime …
BTW, can you really controll whether all VARs or OEMs are paying for
each installed license?

Should QNX stop the NC version because of it can be used illegal?
If NC wouldn’t exist, be sure there will always be some guys with
criminal energy who will find a way to patch the 30 day version, make
a copy from a “friend” or an University or whatever version, etc.

The main question is whether QSSL can make more business with runtime
CD versions and reach additional markets into which they can sell!

I’m very sure that a well working application on top of a rock solid
runtime would create the motivation to work more with this OS …
( → SE, PE)

Satisfaction of customers as well as acceptable sales and price
strategies leads also to more business…


BTW, when you want to resell pre-installed PC-systems, may be you should
read the EULAs of such a new runtime version at first :wink:
For my understanding according the current QNX4, SE and PE license
agreements, no VARs or OEMs are allowed to install QNX Runtimes on any
hardware w/o own software or applications !!!

Also, the case that non pre-installed runtimes will be needed for “stand
alone” Target systems w/o QNX C-application was never considered in
their agreements.

As long as QNX4 runtime systems were delivered together with diskettes
or CDs, most users didn’t realize it :wink:

Please, stop dreaming … Rennie was talking about additional $15
added to the price of the runtime :wink:

BTW, did you hear about support hotlines from other OS vendors?
Have a look to common practice in the market …

Cheers,
Jutta


Bill Caroselli wrote:

I would love QSSL to sell runtimes only too. But there is a very practicle
problem.

If someone buys something, they have right to expact a certain amoutn of
support. So if I were to write a super-automated grmip frizzle and tell my
potnetial customers all they need is a runnning QNX system to install my
product, they may think that they can go out and spend $15 to buy a QNX
runtime system. Now, when they get their CD, just imagine if it didn’t
install right out of the box!?!?!?!? So they try to call QSSL for help? If
QSSL has to answer the phone just once they already lost money on the deal.
I wouldn’t blame QSSL for not fielding those calls.

On the other hand, if I could buy say 20 indivudual runtimes, I could tell
people that they could buy their PC from me with a ligimate copy of QNX
installed. Then I would be responsible to the support on those 20
individual systems. If I am charging enough for my grimp frizzles, then
that is a responsibility that I may be willing to accept.

If my grimp frizzles start selling like hotcakes then I might but 100 copies
the next time, then 500, then who knows!

BTW, I wouldn’t expact QSSL to sell as few as 20 copies for $15. But I
would say that $499 for 1 copy is reasonable. But 10 or more copies and the
price drops to $249 (hell, even I can afford $2490 for somethins tha I can
resell). Say 50 copies drops to $199, etc., etc.

QSSL, I have services that I can sell if the runtime only cost me $249!!!

Now let’s consider the alternative. I start selling my grimp frizzles and
tell people that they need a running QNX system. It’s not too hard to
figure out that they can down load the NC version for free. Then they can
buy my CD adn install it on their system and have a fully functional system.
THEY may be violating the QSSL Non-Comercial terms of the EULA. But that’s
not for me to determine. If they send me a check I’m going to send them a
GF CD. If don’t ask, don’t tell works in the military, then it works for me
too.

BTW, Grimp Frizzles CDs are on sale now for only $79 US. Get yours while
supplies last!

“Rennie Allen” <> rallen@csical.com> > wrote in message
news:bg9pns$8p1$> 1@tiger.openqnx.com> …

Just so you know. This is something that we would buy if it wasn’t too
much extra.

Right now (we are in exactly the same business as Armin) we write our
own installer, since there isn’t an easy to use existing installer
available with the runtime. Maintaining and enhancing our installer costs
us money, and we’d rather not do it, and we’d pay something to not have
to, but we wouldn’t pay too much. I’m just pulling a figure out of thin
air here, but I’d guess that we wouldn’t be willing to pay more than about
$10-$15 above the baseline QNX6 runtime cost for an installer (which is
really what we’re talking here). I would think that if we can afford to
make our own installer for less than around $15 dollars per runtime with
our volumes, that QSS could actually make money charging an extra $10-$15
per runtime at the aggregate volumes of all users like us.

Basically the momentics installer, with a stripped down .qpr to install a
basic OS only, and provided on CD would be great.

Kevin, I’m not sure if it’s still amusing for you when you have really
read all legal stuff…

It’s not very amusing for me to get again and again advices from you to
break the EULA from QSSL!

Notice, when we are not willing to warrent for an OS because of it has
to be sold as “customised version” although an original product is
requested, so it doesn’t mean that we don’t give full warrenty for all
sold software and hardware products.

Kevin, your ideas are sometimes unrealistic …

  • Jutta




    Kevin Stallard wrote:

Whats so funny is that you guys are straining at the most solvable problem I
have ever seen.

Thanks for the laughs…it’s been amusing watch you two go round and round
and round when the problem can be very simply solved and you can look good
to your customers to boot.

Imagine you don’t want to make an install CD for your customer, but you are
willing to port your app to a different OS. And an OS that has NO warranty
to boot…

Priceless

Kevin

“Jutta Steinhoff” <> j-steinhoff@web.de> > wrote in message
news:> 3F28DFC3.F5001AAB@web.de> …
Kevin,

  1. please read carefully all legal stuff from QSSL

  2. please stop your advice when you don’t understand the topic

  3. notice, industrial users (VARs, OEMs, not hobbyists or freaks!)
    want original software products and no second hand copies from
    whatever source when they need a separate (un-bundled) Runtime
    license for a Target system.

  • Jutta


    Kevin Stallard wrote:
  1. Buy QNX runtimes
  2. Make CD with your software and QNX Runtime installer
  3. Give CD to customer.
  4. Include QNX Runtime in purchase price and a bit more for your
    troubles
    in regards to the installer.

“Jutta Steinhoff” <> j-steinhoff@web.de> > wrote in message
news:> 3F28567C.D8982821@web.de> …

Camz, I can’t follow you.

The only I understand is that you are not familiar with non
C-development systems …

Armin Steinhoff <> a-steinhoff@web.de> > wrote:
Yes … I’m the DEVELOPER and I’m not an OEM or VAR.

So there is no issue with you buying qnx runtimes and then offering
them
to your customers (aside from not being able to easily package that
up
for them to install).

Just to make it simple and clear: I’m not the OEM and I’m not
interested
to sell QNX.

Ah, now we get to the crux of it. You don’t have any problem
purchasing
the runtimes, your problem is that you don’t want to do it. That is
a
very different problem. In this case, the requirement for your
customer
to buy a development seat is not QSS’s “fault”, it is yours for
refusing
to sell the runtime licensing along with your product.

They have to give at least the warrenty that their system works as
documented …

Actually, they don’t. And to be quite honest, you probably don’t
list
off
to your customers what the OS does since its an enabling layer that
technically
does not do anything until you actually want to run an app.

Again: I’m not in the position to handle all warranty and legal
issues
of their OS in place of QSSL.

Again, this is a restriction that YOU have placed on yourself. In
all
honesty though, this “requirement” is not unique to you, or QNX.
You’d
have
the same issue with any other OS, so it’s harldy fair to complain
that
it
is QSS’s fault that you would need to deal with it and are not
prepared
and/or
are unwilling to do so. Sounds like you want to be in the business
of
writing software, but not in the business of selling it, and just
hoping
that someone will magically pay you.

There are other alternatives > :slight_smile:

Sure, you could use Linux, have all the same issues, and not have
anyone
to complain to. (you certainly wouldn’t have any hope in hell of
providing
any sort of warranty for the OS, let alone any app developed on it).

Cheers,
Camz.


Martin Zimmerman > camz@passageway.com
Camz Software Enterprises > www.passageway.com/camz/qnx/
QNX Programming & Consulting > www.qnxzone.com

John Halpenny wrote:

[… ] … Is there a process where a box seller could
deliver a legal QNX runtime box?

From my understanding, it’s only possible together with 3rd party
QNX based hard- and/or software products or applications.

Some comments from QSSL ??

  • Jutta