lmao...omg... thats the background color. Each frame has a different color so I can tell what frame is what when they are stacked up in the edit window. Apparently that frame doesn't have a line of code telling it to be grey like the rest when the program starts up. I changed that color this release because its the same as two other frames. THIS warrants an immediate patch!
edit: all fixed up.
http://www.autopatcher.net/apengine/Aut ... 6_1_27.zip
Autopatcher v6.2
- Whatacrock
- Release Maintainer
- Posts: 1967
- Joined: Mon Oct 28, 2013 10:47 am
- Location: Australia
- Contact:
Re: Autopatcher v6.1 beta
All better now !!!
Looking good, I even noticed the menu at the top of the app. NICE
Looking good, I even noticed the menu at the top of the app. NICE
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"
Re: Autopatcher v6.1 beta
Argh, I'm getting the following as a popup:
Path not found
In prjUpdater.mdlScriptParser.replaceVariables at Line 114
after clicking the Download Releases button / area
Click the OK button, and it keeps popping up
Path not found
In prjUpdater.mdlScriptParser.replaceVariables at Line 114
after clicking the Download Releases button / area
Click the OK button, and it keeps popping up
Re: Autopatcher v6.1 beta
hmm... That is the line where it tries to replace the word "temp:" with the path to the temp directory that was chosen. Usually "<The_AP_Dir_You_Started_From>\temp_bin" or <Drive_That_Windows_Is_On>:\#AutoPatcher_Temp#
Run it again and see if either of these exist when the application is running... also create a log with verbose please.
Run it again and see if either of these exist when the application is running... also create a log with verbose please.
Re: Autopatcher v6.1 beta
Both the temp_bin and #AutoPatcher_Temp# folders get created this time. And no popup boxes saying the same thing.
Log too long as a post, so attatched.
Log too long as a post, so attatched.
- Attachments
-
- autopatch.log
- (138.85 KiB) Downloaded 291 times
Re: Autopatcher v6.1 beta
bah... reading large logs like that reminds me to figure out some more things to cut from the log reports. Probably going to cut a lot of path information out.
Re: Autopatcher v6.1 beta
A couple of things to keep in mind regarding bugs, logs & AutoPatcher 6x.Nchalada wrote:Log too long as a post, so attatched.
Select fewer scripts when downloading fresh (new) releases. Your log shows only Admin Tools as existing, the rest appear to be new - that's 10 scripts and roughly 3.2GB of data.
Run AutoPatcher a second time to create a smaller log file (2nd run log). Select the same scripts of course . This will reduce the size of the log considerably, for one, it will (hopefully) have no missing files lines. A good thing to look for in the log is Files to Download = 0 - near the end of the log. This wont always be the case, but using your log as an example you might reduce 316 files down to a mere few. If possible, a 2nd run log with the same scripts selected is ideal.
Determine if the issue is Downloading Updates (DU) or Installing Updates (IU) - provide that log only This is new in AP 6x, one log can contain both downloading information & installation information The simple and easiest way to keep the log as readable as possible is to close AP after downloading the releases and avoid clicking Install Updates. Another way of putting it, if the problem involves downloading - try to download it again, when done and looking at the Download / Install screen once again close AutoPatcher and post the log. If the issue involves installation, at the DU/IU screen, select to load the releases, this will create a log with relevant info regarding installation issues, etc only.
Hope some of this is helpful.
Re: Autopatcher v6.1 beta
A few things.TheAPGuy wrote:bah... reading large logs like that reminds me to figure out some more things to cut from the log reports. Probably going to cut a lot of path information out.
...None of the PreAction details need to be written to the log, If there's an issue Sweeper can address it if run. I used to know the command but forget, it should be in the docs.
...Users need to post either a 2nd run DU or IU log - not both.
There was one more I thought might be worth considering but I don't remember ..., if it comes to me I'll mention it but these 2 along with your idea will help significantly.
Re: Autopatcher v6.1 beta
Maybe local short date should use regional settings from windows (in my case yyyy/mm/dd) not mm/dd/yyyy hardcoded in app?
To me "dd" in the middle looks so "wrong"
--------------------------------------------
Force language - cancel bug still in 6.1.27
Autopatcher v6.1.27 Has Started at 2015.05.10. 11:16:26
Starting Autopatcher From C:\Users\User\Desktop\Autopatcher_6
Detected OS: English (1033) Microsoft Windows 7 Ultimate x64 Service Pack 1
Current Locale: Latvian / Non-Unicode Default: English
***Downloading/Processing Release List***
List file HTTP location: http://www.autopatcher.net/releases.list
Download queue processed. Proceeding to next phase.
***Release list Processed: Waiting for User Input***
Searching For Existing Releases Installed...
Found: AutoPatcher Engine 5.7.56 Is Not Current.
Found: AutoPatcher for Windows 8.1 (x64)
Found: AutoPatcher for Windows 8.1 (x86)
Found: AutoPatcher for Windows 7 SP1 (x64)
Found: AutoPatcher for Windows 7 SP1 (x86)
Found: AutoPatcher Common Modules
Found: Microsoft Security ENU Addon Pack
Found: Microsoft Redistributables
Found: Extras Addon Pack
Found: Java JRE 8.45 (x64) (See Note after download)
Found: Java JRE 8.45 (x86) (See Note after download)
Found: DirectX 9.0c (v9.29.1974) Addon Pack
Found: AutoPatcher Office 2007 SP3
Found: Office Addon Pack (English)
Found: Adobe Air 17.0.0.144
Found: Adobe Reader XI (11.0.10)
Found: Adobe Acrobat Reader DC
Found: Admin Tools (Requires Users Presence To Install Items)
Search Complete
Error Detected: Type mismatch in frmMain.ForceLanguage At Line 100
To me "dd" in the middle looks so "wrong"
--------------------------------------------
Force language - cancel bug still in 6.1.27
Autopatcher v6.1.27 Has Started at 2015.05.10. 11:16:26
Starting Autopatcher From C:\Users\User\Desktop\Autopatcher_6
Detected OS: English (1033) Microsoft Windows 7 Ultimate x64 Service Pack 1
Current Locale: Latvian / Non-Unicode Default: English
***Downloading/Processing Release List***
List file HTTP location: http://www.autopatcher.net/releases.list
Download queue processed. Proceeding to next phase.
***Release list Processed: Waiting for User Input***
Searching For Existing Releases Installed...
Found: AutoPatcher Engine 5.7.56 Is Not Current.
Found: AutoPatcher for Windows 8.1 (x64)
Found: AutoPatcher for Windows 8.1 (x86)
Found: AutoPatcher for Windows 7 SP1 (x64)
Found: AutoPatcher for Windows 7 SP1 (x86)
Found: AutoPatcher Common Modules
Found: Microsoft Security ENU Addon Pack
Found: Microsoft Redistributables
Found: Extras Addon Pack
Found: Java JRE 8.45 (x64) (See Note after download)
Found: Java JRE 8.45 (x86) (See Note after download)
Found: DirectX 9.0c (v9.29.1974) Addon Pack
Found: AutoPatcher Office 2007 SP3
Found: Office Addon Pack (English)
Found: Adobe Air 17.0.0.144
Found: Adobe Reader XI (11.0.10)
Found: Adobe Acrobat Reader DC
Found: Admin Tools (Requires Users Presence To Install Items)
Search Complete
Error Detected: Type mismatch in frmMain.ForceLanguage At Line 100
-
- Posts: 181
- Joined: Sat Feb 22, 2014 7:33 pm
Re: Autopatcher v6.1 beta
Having spent 27+ years in the US Air Force my preferred option for the date is: dd/mm/yy with a 24 hour clock - no AM or PM.