Sample app did not properly cleanup objects ошибка

Status: Beta

Brought to you by:
ghotik

• 

  I was able to CreateProcess() __COMPAT_LAYER=256Color on Win7 32-bit

  • 

    I tried and succeeded too, that is fantastic!
    The only big trouble is that activating compatibility mode seems to inhibit dxwnd hooking, making it perfectly useless…. But I kind of remember it was possible to hook a program with compatibility modes set. Either I don’t remember exactly, or something happened to my PC!

• 

  Just a heads up, GPW breaks with 2.02.43. Getting error «Sample app did not clean up objects» or so, which I know is a debug message in gpw.exe. From what I remember its part of the preliminary tests before launching the game. No major…

  Couldnt test with v2.02.42, as the dll is missing from the download package. But happily playing GPW with 2.02.41 for now.

  • 

    You should check the «DirectX / Fix ddraw ref counter» flag.
    I wasn’t sure it was possible and safe to do this trick on all games, so I left it as a optional (defaulted) feature.
    Does this fix the problem, or was it checked already?

• 

  Hi Gho, sorry for the late reply. Yes, good news is that v2.02.43 works correctly, once the ‘Fix ddraw ref counter’ flag is checked. I also noticed that the game now shuts down correctly without error, and doesnt freeze.

  FYI I just tried the latest version 2.02.48 but GPW doesnt seem to like the changes. It flicks into full screen mode, and then back to windowed mode and the window stays black, which is quite a change to earlier verisons. Not a problem for me, as I’ll just use the v2.02.43 but just letting you know. Cheers

• 

  I think that newer releases of DxWnd should still let you play Grand Prix World finely: I noticed some problems with the earlier configurations, but that could depend on some garbage config flags that are not visible in non-debug mode: would you try to save a copy of your dxwnd.ini file, then run DxWnd, delete the config entry for this game and create a new one from scratch (or import it from the export folder): maybe that could fix the problem?

• 

  Hi Gho, thank you for your earlier work for GPW to run under DxWnd.

  Can I please request that the DXW export file for Grand Prix World is updated so that the «DirectX / Fix ddraw ref counter» flag is checked by default. This will help those who will inevitably strike this problem on future releases of DxWnd when giving GPW a go.

  I can confirm the current version 2.02.79 works a treat with GPW (once the flag is enabled), and I see you’ve made some fantastic additions over the last six months, especially obtaining elevated rights. Great stuff. Many thanks for your work.

  • 

    Done. The change will be available (if I don’t mess with files again!) in the next release, the «DirectX / Fix ddraw ref counter» flag checked by default and the logging disabled (that could prevent some gamer to find his HD flooded with gigabytes of trace messages).
    For those who can’t wait, here is the new export in attach.

    Last edit: gho 2014-06-17

• 

  Hi gho, thanks for all your work on this with Veedub, made some huge improvements to one of my all time favorite games. Unfortunately i’m not much of a programmer at all, but I wondered if you knew a way of getting this working on Windows 8.1 (the killer to all old games). Get a lot of different effors, the usual is «%%%Sample app did not properly cleanup objetcs»

  Tried compatability mode and installing to C//: root, but no success. Thanks.

  • 

    I have to admit that not owning a Win8.1 licence I have no way to replicate this problem. I don’t know if anyone can help suggesting what to do….

    • 

       

      Last edit: ivdok 2014-12-25

      • 

        The problem is I’m not so sure I want this win8.1 rubbish even close… within a vm, maybe…
        

        Last edit: gho 2014-12-25

• 

  Hello!

  I just noticed this site yesterday and I think this program very useful. The only problem is: it doesn’t work for me..What could be the problem? I do everything like you wrote here but GPW runs in full-screen mod no matter what.
  I downloaded the latest build and I run it as an administrator. I also try it with F1C 99-02 but pretty much the same.
  My operation system is win7 64bit. I use a 21:9 LG monitor with 3440*1440 desktop resolution.

• 

  Hmm, I unchecked the win 98/ME in the gpw.exe compatibility and it runs in windowed mode but the game freezes when the FIA logo comes.

  • 

    The game is working for me on Win10 and latest release. I’d start replicating the same environment, so please, if you didn’t do that already, install latest release v2.03.49.fix3 and use the included import file for GPW, that you can find in the «export» folder.
    I’m pretty convinced that this won’t fix the problem that will be still there, but in this case you should activate the log flags as shown in the screenshot below, run the game until it freezes, kill it by the DxWnd «kill process» command (or with the task manager), seek for the dxwnd.log file that should be created in the game install folder, compress it and send it to me.

• 

  Now, works me too with the gpwxp.exe because no need to compatibility mode with it. With the 1.03b gpw.exe it needs. If I unchecked it works with it too but the game crashes at the FIA logo.
  I would like to run it with the 1.03 because this patch has a lot of good thing in it. By the way..is time stretch working for you? I set it to 16x but I don’t see any changes.

  Last edit: Bisovic Béla 2015-12-31

  • 

    I think that to replicate exactly your environment I need to install the game and the patch exactly as you did, from the same files you used. If you prefer, you can PM me with instructions and links using the sourceforge messaging.

    update

    Environment and problem perfectly replicated. Now comes the hard part …. fixing it.

    Last edit: gho 2015-12-31

• 

  I read a comment on an other site. Here it it is:

  The problem: «The game will load in a window but will freeze at the FIA logo screen. When compatability mode is set for the exe it launches as it normally would in fullscreen. I tried the solution that was provided in the post but it did not work for me either.»

  And the solution: «On a good note I managed to get DxWnd to work. It would appear that DxWnd doesn’t like you using a path which contains a space.

  I had originally named the folder in my root C directory as «Grand Prix World». After changing it to «GPW» DxWnd recognised it.

  Therefore, I assume the reason why the installation in «Program Files» doesn’t work is not necessarily down to administrator privileges but rather the folder name contains a space.

  On a bad note, the game crashes following the conclusion of the race after the constructor points table has been displayed. I’ve tested the original exe, 1.01 and 1.03b and they all crash at this point.

  Do you have any ideas what the issue might be?»

  I tried it but i get the following error message «Try to enabling the reference rasterizer by executing EnableRefRast.reg»

  • 

    I tried to eliminate spaces in the current path and also to move everything in C:GPW, but nothing changed: the game keeps freezing.
    I did some debugging, the main thread keeps locking on semaphores, but that could be normal, if it is waiting for the intro movie termination.

• 

  Hmm..its really sad because th timing stretch speed up the game perfectly with the gpwxp.exe
  So it would be very cool if i can play with the 103b too.

  • 

    Never say never ….. but the patch classified as a «beta» let me think that it could be a different problem. In any case, I’ll keep working on it.

• 

  On my laptop it works but when I start a race weekend than the screen crashes like when the vga is wrong. It also happened 2 days ago on my pc. I change the values in the ‘window initial position and size’ section but now this didn’t help and I don’t know why.
  On the laptop the race screen also crashes with the gpwxp.exe too. In the menu everything is fine until I start a race weekend.

  Last edit: Bisovic Béla 2016-01-03

  • 

    I haven’t tested a race yet, but I think I’ve got the ‘hook’ from DxWnd to the gpw exe working.

    I think the one thing I did that’s different from what I’ve seen hear is that I went into the compatability settings in windows explorer and tried Win95 on the exe itself, instead of the Win98 settings. I think it was that change that got it past the lock up on the gold FIA screen and into the program.

    So, I’m in the program in a windowed mode. Its late, so I haven’t tested a race and the main thing I’m trying to solve which is an awful flicker in the game which also seems to bring the processing of a race to a crawl. I’ll have to try to beat on it some more and see how good this realy is.

    The one odd thing right now is that on a two monitor screen, the first window with the DxWnd logo is on my main monitor (with windows task bar), while the window for the game then opens on my 2nd monitor.

    This is all on Windows7. My DxWnd export is attached. Although, there might be some odd settings in there as I did a bit of checking things I don’t understand during a phase when I was trying to get it working.

    Last edit: Marc 2016-03-22

    • 

      Hi, I feel like I’m close, but not there yet.

      The race sequence runs and doesn’t crash. But the colors are all wrong. Kinda like when something’s wrong with the palette in an old game, except there’s also an effect of diagonal pattern running through this. I can see some of the controls that seem to be ‘on top’ of the graphics, so I can easily see and press the button that lets me go to the options screen. That displays well, just like the main program, so I can exit the game and try again.

      So, I think what I need is some help with some of the many options to try to fix two problems.
      1) The bit where the window appears on my main monitor, but the graphics that should be inside instead paint in the same place on the secondary monitor.

      2) Getting the colors and display correct in the race sequence displays.

      If you have any suggestions on which of many checkboxes might address those sorts of issues, I’d appreciate any help someone wants to toss my way. Otherwise, I can always just try my random check-box ticking to see if I can stumble upon any answers.

      The good news is that the bad display with the messed up colors doesn’t seem to ‘flicker’ any more. Hard to tell, as before it would sometimes go several seconds before beginning this action, so maybe I’m just not waiting long enough before exiting. But, like I said, I feel like I’m close.

      Thanks for the excellent tool and the good info I’ve found above.

      • 

        Things you may try:

        1) send me a full printscreen of your double-monitor desktop when the problem appears (just hit the print-screen key without the Alt key)
        2) Set the Video / «Hide multi monitor config.» flag that will let the program you have a single monitor (though I doubt it will work….)
        3) if you see diagonal stripes, that could be cured by two flags that (for lack of space) I put in the Direct3D section: «Lock / Unlock pitch fix» and «Width no power of 2 fix».

        The palette problems could (I don’t know why, but it worked with «Men in Black»!) be fixed chosing the Libs «Share ddraw and GDI DC» option.

Status: Beta

Brought to you by:
ghotik

• 

  Thanks for the ideas.
  Here’s a picture of the desktop, although if you were asking about the problem of painting in on the wrong screen, I’d fixed that issue (see post below) and this now shows the painting inside the proper window frame. Before, the part that should have been within the frame was appearing on the other monitor with the same (or close) 50,50 offset from the top-left of that display. So, the frame was on the main window (right side of this image) while the painting was occuring on the left side.

  The image does show what the race mode looks like now.

  When I tried the two flags (Lock/unlock pitch fix and Width no power of 2) together, the overall graphics of the game were scrambled on stop and I had to kill the program. The Lock/unlock pitch fix flag alone does the same, while the Width no Power of 2 flag alone runs the program but has the same look to the race screen as in the screen shot. The Share ddraw and GDI DC option alone had the same look also.

• 

  OK, got a step closer.

  First, I went back to the file for GPW that comes in the ‘exports’ folder. Left the windows explorer compat settings alone.

  Then, I found a checkbox that says «Don’t Fix Pixel format» under the DirectX tab and checking that makes the ‘paint’ occur inside the window on my main monitor. So, one issue down. The race is still unreadable due to color or other issues, but now I seem to be down to one issue.

• 

  Hi Marc, this method is worth a try. Go to Direct3D tab > uncheck «Fix ddraw refcount» and check «Return 0 refcount». Does that make the problem less serious?

  If this method not work, please revert to previous setting.

  • 

    Pretty much the same. Here’s a pic, but it looks a lot like the one I just cleared ouf of Paint.

    

• 

  I saw the picture, and it is strange indeed. This sort of things usualy happens when the program doesn’t manage the graphic in the proper way (that is using the system calls) but takes some shortcut for supposed optimization and generates a full mess.
  Usually the problem disappear if the program works in the exact resolution he supposes to be. Could you try to set the window heigth and width values to 0, 0 in the main DxWnd conf panel and see if the problem disappear?

  • 

    OK, here goes then. I’ve got the check box back to «fix ddraw refcount’, and now the H and W set to 0.

    With game programmers, especially from that era, it wouldn’t surprise me at all if they were doing some shortcuts. Strange, a game like this they shouldn’t have had to, but the game is littered with these useless 3d views of race cars on a race track so they may have done something to get more speed in there.

    Had to wait for it, Program was slower to appear. Then had trouble getting the mouse to work. But in the end, it got to the race mode and no difference.

    At this point, I think I’m still close to the shipped settings for GPW, with the changes put in to test and then removed once they don’t work. But, here’s a export of my latest version.

    BTW, I think 800 x 600 was the correct size (values in H and W before I tried 0 and 0). I think I saw that somewhere in display settings while messing around with this in fullscreen (no dxWnd) mode.

    Thanks for the help and for giving it a try.

    • 

      What happens if you temporarily turn off your secondary monitor and configure the desktop accordingly? I’s like to be sure the problem depends on the two monitors, and this test is pretty easy to do.

• 

  I fear that I need help.
  I tried running GPW through DXWnd following the steps listed in this guide: http://www.gprm.co.uk/forums/index.php?topic=5835.0

  But I alternatively get these two error messages:

  1 «sample app did not clean up objects»
  2 (much more frequent) «%%%sdevices. Try enabling reference rasterizer by running refrast.reg» (a file that does not appear to exist on my computer).
  What’s going on? T_T

• 

  Hi Gianmarco,
  I’ m replying from mobile phone but it’ s not easy.
  I’ll be back from holyday twesday, I will make tests then.
  Be patient and happy Easter.

• 

  Here I am. back to work.
  The problem may depend on the version of the game. What I’m actually supporting is a variation of the windows XP port of the game, «gpwxp2.exe», that I can’t even remember how exactly I got it.
  In any case, I would make a clean start putting both you and me in identical conditions: so, please
  1. download the latest DxWnd release v2.03.58,
  2. import the included file «Grand Prix World.dxw» from the DxWnd export folder
  3. unzip the attached version of the game in the game folder.
  4. adjust the dxwnd path field in the configuration so that it points to the gpwxp2.exe file.
  At this point, If it doesn’t work, at least we will share equal conditions.

• 

  Hello Gho,
  thank you. I will try this out in the afternoon as soon as I am back home and tell you what happens.
  Hope you had pleasant holidays.

• 

  Okay Gho,
  I tried. I think we’ve made progress. It now says «ensure that game CD is inserted». I suppose I need a no-CD patch of some kind.

  • 

    Uhm…. no, I think that the problem is that you didn’t install the full gpwxp patch, that likely copies more resourced on hard disk and makes the CD useless. I provided just the exe, but this is not enough.
    Have a look at here: http://www.simracingworld.com/files/download/1086-grand-prix-world-windows-xp-patch/ and follow the instructions. In any case, keep the gpwxp2.exe that I sent you because it may work better with DxWnd (Oh, my! I can’t remember why I patched it!)

• 

  Hello Gho,
  I downloaded the patch you linked, and kept your exe, but I still get the no cd issue.

  • 

    What OS are you trying to run it on? I heard that some copy protection schemas were left unsupported by MS recently, and maybe with the protection, also the crack was gone …
    In any case I had it working on WinXP, Win7 and Win10. I left untested only Win8 and 8.1.
    More likely, there must be some error in the installation, but from here I can hardly tell….

    Last edit: gho 2016-04-02

• 

  I am running it under windows 8.1.
  I tried with a pirated version of the game. It’s hard to find a legitimate copy and I would be hesitant to buy it when it may very well not run at all. :/

  • 

    I never had the (mis)fortune to verify this, but the general opinion on Win8.1 is not very good, since it gained on the field the nickname of «Game killer»!
    You should have a proposal from MS for a free upgrade to Win10, and even if you don’t, there should be a way to di that for free. My personal suggestion is to migrate to Win10: I also was a bit reluctant, but then I migrated directly from Win7 to Win10 in a single step and it was absolutely ok: you loose nothing (as far as I can tell) and you gain some disk space (strange, but true), a more efficient OS and a better back-compatibility with everything, including an integrated support to emulate 8 or 16 bit color depth in a window (they must have copied something from DxWnd, I dare say…).
    In any case, I’m afraid I can hardly support you on 8.1, since I don’t have it. The only final attempt could be to try the last DxWnd beta that I updloaded a few hours ago: that manages much better some latest Window versions.

• 

  Thank you gho, you have been very kind and I sincerely appreciate that.
  The upgrade to Windows 10 sounds nice. I will consider it, first I want to verify what the web says about the other games I play often running under 10, but since they’re mostly recent I don’t think it’s going to be a problem.
  I will come back to you as soon as I have upgraded to 10 and let’s see if that fixes things.

  • 

    Release v2.03.60 fixed many problems about ddraw method hooking, that has become more and more selective from WinXP up to Win10. If you like, you may also try this last version, there’s a slight possibility of improvement.

• 

  Hey Gho, the OP back again

  For future tests, can you please test Grand Prix World with DxWnd and gpw103b.exe? Basically, while gpwxp.exe was repackaged by the developer to work with Windows XP, it isnt the latest official version of the game. The latest official version is gpwv101b (packaged for Win98), and I managed to patch out the WinXP bugs and get it working with Windows XP eventually (creating the unofficial gpwv103b.exe). So as a community, we want to use gpw103b going forward where possible.

  You will need to install gpwv101b first, and then apply gpwv103b (which is also a no-cd exe).
  gpwv101b: http://www.edwardgrabowski.com/downloads/gpwv1.zip
  gpwv103b: http://s000.tinyupload.com/index.php?file_id=66902834389965582469

  Of course for GPW to run on any system, you should set compatibility mode on the gpwxxxx.exe file to Windows 98 to get past the game freezing at the gold FIA logo.

  I’m hoping you can help us with the following problem a user has raised to my attention:

  • Unfortunately the 103b patch doesn’t run on Windows 10 but apparently gpwxp2.exe does
  • The same error messages that came up in that Sourceforge thread appear —
  • ‘Sample App Did Not Properly Clean Up Objects’ if you use XP Compatibility mode and
  • ‘Try enabling the reference rasterizer by executing EnableRefRast.reg’ if you use Windows98 compatibility mode.

  I suspect these errors relate to when the game initialises and tests the hardware/software graphics capabilities. As it is Windows 10, I have very little knowledge on this issue but I’m hoping you may understand what is causing these checks to fail or how to bypass them. Apparently the gpwxp2.exe that you created at the start of the thread does seem to work with Windows 10, so it may just be possible to get gpw103b.exe working as well. I did a binary diff on gpwxp.exe, and your exes gpwxp2.exe and gpwxp3.exe to note your changes and will see if I can carry those changes across to gpwv103b.exe (I’ll have to fire up idapro, and cross reference the code) but I suspect there may be more issues to solve. The two versions (gpw101b.exe and gpwxp.exe) have quite different disassembly layouts but the same start up logic.

  Thank you for your efforts so far, any help appreciated. I’ll let you know if I make any discoveries, once I get my own Win10 box up and running, hopefully one day soon.

  Also, not DxWnd related but it is graphics related, can anyone/graphics experts explain this issue with flickering graphics? From the ~3:30 mark in the video, the UI starts to flicker. This is when playing the game normally at full screen on any system/OS. Some system configurations cause the flicker, others work perfectly fine. Our suspicions are that its graphics hardware/driver related (possibly nvidia only). I wonder if it is GDI vs DirectX interference or something or clockspeed, as I notice the system that the game flickers on has unhelpfully super responsive button clicks?

  Youtube video: https://www.youtube.com/watch?v=0glTWBjZHXk&t=3m30s
  Google suggestion: http://community.pcgamingwiki.com/topic/811-flickering-in-old-games-on-nvidia-very-strange-problem/

  Regards, Veedub

  • 

    Ok, I’ll do my best.
    Unfortunately MS changed a lot of things in these last years and, despite the declaration of Win10 as the last Window version, it has a dynamic patching feature (shims) that makes things changing (usually for the better…) almost every day, but this way you can never say you’re done wirh a game!
    One very positive thing is that now Win95/98 emulation is no longer made through a virtual machine, then it is now compatible with DxWnd and the two mechanisms (Windows compatibility assistant and DxWnd) can help each other to reach the goal.
    Wait for news (and if they don’t come, remind me every now and then….)
    bye

• 

  I compared the dxwnd logs of gpwxp2 and your gpwv103b, and the cause of the ‘Sample App Did Not Properly Clean Up Objects’ error message is the lack of Release upon the backbuffer surface, that is also linked with two references to the directdraw session and inhibit the resource freedom (see picture).
  The error message can be easily eliminated setting the DxWnd «return 0 refcount» instead of «fix ddraw refcount», but this is just a fake 0 number returned to the application while the resources still have references, and I suspect that this causes the block of the application right after that.
  I attach also the full log files, in case they could help to localize the code that needs a fix.

  Last edit: gho 2016-05-07

  

• 

  Bad news: in the attempt to trick the program and make a workaround, I made a sperimental version of DxWnd that counts (and logs) the DirectDraw4::Release() methods, so I found that the missing call is after the 19th cycle and I modified again DxWnd so that it doubles the Release call when the counter reaches 19.
  The result is that the error message no longer appears, the logs show that the game go further ahead, but it keeps stopping on the splash screen (or maybe it is not stopped, but the output operations are not visible?).
  In any case, it seems that the missing Release operation is not your only and main problem!
  In attach the crazy dll that makes the trick, just in case you want to see what changes (nothing at all).

• 

  Thank you for your efforts so far Gho — at least it gives me some leads to go on when I get to analysing the code. In v1.03b i have freed up a lot of bytes in the exe to write new asm, so potentially (if i’m clever enough) I can rewrite the start up sequence and see what I can eliminate or copy over from gpwxp.exe, and get something working in Windows 10. We dont have many clues from the developers as to what they actually changed between gpw.exe (v1.00) and gpwxp.exe to make it XP compatible but as far as I could tell it was recompiled with a newer version of Visual C++ (upgraded from v4 to v5) and probably had minor code changes, so that could be the subtle difference.