Crush deluxe! constant application error

[rob]

I am trying to get Crush! deluxe to run on my win 10 HP notebook laptop via DXwnd. But i end up with the constant error message popping up, specifically "The application was unable to start correctly (0xc0000022). Click OK to close the application" message. i tried the option provided to me, such as the allow admin caps, flip emulation, emulate win maximize, compat options, same result. What could be going wrong here?

Also theres a guy on YouTube, who got the game to work using your program: https://www.youtube.com/watch?v=8FADeKbBkHg&t

[gho]

Sadly, I got the game working too at first shot and with default settings.
First of all, be sure you hooked the good executable, that should be CRUSHD.exe (not CRUSH.EXE!) though I doubt you made this error since in any case you shouldn't get the 0xc0000022 error code.
Then, you should check that the error is NOT introduced by DxWnd: do you get the same error running the game without DxWnd? I hope so ...

Looking at MSDN this is the explaination, generic enough to imply almost everything:

   "The application failed to initialize properly (0xc0000022)." 

But some hint follows:

This is due to the DLL that is used by the application you are going to execute doesn't have the rights for the current user or system user.

Now, the game has some private dll, but going through the dependencies here are some possible culprits, that could be either missing or lacking privileges (?):

• DSOUND.DLL
• DDRAW.DLL
• DPLAY.DLL
• MFC40.DLL
• MSVCRT40.DLL

Now, DSOUND and DDRAW should exist in your Win10 HP, but it is possible that you have some streamed version that lacks support for legacy old ddraw releases (I'm not sure I know what I'm saying...), DPLAY.DLL could simply be missing. Finally, MFC40.DLL and MSVCRT40.DLL should be an old version of C runtime libraries, it could be useful to download them from a safe place and put a copy of them in the game folder. In any case, using a dependency walker tool you should get some precise info without need of guessing, I'll try to find one for you.

Talking about permissions, then, I recall that in some cases Win10 doesn't like executing legacy programs below the desktop folder. You may try to install the game somewhere else.

I tested the game quickly on my Win7, later on I'll repeat the test at home on a genuine Win10. In the meanwhile, please, let me know the results of your experiments.

[rob]

Downloaded the missing .dlls and put them in the game folder, played without Dxwnd, nothing but error, played with Dxwnd, same result, hooked and unhooked, nothing changed. I hope you found a workable solution for this game.

[gho]

Sorry, yesterday evening I was bus with v2.04.34 release and I couldn't test the game on Win10, though I fear I will get another unfortunate success. I'll try again this evening.
In the meanwhile I just noticed that the first thing the game does is showing a dull intro movie (the one with a crushed CD-ROM), that could be encoded with some esoteric codec and cause troubles. Do you see the crash before or after the intro? If it's before it could be useful to delete (or, better, rename) the "video\MEGALOGO.AVI" file and see what happens. Also, playing that video with some AVI player does replicate the problem? I tested the game, and it works perfectly also without intro movie.
In addition, just in case the game crashes not immediately but after DxWnd has a chance to log something, could you set the log flags (you have to enable "expert mode" for that) as in the picture, grab the dxwnd.log file in the game folder (if it exists) and post it here?
Final desperate attempt, you could try to set the "Compatibility/Handle Exceptions" flag.

[rob]

Neither, it hardly shows the intro or starts the game at all, just the confounded error message, straight out of the gate as i launch, that seems to repeat itself over and over again. Which means, its apprantly going no where and not logging anything. This is ofcourse a Abandonia copy i had, and it worked on other computers such as the Vista, created teams, had cpu leagues and playoffs with them, watch every game start to finish. Tried it on wins 7, all i got was the menu but ofcouse old games don't usually work out well with 7. you get the music of the game, but the cursor and menu either is stuck or flickers until you minimize it and show you the menu an cursor. When i get to play it on Win 10 finally, i hope to not see that performance again.

[gho]

Strange indeed. I mounted the Abandonia RIP too, and it works (provided that what I see is the indended behaviour) very well on my development Win7 pc using DxWnd. I fear that whatever could be the reason for your troubles, it must depend on your machine, and that won't make it easy at all to find out. Unfortunately, since the game crashes before DxWnd hook, we can't rely on the logs to get some clue.
If I were you (or, if you were me, but we're not...) here is what I would try right now: download a copy of OllyDBG v2.01 (google and find it..), run it fullscreen (maximize the window) and run the game through it (File -> Open ... and input the game full path, then press F9 to run) until the debugger detects the crash, then take a screen picture and post it here: the location of the crash should at least point to a specific dll and there we may concentrate our efforts.
P.s. sometimes the debugger finds continuable exceptions that don't hurt the game: to be sure you got the final point, press <Shift><F9> a few times to try to step over.

[rob]

something like this?

or like the other screen?

[gho]

Bad news here: finally I could try it on a genuine Win10, but perfect hit at first shot, the game is running with no problems. What about you?

[rob]

No dice? you think it could be my computer?

[gho]

The OllyDGB screenshots are not the same thing as having the live session behind, but neverthless error3.png gives some clue:

Module WOW64_IMAGE_SECTION - failed to initialize

I googled a little in search of similar problems (keywords: WOW64_IMAGE_SECTION failed to initialize C0000022) and the results are far from consoling: this error could be generated by failed windows updates, HD failures, corrupted registry, virus and so on. The only missing reference is invasion of grasshoppers, but you know, web recipies tend to be quite pessimistic sometimes.
So, I fear that for sure the problem depends on your specific pc, probably (since I suppose all the rest is working) something referred to this specific game (hard disk where installed, failed DLL installation, ...) but I would suggest to start by looking at the Windows error logs and to reinstall/update anything is not giving harm, following cautiously (don't take everything for true) advices from the web. Keep in mind that, if the problem is as such, it could quickly impact other more important things than this game (make a backup soon!).
I'm sorry, but this is not my main expertise, so I car provide really limited help.

[FunkyFr3sh]

It's for sure a missing dll, for DirectPlay you need multiple dlls, are you sure you got all the needed files? Where did you download them?

Normally windows downloads such legacy components automatically, but some anti virus programs can break that feature in windows.

Try this: https://www.youtube.com/watch?v=6XYyGB-Tn3g&feature=youtu.be

I tested it on a VM, got a DirectPlay game working by putting the following files into the game folder:
dplayx.dll dpmodemx.dll dpnathlp.dll dpwsockx.dll

[gho]

One quick test could be performed by downloading the dependencywalker 2.2 tool (MMM.dependencywalker.COM, the first link I found, but seemingly good) and analyzing the DLL dependencies of CRUSHD.EXE (run the tool and drag&drop the exe on the window, can't be easier than this).
Unfortunately, the game shows many missing dependencies even in a situation where it works, so here is a snapshot of the situation on my pc: anything reported that is in my list (see red lines) shouldn't be a real problem.

[rob]

Yes, your right. it was Directplay being disabled causing the game to not run in the first place. It works now when i engaged it from the program and features. Thank you both so much for helping.

[huh]

Shame, I was on vacation.
I could save yours time, I published this error in my post here (at the end)
https://sourceforge.net/p/dxwnd/discussion/general/thread/25426033/?page=1