DirectDraw applications Freeze on Windows 7 anywhere between 1 minute and 3 hours into running them.

Just to chime in, I'm having the same trouble, Windows 7 Ultimate 64-bit - Starcraft freezes within about 5-10 minutes of playing. I've tried the latest patches, latest drivers, processor affinity, in fact pretty much all the things Squall has listed, and I have the exact same trouble.

As I understand it, DirectDraw assumes it can lock the primary draw buffer, and Windows 7 itself draws to the buffer, since so much of the GUI is now done in 3D e.g. Aero. At some point they both try and draw to the buffer at the same time, resulting in a freeze of the display (both programs are waiting for the buffer to be released, neither lets go, and thus you get a classic deadlock due to the inter-process race condition).

XP Compatibility mode achieves nothing sadly - neither does XP Mode, as Squall mentions, the game can't switch display modes under XP Mode.

Having re-read the Windows 7 Compatibility guide that Squall mentions (which I'd read for work but had completely forgotten about), it strikes me that this freezing sounds more and more like a Windows 7 64-bit bug. The default behaviour for Windows 7 is supposed to be, and I quote 'Windows Vista (default): Applications will be able to acquire a lock on the primary video buffer as legacy applications depend on this behavior. Running the application turns off Desktop Window Manager.'

Going by Microsoft's own docs, older applications that lack the Windows 7 Compatibility manifest should be working in this manner, and yet clearly they are not in all cases.

I'll be fascinated to hear if a wrapper DLL can work around the issue.

the latest patch does indeed add the cpu throttling, however it doesn't fix the Win7 freeze.  I've already checked around and it seems it effects all DirectDraw applications and games in some form or another, some worse then others (worst being freeze).

the x32 version of 7 seems to be ok, and Ddraw apps seem to lock the buffer properly, but in Win 7 x64, i verified in the emulator FCEUX that Vsynching with VBlank, and double buffering are not working at all.

the XPM suggestion unfortunately is not viable, as it doesn't support display mode switching which some of these apps require.

Changing the compatibility doesn't help either.

Ah well, thanks for the help anyway, I'm working with a friend now to fix this and the ddraw colour issue  by wrapping DDraw to Direct3D via a drop in ddraw.dll.

Squall,

  I have a friend that is a Starcraft player.  He has installed and is running Starcraft on Windows 7.  According to him what you need to do is log into Battle.net and download the latest version from there.  It has some updated components that should get it it to run on Windows 7.  That being said I could not find any information that they plan on making any updates for Starcraft.  I believe they are focusing on Starcraft 2.

All,

   As with any forum, when in doubt, create your own thread.  It is the best thing to do to get assistance with your specific issue.  This thread was started to discuss DirectDraw issues specifically.  If you have a problem with a game and you are unaware if it uses DirectDraw or not then it is probably safer to start a new thread.

Squall,

    Most of the games you have listed are either not Windows 7 compatible or are currently unknown in their compatibility.  Make sure to check the Windows 7 compatibility center for any software before trying to install\run it on a Windows 7 machine.  

Starcraft (information pending)

Worms (not listed for Windows 7, listed not compatible with Vista)

Sierra's Pharaoh/Cleopatra (not listed for Vista or Windows 7) 

So with that in mind the only thing I could suggest would be to right click the game .exe file and change the compatibility mode to XP.  Also depending on what version of Windows 7 you have, you may able to install XP Mode and run it with that.

this is a one problem only thread, and it its about games that freeze because of DIRECTDRAW!, if you have problem understandig what that means, don't try to talk about something you know nothing about, if you need help with your problem, I am very sure there are threads for your specific problem. Even if not, make one your self. There are only 18 games listed because these are the games having problem caused by DirectDraw (again, you understand?, not D3D games) like the title of the thread says. Only by making a thread like this, containing one problem, we could be able to solve it, not by making a general "I have a problem with a game in W7" thread. Hope this clears thing out for you...