Run Time Error 0
Klaus_1250
05 Jan 2008
From the apup log:
After the last message, apup spits out a "Run Time Error 0". Manually unzipping the file is no problem.
Edited by Klaus_1250, 09 January 2008 - 05:43 PM.
... Starting detection routine for item AutoPatcher Executable 5.6.81 Looking for file C:\Program Files\AutoPatcher\autopatcher.exe File does not exist!!! Item AutoPatcher Executable 5.6.81 doesn't appear to be here. Adding its downloads to queue... Adding http://www.autopatcher.com/apengine/apengine_exe.zip. ... Attempting to unzip C:\Program Files\AutoPatcher\apengine_exe.zip into C:\Program Files\AutoPatcher\
After the last message, apup spits out a "Run Time Error 0". Manually unzipping the file is no problem.
Edited by Klaus_1250, 09 January 2008 - 05:43 PM.
Klaus_1250
05 Jan 2008
While I'm at it: Apup also fails to download any updates for Autopatcher. Here, the log-file is less than helpfull :-( Downloading autopatcher_xp_x86_enu.script works, but after that, "Run Time Error 0"...
The apup log only contains this:
Awarkly enough, before I completely cleaned out the Autopatcher directory (which already has some modules downloaded), I also got Run Time Error 0, but later in the process and I was even able to download some modules.
The apup log only contains this:
AutoPatcher Updater starting. List file HTTP location: http://www.autopatcher.com/releases.list Download queue status: 1 files waiting. releases.list: Download complete. Download queue status: 0 files waiting. Download queue status: 1 files waiting. autopatcher_xp_x86_enu.script: Download complete. Download queue status: 0 files waiting.
Awarkly enough, before I completely cleaned out the Autopatcher directory (which already has some modules downloaded), I also got Run Time Error 0, but later in the process and I was even able to download some modules.
Klaus_1250
05 Jan 2008
One more thing: I checked out the DirectX module a bit more closely:
The first lines works, e.g. \modules\Components\DirectX_enu.apm is deleted if present and this is logged in the apup logfile. The second line (PreAction =del instead of PreAction.FileDelete) does NOT work. The file is never deleted if present, nor does the logfile mention it is trying to delete the file...
PreAction.FileDelete=autopatcher:\modules\Components\DirectX_enu.apm PreAction=del "autopatcher:\autopatcher_directx_nov07.script" PreAction=del "autopatcher:\dx_x86.rti" PreAction=del "autopatcher:\dx_x86.ver"
The first lines works, e.g. \modules\Components\DirectX_enu.apm is deleted if present and this is logged in the apup logfile. The second line (PreAction =del instead of PreAction.FileDelete) does NOT work. The file is never deleted if present, nor does the logfile mention it is trying to delete the file...
Klaus_1250
22 Jan 2008
/bump.
Still the same; I noticed some scripts have been updated, but still use PreAction=del instead of PreAction.FileDelete ??? (which causes the runtime errors).
Any ETA when these will be fixed?
Still the same; I noticed some scripts have been updated, but still use PreAction=del instead of PreAction.FileDelete ??? (which causes the runtime errors).
Any ETA when these will be fixed?
sh1leshk4
22 Jan 2008
Have you tried to re-download apup through the link posted here?
apup 1.0.3 has two versions in which the first one is buggy and once posted in that thread.
A newer version has been out since then and the link on that first post has been fixed to point to the new one.
I suspect you're using the older version since no one has reported such an error as yours.
(personally I also have no problem with any of the scripts)
apup 1.0.3 has two versions in which the first one is buggy and once posted in that thread.
A newer version has been out since then and the link on that first post has been fixed to point to the new one.
I suspect you're using the older version since no one has reported such an error as yours.
(personally I also have no problem with any of the scripts)
Erik Ramey
22 Jan 2008
I agree with sh1leshk4. Could you redownload APUP including the apbin directory and try again?
BlkWolf
22 Jan 2008
sh1leshk4, on Jan 22 2008, 08:20 PM, said:
I suspect you're using the older version since no one has reported such an error as yours.
(personally I also have no problem with any of the scripts)
(personally I also have no problem with any of the scripts)
Decided to register to say that i have the same problem. Besides, from time to time apup would just "freeze". As in it just sits there doing nothing, waiting for a download to start, although it respnds to commands (exit). After program restart it would work ok on that download, then stop on another one later. That was while downloading standard XP patches. Now i'm done with that and trying to get the addons. Got some of them, also got some " Run-time error '0' " messages. Now it's trying to download java, gets a 404 error from the server, and ends in "error 0". Also, starting apup on a comp without any internet connection results in the same error. So... i guess that's where the problem is. Maybe it's not a problem with deleting and unziping, but with read errors while trying to download a file.
Oh, and i got the 'good' version. Twice.
sh1leshk4
22 Jan 2008
The older version does have the troubles Klaus_1250 had.
While "run-time error 0" is a "widely known bug" in the newer version; so nothing new here.
But I won't leave this thread w/o explanation either.
When it freezes, chances are it's in the middle of checking what files you already have all the while generating the download list.
On my A64 3500+ w/ 1GB PC3200 DDR DRAM (single channel), using the default downloads could take up to a minute or two before the download starts.
It might also be caused by an I/O bottleneck; fragmented h/ds, slow h/d RPMs, anything.
Also, keep in mind that while it checks the files it also compares the MD5 hashes of each and every file, so slower systems might take longer.
But this is true only if you already have files present on the folder where you run apup.
In a new, empty folder, it should start download almost immediately since it has nothing to check aside from apup itself.
Now, regarding "run-time error 0", it means apup doesn't know what to do when an error occurs.
When apup asks for a file, if it can't find the file or can't connect into a server, it'll spew out "run-time error 0" because it doesn't know what to do when that happens.
This is why a "run-time error 0" (usually) happens only when it starts trying a new download.
Yes, my explanation won't help in solving any apup problems at all, but this is the "widely known" limitations of the current apup (1.0.3).
While "run-time error 0" is a "widely known bug" in the newer version; so nothing new here.
But I won't leave this thread w/o explanation either.
When it freezes, chances are it's in the middle of checking what files you already have all the while generating the download list.
On my A64 3500+ w/ 1GB PC3200 DDR DRAM (single channel), using the default downloads could take up to a minute or two before the download starts.
It might also be caused by an I/O bottleneck; fragmented h/ds, slow h/d RPMs, anything.
Also, keep in mind that while it checks the files it also compares the MD5 hashes of each and every file, so slower systems might take longer.
But this is true only if you already have files present on the folder where you run apup.
In a new, empty folder, it should start download almost immediately since it has nothing to check aside from apup itself.
Now, regarding "run-time error 0", it means apup doesn't know what to do when an error occurs.
When apup asks for a file, if it can't find the file or can't connect into a server, it'll spew out "run-time error 0" because it doesn't know what to do when that happens.
This is why a "run-time error 0" (usually) happens only when it starts trying a new download.
Yes, my explanation won't help in solving any apup problems at all, but this is the "widely known" limitations of the current apup (1.0.3).
Klaus_1250
23 Jan 2008
Tried the new version, but same behavior. Runtime error 0. I think it was already the same version I used.
Isn't there someone who has access to the apup-codebase and can see what makes the difference between PreAction = del and PreAction.Filedelete ???
The first one causes an Runtime error 0, the second does not (it works, no runtime-error). Seeing that both are found in the current scripts-files, someone does know about this error and fixed it. But for some awkward reason, nobody seems to know this. So, the sum it up, if PreAction = del would be replaced by PreAction.FileDelete, that would solve part of my runtime 0 problems. I think that the runtime error 0 I receive when autopatcher needs to unzip things are related to this.
PS: A wild guess, but could it be related to 8+3 filename support? I don't have it, and I remember that there used to be a few apps who would give awkward errors because they couldn't find files.
Edited by Klaus_1250, 23 January 2008 - 06:40 PM.
Isn't there someone who has access to the apup-codebase and can see what makes the difference between PreAction = del and PreAction.Filedelete ???
The first one causes an Runtime error 0, the second does not (it works, no runtime-error). Seeing that both are found in the current scripts-files, someone does know about this error and fixed it. But for some awkward reason, nobody seems to know this. So, the sum it up, if PreAction = del would be replaced by PreAction.FileDelete, that would solve part of my runtime 0 problems. I think that the runtime error 0 I receive when autopatcher needs to unzip things are related to this.
PS: A wild guess, but could it be related to 8+3 filename support? I don't have it, and I remember that there used to be a few apps who would give awkward errors because they couldn't find files.
Edited by Klaus_1250, 23 January 2008 - 06:40 PM.
sh1leshk4
23 Jan 2008
If it can't connect to a server then it's always "run-time error 0"; no matter which version.
Regarding that PreAction problems, it's better to give out the filenames instead of just telling there are problems with some files.
List the .script files that you find problematic.
You don't have 8.3 naming support?
Both FAT32 and NTFS supports 8.3 file naming, IIRC.
Regarding that PreAction problems, it's better to give out the filenames instead of just telling there are problems with some files.
List the .script files that you find problematic.
You don't have 8.3 naming support?
Both FAT32 and NTFS supports 8.3 file naming, IIRC.
Klaus_1250
23 Jan 2008
But it can connect to a server fine. No problem. Never seen a Runtime Error 0 for that. Everything works, except for unzipping and PreAction = del
As for PreAction problems: every file which has PreAction = del. Every script with PreAction = del lines in it. See my earlier posts. As I said before, PreAction = del fails. It isn't even logged (PreAction.FileDelete is), it just returns Runtime Error 0. Doesn't matter which file. Doesn't matter whether the file exists or not, it is not deleted, nor is the action to try logged with PreAction = del. PreAction.FileDelete works though, logs, deletes and doesn't return a Runtime Error 0. Please read my earlier posts.
And yes, NTFS does suport 8.3 filenaming, but I turned it off. I don't use anything that should require 8.3 support, so leaving it on just wastes bytes and cpu-cycles. But that was just a wild guess anyhow.
Edited by Klaus_1250, 23 January 2008 - 10:53 PM.
As for PreAction problems: every file which has PreAction = del. Every script with PreAction = del lines in it. See my earlier posts. As I said before, PreAction = del fails. It isn't even logged (PreAction.FileDelete is), it just returns Runtime Error 0. Doesn't matter which file. Doesn't matter whether the file exists or not, it is not deleted, nor is the action to try logged with PreAction = del. PreAction.FileDelete works though, logs, deletes and doesn't return a Runtime Error 0. Please read my earlier posts.
And yes, NTFS does suport 8.3 filenaming, but I turned it off. I don't use anything that should require 8.3 support, so leaving it on just wastes bytes and cpu-cycles. But that was just a wild guess anyhow.
Edited by Klaus_1250, 23 January 2008 - 10:53 PM.
sh1leshk4
23 Jan 2008
And if "PreAction = del" failed on you, why it didn't for me?
Well, if it's a scripting error, then it should all apply for all users since they (and I) used the same apup and scripts just like you did.
I've read your posts.
The first one is because you used the older version.
The second one is because it's currently "inherent" in apup 1.0.3; widely known bug.
The third one, however, is probably caused by one thing or another but it's definitely not the scripts.
From autopatcher_xp_x86_enu.script :
I'm not trying to be ignorant, I just can't seem to recreate your problems over there.
Edited by sh1leshk4, 23 January 2008 - 11:07 PM.
Well, if it's a scripting error, then it should all apply for all users since they (and I) used the same apup and scripts just like you did.
I've read your posts.
The first one is because you used the older version.
The second one is because it's currently "inherent" in apup 1.0.3; widely known bug.
The third one, however, is probably caused by one thing or another but it's definitely not the scripts.
From autopatcher_xp_x86_enu.script :
PreAction=del "autopatcher:\modules\NonCritical\KB895181_enu.apm"From apup.log :
Executing shell command: del "C:\Program Files\AutoPatcher\modules\NonCritical\KB895181_enu.apm"...and it's from just this minute running of apup.
I'm not trying to be ignorant, I just can't seem to recreate your problems over there.
Edited by sh1leshk4, 23 January 2008 - 11:07 PM.
Klaus_1250
23 Jan 2008
sh1leshk4, on Jan 24 2008, 12:06 AM, said:
And if "PreAction = del" failed on you, why it didn't for me?
Quote
Well, if it's a scripting error, then it should all apply for all users since they (and I) used the same apup and scripts just like you did.
Quote
I've read your posts.
The first one is because you used the older version.
The first one is because you used the older version.
Quote
PreAction=del "autopatcher:\modules\NonCritical\KB895181_enu.apm"From apup.log :
Executing shell command: del "C:\Program Files\AutoPatcher\modules\NonCritical\KB895181_enu.apm"
Attempting to delete file C:\Program Files\AutoPatcher\modules\Components\DirectX_enu.apmif PreAction.FileDelete is used. Nothing if PreAction = del is used (except Run Time Error 0).
Quote
I'm not trying to be ignorant, I just can't seem to recreate your problems over there.
I'll switch to Ct updater, so you can close this report.
sh1leshk4
24 Jan 2008
Klaus_1250, on Jan 24 2008, 06:21 AM, said:
I have never seen that line in the apup.log I get
Attempting to delete file C:\Program Files\AutoPatcher\modules\Components\DirectX_enu.apmif PreAction.FileDelete is used. Nothing if PreAction = del is used (except Run Time Error 0).
It might be that it's the PreAction.FileDelete that's causing problems.
Since the log was stopped at...
Attempting to delete file C:\Program Files\AutoPatcher\modules\Components\DirectX_enu.apm...then it might be caused by PreAction.FileDelete itself so that apup had an error and stopped logging altogether.
Klaus_1250, on Jan 24 2008, 06:21 AM, said:
I can understand that you cannot recreate my problem. But the way it is going now, it doesn't look like anyone cares about solving it. Apparently, Run Time Error 0 is some magical non-descriptive User Fault.
Klaus_1250, on Jan 24 2008, 06:21 AM, said:
I'll switch to Ct updater, so you can close this report.
BlkWolf
25 Jan 2008
@Klaus_1250
could you try just one thing? Try to delete a file in one of the autopatcher\modules subdirs from the command prompt using the "del" command. Something like
Tried that one. Not bad, but I think they only get the critical updates. Might be wrong, though.
Edited by BlkWolf, 25 January 2008 - 05:47 PM.
could you try just one thing? Try to delete a file in one of the autopatcher\modules subdirs from the command prompt using the "del" command. Something like
del "C:\Program Files\AutoPatcher\modules\Components\DirectX_enu.apm"Also, if that "PreAction = del" thing calls the same del command used by 'command prompt' the file path should be quoted if there is a space in there (as in "Program Files"). And, AFAIK, there are two cmd/command shells that execute, one for win32 programs and one for legacy programs. Between all these and turning off 8.3 support in NTFS (btw, how do you do that?), something might get screwd.
Klaus_1250, on Jan 24 2008, 01:21 AM, said:
I'll switch to Ct updater, so you can close this report.
Edited by BlkWolf, 25 January 2008 - 05:47 PM.
Erik Ramey
25 Jan 2008
I appologize in missing this thread. I'm working on the scripts so much that I sometimes miss a couple threads here and there. Please feel free to PM me in the future =)
Lately I've been noticing some errors when using the shell commands like PreAction.FileDelete which is why I'm converting to preaction= "del....." I didn't notice that one was still in the Directx list, which I'll update tonight. In the mean time, could you go ahead and use APUP and download each catagory one at a time.
If/when you receive errors, be as specific as possible: Which list are you updating, what file in the APUP log is trying to be deleted, etc.
Lately I've been noticing some errors when using the shell commands like PreAction.FileDelete which is why I'm converting to preaction= "del....." I didn't notice that one was still in the Directx list, which I'll update tonight. In the mean time, could you go ahead and use APUP and download each catagory one at a time.
If/when you receive errors, be as specific as possible: Which list are you updating, what file in the APUP log is trying to be deleted, etc.
