|
|
Post by oldpop2000 on Jul 22, 2016 15:42:43 GMT -6
 I've gotten SAI to V1.63 with the Campaign to V1.55. But I get an error that I can't access the update file. When I finally did, my version still show 1.63. So, what is the old guy doing wrong? I did not completely follow the order you specified, but does it really matter? Can I leave the SAI game at 1.63? Yes I have permissions and yes I have run it as an administrator and yes, I have moved the file to the NWS directory.  |
|
|
|
Post by randomizer on Jul 22, 2016 16:48:02 GMT -6
I just downloaded the 1.64 executable and tested on a 1.63 version of SAI without an issue. That said you may be doing nothing wrong but I would ask you to check something before moving forward.
Inside your SAI root folder there should be a file named Patchwise.log that opens using M$ Notepad or similar text editor. After the 1.64 upgrade it should read:
If any of those files are doctored or missing, this might prevent the 1.64 patch from completing the upgrade. If this is the case then restoring those files and then executing the update again may work.
Your updated SAI root directory should have a PatchWise.bak folder that contains the files from the previous version so copying the files listed above from that folder back to the Data and main folders should roll back your installation to v1.63. However I would recommend trying to solve the 1.64 installation problem before rolling back the game but of course it's your call. Proceeding this way is probably easier than uninstalling and reinstalling the game from scratch, seldom an enjoyable evolution. Let us know how you make out and good luck.
|
|
|
|
Post by oldpop2000 on Jul 22, 2016 17:00:01 GMT -6
I just downloaded the 1.64 executable and tested on a 1.63 version of SAI without an issue. That said you may be doing nothing wrong but I would ask you to check something before moving forward. Inside your SAI root folder there should be a file named Patchwise.log that opens using M$ Notepad or similar text editor. After the 1.64 upgrade it should read: If any of those files are doctored or missing, this might prevent the 1.64 patch from completing the upgrade. If this is the case then restoring those files and then executing the update again may work. Your updated SAI root directory should have a PatchWise.bak folder that contains the files from the previous version so copying the files listed above from that folder back to the Data and main folders should roll back your installation to v1.63. However I would recommend trying to solve the 1.64 installation problem before rolling back the game but of course it's your call. Proceeding this way is probably easier than uninstalling and reinstalling the game from scratch, seldom an enjoyable evolution. Let us know how you make out and good luck. I did look at it and the last entry was there, but not the other. I replaced the files with the .BAk, no joy. SOOOOO, I will uninstall, and reinstall tomorrow. I am still granddaughtering today. Tomorrow, is another day. Thanks, I will keep you posted. |
|
|
|
Post by oldpop2000 on Jul 22, 2016 17:29:59 GMT -6
The problem is solved, SAI is now at 1.64 and the Campaign at 1.55. When AVAST started to scan the file for viruses, I clicked on "View Details" and saw the "Run anyway(not recommended)". I clicked on that, the update ran and that fixed the problem. I should know better. You should disable your antivirus after downloading the updates to shut down that scanning but this was the first time it has caused me some grief. Hope this information will be beneficial to others. You might want to add that little bit of information on your installation screens because antivirus and malware software are really getting sophisticated and can really cause some grief.
Thanks
|
|
|
|
Post by oldpop2000 on Jul 24, 2016 8:24:09 GMT -6
For those of you who read this thread and don't understand what happened, I will explain. Anti-virus programs when they are scanning an individual file for possible virus or malware, isolate the file. It's called "quarantine". There are various ways of doing it but one way is to move the file to special folder that only the anti-virus can access then change the permissions to only enable the AV to access the file during scanning. If you try to access the file, the operating system might tell you that the file is not accessible due to permission changes or is missing. You have to wait until the scan if finished or tell the AV to stop and give you access. In this case, AVAST gave me a popup with "close" on it. That did not mean to stop, it just meant close the popup. When I finally realized it, I clicked on details. That gave me more information and allowed my to just stop the scan and run the file. This is the best way to download and run the application. It's the safest, to let the AV download, scan and confirm there are no virus or malware present. If you now try to run it, some AV's will scan it again, a good safe policy, and then you will have to tell it to stop. That is basically the simplest explanation for you, to understand how all this works. My problem was that it had never had a problem before and apparently I was not paying attention. I should know better after forty years of working on computers. My bad or what. It took about 20 minutes for me to pull my head out, and fix the issue. Ich!!
|
|
