27 replies to this topic

[Cristiano]

hello everybody!

as promised, seven support was added for apup.exe and autopatcher.exe. the releases for seven will be online shortly. so, stay tunned…

just one warning: in order to work properly with seven, booth autopatcher and apup must be updated. if not, they will not behave as they should. this time, we had to enforce the update for apup aso please, let autopatcher and apup checked.

edit:
# 2010-03-09

we had a few reports, regarding the “remember selections” feature from ApUp, where the wrong value for the “remember selections” could be saved when the user is running an ENU OS with an translation pack.

that issue was tracked and is now solved. only one issue: yours may have to set your defaults again. the update isn't mandatory, since it affects only those running an ENU OS with an translation pack, but update it is recommended

sorry for the trouble

AutoPatcher Team

[]s

Edited by Cristiano, 09 March 2010 - 10:42 PM.

[_def_x_]

I zipped up autopatcher.exe v5.7.0 for safe keeping - should I get rid of it, is v5.6.100 an update to v5.7.0

[Cristiano]

yes, it is. we had an couple of drawbacks during our tests. 5.7 generates an more complete log, but also generates problems with certain systems. so, we had to remove certain features for now. by the way, ap 5.6.81 also was an update for ap 5.7. antonis was doing an update on it and something happened, i don't remember anymore what. and then, drawback...

[]s

[BrainDedd]

Some small issues ... the buttons are no longer skinned by the OS.
Also AutoPatcher crashes under Windows 7 x64 with an MD5 fail for a missing file aamd532.dll, which I suppose is understandable in some ways as there are no updates included in AutoPatcher for it yet.

Edited by BrainDedd, 08 March 2010 - 12:15 PM.

[dkdk_it]

Bug fixed!
We'll release new version as soon as possible.

Sorry.

Edited by dkdk_it, 08 March 2010 - 12:32 PM.

[dkdk_it]

New autopatcher.exe release (to fix an issue on Windows Seven x64).
Please update your AP engine.

AutoPatcher for Windows 7 x64 released!

[BrainDedd]

Not sure if it updated correctly, but now I'm getting a 'the version of this file is not compatible with the version of Windows you are running' prompt on 7 x64 ...

[Antony]

what about logs?
please attach them here on forum....
But before that - please start APUP from scratch in the newly created empty folder

apup.exe /log

this cmd will produce log inside the same dir where this tool is located.
Autopacther.exe is producing log in folder %SysDisk%:\%WinDir%\ in file autopatcher.log

(C:\Windows\autopatcher.log for example)

[dkdk_it]

And please, can you specify your Windows 7 version? (Starter, Home Basic, Home Premium, Professional, Ultimate or Enterprise)

Thanks

[Antony]

Ou!!! also please provide us with MD5 of all used files.....

[Cristiano]

ok folks. apup was updated to fix that reported issue.

thanks again, Antony

[]s

[BrainDedd]

Windows 7 x64 Ultimate Edition ...

AutoPatcher.exe - 72aed72bd45d46fcab5a5078a5923aba
ApUp.exe - 332a971bba6022952fe1978ae3766ac1

May be something funny with how it copied ... checking.

Edited by BrainDedd, 10 March 2010 - 08:23 AM.

[Antony]

BrainDedd!!
LOG!!! we need a log!!
AS you definitely was able to run APUP - you should get also LOG from this tool.
We need this log!
again -

Quote

But before that - please start APUP from scratch in the newly created empty folder

apup.exe /log

this cmd will produce log inside the same dir where this tool is located.

and current version of tools have these MD5:
332a971bba6022952fe1978ae3766ac1 *apup.exe
ece5f7787646d6c39901bacebfb608a9 *autopatcher.exe

[BrainDedd]

Sorry man, was investigating something ... for some reason when I copied the files across with windows copy they seem to have corrupted ...

Not sure if it's being cached somewhere, but my autopatcher.exe does not match your MD5 and re-downloading still gives the 72aed one, which verifies correctly with the apengine.script.

Edited by BrainDedd, 10 March 2010 - 09:07 AM.

[Whatacrock]

Ran a new clean apup directory on my pc today and after finishing noticed with the new version, there was an missing item, the windows genuine advantage.
My OS is XP x86 English
Look through all the updates and it no longer appears
Just wondering if there is any reason for this.
My log log file is posted in the Direct X Addon section.
Cheers
Bruce

[BrainDedd]

Quote

What AutoPatcher was trying to do
It appears that the error occured while AutoPatcher was trying to get a file's MD5 hash.

Where: mdlReleaseIntegrity.getMD5HashFromFile()
Error Code: 0x30: File not found: aamd532.dll

Log file here

[Cristiano]

> but my autopatcher.exe does not match your MD5 and re-downloading still gives the 72aed one, which verifies correctly with the apengine.script.
impossible:
Item=AutoPatcher Updater 1.3.0.1

DetectFile=app:\apup.exe
DetectHash=332A971BBA6022952FE1978AE3766AC1
DownloadFrom=http://www.autopatcher.com/apengine/apup131_exe.7z
DownloadTo=app:\apup_exe.7z
ExpectedSize=75947
ExpectedHash=3D1CDD22D5404BE214F1C25B3BA336D7
ActionAfterDownload.DeleteFile=app:\apup.exe.old
ActionAfterDownload=ren "app:\apup.exe" "apup.exe.old"
ActionAfterDownload.Unzip=app:\apup_exe.7z :: app:
ActionAfterDownload.DeleteFile=app:\apup_exe.7z

i've just checked and the md5 that is at releases list and the version that is online match with the md5 provided by antony. but it's possible that you may have an issue in the download process. can you please reach the link that is at DownloadFrom= and download that file manually, just to check?

another thing: most of the time, we may be behind an corporate firewall, that locks access to certain sites, like mediafire and other sharing sites. the logs are in txt format, so please, when posting one, just copy and paste it into an post, that will make our life far easier

thanks

[]s

[Antony]

Error Code: 0x30: File not found: aamd532.dll

that's outdated problem. it was fixed in latest 1.3.1 build with MD5:
332a971bba6022952fe1978ae3766ac1 *apup.exe
and 5.6.100 build with MD5:
ece5f7787646d6c39901bacebfb608a9 *autopatcher.exe

and again - do you start APUP in initially empty ofler?
or you are trying to reuse existing one???

P.S. We found one bug on our server regarding this file... ASAP it will be fixed
and you can download definitely correct ece5f7787646d6c39901bacebfb608a9 *autopatcher.exe file

[BrainDedd]

Well if you had a bug on the server then I'll try re-download when it's fixed. Thanks.

Edited by BrainDedd, 10 March 2010 - 12:36 PM.

[Antony]

try now...
you should get in script:

Item=AutoPatcher Executable 5.6.0.100

DetectFile=autopatcher:\autopatcher.exe
DetectHash=72AED72BD45D46FCAB5A5078A5923ABA
DownloadFrom=http://www.autopatcher.com/apengine/apengine_exe_5.6.0.100_reloaded.7z
DownloadTo=autopatcher:\temp_bin\apengine_exe.7z
ExpectedSize=119311
ExpectedHash=9D7E7A417A3BA15BB0A8DA528C70E5C1
ActionAfterDownload.Unzip=autopatcher:\temp_bin\apengine_exe.7z :: autopatcher:\