Not only does the script not download anything - so the 'chrome' directory doesn't get replaced - it then leads to a 'loop' situation where the browser keeps asking you to update, every time the browser is launched. Either that, or the 'current' release number isn't correctly forwarded to the above-mentioned webpage. On occasion, there is a problem at Google's end where the current stable release is not actually in the repo. Normally, it's reliable, and works without issue. This 'tweak' was courtesy of Forum member baraka. ![]() This webpage gives the current stable release number, and is used to then trigger the 'Updater' script if the version given doesn't match the 'Last Version' file in Chrome's profile. ![]() ![]() The 'LAUNCH' script is written to check this webpage when it's run. The updater script I wrote for the portable build of Google Chrome periodically runs into exactly the same issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |