• 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

I think I broke my HeroLab, won't launch now...

Gumbytie

Well-known member
Not sure what happened, submitted a help ticket but thought I would throw error message up on forums as well:

C:\Program Files (x86)\Hero Lab\HeroLab.exe
4.0c 324
ACCESS VIOLATION
Address: 0x0042490f
Type: bad read
major: 6, minor: 1, build: 7601, platform: 2, version: Service Pack 1, spmaj: 1, spmin: 0, suitemask: 00000300, type: 1

I have been working on a Hollow Earth ruleset using Authoring Kit (to learn coding) and had changed out a logo.bmp in Savage Worlds to test something. That is all I remember doing before closing and then trying to relaunch.

Any suggestions?

I was going to delete the Authoring Kit game and Savage Worlds (backed up of course) and try and launch, last thing I can think of trying.

Cheers,
Gumbytie
 
Check out this issue I found:

http://forums.wolflair.com/showthread.php?t=24085

Try this: Copy logo.bmp from another known good directory (d20? Pathfinder?), and replace the logo.bmp that you created.


BoomerET

Edit: Just checked my own post, sounds like the exact same issue, bad read!!!

Let me know if this solves your problem, maybe LW can update the bmp library they use.
 
Last edited:
Boomer,

Thanks man that was exactly the problem. Wow, don't mess with the logo.bmp apparently. And all I was doing was adding the playing card symbols to Savage Worlds logo in order of importance. Thought it looked cool and would help us remember which suit was more important :)

Oh well. It is what it is.

Cheers.
 
Thanks for reporting this - I've found an issue that could cause such a crash, so it'll be fixed for the next release.

Make sure the file you were replacing the logo with was a bitmap with the correct color depth (8 bits/pixel) - if you change that, the Windows functions we use to load bitmaps can't load it, so it'll be ignored (or cause a crash as you found).
 
Back
Top