Unknown Unofficial Release?
Posted 21 August 2008 - 05:10 PM
I have gone over the entire forum and found similar problems to mine and various reasons. I tried all the fixes mentioned, nothing seems to work. I did finally by just clicking on apup to finally got what appears to be a complete download and all the current files. There is just one problem. The title bar on top of Autopatcher tells me that this is an Unknown Unofficial Realease and also Unnofficial/Unsupported Release. If this is truly the case I'l just wait until the "Official" release happens. I've seen no mention of notices about official or unofficial releases in regards to the August 08 release for WinXPSP3 so I'm not sure what is really happening here. Nothing has changed on my system. I re-installed a working XP partiton image that worked with the last apup for July 2008 on a backup machine just to make sure.
I too get that dreaded "Run-time error '0'" and "One or more files failed verification. Would you like to continue at your own risk?" I notice that at around the 32% or so mark the amount of download changes from 172.16MB to 169.45MB. I'm not going to go through all that send in the log file stuff, I'm just reporting my experiences here as I'm not really interested in a dialog at the moment, too busy doing real life business stuff if you know what I mean.
I also notice that when I run apup for the first time apengine.exe does not unzip and turn into autopatcher.exe. Autopatcher.exe appears when I run apup a second time. I get the messages mentioned above no matter how often I click on apup to redownload (into the same folder I just downloaded previously).
I have used your excellent software for as long as you were around. I find it really does help save time when doing a new installation from scratch. I personally hate to do installations or updates that involve being connected to the internet. I always update to an clean up-to-date (backup) image. Thats just how I do things and sites like your are a great help in that regard. I liked your last system before MS got on your case, but this one works as long as Microsofts servers are working and the files haven't been changed around on their servers which means using a current apup download I suppose.
Like I mentioned before I'll wait a while longer to update with apup until the bugs get worked out.
Posted 21 August 2008 - 05:30 PM
not all releases are signed right now. due that, in some scripts you in deed see that. just also a sample, i didn't have the time to figure how to use the tool to sign the modules. the reason is pretty simple: this avatar that i'm choosing right now shows my broken scapula bone, in my right arm (i'm not sure about the translation). so, right now, i'm more concerned about fix it at once than sign the modules
plus, there's an issue regarding an autopatcher translation, that i believe that will be fixed soon.
by the way: what is the language of the script that you are downloading?
Posted 21 August 2008 - 06:10 PM
Posted 21 August 2008 - 06:54 PM
Posted 22 August 2008 - 02:49 PM
the hotfix KB951618 got a v2 version
autopatcher expects file at http://download.microsoft.com/download/a/f...618-x86-ENU.exe
but microsoft changed to http://download.microsoft.com/download/a/f...-v2-x86-ENU.exe
so autopatcher gives an error '0' that means no file found
download the missing file at http://rapidshare.com/files/136895338/Wind...618-x86-ENU.exe and put it to modules\NonCritical\KB951618_xp_x86_enu.apm_file
re-run autopatcher and the problem is fixed
Posted 22 August 2008 - 05:49 PM
Posted 22 August 2008 - 08:07 PM
Posted 23 August 2008 - 12:32 AM
I won't be able to generate a new RTI for now which means the XP thread will show as "Unoffical" until it's updated.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users