[solved]Windows 10 thanks Aqrit!

[mousEtopher]

ddraw.dll ?

[Warchief Lightbringer-]

INGORE MY PREVIOUS POST ON DELETING DDRAW.INI. It was in my war2 folder for God knows what testing. I am enquiring on what could have caused it....
Anyone with a Win10 can you please backup War2Patch.mpq and replace with the version attached and report back?
Thanks

[iL]

On win10 make sure you have NO files ddraw.dll and ddraw.ini exist in war2 directory where you start war2 from.

ddraw is a wrapper that fixes an error in ddraw for win7 only!
Not useful but causes problems in win8 and win10.

When you install combat 4.01 make sure ddraw checkbox is disabled.
It should be disabled by default for any OS except win7, but you can enable it, that is strongly not recommended.

[Paper_Boy]

I hear in Windows 10 they install adds in solitaire and to disable them you have to pay a monthly subscription fee.  That is the most fucked up thing i've ever heard, taking advantage of retards and old people that don't know any better. What ever happened to buying software and owning it. Trying to switch everything to a subscription model screams desperation with so many better free alternatives out there.

[mousEtopher]

That is.. downright dystopian.

[shesycompany]

windows 2000 was winblows last real one ..taking advantage of people was the next move.i really dont get the 8's and 10's and why you would want them.

people still play solitare worst card game ever!i suggest u delete, free up the kb's and do a
 "52 card pickup in flash" alternative.

[EviL~Ryu]

Windows 10 is great.


Sent from my Motorola DynaTAC 8000X using Tapatalk

[iL]

My test for that:

The latest version of War2combat has display glitches in Windows 10. Here are two things you can try:

• When installing War2combat on Windows 10 make sure you UNCHECK the ddraw checkbox in the installer. It should be disabled by default for any OS except Win7. There should be NO files called "ddraw.dll" or "ddraw.ini" in the /war2combat/ directory. (ddraw is a wrapper that fixes an error in ddraw for win7 only! It causes problems in win8 and win10.)
  
  
  
  
• If that doesn't work you can install the previous version of War2combat (3.15), located here.

Please try these things before you make a post about Win10 issues!

I just tried to install new clean windows 10 and war2 to it. That is what i see:

1. DDraw compat checkbox is disabled by default (that is correct behaviour).

2. I try to check the DDraw compat checkbox and install combat. Then i install it again to the same folder.
2.1. Checkbox is checked by default now. (options being kept from previous installation).
2.2. If i uncheck the DDraw compat checkbox before repeatedly installation, it will NOT delete these files (ddraw.dll and aqrit.cfg). That looks like a definite bug.

So, my plans for next version:
1. should do: to delete these files if you uncheck the checkbox during repeated installaion.
2. need to think about: don't remember last choice for this checkbox, always set is depending on windows version.
The question is about other checkboxes: all the checkboxes are being kept from previous installation, should i keep them all except ddraw?
3. even more agressive behaviour: to show gray (non-clickable) checkbox for directdraw (depend on windows version). I have no idea why you will need that ddraw fix under any win except 7.
At the same time i don't understand why anybody switch this checkbox on under win 8 or win 10. To click everything just in case or what?

4. i also can add functionality to delete ddraw for non-win7 computer into loader. You try to start war2ploader, it asks if you want to delete ddraw that is not compatible with your win version or continue as is.

Here are 3 more screenshots:
how it works with ddraw.dll:


And without it (that is how it should work). Here's no any known solutions to show icons in chat:

[mousEtopher]

3. even more agressive behaviour: to show gray (non-clickable) checkbox for directdraw (depend on windows version). I have no idea why you will need that ddraw fix under any win except 7.

That's probably best. Or at least update the description to explicitly state "Win7 ONLY, not for use with Win8 & 10", the wording is a little ambiguous

At the same time i don't understand why anybody switch this checkbox on under win 8 or win 10. To click everything just in case or what?

Win10 is a free upgrade from Win7 so maybe the people having the problem already had war2 installed, then did the upgrade to Win10, thus the ddraw files are present. If these people are doing fresh installations of war2 on Win10 then I don't know -- it doesn't explain why so many Win8 users have the problem either.

[EviL~Ryu]

I know I did have that problem after upgrading from 7 to 10. Maybe put some instructions on forum when upgrading from 7 to fully uninstall and reinstall war2combat.


Sent from my Motorola DynaTAC 8000X using Tapatalk

[EviL~Ryu]

I found combat works on Windows 10 Home and Pro, but crashes on Enterprise for some reason [emoji54].


Sent from my Motorola DynaTAC 8000X using Tapatalk

[Certified MENSA Genius Brain (smart)]

And without it (that is how it should work). Here's no any known solutions to show icons in chat:

That's not too important, but is that because of the file format of the icons?

[iL]

I found combat works on Windows 10 Home and Pro, but crashes on Enterprise for some reason [emoji54].

That's interesting!
Just empty default win ent? Did you try it on different hardware? Also did you try home and pro on the same hardware?

[iL]

That's not too important, but is that because of the file format of the icons?

It's because of different drawing methods for bnet chat, bnet icons and everything else. Something becomes broken in new windows...

[EviL~Ryu]

I found combat works on Windows 10 Home and Pro, but crashes on Enterprise for some reason [emoji54].

That's interesting!
Just empty default win ent? Did you try it on different hardware? Also did you try home and pro on the same hardware?

Yes, clean install from MSDN. Same hardware on all versions. I doubt many users would even have access to the Enterprise edition thought...so shouldn't be a major concern [emoji14]


Sent from my Motorola DynaTAC 8000X using Tapatalk