AutoPatcher Forum

I’m using your latest version but even if I try to download one file at a time, sometimes it keeps freezing up on me. I’ve managed to get all but one file (AutoPatcher for Windows XP (x86) – Beta 3.3). Although I’ve tried several times it freezes up. In my latest attempt, it stopped at 236.22 MB of 259.51 MB. Is there an easier way to do this?

Edit 1: I've found that though it may stop for several minutes, it always starts again so I just have to be patient. It it does freeze, just exit and start again and it will pick up where it left off.
Edited by obe1, 06 December 2007 - 09:36 PM.

Lucas Malor, on Dec 3 2007, 05:36 PM, said:

Although you could, in theory, continue from where that one left off, there have been so many changes in the mean time that I recommend, if at all possible, to just start over. To try to reuse it, extract the old core/update release to your folder of choice. Then download apup here: http://www.autopatch...engine/apup.zip and extract it so that apup.exe and the modules folder which you saved are in the same folder (don't put apup.exe in the modules folder). Then run apup.exe, although you could run into some errors.

obe1, on Dec 3 2007, 08:44 PM, said:

First, there are two versions released on Dec 3, so make sure you have the newer of the two (v1.0.3) from here: http://www.autopatch...engine/apup.zip Other than that, we know that a slow connection, a high latency connection, or a busy MS server can cause the problem you are experiencing. Just Close, select the list again, and let it go a bit farther than it did last time until Antonis can provide a more permanent solution to that bug.

I found a possible problem. When I leave all the checkmarks at their default values (all versions of office & new apup & autopatcher engine) the program (apup) stops responding. However if I choose only the one that I want it downloads fine (a bit glitchy and it stops often like everyone elses). I also tried selecting just the one I wanted plus one other package that I had already downloaded and it also stopped responding in this case. From how the program is acting I think that it only downloads until it finds the first release that is complete and then either gives up and dies or possibly just doesn't know what to do. I don't expect you to help me specifically but I just wanted to let you know that it isn't working quite correctly (though I'm sure this isn't the only bug since it is a pre-release version). Other than that good job on finding a new way to keep the project ongoing.

EDIT: it could be that I am just not giving it enough time to check what it has already downloaded though since it takes a while to resume even for just one release selected.

Ah yes and I had been getting the runtime error 0 using the previous version but this version hasn't given me that. Also I am using Vista Ultimate so at least you know that it is now running on that OS as well

EDIT2: Is autopatcher supposed to find things that it can update on a Vista PC even though none of the releases are for Vista?
Edited by langes01x, 04 December 2007 - 05:28 AM.

If proxy support was added, more of stuck behind them could test the software.

Hello Group;

I get a time out error when I try and use the latest version of "apup". I am behind a fire fall which does prevent some automatic updates on other items. I usually have to down load the file maually. I use spybot as an example and Clamwin as another example. I can not check for any updates useing their built in feature. But I can manuall down load the updates from thier site manually.

I know this is still a BETA so I am just informing you of my problem. Hopefully you can address this in a future version.

Elderberry

If you are behind a firewall, are there any special ports that should be opened for APUP to work successfully?

(Sorry for the Q - I'm desperately trying to catch up on APUP, having been off work for a month)

--
James

I've successfully used APUP to update August Core so no problems there

Also, AFAIK, AutoPatcher only makes requests on port 80.

Hello. I noticed that if the connection times out that APUP will stop. Possibly it could be made to detect this and auto resume the download?

They should update it soon to support retrying failed downloads or ones that time out. If you still have hard disk activity, don't close out of apup.exe, there's a chance that it's still working. On a slow (1.2GHz) laptop it took more than 5 minutes to go through all updates and create checksums for them, so be patient if your hard disk light is on. For now there is no way to get around corporate firewalls besides opening port 80, allowing apup.exe access, and/or temporarily disabling it. Note: if you have a firewall only on each computer/workstation there should be no problem. It works fine with 3 PCs that I have which are running 3 different firewalls. For better answers you would need Antonis or Renato to answer your questions.

Another way to check if its working, look at the log file to see if new lines get added. It looks like this:

AutoPatcher Updater starting.
List file HTTP location: http://www.autopatch...m/releases.list
Download queue status: 1 files waiting.
releases.list: Download complete.
Download queue status: 0 files waiting.
Download queue status: 4 files waiting.
autopatcher_directx_nov07.script: Download complete.
Download queue status: 3 files waiting.
autopatcher_xp_x86_enu_nov07.script: Download complete.
Download queue status: 2 files waiting.
apengine.script: Download complete.
Download queue status: 1 files waiting.
apup.script: Download complete.
Download queue status: 0 files waiting.
Executing shell command: del "H:\AutoPatcher\XP\modules\Components\__dotnet\dotnet1.1_enu.apm"
Executing shell command: del "H:\AutoPatcher\XP\modules\Components\WinLiveMsngr_xp_x86_enu.apm"
Starting detection routine for item AutoPatcher Updater 1.0.2
Looking for file H:\AutoPatcher\XP\apup.exe
MD5 Hash matches (fb9210ddc9a06ac1b4230ce200c21afa).
...........etc.

Note on version:

apup.script shows 1.0.2, please amend

Item=AutoPatcher Updater 1.0.2

DetectFile=app:\apup.exe
DetectHash=fb9210ddc9a06ac1b4230ce200c21afa
DetectFile=app:\apup_bin\uz.exe
DetectHash=10776112cc253545a40462f6b1309e87
DetectFile=app:\apup_bin\mscomctl.ocx
DetectHash=774a15583db1ad44c5ee32309c840c96
DetectFile=app:\apup_bin\mswinsck.ocx
DetectHash=e8a2190a9e8ee5e5d2e0b599bbf9dda6
DetectFile=app:\apup_bin\capcab.exe
DetectHash=75035b0d1823982b4bbb4d106dc38234
DetectFile=app:\apup_bin\aamd532.dll
DetectHash=cefd956a1ef122cda4d53007bab6c694
DownloadFrom=http://www.autopatcher.com/apengine/apup.zip
DownloadTo=autopatcher:\apup.zip
ExpectedSize=722872
ExpectedHash=b9bbb2390898ff247965c114dba911d2
ActionAfterDownload.RenameFile=app:\apup.exe | apup.exe.old
ActionAfterDownload.Unzip=app:\apup.zip :: app:
ActionAfterDownload.DeleteFile=app:\apup.zip
ActionAfterDownload.DeleteFolder=app:\rt
#ActionAfterDownload.DeleteFile=app:\apup.exe.old

According to the main releases list, it should be 1.0.3.

Cyrus, on Dec 4 2007, 04:28 AM, said:

Mmmmhhh.... it seems to me apup re-downloaded all stuff again. I've put apup in old Autopatcher folder as you wrote.

EDIT: a little correction: now I started a fresh download. The actual download size is 540 Mb; before I had re-downloaded "only" 350 Mb. It seems too much anyway (my backup is only few months old). IMO it could be useful in a future an import tool for old backups.
Edited by Lucas Malor, 05 December 2007 - 01:50 PM.

Hi Renato,

can you please fix the download http://www.autopatch.../files/apup.zip, in the beginning of the post, it has the wrong apup.zip. It still is version 1.0.1

http://www.autopatch...engine/apup.zip, has the correct apup.zip
Edited by Rudy, 05 December 2007 - 09:38 PM.

Lucas Malor, on Dec 5 2007, 02:07 AM, said:

.NET 3.5 was not in the old version, and that alone is 197MB, so that's where a large portion of the 350MB is coming from.

Rudy, on Dec 5 2007, 11:36 PM, said:

2 days ago
version 1.0.0.1 runtime error "0". when running in autopather dir. after many stoooops and reruns somehow it managed to download the newer autopather.exe and the newer apup 1.0.0.3 but I had to unzip them manualy. Never seemed to give an error about download stops. After some reruns all newlly inserted patches recognized by the new unofficial autopather and now installed (installed OK, thats a nice1). I hope 1.0.0.3 or a newer version will fix the download unzipping // stopping problems.

nice method to keep autopatcher alive, it seems it can do the work

A suggestion: .Net 3.5 or all .Nets ... could be a separate, different group of downloads like directX

@jazalez

I talked to Antonis about updating the APUP script last night which he did. Hopefully the extraction issues shouldn't happen again.

Net 3.5 - I'm going to look into this but no promises

One more vote for keeping .net separate!

Reporting...I moved the latest v.1.0.3 of apup to a spare XP system I run. It has a fairly fresh load already installed with nothing extra fully updated. I created an Autopatcher folder on my desktop and extracted the apup files there. I created a shortcut to run apup with the /log switch just in case. It ran with no errors however it did stop downloading about 5 or 6 times. I simply cancelled and restarted and let it start over. Again no errors once the full download was finished.

I checked the XP, Autopatcher updater, Autopatcher engine and Office XP blocks.

When I do the same thing on a current APUP folder on my main system I get the divide by 0 error. Perhaps this is more software related.

Cyrus, on Nov 11 2007, 03:28 PM, said:

You aren't the only one with this problem using apup 1.0.3. When I click next it just sits there. I have dotnet 3 installed and patched. My home network is patched by WSUS if that is any consolation.

I have deleted the release list to ensure that it downloads the latest version.