Usage Count Expiry - How do I reset it?

[freddy4242]

After previously using version 6, I am now new to version 7. I am testing some of the neat features of version 7 and decided to set a Usage Count Expiry for my "test install" to see how it worked. I set it to expire after 2 installs. It worked wonderfully. But, now my build is "expired". I would like to be able to "reset" the expiry counter for this install back to zero. (I would have thought a subsequent BUILD of the project would reset the count?)

If this was a real project, how would I "reset" the count to zero after testing my installation, so that I could then rebuild and subsequently distribute it?

I know that this is written to the registry, but where? Can the created expiry key be deleted? Or, perhaps it can be done in SUF7's interface somewhere and I have just missed it (I can find no mention in the manual of how to reset the count)?

I suppose the same would apply to expiry dates etc.

Hi there..

May I suggest that you could RAISE the usage count in the same Project
and rebuild...should allow you to continue testing the created Runtime.

Have you tried to Disable-Deselect this Option in Advanced Options, Save
then rebuild the Project ?

Hope helps..

[freddy4242]

Yes, I did think of doing that (raising the count). That way I could continue to test on my own system without a worry. Then, when it comes to building the final installation package, I would simply set it back to what I wanted it to actually be and build it. This method would work. But, if I need to use my installation to install the software on my own system at a later date ... or ... if a user then calls me up (I create installations for people whom I also provide customer support for) and alerts me to a fault in my install which I would like to see for myself by running it ... or whatever other reason ... then I will be unable to run it because my own system would have surpassed the allowed number.

As for trying to disable, save and then rebuild ... yes, I tried that too. No avail.

So, basically, I am still left with the inability to actually run an install (that I myself created) on my own system once the set number of usage counts has been exceeded. It seems silly. So I am sure there is or must be a way to either work around this or clear it somehow.

[freddy4242]

Hmmm. Actually, it occurs to me that one way to go would be to actually create the installation WITHOUT the usage count. This is the file that I save on my system for my own use or testing purposes. But, when it comes to distributing to the users, put in the usage count, build and ship. So the user ends up with a usage count limited version, but the one on my own development system is NOT set with a usage count limit. This is probably how IndigoRose designed it to be used. But for this method to work, I build once for the user (with a usage count), and then build a second time for myself (removing the usage count). So, in other words, do two builds. Doesn't seem right if I have to do it like that. I am sure I am missing something simple here ?????

[Brett]

Open a support tickat at http://support.indigorose.com. We will tell you how to reset the count there. Not something that we want publically posted.

[Jason Pate]

I would never run my installer on my development system, in the old days always used GHOST to do images on a test system. Now days I use Microsoft Vitural PC. Its not a true test of a install if its run on the development system. Aslo both Ghost and VPC allow me to test different OS.

[Adam]

I must agree that Virtual PC is supper useful for testing installs. I use it constantly.

Adam Kapilik

[gbrown]

Yes, a virtual PC is THE way to test things out to make sure you have the full set of DLL's OCX's etc etc. I use VMware and have an "out of the box" install of XP and 2000. I boot up in one, do the install, and run the software. If I get a "file missing" message (WHY doesn't the Microsoft error gizmo say "aardvark.dll is missing"????) I figure out what's what, throw away the current VMware session and try again.

[freddy4242]

Originally Posted by Jason Pate

I would never run my installer on my development system, in the old days always used GHOST to do images on a test system. Now days I use Microsoft Vitural PC. Its not a true test of a install if its run on the development system. Aslo both Ghost and VPC allow me to test different OS.

I agree. The way it works here in my company is the developers hand the softare over to me for final testing and, when we're all happy, for the creation of the install. So the machine I use is actually technically not the "development" PC for the software. It is for the installs, but not the actual software. I create the install, test it on my machine and THEN go to a different machine (usually one that is "clean" from a format and fresh install of Windows) and run the final tests of the installer there. But for the initial creation and testing of the "draft" install, I use my own machine. It is this machine that I use to create the install on that I need to not give me grief about usage expiry etc.

[freddy4242]

Originally Posted by Brett

Open a support tickat at http://support.indigorose.com. We will tell you how to reset the count there. Not something that we want publically posted.

Thankyou Brett. I have submitted a support ticket.

May I suggest that when using these functionalities in created Projects:
Keep an accurate record of the " ID " for future reference...

Side Query: for 'tricky ricky' - autoreset coding at runtime

eg: resetting an updated trial when wanting to use same ID
(or wanting to detect if an earlier version trial has 'expired' etc.)

runtime sequence: is the default Global 'loaded' before the 'checks' ?
Without revealing anything of course, a yes\no would suffice...