Autopatcher v6.1.21 Has Started at 31.12.2014 15:46:58
Starting Autopatcher From F:\Apup_1_4_38_Win7
Unknown Language ID: 9242
Detected OS: English (1033) Microsoft Windows 7 Professional x64 Service Pack 1
Current Locale: / Non-Unicode Default: English
Installing Update for Windows 7 for x64-based Systems (KB2522422)
Installing Update for Windows 7 for x64-based Systems (KB2834140-v2)
Installing Update for Windows 7 for x64-based Systems (KB2847077)
Installing Update for Windows 7 for x64-based Systems (KB2913431)
Installing Work Folders for Windows 7 (64 bit) (KB2891638)
Error Detected: File not found in ExecuteCommand At Line 114
A new application error
Re: application error
I got this
-
Whatacrock
- Release Maintainer
- Posts: 1967
- Joined: Mon Oct 28, 2013 10:47 am
- Location: Australia
- Contact:
A new application error
Moved post from "application error" to new thread
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"
Re: A new application error
Thats a scripting error. One of the APMs must have a bad command line in them.
-
Whatacrock
- Release Maintainer
- Posts: 1967
- Joined: Mon Oct 28, 2013 10:47 am
- Location: Australia
- Contact:
Re: A new application error
Strange this occurs as have reinstalled several machines with Windows 7 x64 over the last week and received no errors. Double checked the apm modules posted by Talaba and all seem to be in order...
@Talaba -- what is the status of your autopatcher ?? -- maybe your release is incomplete (that is :- missing installer files)
@Talaba -- what is the status of your autopatcher ?? -- maybe your release is incomplete (that is :- missing installer files)
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"
Re: A new application error
My bad wac, that error is internal. From memory I thought that was the line that ran the programs. Its an error that should not happen though. Its the line that closes the batch file after writing to it. Meaning either the system wasn't done writing the file or the file doesn't exist. If its the latter then The OS should have coughed up an error saying access forbidden. I can put in a tiny 10ms pause in there to help the os catch up.