VOGONS

Common searches


First post, by miller11568

User metadata
Rank Newbie
Rank
Newbie

I have a retail copy of Crashday v1.0 but it won't start on Windows 10, but it does on my old Windows XP system. Why is this and can someone help me fix the crash by hex-editing the executable or applying the latest official patch to run on Windows 10?

Reply 1 of 9, by myne

User metadata
Rank Member
Rank
Member

You're going to have to put more effort into explaining what happens and what you've tried.

Because right now it reads like the classic "it worked fine yesterday!" which is true of literally everything that dies - including people.

Eg
Error message?
Compatibility modes tried?
What on earth makes you jump directly to hex editing as a solution?

Things I built:
Mechwarrior 2 installer for Windows 10/11 Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11 auto-install iso template (for vmware)
Script to backup Win9x\ME drivers from a working install

Reply 2 of 9, by miller11568

User metadata
Rank Newbie
Rank
Newbie
myne wrote on 2024-05-15, 08:11:
You're going to have to put more effort into explaining what happens and what you've tried. […]
Show full quote

You're going to have to put more effort into explaining what happens and what you've tried.

Because right now it reads like the classic "it worked fine yesterday!" which is true of literally everything that dies - including people.

Eg
Error message?
Compatibility modes tried?
What on earth makes you jump directly to hex editing as a solution?

I tried a compatibility mode and Crashday does not get an error message but it crashes. I have a debugger called IDA getting a warning message named:

87836A: The instruction at 0x87836A referenced memory at 0x6FFB4. The memory could not be read -> 0006FFB4 (exc.code c0000005, tid 17216)

So, can you help me hex edit the executable to fix the crash and be able to play Crashday v1.0 on Windows 10?

Reply 3 of 9, by myne

User metadata
Rank Member
Rank
Member

I think you're barking up the wrong tree with the hex editing.
I'd try dxwnd because its memory emulation hooks and exception handler are likely to make it work without modification.
The other option is the windows compatibility toolkit.

I can't say much more than that. The local expert I'm aware of is BEEN_Nath_58, who is in the first thread in my signature.

https://sourceforge.net/p/dxwnd/

https://learn.microsoft.com/en-us/windows/win … y-toolkit--act-

Scratch all that.
https://www.pcgamingwiki.com/wiki/Crashday

See the notes on the drm update

Things I built:
Mechwarrior 2 installer for Windows 10/11 Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11 auto-install iso template (for vmware)
Script to backup Win9x\ME drivers from a working install

Reply 5 of 9, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t
myne wrote on 2024-05-15, 10:49:
I think you're barking up the wrong tree with the hex editing. I'd try dxwnd because its memory emulation hooks and exception ha […]
Show full quote

I think you're barking up the wrong tree with the hex editing.
I'd try dxwnd because its memory emulation hooks and exception handler are likely to make it work without modification.
The other option is the windows compatibility toolkit.

I can't say much more than that. The local expert I'm aware of is BEEN_Nath_58, who is in the first thread in my signature.

https://sourceforge.net/p/dxwnd/

https://learn.microsoft.com/en-us/windows/win … y-toolkit--act-

Scratch all that.
https://www.pcgamingwiki.com/wiki/Crashday

See the notes on the drm update

I will have to see why the game reaches that stage first. Secondly the game uses the WinNT heap manager so that wasn't to be a problem either

previously known as Discrete_BOB_058

Reply 6 of 9, by Nicknine

User metadata
Rank Newbie
Rank
Newbie
tgomola wrote on 2024-05-15, 11:26:

Find and install a crack. Sometimes old DRM doesn't work on modern Windows and cracking the game is the only way to get it running.

SecuROM (which is the protection used by Crashday and only in EU release) works perfectly fine on modern Windows, don't spread misinformation, please.

Reply 7 of 9, by miller11568

User metadata
Rank Newbie
Rank
Newbie
BEEN_Nath_58 wrote on 2024-05-15, 11:52:
myne wrote on 2024-05-15, 10:49:
I think you're barking up the wrong tree with the hex editing. I'd try dxwnd because its memory emulation hooks and exception ha […]
Show full quote

I think you're barking up the wrong tree with the hex editing.
I'd try dxwnd because its memory emulation hooks and exception handler are likely to make it work without modification.
The other option is the windows compatibility toolkit.

I can't say much more than that. The local expert I'm aware of is BEEN_Nath_58, who is in the first thread in my signature.

https://sourceforge.net/p/dxwnd/

https://learn.microsoft.com/en-us/windows/win … y-toolkit--act-

Scratch all that.
https://www.pcgamingwiki.com/wiki/Crashday

See the notes on the drm update

I will have to see why the game reaches that stage first. Secondly the game uses the WinNT heap manager so that wasn't to be a problem either

Which offset how can I hex edit the executable?

Reply 8 of 9, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t
miller11568 wrote on 2024-05-15, 20:04:
BEEN_Nath_58 wrote on 2024-05-15, 11:52:
myne wrote on 2024-05-15, 10:49:
I think you're barking up the wrong tree with the hex editing. I'd try dxwnd because its memory emulation hooks and exception ha […]
Show full quote

I think you're barking up the wrong tree with the hex editing.
I'd try dxwnd because its memory emulation hooks and exception handler are likely to make it work without modification.
The other option is the windows compatibility toolkit.

I can't say much more than that. The local expert I'm aware of is BEEN_Nath_58, who is in the first thread in my signature.

https://sourceforge.net/p/dxwnd/

https://learn.microsoft.com/en-us/windows/win … y-toolkit--act-

Scratch all that.
https://www.pcgamingwiki.com/wiki/Crashday

See the notes on the drm update

I will have to see why the game reaches that stage first. Secondly the game uses the WinNT heap manager so that wasn't to be a problem either

Which offset how can I hex edit the executable?

Quick solution: Install 1.1 patch

previously known as Discrete_BOB_058