You can view the page at http://forums.auran.com/trainz/content.php?49-TS12-SP1-Hotfix-1-now-available
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
That's slightly surprising - mine ran as normal and only took 5-10 minutes. Probably related to the database repair it does.
Shane
That may affect things, as JAConverter has failed to run on your version.
Shane
A note to those using IE10 to download this patch - Smartscreen Filter will cause you problems (N3V - may be worth looking into digitally signing these patches).
Shane
Yeah it looks like something nasty happened there. Was this the first time you attempted to patch to 57825? Or did you have a patch that stalled previously and this was a second attempt? I take it you didn't have any problems patching to 57720?I know, I know, first thing I usually do. Avast was running it in the sandbox.
eady to install from local patch file.
Current version: 57720.
Checking for available disk space for patching.
Unpacking patch file...
Patching from 57720 to 57825...
Failed patch command: "E:\TS12\bin\JAConverter.exe" patchapply "E:\TS12\Base.ja.pbk" "C:\Users\dads\AppData\Local\Temp\file3206023\data\Base-diff.ja" "E:\TS12\Base.ja"
Failed patch command: "E:\TS12\bin\JAConverter.exe" patchapply "E:\TS12\Data.ja.pbk" "C:\Users\dads\AppData\Local\Temp\file3206023\data\Data-diff.ja" "E:\TS12\Data.ja"
There are no more patches for this build.
Updating Trainz asset database... (this may take several minutes)
I think I can understand what's happened in fran1's case. Avast has a 'sandbox' feature, where it runs programs but isolates them from the rest of the system, and prevents them from running external processes. Another reason for people to pay attention to the 'turn off your antivirus software first' message.
Shane
What about the other bugs discussed in the 'TS12 SP1 bugs' thread? I hope to see them fixed too!
I think you might be right there... Obviously, we'd advise turning off/disabling Avast entirely during patching, but I'll see what we can do about getting a copy here to confirm whats going on. We most likely will not fix the issue (because the fix more simply "don't do that") but it might help in identifying these issues for helpdesk, etc.