Hi,
I installed SP1, only to find out that our BSP (Sandpoint) is not
supported by SP1.
After uninstalling SP1, I can no longer open up the “builder window”
– Clicking on ‘project.bld’ gives the error:
“Unable to load QNX License DLL.
Your QNX License could not be obtained, some QNX functionality will be
disabled.”
How can I get my configuration/workspace back the way it was???
Thanks for any help,
John Kiernan
Bio-Imaging Research
Welcome to the world of Digital Rights Management, where
software comes with an auto self destruct feature.
We threw out QNX 6.3 because of that. Too risky.
John Nagle
John Kiernan wrote:
Hi,
I installed SP1, only to find out that our BSP (Sandpoint) is not
supported by SP1.After uninstalling SP1, I can no longer open up the “builder window”
– Clicking on ‘project.bld’ gives the error:“Unable to load QNX License DLL.
Your QNX License could not be obtained, some QNX functionality will be
disabled.”How can I get my configuration/workspace back the way it was???
Thanks for any help,
John Kiernan
Bio-Imaging Research
Windows hosted or self hosted?
Kevin
“John Kiernan” <jkiernan@birinc.com> wrote in message
news:d008ig$a91$1@inn.qnx.com…
Hi,
I installed SP1, only to find out that our BSP (Sandpoint) is not
supported by SP1.After uninstalling SP1, I can no longer open up the “builder window”
– Clicking on ‘project.bld’ gives the error:“Unable to load QNX License DLL.
Your QNX License could not be obtained, some QNX functionality will be
disabled.”How can I get my configuration/workspace back the way it was???
Thanks for any help,
John Kiernan
Bio-Imaging Research
\
It’s only risky if it affects your targets. I have 6.3 installed on two
SBC’s (just the OS and binaries to make our stuff work) and we don’t have
any licenses/ DRM issues. I don’t believe we installed any kind of
licensing whatsoever for these to work, they just work.
It only affects development seats as far as I know…
Kevin
“John Nagle” <nagle@overbot.com> wrote in message
news:d03c3o$l60$1@inn.qnx.com…
Welcome to the world of Digital Rights Management, where
software comes with an auto self destruct feature.We threw out QNX 6.3 because of that. Too risky.
John Nagle
John Kiernan wrote:
Hi,I installed SP1, only to find out that our BSP (Sandpoint) is not
supported by SP1.After uninstalling SP1, I can no longer open up the “builder window”
– Clicking on ‘project.bld’ gives the error:“Unable to load QNX License DLL.
Your QNX License could not be obtained, some QNX functionality will be
disabled.”How can I get my configuration/workspace back the way it was???
Thanks for any help,
John Kiernan
Bio-Imaging Research
That is correct - licensing is incorporated on the host side not on the
target side.
Thanks
Mike
“Kevin Stallard” <kevin@airrilabs.net> wrote in message
news:d05bmq$89h$1@inn.qnx.com…
It’s only risky if it affects your targets. I have 6.3 installed on two
SBC’s (just the OS and binaries to make our stuff work) and we don’t have
any licenses/ DRM issues. I don’t believe we installed any kind of
licensing whatsoever for these to work, they just work.It only affects development seats as far as I know…
Kevin
“John Nagle” <> nagle@overbot.com> > wrote in message
news:d03c3o$l60$> 1@inn.qnx.com> …
Welcome to the world of Digital Rights Management, where
software comes with an auto self destruct feature.We threw out QNX 6.3 because of that. Too risky.
John Nagle
John Kiernan wrote:
Hi,I installed SP1, only to find out that our BSP (Sandpoint) is not
supported by SP1.After uninstalling SP1, I can no longer open up the “builder window”
– Clicking on ‘project.bld’ gives the error:“Unable to load QNX License DLL.
Your QNX License could not be obtained, some QNX functionality will be
disabled.”How can I get my configuration/workspace back the way it was???
Thanks for any help,
John Kiernan
Bio-Imaging Research
I have forwarded this to the Tools group for comment - I suspect that you
either need to restore your .metadata from 6.3.0 or else need to reimport
your projects so that the metadata is refreshed - there are notes to this
effect in the SP1 Install Note under ‘Uninstalling SP1’.
Thanks
Mike
“John Kiernan” <jkiernan@birinc.com> wrote in message
news:d008ig$a91$1@inn.qnx.com…
Hi,
I installed SP1, only to find out that our BSP (Sandpoint) is not
supported by SP1.After uninstalling SP1, I can no longer open up the “builder window”
– Clicking on ‘project.bld’ gives the error:“Unable to load QNX License DLL.
Your QNX License could not be obtained, some QNX functionality will be
disabled.”How can I get my configuration/workspace back the way it was???
Thanks for any help,
John Kiernan
Bio-Imaging Research
\
Kevin Stallard wrote:
It’s only risky if it affects your targets.
Some of the DRM is in “diskboot” and if you have target
machines with disks, and use “diskboot”, this can be a problem.
See the thread “QNX 6.3 copy protection won’t allow safe mode -
cannot run chkfsys” in the “qnx.rtos” group for a discussion
of this. Attempting to boot into safe mode yielded the
messaage “No valid commercial license found”, after which
any further input was ignored. It was never quite clear whether
the DRM was broken or whether “diskboot” was broken.
Did that ever get fixed? After a month of messages last
August and September, the problem had been verified by
multiple users and QSSL. But not fixed. We gave up and
went back to QNX 6.21.
John Nagle
If you read through that thread it was shown that DRM had nothing to do
with the problem - safe mode was busted in diskboot.
The only DRM in diskboot is that if it doesn’t find a license it will
print out the message.
John Nagle wrote:
Kevin Stallard wrote:
It’s only risky if it affects your targets.
Some of the DRM is in “diskboot” and if you have target
machines with disks, and use “diskboot”, this can be a problem.See the thread “QNX 6.3 copy protection won’t allow safe mode -
cannot run chkfsys” in the “qnx.rtos” group for a discussion
of this. Attempting to boot into safe mode yielded the
messaage “No valid commercial license found”, after which
any further input was ignored. It was never quite clear whether
the DRM was broken or whether “diskboot” was broken.Did that ever get fixed? After a month of messages last
August and September, the problem had been verified by
multiple users and QSSL. But not fixed. We gave up and
went back to QNX 6.21.John Nagle
John - here’s an update:
You’ll need to delete the workspace/.metadata/.config/platform.cfg file (it
is pointing to the newer plugin version of SP1 license file folder which has
now been uninstalled) Restarting the IDE will reacquire the older restored
plugin version
Hope this helps,
Mike
“Mike Lemke” <nospam@qnx.com> wrote in message
news:d05d6v$9ek$1@inn.qnx.com…
I have forwarded this to the Tools group for comment - I suspect that you
either need to restore your .metadata from 6.3.0 or else need to reimport
your projects so that the metadata is refreshed - there are notes to this
effect in the SP1 Install Note under ‘Uninstalling SP1’.Thanks
Mike
“John Kiernan” <> jkiernan@birinc.com> > wrote in message
news:d008ig$a91$> 1@inn.qnx.com> …
Hi,I installed SP1, only to find out that our BSP (Sandpoint) is not
supported by SP1.After uninstalling SP1, I can no longer open up the “builder window”
– Clicking on ‘project.bld’ gives the error:“Unable to load QNX License DLL.
Your QNX License could not be obtained, some QNX functionality will be
disabled.”How can I get my configuration/workspace back the way it was???
Thanks for any help,
John Kiernan
Bio-Imaging Research
\
…except for diskboot, which I should know.
“Mike Lemke” <nospam@qnx.com> wrote in message
news:d05ccq$8ld$1@inn.qnx.com…
That is correct - licensing is incorporated on the host side not on the
target side.Thanks
Mike“Kevin Stallard” <> kevin@airrilabs.net> > wrote in message
news:d05bmq$89h$> 1@inn.qnx.com> …
It’s only risky if it affects your targets. I have 6.3 installed on two
SBC’s (just the OS and binaries to make our stuff work) and we don’t have
any licenses/ DRM issues. I don’t believe we installed any kind of
licensing whatsoever for these to work, they just work.It only affects development seats as far as I know…
Kevin
“John Nagle” <> nagle@overbot.com> > wrote in message
news:d03c3o$l60$> 1@inn.qnx.com> …
Welcome to the world of Digital Rights Management, where
software comes with an auto self destruct feature.We threw out QNX 6.3 because of that. Too risky.
John Nagle
John Kiernan wrote:
Hi,I installed SP1, only to find out that our BSP (Sandpoint) is not
supported by SP1.After uninstalling SP1, I can no longer open up the “builder window”
– Clicking on ‘project.bld’ gives the error:“Unable to load QNX License DLL.
Your QNX License could not be obtained, some QNX functionality will be
disabled.”How can I get my configuration/workspace back the way it was???
Thanks for any help,
John Kiernan
Bio-Imaging Research
\
Hi John,
The advice I gave to Mike to pass along to you is incorrect (my error).
On closer inspection it sounds like it it the licensing of the Sandpoint BSP
that is busted after the uninstall.
I’m trying to reproduce the issue now. I will post more when I can isolate
the cause (hopefully today).
Dave Young
Tools Test Lead
QNX Software Systems
david.young(at)qnx.com
“Mike Lemke” <nospam@qnx.com> wrote in message
news:d075tu$k4n$1@inn.qnx.com…
John - here’s an update:
You’ll need to delete the workspace/.metadata/.config/platform.cfg file
(it
is pointing to the newer plugin version of SP1 license file folder which
has
now been uninstalled) Restarting the IDE will reacquire the older restored
plugin versionHope this helps,
Mike“Mike Lemke” <> nospam@qnx.com> > wrote in message
news:d05d6v$9ek$> 1@inn.qnx.com> …
I have forwarded this to the Tools group for comment - I suspect that you
either need to restore your .metadata from 6.3.0 or else need to reimport
your projects so that the metadata is refreshed - there are notes to this
effect in the SP1 Install Note under ‘Uninstalling SP1’.Thanks
Mike
“John Kiernan” <> jkiernan@birinc.com> > wrote in message
news:d008ig$a91$> 1@inn.qnx.com> …
Hi,I installed SP1, only to find out that our BSP (Sandpoint) is not
supported by SP1.After uninstalling SP1, I can no longer open up the “builder window”
– Clicking on ‘project.bld’ gives the error:“Unable to load QNX License DLL.
Your QNX License could not be obtained, some QNX functionality will be
disabled.”How can I get my configuration/workspace back the way it was???
Thanks for any help,
John Kiernan
Bio-Imaging Research
\
John Nagle <nagle@downside.com> wrote:
Kevin Stallard wrote:
It’s only risky if it affects your targets.
Some of the DRM is in “diskboot” and if you have target
machines with disks, and use “diskboot”, this can be a problem.See the thread “QNX 6.3 copy protection won’t allow safe mode -
cannot run chkfsys” in the “qnx.rtos” group for a discussion
of this.
For those of you who want to read it, it is archived here:
http://www.openqnx.com/PNphpBB2-viewtopic-t3737-.html
Colin Burgess wrote:
If you read through that thread it was shown that DRM had nothing to do
with the problem - safe mode was busted in diskboot.The only DRM in diskboot is that if it doesn’t find a license it will
print out the message.
There were claims in that thread that the DRM had nothing to
do with the problem, but nothing definitive. There was this,
from Keith Russell at QNX:
First, my apologies for not getting to this sooner. I only
became aware today…At first glance I would agree with Colin that the license
issue is not related (it would be related to the mounting
diskboot does when running in safe mode). It would appear
that diskboot is broken w.r.t. to the debug shell and/or
safe mode.I have run in safe mode to get to a standard login many times,
typically when I mess up my Photon settings. I have yet to
see this problem. Though it looks easy to reproduce.I’m looking into it and will post my findings shortly.
But there was never a definitive answer in the qnx.rtos
newsgroup. It took a month to get to the point that
the problem was clearly acknowledged. And diskboot
worked before someone messed with it to put in DRM.
Further along in the current thread, there’s this, from
Dave Young at QNX:
The advice I gave to Mike to pass along to you is incorrect (my error).
On closer inspection it sounds like it it the licensing of the Sandpoint BSP
that is busted after the uninstall.
I’m trying to reproduce the issue now. I will post more when I can isolate
the cause (hopefully today).
So there’s yet more DRM. And it wasn’t admitted until it gave a
user trouble. One bug at a time, users have to discover and
disarm the self-destruct devices.
Also note this thread over on
http://www.openqnx.com/PNphpBB2-viewtopic-t4319-.html
where someone is beating their head against the wall trying to get
the Sandpoint BSP to boot on a target machine. Could that be
DRM-related? They spent months on that problem, and seem to have
finally given up.
These are only some of the ways DRM increases business risk
for customers and substantally increases the total cost of
ownership of QNX.
With free versions of embedded Linux available for
most of the platforms QNX targets (see “http://www.timesys.com”)
QNX is shooting itself in the foot here. Piracy of QNX is
not a problem. Declining market share is.
John Nagle
John Nagle wrote:
Colin Burgess wrote:
If you read through that thread it was shown that DRM had nothing to
do with the problem - safe mode was busted in diskboot.The only DRM in diskboot is that if it doesn’t find a license it will
print out the message.
There were claims in that thread that the DRM had nothing to
do with the problem, but nothing definitive. There was this,
from Keith Russell at QNX:First, my apologies for not getting to this sooner. I only
became aware today…At first glance I would agree with Colin that the license
issue is not related (it would be related to the mounting
diskboot does when running in safe mode). It would appear
that diskboot is broken w.r.t. to the debug shell and/or
safe mode.I have run in safe mode to get to a standard login many times,
typically when I mess up my Photon settings. I have yet to
see this problem. Though it looks easy to reproduce.I’m looking into it and will post my findings shortly.
But there was never a definitive answer in the qnx.rtos
newsgroup. It took a month to get to the point that
the problem was clearly acknowledged. And diskboot
worked before someone messed with it to put in DRM.
Well, actually diskboot safe-mode worked before they removed the fs-pkg
from the setup. Adding licensing didn’t do anything at all, other than
the perhaps misleading message.
In any case, a bug was acknowledged (however late) and a workaround was
given.
Further along in the current thread, there’s this, from
Dave Young at QNX:The advice I gave to Mike to pass along to you is incorrect (my error).
On closer inspection it sounds like it it the licensing of the
Sandpoint BSP
that is busted after the uninstall.
I’m trying to reproduce the issue now. I will post more when I can
isolate
the cause (hopefully today).
So there’s yet more DRM. And it wasn’t admitted until it gave a
user trouble. One bug at a time, users have to discover and
disarm the self-destruct devices.
I’m not going to argue our licensing policy.
“Please call your sales representative” :vD
Also note this thread over on
http://www.openqnx.com/PNphpBB2-viewtopic-t4319-.html
where someone is beating their head against the wall trying to get
the Sandpoint BSP to boot on a target machine. Could that be
DRM-related? They spent months on that problem, and seem to have
finally given up.
Well given that the quoted article was from John Kiernan, who started
this whole thread, I gather that he’s still at it. :v)
These are only some of the ways DRM increases business risk
for customers and substantally increases the total cost of
ownership of QNX.With free versions of embedded Linux available for
most of the platforms QNX targets (see "> http://www.timesys.com> ")
QNX is shooting itself in the foot here. Piracy of QNX is
not a problem. Declining market share is.John Nagle
Hi John,
I need your help to reproduce this problem.
I’ll email you directly with questions, until it can be reproduced/resolved.
I’ll post the results back here when we’re done.
david.young(at)qnx.com
“Dave Young” <nospam@qnx.com> wrote in message
news:d07g0o$rea$1@inn.qnx.com…
Hi John,
The advice I gave to Mike to pass along to you is incorrect (my error).
On closer inspection it sounds like it it the licensing of the Sandpoint
BSP
that is busted after the uninstall.
I’m trying to reproduce the issue now. I will post more when I can isolate
the cause (hopefully today).Dave Young
Tools Test Lead
QNX Software Systems
david.young(at)qnx.com“Mike Lemke” <> nospam@qnx.com> > wrote in message
news:d075tu$k4n$> 1@inn.qnx.com> …
John - here’s an update:
You’ll need to delete the workspace/.metadata/.config/platform.cfg file
(it
is pointing to the newer plugin version of SP1 license file folder which
has
now been uninstalled) Restarting the IDE will reacquire the older
restored
plugin versionHope this helps,
Mike“Mike Lemke” <> nospam@qnx.com> > wrote in message
news:d05d6v$9ek$> 1@inn.qnx.com> …
I have forwarded this to the Tools group for comment - I suspect that
you
either need to restore your .metadata from 6.3.0 or else need to
reimport
your projects so that the metadata is refreshed - there are notes to
this
effect in the SP1 Install Note under ‘Uninstalling SP1’.Thanks
Mike
“John Kiernan” <> jkiernan@birinc.com> > wrote in message
news:d008ig$a91$> 1@inn.qnx.com> …
Hi,I installed SP1, only to find out that our BSP (Sandpoint) is not
supported by SP1.After uninstalling SP1, I can no longer open up the “builder window”
– Clicking on ‘project.bld’ gives the error:“Unable to load QNX License DLL.
Your QNX License could not be obtained, some QNX functionality will
be
disabled.”How can I get my configuration/workspace back the way it was???
Thanks for any help,
John Kiernan
Bio-Imaging Research
\
Mike Lemke wrote:
I have forwarded this to the Tools group for comment - I suspect that you
either need to restore your .metadata from 6.3.0 or else need to reimport
your projects so that the metadata is refreshed - there are notes to this
effect in the SP1 Install Note under ‘Uninstalling SP1’.
Mike,
Thanks, I fixed the problem by restoring the .metadata directory from a
clean install of 6.3.0. (except for org.eclipse.core.resources)
Thanks for your help,
John Kiernan, Sr. Software Engineer
Bio-Imaging Research, Inc.
jkiernan@birinc.com