In such a case, keep them high, David and explain me QSSL philosophy: the
reason of the new format is
- putting pressure to stop usage of QNX4 or
- to get money from selling CDs or
- to block ilegal redistribution of software or
- another reason - (how?)
Really the .tarx files are not interesting for us becuse we would need to
change the whole installation procedure or our products. So your effort on
e.g. supporting hardware is useless for us. Rather that modification of the
older product for QNX4 we use a newer product on another platoform instead
(btw. it is not QNX6, so for QSSL such a decision causes loss). On the other
way, we see no problem to pay for updates in the appropriate form regarding
prices as for the update CD.
Andy
“QNX” <david_orr@cascades.com> wrote in message
news:b8r7k1$8v$1@inn.qnx.com…
Here is my hand up high on that notion Andy!!
David
andy@microstep-mis.com> > wrote in message
news:b83luu$4ca$> 1@charon.microstep-mis.sk> …
And can’t you distribute .pax.F files on the CDs instead .tarx ? or both
?Andy
Martin Walter <> martin@qnx.com> > wrote:
Wow… I don’t read news for a couple of days and look what I come
back
to!
I just read through this thread, and could have commented to each
message,
but decided to just add a commnet to the end of the thread…I couldn’t agree more…
/etc/install was simple and effective, it’s a shell script everyone
can
see
what’s going on.
QUICS, same thing simple and effective. The update system built a
custom
environment for each user based on the product licenses they had
registered
and gave them access to the appropriate updates. Guess what MyQNX
accounts
will do? The exact same thing but with a pretty front end.Unfortunately even the good things change. We went to a CD
distribution
because floppies were getting too difficult to source, the quality was
going
down, the number required was going up, and everyone wanted the
product
on
CD.
With the CD came the ability to keep track of the products that were
installed, and even un-install them. We changed the format to include
encryption so that a license was required for each product in order to
be
able to install it, this enabled us to hand out CD’s with short
duration
licenses as evals.I could/should have addressed more o fteh questions/ and poinst that
were
raised, but there’s no point in flogging a dead horse >BTW… I vote for /etc/install and keeping QUICS around
-Martin.
“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:b7k7jt$d13$> 3@inn.qnx.com> …
Rob <> rob@spamyouself.com> > wrote:[very good discussion deleted]
Don’t get me wrong… I sincerely appreciate the fact that you
(QSSL)
have
committed to adding/upgrading drivers and addressing bug fixes for
Qnx4
for
the foreseeable future. And that you have followed through by
making
the
recent updates available. These are all very good things , thank
you.
Further, this is appropriately where continuing Qnx4 development
should
be
concentrated. BUT, Please! Please! Please! Continue to do “very
good
things”, by also supporting .tar.F updates that are a tried, true,
complete
and fully supported methodology for installing these updates.That’s my $.02 US
I completely agree.
QSSL has come out with several upgrades/bug fixes that I don’t have
because they were only offered on the silly ass .tarx CDs.Let’s see a show of hands. Who else would like a traditional upgrade
option for their final version of QNX V4 software?
\
