AutoPatcher Forum

When I used apup December 3 version, starting from scratch, checked just autopatcher updater and Autopatcher Engine, it downloaded the zip files (apengine.exe,zip, apengine bin.zip, ....lng.zip, then said finished. The zip files were downloaded (I was watching the folders), then deleted but not extracted!! So no autpatcher.exe, nothing in bin and translation folders. Repeated this several times.

Other downloads (xp, directxaddon, Office XP completed OK fromm microsoft without error messages, BUT the apm files were not downloaded, except for 3: __dotnet.apm, __msxml.apm, directx.apm in components folder, none in critical, non critical and office XP folders.
Edited by JRosenfeld, 03 December 2007 - 06:56 PM.

@JRosenfeld - There should be a new folder called apup_bin that has a zip inside of it. Go ahead and extract everything from the zip into the folder. This is the new location for uz.exe which deals with the unzipping. I'll talk to the other to see if uz.exe can be downloaded without already being in a zip since it's needed to unzip itself... Confusing huh?

The apup_bin folder contains no zip, but 5 files that were presumably extracted from it:

aamd532.dll
CAPCAB.EXE
MSCOMCTL.OCX
MSWINSCK.OCX
uz.exe

@JRosenfeld: Hmmm.. I haven't had a chance to play with the new setup so I'm not sure. What happens if you copy uz.exe to where it use to be in the BIN folder?

@JRosenfeld: I just thought of something. Could you post the hash of your apup.exe?

I think I found the problem: I had also checked apup updater. This converted the apup.exe to apup.old
Maybe the apup I downloaded was not the right version, or that updater 1.03 is misbehaving?

I redownloaded apup.zip, this time did not run updater, only Autopatcher. Now the files were extracted.
I then checked XP, Office XP and directxaddon. Now the apm files were also downloaded. So got the complete set. No errors.


I'm going to strt again from scratch, omitting apup updater.exe
Edited by JRosenfeld, 03 December 2007 - 09:51 PM.

JRosenfeld, on Dec 3 2007, 01:45 PM, said:

Please post your results after you're done. This is something I'm also going to play around with later.

Thanks JRosenfeld!

Checking the apup list should not be a problem. If you can't get it to work, download the new version directly at http://www.autopatch...engine/apup.zip

Downloaded 03 Dec apup.zip and extracted same to my test folder.

Deleted all scripts therein and ran APUP - it downloaded scripts and files, noticed one was the Nov Dx 9.0c redistributable.

Ran AutoPatcher, at Microsoft Windows - Updated Components the listing showed Microsoft DirectX - August 2007. Went back and checked my test folder - the script there is: autopatcher_directx_nov07.script - so why is it not being correctly reported in AutoPatcher itself?

Anyway, everthing else came with no problems.

OK Ran every thing from scratch, unchecked Autopatcher updater.

Checked Windows XP, Autopatcher, diectxaddon, Office XP. Everything downloaded and unzipped correctly.

Only slight hitch was that when needing to download from autopatcher.com, it appeared too lose contactwith the server. Exited apup, started it again, it downloaded the remaining files.

So I think my problems with the first try were due to the updater.

BTW there is no apup_bin folder this time.

Md5 hash for apup.exe itself (not the .zip download) is 694E9522A30C8897F21A5E323A848FE8, size 159744 bytes.

Concerning uz.exe, one is included in apup.zip, placed in the rt folder.

As a test, in a new folder, I again extracted the apup.zip (MD5 hash as in edit 6 of announcements post). Ran apup.exe from there with just updater and Autopatcher checked: the apup_bin folder was created (no zip, just the extracted files), again the bin and translations folders were empty and no Autopatcher.exe file either. Also the rt folder was removed.
Again apup.exe was renamed apup.exe.old the new apup is MD5 FB9210DDC9A06AC1B4230CE200C21AFA, 167936 bytes.

So it would seem that there is another (later?) version of apup.exe that gets downloaded by the updater, and that is the version that does peculiar things, such as downloading zip files then deleting them withoutfirst extracting their contents..


EDIT: I now downloaded the apup.zip file from the link Cyrus gives in post 8 of this thread.

This time, with Updater and Autopatcher checked it downloaded and extracted the files.

I blame the link in announcements now!!
Edited by JRosenfeld, 03 December 2007 - 11:39 PM.

@JRosenfeld, there was another version of apup (1.0.3) released today which is not downloadable from the annoucement thread. To get it you have to use the list in the current apup (or go to http://www.autopatch...engine/apup.zip if you really want to bypass the script). fb9210ddc9a06ac1b4230ce200c21afa is the new hash.

@DesertJerry, that problem has been fixed, run the updater again.
Edited by Cyrus, 03 December 2007 - 11:29 PM.

Got it. Must have been too early to click the link in the announcements :-).

Nevertheless, with previous version installed, running the updater, the zip files are deleted without being extracted. So there is still someting odd about the updater.

With the latest version from your link, the updater has nothing to do, so files are extracted properly.

I am testing it now for XP, Office and directxaddon as it did do autopatcher properly.

Some time later: All downloaded and correct :-)
Edited by JRosenfeld, 04 December 2007 - 01:33 AM.

@DesertJerry, that problem has been fixed, run the updater again.
[/quote]

Re-ran - got same result.

Opted to delete all script files; re-ran, same result - still shows August DirectX

Now what?

Can you post a screenshot so that we can take a loot at it? Mine shows November.

I've just tested apup.exe (1.0.3), with clean install of XP and DirextX, both downloaded perfectly.

DirectX downloaded as November 2007, script below.

Item=Module DirectX - November 2007

DetectFile=autopatcher:\modules\Components\directx.apm
DetectHash=9028983A73996877C90695C5279AF08B
DownloadFrom=http://www.autopatcher.com/releases/modules/directx.apm
DownloadTo=autopatcher:\modules\Components\directx.apm
ExpectedSize=2211
ExpectedHash=9028983A73996877C90695C5279AF08B

Item=Update DirectX - November 2007

DetectFile=autopatcher:\modules\Components\directx_files\directx_nov2007_redist.exe
DetectHash=B1CD797AB2ABC148F0AE045C206250C7
DownloadFrom=http://download.microsoft.com/download/c/6/a/c6af7ea3-f85c-4fef-a475-5810f82def1f/directx_nov2007_redist.exe
DownloadTo=autopatcher:\modules\Components\directx_files\directx_nov2007_redist.exe
ExpectedSize=67196968
ExpectedHash=B1CD797AB2ABC148F0AE045C206250C7

If I remember right, August was the last DirectX version before the whole Microsoft thang happened. If you are using APUP in conjunction with an old version of AP, try putting APUP in a new folder and download everything from the beginning.

If you don't want to download the entire thing again, just delete the "directx_files" folder and "directx.apm," both of which are in (your apup folder)\modules\components\ and it should work.

Cyrus, on Dec 5 2007, 12:43 AM, said:

Would post a screen shot if I knew how, and what good would it do anyway? Please enlighten me as I really am not being difficult I just feel my comments should be enough.

Also, I re-ran APUP in my original AutoPatcher folder (not the test folder as mentioned above) and got the same results concerning DirectX for November after it downloaded the latest scripts and updates.

Then I re-ran the latest APUP on my XP Home system and it downloaded the latest scripts (which included DirectX for November). Autopatcher was then started and Microsoft Windows - Updated Components showed Microsoft DirectX - August 2007 but the AutoPatcher folder had a script: autopatcher_directx_nov07.script.

So, I got the same results twice on my Pro system and once on my Home system. I really don't want to try a new folder and spend an hour plus having APUP download everything from the beginning.

Erik Ramey, on Dec 5 2007, 03:43 AM, said:

The November DirectX redistributable was posted on the Microsoft download site around the 24th of October (at least that's the date I downloaded it).

I believe I may have found what could be causing the problem here.

I checked in the AutoPatcher > Modules > Components > DirectX_files folders.

In the Components folder I found the following: directx.apm 05 dec 07 and DirectX_enu.apm 16 Aug 07. Why these two? Which one is being read/used when AutoPatcher is run? I ask because when I checked within Autopatcher > About > Release Info the lisiting was: DirectX August 2007 x86 ENU Addon - probably resulting in my system showing in - Updated Components the Aug release of DirectX.

In the DirectX_Files folder I found the extracted DirectX files for August and the complete Nov redistributable file. Should not the Nov file have been extracted and overwritten or been added to the Aug files already in the folder?

I checked both my AutoPatcher and AutoPatcher test folder and found the same in both places.

I did not fire up my Home system but I'll warrant a guess the same occured there.

So, is there an easy fix I can/should accomplish and what do you do to prevent similar occurances for other users in the future?