• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Requires new version every time I start up

Reyzoul

Member
Every time I start up lately, like.. in the last three days..
HeroLab assures me that i need a new version of HeroLab to load the Pathfinder rule set.

I let herolab download the update, unpack it, update itself, and restart.. Now I can load whatever system I want.

I can close Herolab and restart it again.. and I'm right back to where I started.. it wants to get an update because it claims the pathfinder ruleset requires it.

Um.. what?

It is downloading around 8Megs from wolflair every time I start the system.
Unnecessarily.
 
(a) if I close herolab
(b) restart herolab
I go through this process

no license was activated between those two steps

after herolab downloads and updates itself, it does go re-obtain the license.

and I did happen to purchase three new licenses recently.

but between step (a) and step (b), I am not going to woflair and purchasing licenses.

I'll go through the process right now for example.

Yep.. there it is.. it wants to download the new version of herolab so that pathfinder ruleset can load... argh.. click the exclamation mark.. wait while it downloads the 8m of data. herolab exits and updates itself. herolab restarts on its own. herolab wants to retrieve my license because a new version of herolab was just installed (no it wasn't.. the same version was installed!).. ok fine.. retrieve license. Now it shows me the rulesets and no exclamation mark. Ok fine. I select pathfinder and I can work with it just fine.. up until the next time I close herolab.

Now I close herolab. click on herolab to start it up again.
O look. exlamation mark next to the pathfinder ruleset again...
and round and round we go.
 
Ha.

I found the problem. Not sure how to fix it.

I have herolab installed @ "D:\HeroLab\Hero Lab\HeroLab.exe"

When herolab is downloading itself and re-installing and restarting itself.
the herolab that is starting is @ "C:\Program Files (x86)\Hero Lab\HeroLab.exe"

Bad program... Bad.
 
Well now that you've caught the error you know to watch the directory you're installing updates for.
 
I performed some registry surgery, that wasn't successful. I thought it would work since herolab clearly is not examinig from where it is executing to determine to where to put updates/restart.. stands to reason the location must be in the registry somewhere. But either it isn't, or I didn't find it. So went with plan b.

Uninstalled the herolab that was installed according to add/remove programs on the C drive (I don't recall installing on C: drive though.. I dont' install anything there except the OS as a rule.. maybe I made a mistake).. then re-executed the one @ D: and.. it acted as if I had never run it before, asking for the license information.. Ok this seems good.. new behavior is good.

Spent time updating itself, downloading all the systems, the pdf writer, the hero images, the and whalla.. still have the same problem.. OMG..

I shut down herolab, restarted it, and it thinks it isn't updated. It downloads the new version, and this time I watch where it installs.. it does not install to the same location it is executing from which would be the right thing to do.. instead it installs to "C:/program files/hero lab" -- it has to create that directory to even do that. That's the problem.

Is this path hard-coded?

I am going to try re installing fresh. (But surely there's a registry entry or a file or somewhere that configures this)
 
Last edited:
Looks like doing a fresh install fixed it finally.

herolab executable now firmly resides on the D: drive, and I hope... next time there is an update to the executable, it updates it on the D: drive in my custom location as it should... and doesn't try to create some fresh install on C:.
 
Back
Top