directx9 can't be installed (in 64-bit wineprefix at least)

[Danfun64]

I'm testing Debian in a virtual machine, and am trying to install the directx9 package in wine (yes, I know it's "overkill", but...). Unfortunately, there appears to be something... off ... with directx_feb2010_redist.exe

http://paste.debian.net/1063871/

I'm running Debian Testing with the winehq repository and the latest winetricks. I was hoping to play a 64-bit only game, hence why I'm using a 64-bit wineprefix.

[Danfun64]

I suspect the problem involves cabextract. Maybe I shouldn't be using the debian repository cabextract with winehq wine?

I tried bypassing the directx9 package but I still had issues. I also had issues with Visual C++ 2010 x64.
http://paste.debian.net/1064230/

[austin987]

What version of cabextract do you have?

[Danfun64]

1.9-1 . Checking the version revealed that at least part of the problem wasn't with cabextract. The main change of 1.9-2, which is what SID uses, is "Force libmspack0 version >= 0.9.1-1 to avoid bugs in that package". Lo and behold, libmspack0 in Debian Testing is 0.8-1 as of this writing, with SID of course having the newer version. Having backported libmspack0 0.9.1-1 to Testing, I deleted my wineprefix and cache and started from scratch. I'll let you know the results in a moment.

[Danfun64]

http://paste.debian.net/1064520/

[austin987]

Executing wine64 regsvr32 quartz.dll
0009:err:ole:COMPOBJ_DllList_Add couldn't load in-process dll L"C:\\windows\\system32\\devenum.dll"
0009:err:ole:CoGetClassObject no class object {4315d437-5b8c-11d0-bd3b-00a0c911ce86} could be created for context 0x3
regsvr32: Failed to register DLL 'quartz.dll'

Yeah, it's a real issue, but only in 64-bit. I'll take a look.

[austin987]

When registering quartz, it loads devenum. While winetricks has 32/64 bit quartz, there's only 32-bit devenum, so it fails to load.

We'll probably have to find a 64-bit devenum, but the only one I've found is a .msu (https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2016/ms16-007)

[austin987]

For a workaround, we could skip those dlls on win64:
austin987@834c279

does that, if you'd like to test.

@gverm what do you think, since you added those dlls? I suspect qcap may need to go too (it at least registers without issue).