APUP2 Dos Command Problem
rickmastfan67
07 Jun 2012
ViroMan, on 12 May 2012 - 11:48 AM, said:
@Whatacrock is it true that .net doesn't work for you if you use apup2 but, its fine with apup1? If so I need to look into this because no one else has complained. It seems to work for me though. Have you tried using the supplied MD5 files to cross check for extra or missing files?
Both of the .NET scripts seem to cause my copy of apup2 to hang badly. They are the only scripts that seem to do this. And once the program un-freezes, I get the following error message almost without fail: "Invalid argument". And when I hit the "OK" button, apup2 closes itself.
One time, I was lucky to get the x86 script to download the entire copy of .NET. But that script only worked twice out of the 40+ times I attempted it. Really annoying. Plus I haven't even been able to get the x64 version to work once in apup2. All I get with the x64 script is the error message I mentioned above.
Whatacrock
07 Jun 2012
@rickmastfan67-- did you read post #233 which gives instructions for downloading the dotnet x64 and x86 updates ?
It's easier to download each release seperately. Suggest you start with x64 allow APUP to finish then restart and download the x86 release next.
Since you have already tried you can go into modules\Components\__dotnet and remove the cmd file, this will be redownloaded and allow you to redownload the 2 releases as suggested.When the cmd files runs will ask if you wish to keep both x64 and x86,86 only or x64 only...answer this to your preference.
You send up with 3 folders...x86...x64 and x86/x64 if you want to keep both
Hope this helps you out
Edited by Whatacrock, 07 June 2012 - 01:56 PM.
It's easier to download each release seperately. Suggest you start with x64 allow APUP to finish then restart and download the x86 release next.
Since you have already tried you can go into modules\Components\__dotnet and remove the cmd file, this will be redownloaded and allow you to redownload the 2 releases as suggested.When the cmd files runs will ask if you wish to keep both x64 and x86,86 only or x64 only...answer this to your preference.
You send up with 3 folders...x86...x64 and x86/x64 if you want to keep both
Hope this helps you out
Edited by Whatacrock, 07 June 2012 - 01:56 PM.
rickmastfan67
07 Jun 2012
@Whatacrock -- I was downloading each seperately in apup2. That's how I got lucky to get the x86 version fully (passed the md5 check in autopatcher). Anyways, I installed and am trying to use the apup1 to download the x64 version and it took FOREVER to even start downloading, but it just did a moment ago.
Still, it would be nice to see both of those scripts working properly in apup2.
Still, it would be nice to see both of those scripts working properly in apup2.
ViroMan
07 Jun 2012
Well this is indeed strange... I have no problem with his scripts. You are using the latest version of APUP2 I assume?(1.0.5.13)
Have you looked into the log file? Does it show anything interesting? Can you post it here?
So you are having problems with both versions of APUP?
Edited by ViroMan, 07 June 2012 - 10:53 PM.
Have you looked into the log file? Does it show anything interesting? Can you post it here?
Quote
Anyways, I installed and am trying to use the apup1 to download the x64 version and it took FOREVER to even start downloading, but it just did a moment ago.
Edited by ViroMan, 07 June 2012 - 10:53 PM.
rickmastfan67
07 Jun 2012
ViroMan, on 07 June 2012 - 10:53 PM, said:
Well this is indeed strange... I have no problem with his scripts. You are using the latest version of APUP2 I assume?(1.0.5.13)
Have you looked into the log file? Does it show anything interesting? Can you post it here?
Have you looked into the log file? Does it show anything interesting? Can you post it here?
Yes. I was running the 1.0.5.13 version of apup2 when this was happening. Here's the log from earlier this morning. I had it set in debug mode when I got this.
Spoiler
ViroMan, on 07 June 2012 - 10:53 PM, said:
So you are having problems with both versions of APUP?
Somewhat. It took about 3 minutes before it even started to download the x64 version of the .NET script. But it did finally start and finished downloading.
ViroMan
08 Jun 2012
Was that the entire log file? If so it seems to have died at a dos move command. hmm..
Also the taking forever part for both of them is due to the MD5 checking in progress... with APUP2 you can see the list of files it checks go by but, you don't really see what is going on with apup1. There is a lot to check.
Edited by ViroMan, 08 June 2012 - 02:06 AM.
Also the taking forever part for both of them is due to the MD5 checking in progress... with APUP2 you can see the list of files it checks go by but, you don't really see what is going on with apup1. There is a lot to check.
Edited by ViroMan, 08 June 2012 - 02:06 AM.
rickmastfan67
08 Jun 2012
ViroMan, on 08 June 2012 - 02:05 AM, said:
Was that the entire log file? If so it seems to have died at a dos move command. hmm..
Yep, that was the entire log.
ViroMan, on 08 June 2012 - 02:05 AM, said:
Also the taking forever part for both of them is due to the MD5 checking in progress... with APUP2 you can see the list of files it checks go by but, you don't really see what is going on with apup1. There is a lot to check.
Why would it have to do a MD5 check when it was the first time ever downloading the files? (I expect it to do a MD5 check if I had at least one file downloaded so far.) I don't recall APUP2 doing that untill I have at least one file downloaded and I have to restart the download via the script if the connection dies on any of the other scripts.
ViroMan
08 Jun 2012
ohh, well there is all the moving to be done as well(when the moving works that is). Moving around 1gb+ isn't instant but, it shouldn't take more then 20-40 seconds or so(depending on the speed of your HD).
Well I looked into the error and it was not an error I setup. That means it was a system reported error. I will look into it further. I have some leads since it happens when running a dos command. So I know where to start poking around.
edit:
However... even the system errors have titles that I assign to them. If you can try again and get that same error... read the title and the error message. The title will be in the windows name itself. That will give me an exact location to check.
Edited by ViroMan, 08 June 2012 - 04:02 AM.
Well I looked into the error and it was not an error I setup. That means it was a system reported error. I will look into it further. I have some leads since it happens when running a dos command. So I know where to start poking around.
edit:
However... even the system errors have titles that I assign to them. If you can try again and get that same error... read the title and the error message. The title will be in the windows name itself. That will give me an exact location to check.
Edited by ViroMan, 08 June 2012 - 04:02 AM.
rickmastfan67
10 Jun 2012
I just tried the .NET x86 one again and no errors this time. HOWEVER, the MD5 check window NEVER showed up, even though I could tell that it was checking those files. Every other script that is offered shows the MD5 check window when apup2 is checking the files. Whenever I run either of the .NET scripts, apup2 just hangs completely till I get an error message, or it
And now I've just run the x64 .NET script, and an error shows up. After I hit the OK button, apup2 closes itself.
Ohh ###### there is an Error
Perrmission denied
OK
And now I just got the other error message again on the x64 one:
Ohh ###### there is an Error
Invalid argument
OK
I hope this is what you wanted.
(was with 1.0.5.13)
Edited by rickmastfan67, 10 June 2012 - 11:33 PM.
And now I've just run the x64 .NET script, and an error shows up. After I hit the OK button, apup2 closes itself.
Ohh ###### there is an Error
Perrmission denied
OK
And now I just got the other error message again on the x64 one:
Ohh ###### there is an Error
Invalid argument
OK
I hope this is what you wanted.
(was with 1.0.5.13)
Edited by rickmastfan67, 10 June 2012 - 11:33 PM.
ViroMan
11 Jun 2012
ahh yes. It is failing when it tries to execute dos commands. You are the second person to complain about the dos commands not working. hmm... It works perfectly fine for me... I don't know how to troubleshoot this without seeing the error while in debug. I have compiled a newer version of the exe. I will post it shortly. It has minor fixes and more debugging for the dos command issue.
Try the newer version. It will probably still crap out but, it will give me a lot more in the log file if you put in debug mode.
I think the error might be in the process command this should tell me. Each time it runs a dos command it runs it by starting a new process. In the initialization of the process I can give it various settings. This is how it stays hidden(no dos window). The problem might be in the initialization part of the process.
Edited by ViroMan, 11 June 2012 - 01:37 AM.
Try the newer version. It will probably still crap out but, it will give me a lot more in the log file if you put in debug mode.
I think the error might be in the process command this should tell me. Each time it runs a dos command it runs it by starting a new process. In the initialization of the process I can give it various settings. This is how it stays hidden(no dos window). The problem might be in the initialization part of the process.
Edited by ViroMan, 11 June 2012 - 01:37 AM.
rickmastfan67
11 Jun 2012
Ok, I just tested the new build on the x64 .NET script. No error message came up, but some crazy stuff in the log did show up in Debug mode.
Spoiler
ViroMan
11 Jun 2012
wow... the incorrect function error I threw in there to stop the compiler from giving a warning about it not returning a value. It should not get to that point since it returns values before then if running the command failed or succeeded. I will look into why it jumps out of the nested if statement. probably just a tiny error as all hard to find things are. >
ohh I can't promise anything soon though due to looking for a job.
Edited by ViroMan, 11 June 2012 - 02:39 AM.
ohh I can't promise anything soon though due to looking for a job.
Edited by ViroMan, 11 June 2012 - 02:39 AM.
Whatacrock
11 Jun 2012
Ran APUP 1.0.5.13 today and received the same error also.
When i looked at the log it seems it stopped at
Executing shell command: del "C:\APUP\modules\Components\__dotnet.apm
Also the temp_bin folder is still present in main folder.
When i looked at the log it seems it stopped at
Executing shell command: del "C:\APUP\modules\Components\__dotnet.apm
Also the temp_bin folder is still present in main folder.
ViroMan
11 Jun 2012
ya.. I noticed reason for the error right away when I looked. Forgetting to uncomment a line is detrimental to my health. I already fixed it. I am looking into something else atm though... I will remove the new one for now.
Edited by ViroMan, 11 June 2012 - 03:07 AM.
Edited by ViroMan, 11 June 2012 - 03:07 AM.
ViroMan
11 Jun 2012
Uploaded... try the new one. http://www.autopatch...apup2-download/
Edited by ViroMan, 11 June 2012 - 04:05 AM.
rickmastfan67
11 Jun 2012
Just downloaded v1.0.5.16 and for the first time ever, I did see the MD5 check window for one of the .NET scripts! However, it was hidden behind the main window of apup2.
So, I then created a new install of v1.0.5.16 to make sure there were no problems downloading from the beginning (thank goodness for unlimited download, lol). So, I started off with the x86 .NET first. It timed out once. Then I got an error message. Here's what it says:
Command Execution Error
Invalid argument
OK
And here's the log:
And here's what the "modulecode.bat" file said inside of it if this will also help:
Edited by rickmastfan67, 11 June 2012 - 04:44 AM.
So, I then created a new install of v1.0.5.16 to make sure there were no problems downloading from the beginning (thank goodness for unlimited download, lol). So, I started off with the x86 .NET first. It timed out once. Then I got an error message.
Here's what it says:Command Execution Error
Invalid argument
OK
And here's the log:
Spoiler
And here's what the "modulecode.bat" file said inside of it if this will also help:
Spoiler
Edited by rickmastfan67, 11 June 2012 - 04:44 AM.
ViroMan
11 Jun 2012
Well now we know the problem. Although I just can not comprehend atm why it is failing.
When you hit OK, did the program stay there waiting for you to hit EXIT or did it close? I don't see the rest of the log there that should happen when you close it.
Also I am wondering if this problem is only on windows 7 computers. The other person who had problems was also a windows 7 machine if I remember right. Can someone else with windows 7 verify if this works for them?
I need to get me a job so I can afford windows 7.(no way am I getting win8)
Edited by ViroMan, 11 June 2012 - 04:54 AM.
When you hit OK, did the program stay there waiting for you to hit EXIT or did it close? I don't see the rest of the log there that should happen when you close it.
Also I am wondering if this problem is only on windows 7 computers. The other person who had problems was also a windows 7 machine if I remember right. Can someone else with windows 7 verify if this works for them?
I need to get me a job so I can afford windows 7.(no way am I getting win8)
Edited by ViroMan, 11 June 2012 - 04:54 AM.
rickmastfan67
11 Jun 2012
ViroMan, on 11 June 2012 - 04:53 AM, said:
When you hit OK, did the program stay there waiting for you to hit EXIT or did it close? I don't see the rest of the log there that should happen when you close it.
When I hit the "OK" button, apup2 closes itself right away. That's why you don't see anything in the log mentioning me hitting the "exit" button.
Whatacrock
11 Jun 2012
Ran newest version several times and got an error each time
The temp_bin folder still resident in main folder
Edited by Whatacrock, 11 June 2012 - 05:00 AM.
Spoiler
The temp_bin folder still resident in main folder
Edited by Whatacrock, 11 June 2012 - 05:00 AM.
ViroMan
11 Jun 2012
hmm.... this is odd. It crashes then instead of exiting. Can one of you check the permissions of the bat file in temp_bin. Specifically I am looking to see if that damn thing gets anything set on it.
I will take down the link for now. I just can't concentrate on the code right now.
Edited by ViroMan, 11 June 2012 - 05:13 AM.
I will take down the link for now. I just can't concentrate on the code right now.
Edited by ViroMan, 11 June 2012 - 05:13 AM.
