Richard Chambers
06-27-2003, 08:41 AM
One of my developers, Russell Herrington, found a solution which
appears to work at the customer site.
The solution requires that the customer edit the Windows registry and
delete the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\LicenseName]
This is the key that the Softlocx control creates using the license
name information we supply using the SetLicenseName(_T("LicenseName"))
method of the Softlocx control. Our application actually uses
something other than LicenseName.
We also told them to delete the LicenseName.slx file that the Softlocx
control creates, as our source code requested, to backup the licensing
information in case the information stored in the Windows registry
gets clobbered for some reason.
I have spoken with Bit-Arts design, Joe Dillion, this morning who has
provided me a Visual Basic application which uses the Softlocx Remove
method to remove the licensing information, much cleaner than registry
editing.
After a discussion with Joe, we have asked the customer to do the
following for their deployment CD:
- do a clean install of Windows NT and service packs
- install their standard applications including ours
. do not start up our application after installation
- create the deployment CD
- test the deployment CD on a new PC
- at the time of the test, try our application
This should result in a clean deployment CD which should not require
any registry editing in order to complete the licensing procedure for
our application.
We believe this will address the issue.
We will be adding this procedure and a Caution to our installation
notes.
My thanks to Joe at Bit-Arts as well as Brian, customer support
manager at Smarte Solutions, who was prompt and courtious despite my
irritation about the issue.
appears to work at the customer site.
The solution requires that the customer edit the Windows registry and
delete the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\LicenseName]
This is the key that the Softlocx control creates using the license
name information we supply using the SetLicenseName(_T("LicenseName"))
method of the Softlocx control. Our application actually uses
something other than LicenseName.
We also told them to delete the LicenseName.slx file that the Softlocx
control creates, as our source code requested, to backup the licensing
information in case the information stored in the Windows registry
gets clobbered for some reason.
I have spoken with Bit-Arts design, Joe Dillion, this morning who has
provided me a Visual Basic application which uses the Softlocx Remove
method to remove the licensing information, much cleaner than registry
editing.
After a discussion with Joe, we have asked the customer to do the
following for their deployment CD:
- do a clean install of Windows NT and service packs
- install their standard applications including ours
. do not start up our application after installation
- create the deployment CD
- test the deployment CD on a new PC
- at the time of the test, try our application
This should result in a clean deployment CD which should not require
any registry editing in order to complete the licensing procedure for
our application.
We believe this will address the issue.
We will be adding this procedure and a Caution to our installation
notes.
My thanks to Joe at Bit-Arts as well as Brian, customer support
manager at Smarte Solutions, who was prompt and courtious despite my
irritation about the issue.