my haxmedit dos version doesn't work on my Pentium 4
- Sapphire Wolf
- DBB Admiral
- Posts: 1463
- Joined: Mon Nov 24, 2003 3:01 am
- Location: Nope.avi , gender: male
- Contact:
my haxmedit dos version doesn't work on my Pentium 4
When I open haxmedit (dos) with haxmedit32, haxmedit (dos) closes, it used to work on my old Windows XP, but not any more on my current Windows XP(home edition), how do I make Haxmedit dos work?
Oops, Wrong section!
Mod, Move this to "Coder's corner"
Oops, Wrong section!
Mod, Move this to "Coder's corner"
- Sapphire Wolf
- DBB Admiral
- Posts: 1463
- Joined: Mon Nov 24, 2003 3:01 am
- Location: Nope.avi , gender: male
- Contact:
- Sapphire Wolf
- DBB Admiral
- Posts: 1463
- Joined: Mon Nov 24, 2003 3:01 am
- Location: Nope.avi , gender: male
- Contact:
- Sapphire Wolf
- DBB Admiral
- Posts: 1463
- Joined: Mon Nov 24, 2003 3:01 am
- Location: Nope.avi , gender: male
- Contact:
Maybe you have the infamous divide by zero condition. In some situations, assembler code make a timing and then a division based on that timing. Older software containing that code running on faster computers may run so fast, the timing resolves to zero and the CPU hangs on a divide by zero error.
However, if you're running it in a virtual and protected environment (like Windows) it shouldn't take the whole machine down, only the program itself.
If you don't understand the above, ignore it. It's not really relevant anyway
However, if you're running it in a virtual and protected environment (like Windows) it shouldn't take the whole machine down, only the program itself.
If you don't understand the above, ignore it. It's not really relevant anyway

I can't remember the specifics exactly, but I think 32 didn't allow you to edit weapon info from any ham file, whereas DOS allowed it so long as it wasn't your descent2.ham file, or at least a file named descent2.ham, not sure of their determining methods. It was more of a matter of their hacker protection or something. I don't think either allowed modifying ship info in any condition, but you could still use the programs to determine offsets and use a hex editor to do it yourself.
And, yeah, 32 was definitely a resource whore back in the 9x days, if that's what you're referring to.
And, yeah, 32 was definitely a resource whore back in the 9x days, if that's what you're referring to.