Digital Workshop

Hi

Does anyone know if you can set the number of days (Pub Properties Security tab) until the evaluation version expires to 0?

The evaluation key generating feature is a nice security option since each computer will need a unique unlock code. The Security tabs timeout spin buttons (days or number of times to run) stop at 1, not 0. You can delete 1 in the box and replace it with 0, but will this actually result in 0 days or run's?

Any help would be appreciated.

Kind Regards,

Simple answer, why not just try it?

Ron.

Ron

Thanks for your reply. I did try it, and the "0" setting will not hold. It automatically reverts to "1."

Perhaps, there is a way to script the evaluation period to equal 0, but I'm unsure how.

Kind Regards,
Stephen

Hi Stephen,

Why do you want the evaluation to be set at 0 days or 0 times to run? Maybe you can clarify what you're trying to do?

Thanks Steve for your reply.

I have a project that is comprised of 2 executable Opus pubs, a main one and a secondary one. The main one is freely accessible, while the second one, which has chapters only accessed from menu buttons, hyperlinks in the first, would require an unlock code to enter. Easy enough if I set the second up as an evaluation with a number of days or runs before expiry.

I would rather not have the viewer access the seconday one at all, unless they have an unlock code. The Opus XE 5.5 feature is a wonderful device in that each viewer's computer will generate a unique registration code for which the key generator utility can create a unique unlock code. This is preferrable to a single password to unlock the second pub. A non-unique password, I'm afraid, can be given out, defeating its security, while a unique arrangement far better protects the second pub.

I recognize that if a "0" evaluation could be set for the second pub, I would also need to create a pop-up screen with slightly different wording than the default Opus evaluation expired screen, yet the same input boxes to unlock the pub. They would need to paste into a text input box the unique code I would supply from the key generator utility, which would then unlock only their copy.

I hope I have expressed this clearly enough. I appreciate your inquiry and am hopeful there's a solution.

Kind Regards,
Stephen

A simpler solution would be to always pass a parameter to the second publication from the Launch command - for example "/hfvsdufwh" (anything unique and complicated would do). Then just check the parameters in the second publication and just exit again if the parameter hasn't been passed. Since the end user cannot see the Launch commands there is no way they could tell what you were doing.

See the Passing Parameters to Launch File action help topic for more inforamation.

Thanks Duncan for your reply.

Passing parameters is how I've set up the second publication to be accessed from the first. What I need to do, if possible, is set a restriction to launching or entering the second pub, if a purchase has not been made and an unlock key, unique to that viewer's computer, not obtained from me.

The difficulty with a generic password sent back by me, and set up as part of the parameters, is that anyone could then use it to unlock multiple copies of the second pub. The evaluation feature utilizes a unique code for each separate computer.

Can this evaluation feature be set/scripted to 0, so that the second pub never opens without a unique unlock code generated by the key generator utility and sent by me? I would then simply set up a custom pop-up when the viewer tries to enter the second pub (couldn't say "evaluation expired" but rather "in order to access this material, please send your registration code" and "please enter the unlock code"). When the pop-up's conditions are met (unlock code entered), it would then permanently unlock the second pub.

Can this be done? If not: please add to the wish list.

Kind Regards,

Hi

I've been struggling to set up actions/scripts as best as possible to try to create the evaluation/unlock features as discussed above, using a sample pub.

Since the pub eval cannot be set below running 1 X, I've used this. After the first runtime which gets the viewer to the first page, subsequent runs will take the viewer to the expired page, where the PubEvalKey is displayed. The viewer is asked to enter the unlock code (presumeably furnished by the pub's author, me). You can get this by using the key generator utility in your copy of Opus (Pub ID= open). Once the correct unlock code is entered and the unlock button clicked, it should (1) permanently unlock the pub and (2) take the viewer to the second page, showing the pub is unlocked.

Up to now, I can't get it to work.

I've attached the sample .imp file in the hope that a solution can be suggested. I must be doing something wrong, or this feature is not able to be set up.

Any help will be appreciated.

Kind Regards,

Hi Stephen,

Have a look at the ammended IMP. It should work as you expected. I'm not sure why you had any reading/writing to the registry, as it does not appear to be needed. I've added a reset button on the first page, so if the pub is made to be non-expire, you can test it again.

You should now be able to customise things on your "real pub" so you can take advantage of the unlock feature. Hope this helps.

Hi Steve

Thank you so much!

Kind Regards,