Patch 1.07 will not run on Win2K

[Tako_Kichi 0]

Hi, I downloaded the 1.07 beta patch yesterday and then spent eight fruitless hours trying to get it to run.

It took three hours to install and then crashed as soon as I tried to run it. I then defragged my HD, re-downloaded the patch from a different mirror in case I had a corrupt download and re-installed. After another three hour wait it crashed again as soon as I tried to run it.

In each case I got the same error message:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">The procedure entry point TraceMessage could not be located in the dynamic link library ADVAPI32.dll.

After some searching on the web I discovered that there is a difference between the ADVAPI32.dll for Win2K and the one for XP. I can only assume that the build for the 1.07 patch did not take into consideration the users still running Win2K as the DVD case clearly states that Win2K is a supported OS.

I am now left with the option of running the 1.05+ build (which runs just fine BTW) and not playing online with my friends who are now patched to 1.07, waiting for the full 1.07 patch in the hopes that this problem gets fixed or biting the bullet and upgrading to XP at a substantial cost as I have three computers on a LAN here and that money could be better spent on new hardware .

It is not my intention to whine here but simply to bring the problem to the attention of the developers in case it was a simple oversight during the build process (I am a beta-tester for a well known flight sim and understand how these things can happen). Hopefully this can be addressed in the next patch or maybe someone can give me a few pointers on how to fix it to run on Win2K but I have a gut feeling that the problem lies within the patch as 1.05+ runs fine.

Any suggestions greatly appreciated.

Larry

[suma 8]

Thank you for reporting this. You are correct, TraceMessage API call requires Windows XP. I will check if (and why) is this call used, and I hope we will be able to make sure the final patch is Win2000 compatible.

[MehMan 0]

I wish everybody could post like you Tako_Kichi. At least in the sense that there's no flaming in it.

[suma 8]

One additional question: do you see this error when running the patch exe (attempting to apply the patch), or when running the game exe after the game was patched? We will definitely check in on Win2000, but I was checking dependencies meanwhile (having only WinXP here) to speed the resolution up and I do not see TraceMessage used in the patcher exe, at least not directly.

[bladerunner166 0]

Hi,

I can confirm this bug when running the beta exe of patch 1.07. It does not appear while the installation process. I used a tool called 'Dependency Walker' which gave me this result:

- Arma.exe is depending on XInput1_1.dll (from directx) which itself is using function 'TraceMethod' of ADVAPI32.dll. This function is only available in winxp version of ADVAPI32.dll as posted before.

- Arma.exe is depending on Shell32.dll, which uses SHLWAPI.dll which itself uses function 'WNetRestoreConnectionA' of MPR.dll. This function is also not available on my win2k installation (SP4).

I can't confirm that the second one is also a showstopper under win2k because I personally get stucked with the first one. But maybe its helpful for BIS. So please provide us with a hotfix that is not depending on winxp dll's .

Regards,

Joern.

[Tako_Kichi 0]

One additional question: do you see this error when running the patch exe (attempting to apply the patch), or when running the game exe after the game was patched? We will definitely check in on Win2000, but I was checking dependencies meanwhile (having only WinXP here) to speed the resolution up and I do not see TraceMessage used in the patcher exe, at least not directly.

The error does NOT appear with the patch installer. It ONLY appears when you double click on the 'Launch Arma Beta Patch' shortcut.

I can't comment on Joern's observation regarding ....

Quote[/b] ]Arma.exe is depending on Shell32.dll, which uses SHLWAPI.dll which itself uses function 'WNetRestoreConnectionA' of MPR.dll. This function is also not available on my win2k installation (SP4).

...as I never get to see it as the first problem stops me dead in the water.

HTH

Larry

[suma 8]

As using XInput to read 360 controller caused more problems, we will be removing it for the final patch version and switch back to the DirectInput solution we have used before. This should fix this as well. As for Shell32.dll, it is much likely Win2000 has its own functional version, because this is very basic system library, and I do not think using it could case any problems (most programs using any GUI use it for a very long time).

Thanks again for taking your time to report this.

[Bracken 0]

Hi, not sure if this is the same problem as i do not have W2k but i read about a fix for getting it to run on Win2k from page 14 of the main thread about the beta.  You could try that.  Sorry if its a different problem.

Heres the instructions

@Grassmonkey - YES that worked.

anyone else on Win2K got the xinput1_1.dll problem..

FIRST update your DirectX to the April 2007 version using the MS user runtime found here:

Microsoft Apr2007 DirectX user runtime DOWNLOAD FIRST then RUN

THEN

use this to fix it

Edit:Opps links didn't copy, adding them

Its the post made by [WWS]WarWolf

http://www.flashpoint1985.com/cgi-bin....;st=210

[Mr_Tea 0]

I put the files, that WarWolf pointed to, in my Arma dir.

After that the error is gone.

The files can be put into the WINNT\system32 folder too, instead putting them into the game dir.

[Tako_Kichi 0]

I put the above files in my main ARMA directory and I am happy to report that I can now play again .

It needs fixing for the final release though.

[register 0]

..

[ArMoGaDoN 0]

Gotta start the beta using the new shortcut that's added into your main ArmA folder...