Hero Lab V3.6 Released

[rob]

Originally Posted by bocephus

It is working fine now without any compatibility settings though.

So let me make sure I'm understanding the sequence of what happened here...
1. V3.6 crashed once
2. You ran V3.6 in XP compatability mode successfully
3. You stopped running it in XP compatability and are now running fine with no special handling.

Is that correct? If so, and without any details about the crash, there's unfortunately not a lot we can do to investigate this. :-(

[rob]

I gotta stop typing at the same time you're typing. :-)

We'll see if we can reproduce anything on this end with the initial update logic from V3.5.

[Leonal]

I got the same error after downloading the update and clicking yes to install.
Copied from lwderror3512.txt

E:\Games\HeroLab\HeroLab.exe
3.5  203
ACCESS VIOLATION
Address: 0x005813ea
Type: bad read

Running the program and the update again, even without any compatibility mode fixed it.
E: is not my Windows drive, and I'm running Win7 Home Premium 64.

Thanks for the update btw.

[Colen]

Thanks for the error report, Leonal. Based on that crash log, I think this is a bug that I fixed in Hero Lab 3.6.

If you encountered this bug but managed to install Hero Lab 3.6 successfully, please try the following so we can confirm the bug is fixed:

1. Open Hero Lab 3.6, and hit the "Locate Updates" button.
2. Download the "Hero Lab (V3.6)" update and say "yes" to install it, as if you were updating to a new version of Hero Lab.

Did Hero Lab 3.6 crash, or did the update install successfully?


If you can't install Hero Lab 3.6 because of the crash, you can download and run the new installer manually from here:

http://www.lonewolfdevel.com/submit/...asp?product=hp

Sorry for the inconvenience - this bug should hopefully be fixed now, so after you install this update it shouldn't cause any further problems.

[DMG]

I just had the exact same problem in W7x64. But running the installer directly from the download folder worked fine.

[Xorial]

Originally Posted by rob

It crashed? Yikes! It's been rock solid for us here in the office, and both Colen and I are running Windows 7 x64.

When does it crash? Where do you get during use before it crashes?

I use Win 7 Ultimate 64bit. I didn't even know there could be a problem with it crashing on a 64bit system until I read it here. Mine runs just fine.

[Bitter Thorn]

I tried to down load the HL 3.6 update, but the program will not auto restart, so I tried to do a manual download off of the site, and now I can't open HL at all.

I get this error message:

Error on line #13 in C:\herolabProduct\.\base_updatescfg.xml - Unrecognized attribute 'scalemax' in element 'form'

My OS is 2000 professional.

Please help!

Thanks.

[Bitter Thorn]

Originally Posted by Bitter Thorn

I tried to down load the HL 3.6 update, but the program will not auto restart, so I tried to do a manual download off of the site, and now I can't open HL at all.

I get this error message:

Error on line #13 in C:\herolabProduct\.\base_updatescfg.xml - Unrecognized attribute 'scalemax' in element 'form'

My OS is 2000 professional.

Please help!

Thanks.

OK. I installed the upgrade with HL off, and then I started it. It requested license authentication when I turned the program on, and now it seems to be OK.

[Kinsfire]

I don't know if this needs its own thread or should be here.

I have HL installed on multiple machines (licenses for each one, don't worry - I'm legal ), and one of them is my wife's netbook. We have 3.6 running on the thing just fine (XP Home SP3), but have the problem that in certain tabs (such as wizard), even if it is obvious that the data continues below the bottom of the screen, there is no way to move lower.

In installing, we noticed the Choose Form reference as one of the things fixed. Is this a choice in the menu, or an automatic thing? If it is in the menu bar, then where is it?

[rob]

Originally Posted by Bitter Thorn

OK. I installed the upgrade with HL off, and then I started it. It requested license authentication when I turned the program on, and now it seems to be OK.

This sounds like something got stuffed up with the installation process. I'm glad a re-install cleaned up the problem. Installing just overwrites what's there, so a re-install will usually fix issues like this.