Missing main AP executable
Posted 27 June 2010 - 07:40 PM
New user to this pgm.
I downloaded the APUP file and ran it, it took about 2 hours to get all the downloads, but there is NO Autopatcher.exe file!!
I ran the APUP prgm from a second partition on my HDD, (Not C:)!
Can I just copy all the folders & files over to "C:" and some how just refresh everything or do I have to delete everything and start APUP and the Large download(s) again???
Does APUP actually install anything to the "C" drive? And if so - does APUP have to be put into the C:\program files folder??
Thanks a bunch, am anxiously awaiting answers!!
Posted 27 June 2010 - 10:24 PM
probably you have forgot to select the first 2 scripts in apup dialog screen
> I have to delete everything and start APUP and the Large download(s) again?
no. all that you have to do is run apup again and select the first 2 scripts. to update the scripts in the following months, it's the same thing. the scripts will do the proper changes, downloading only the missing updates
> does APUP have to be put into the C:\program files folder?
no. apup and autopatcher can run from any folder (but please, short paths), even removable ones (but not from remote folders)
Posted 29 June 2010 - 08:54 PM
something is amiss
1) the first two items (program and engine) are already checked - i do not uncheck them
2) the first time i ran the program, it seemed to work fine
i ran it on a second machine (with different update status, of course), and problems arose
nearly finished, a dialog box came up telling me an MD5 didn't match
3) running it again, i created a log file
the log file says the executable, update lists translation folder (and on and on) are missing
i am able to manually download these items using the URLs from the log file
4) to verify, i deleted the whole mess and downloaded a fresh copy of the apup130 zip file
i know a little about programming - so i will take a stab at one possible cause
it behaves as though there is a registry entry created by the program
once this entry has been created, the program no longer wants to run properly
just a guess
i attached a copy of the log
as you can see, the necessary items were selected
EDIT - i am going to put the original HD image back on this drive and try it from scratch
this time, i will create the log file on the first pass - maybe i can help troubleshoot for you
Edited by dedndave, 29 June 2010 - 09:00 PM.
Posted 29 June 2010 - 10:07 PM
i have changed my conclusion
the machine on which it worked has SP3 installed
the machine on which it did not work does not have SP3 installed, yet (only went as far as WMP11 on this build)
i wanted to get an idea of which KB's would be required prior to installing SP3
let me see if that is a valid conclusion
i will install SP3 and try again
Posted 29 June 2010 - 10:36 PM
i also tried enabling/disabling the Automatic Updater Service
and, i tried copying the already downloaded files from the other machine (translations folder, etc)
oh - and i tried running with no log file, as well
maybe there is some KB that i have installed on the other machine that i do not have on this one that is the culprit
i will have to use WMI to make 2 lists and compare them
now, let me see if i can remember how to do that - lol
Edited by dedndave, 29 June 2010 - 10:39 PM.
Posted 29 June 2010 - 11:12 PM
tomorrow, i will see if i can make the failing machine work by installing a few KB's
interesting to note - the very first line
i did not know WMIC needed to be "installed"
first thing tomorrow i will see if that has an effect before installing KB's
Posted 30 June 2010 - 12:42 AM
Let me try to clarify a few things to get you back on track. All you are trying to do is get a complete release right, all this other stuff is irrelevant at the moment, the status of the machine or SP level, updates installed etc. This only matters when you begin to install the updates not when you are simply trying to download a complete release.
APUP is essentially a download manager, it wont write any registry settings, it will create the structure of the \modules folder via a script but nothing more. Anything you download can just as easily be deleted by getting rid of the \apup or \autopatcher folders (whatever you may have named them).
I'm a little lost in all your posts but it seems to me you are having troubles downloading a complete package, and that failed verification is common and easily fixed but the issue has to be presented in an easily understood manner - no big deal here, but I have to re read your posts and have a look at your attachments but usually an APUP and/or AutoPatcher log will give many clues. BTW, APUP and AutoPatcher are not the same - APUP (apup.exe) will download and maintain the release and AutoPatcher (autopatcher.exe) will install the updates (update your machine).
I'm not sure exactly if by re running you mean you started over or did you re run APUP in the same folder (this is the proper method) - what might have been missed the first time in most cases will get picked up the second time. It isn't impossible there is a script glitch - I'm testing it now. I'll download apupxxx.zip and see if I can get all the files associated with AutoPatcher Updater (apup.exe) and AutoPatcher Engine (autopatcher.exe).
Also, just put the contents of the log file in [spoiler ] log file here [ /spoiler] - much easier to read. Bring the brackets together - see Spoiler below.
OK, I just downloaded apup131.zip, extracted it, ran it to download AutoPatcher Updater and AutoPatcher Engine, I unchecked the XP release - I'm on dialup. Everything checked out, downloaded fine including autopatcher.exe. When you run AutoPatcher it can't fully load because no \module exists but you can see the Official status, which I got.
Also, when you run APUP for the first time the log will show a number of missing files - it is the first run - see my first run log...
Posted 30 June 2010 - 02:35 AM
I noticed in your log file that you are trying to download multiple releases at the same time, and your log shows -> Files to be Downloaded: 237. It may help to only select one script at a time. You can leave AutoPatcher Updater and AutoPatcher Engine selected, but only one big release, see if it 'Finishes' (always good to run APUP a second time to trim the log), if so, add one new release until you get everything you want downloaded and all is Official. When updating a package, selecting everything in most cases is fine but you still want to know what release is giving you problems if there is the dreaded Unofficial warning and you can't tell by the log file...
The easiest way is to run AutoPatcher, when the modules load - click 'About' - click 'Release Info'. The problem release is the Title in Red and the Official status is False. Also, most of the packages come with a .md5 checksum file, you will want to run it against the release to see if it gives you any ideas as to what files are missing or are a mismatch. At this point though, you need a lot of files.
Here is a screenshot of a multi-release package - all is Official.
Note: Don't worry if the 'log' and 'apup.ini' don't match, mine may be different, we're mostly concerned with the other missing files.
Posted 30 June 2010 - 05:42 AM
i think i understand what you are saying
but, it still isn't behaving as expected
what i was trying to do was to figure out what the differences were between
the machine where apup works and the one where it doesn't
(they are actually the same machine with different hard drives)
if you look at the 2 HTML's in the last attachment, you will see what i mean
at any rate, i will try to do just the "basic" list, first
on a related note - it seems to want to download the new Adobe stuff, whether i ask for it or not
you guys getting paid by Adobe ?
i have all those files, but i do not install them until later in the build
let me get a couple cups of coffee before proceeding
i will keep you "posted"
Edited by dedndave, 30 June 2010 - 05:43 AM.
Posted 30 June 2010 - 07:46 AM
I managed to get past the "packages" problem. As Mike suggested, reducing the number of
packages worked. However, on one machine, I am able to download 3 packages on the first pass:
1) AutoPatcher Updater 126.96.36.199
2) AutoPatcher Engine 188.8.131.52
3) AutoPatcher for Windows XP SP3 (x86)
On another machine (same machine - different HD build), I had to do 2 packages on the first pass:
1) AutoPatcher Updater 184.108.40.206
2) AutoPatcher Engine 220.127.116.11
Then, on the second pass:
3) AutoPatcher for Windows XP SP3 (x86)
It seems that the program should not continue without having the tools, bin, and translations
folders and files in place before proceeding. At any rate, I do not know why the second build fails
to download these packages if the XP SP3 package is selected.
Microsoft has updated the Network Monitor from version 3.3 to version 3.4.
When you attempt to download the file named "NM33_x86.exe" via direct URL, the MS server aliases a file
named "NM33_x86_exe", instead (probably via PHP). This is actually the error 404 HTML file.
Of course, the file sizes and MD5's do not match.
The direct link for the new x86 file is:
Hope that helps, guys.
Edited by dedndave, 30 June 2010 - 07:51 AM.
Posted 30 June 2010 - 07:51 AM
I see you posted while I was typing so I will delete most of this until I read your post
Also, could you please post a log file for each run, this is why we use them, the error (dead link) should show up but we need to see the log file. Also, by machine don't you simply mean partition or drive - it is confusing when you say - different machine, well same machine.
It looks like you have 2 \apup setups you want to get working, start referring to them as setup1 and setup2 or something, this machine stuff is confusing. Post logs for each setup this is how we do it.
Dave, why aren't you following my instructions, what does the .md5 (md5_checksum_for_AutoPatcher_XP_ENU.md5) show when you run it against XP SP3? What about the .md5 I gave you, you're not telling me anything here - feedback, specifics - what are the tools showing you when you use them?
Also, NM33_x86_exe is part of the 'Extras' package not 'XP SP3', this is why it is confusing, you're jumping all around with bits of info here and there. We need to get the first 2 scripts completed - AutoPatcher Updater and AutoPatcher Engine, if they wont 'Finish' we need to see the log file of that particular run, and find out what is not working -> then move on to XP SP3, or Extras.
Cristiano, it looks as if NM33_x86_exe is a dead link, the file has been updated to NM34_x86.exe if the link in post #11 is the correct update.
BTW Dave, this file's absence from the 'Extras' release will cause the release to be Unofficial.
Edited by gUiTaR_mIkE, 30 June 2010 - 08:44 AM.
Posted 30 June 2010 - 11:18 AM
sorry about that. this issue was reported a few days ago when we was testing 3 updates for this one that shall be deployed in the proper order. sadly, one of the links can't be taken (ticket-based), but nm3.4 breaks the detections for the 3 updates and they still have to be deployed in a certain order. i will look if the module for this one is already ok and fix it tonight
Posted 30 June 2010 - 11:25 AM
I appologize for the "machine" confusion. There are a few of us in the family that have identical
computers. For example, if I need to "fix my nephews machine", I plug his hard drive into my computer
and work on it. In that context, what makes a machine individual is the drive. Sorry about that.
I was also a bit confused, too. When I ran the program on one setup, I selected the 3 default check
marks and everything ran fine. When I tried it on the other setup, I also selected DirectX, Extras, and
.Net. At the time, I did not realize that was where the problems were. The dialog box said "one or more
files failed verification", and the program seemed to stop. When that dialog appears, the tools, bin, and
tranlations folders (as well as some addtional files in the apup folder) have not yet been extracted.
It makes it look like a terminal error, and I made the assumption that the missing files/folders were the
issue. I did not notice that clicking the OK button allowed the program to continue, which is when the
As it turned out, it was the Network Monitor version update that caused the error. But, I continued
under the assumption that the missing files/folders was the problem, and thought there was some difference
in the setup that caused the failure. Now that I have a better understanding of how the program works, I can
see what caused the error. I didn't post log files because I didn't see how they would help. I didn't compare
MD5's because I didn't think the files were present to compare.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users