Suggestions to increast productivity
Posted: Tue Jan 19, 2016 4:33 am
Hi, just suggesting the addition of a cmd line switch to allow Autopatcher to skip hash/md5 checking and go directly to tree generation.
I know this sounds dangerous, but here's my current scenario and how AutoPatcher is holding me back.
I'm currently trying my best to update an MSI "Leader" laptop, running Vista SP1 x86. However the following is/are occuring:
* Some updates need to be installed, then the system rebooted, then the next lot of updates need to be installed (nearly 200 updates in total)
* My AutoPatcher folder contains updates for all my machines ranging from XP, to Vista, to 7. A mixture of x86 and x64 architecture
* After every reboot I have to reload AutoPatcher
* Every time I reload Autopatcher it has to process hash checks and generate the tree
First problem:- Auto patcher asks for me to agree to two separate licenses- Workaround is to use /NOLICENSE cmd line switch, problem solved
Second problem:- Due to the size of my Autopatcher folder and the sheer number of updates contained within, between "Loading Modules" (which loads ALL modules inc incompatible modules), "Verifying Release Integrity" (again, verifies ALL modules) and "Generating Tree" I can lose anywhere up to 30 minutes of loading time. (keep in mind this is on a fast machine, loading from HDD not CD or Flash drive, high spec Intel CPU, gaming motherboard, gaming graphics, high spec WD HDD). Also, yes I could use a separate AutoPatcher folder for each separate OS, I've tried this, but it still leads me to the next problem...
Third Problem:- I cannot always simply copy (or xcopy, or dd) my Autopatcher folder from my main computer to other computers (no its not always to the same computer, mostly when I've just done a fresh install of the OS). Roughly half the time I attempt this, I have to redownload the modules again, either they won't install or they fail hash checking or something else. Sometimes the modules successfully pass hash checking, are blue in the download list, yet still download over and over again? In scenarios such as this, it's often quicker to have windows auto-update the conventional way.
First Suggestion:- I propose a new CMD line switch to bypass hash checking to speed the process up. If I'm using the same autopatcher folder on the same computer and rebooting several times, I think the risk that a file might not pass hash checking is VERY minor. Especially on a fresh, clean install.
Second Suggestion:- I would also propose a semi-permanent history. If Autopatcher was to keep a small history / log file in its folder, it could then remember that module X has been hash checked, passed and is ready for installation.
Third Suggestion:- A completely verbose installation routine, as opposed to the default "quiet" install procedure. If I can at least see what the updates are doing when they try to install, I would have a better chance of figuring out why they all freeze at 98%.
Combine these suggestions with another suggestion I read earlier (to not load incompatible modules) Autopatcher would be outstanding.
To further illustrate my frustration, I have spent the better part of three days trying to get this MSI "Leader" laptop back up to date. Between Autopatchers unavoidable loading times, certain updates freezing at 98% (always 98%) and having to reboot between certain updates, only to have to re-attempt certain updates because they have prerequisite updates that must be installed first, I've had to reboot approximately 20 times, recover from hash-checked updates that caused reboot loops (sometimes without BSOD) and other random Autopatcher crashes. Not to mention having to completely erase corrupted SoftwareDistribution and CatRoot folders (which I apparently have to do again right now, after a boot-loop, followed by system restore, and yes, I have chkdsk /F /X /R several times AND I've run memtest multiple times).
BUT, I do have to offer my greatest thanks and appreciation for Autopatcher, it has saved me a lot of time and bandwith.
I know this sounds dangerous, but here's my current scenario and how AutoPatcher is holding me back.
I'm currently trying my best to update an MSI "Leader" laptop, running Vista SP1 x86. However the following is/are occuring:
* Some updates need to be installed, then the system rebooted, then the next lot of updates need to be installed (nearly 200 updates in total)
* My AutoPatcher folder contains updates for all my machines ranging from XP, to Vista, to 7. A mixture of x86 and x64 architecture
* After every reboot I have to reload AutoPatcher
* Every time I reload Autopatcher it has to process hash checks and generate the tree
First problem:- Auto patcher asks for me to agree to two separate licenses- Workaround is to use /NOLICENSE cmd line switch, problem solved
Second problem:- Due to the size of my Autopatcher folder and the sheer number of updates contained within, between "Loading Modules" (which loads ALL modules inc incompatible modules), "Verifying Release Integrity" (again, verifies ALL modules) and "Generating Tree" I can lose anywhere up to 30 minutes of loading time. (keep in mind this is on a fast machine, loading from HDD not CD or Flash drive, high spec Intel CPU, gaming motherboard, gaming graphics, high spec WD HDD). Also, yes I could use a separate AutoPatcher folder for each separate OS, I've tried this, but it still leads me to the next problem...
Third Problem:- I cannot always simply copy (or xcopy, or dd) my Autopatcher folder from my main computer to other computers (no its not always to the same computer, mostly when I've just done a fresh install of the OS). Roughly half the time I attempt this, I have to redownload the modules again, either they won't install or they fail hash checking or something else. Sometimes the modules successfully pass hash checking, are blue in the download list, yet still download over and over again? In scenarios such as this, it's often quicker to have windows auto-update the conventional way.
First Suggestion:- I propose a new CMD line switch to bypass hash checking to speed the process up. If I'm using the same autopatcher folder on the same computer and rebooting several times, I think the risk that a file might not pass hash checking is VERY minor. Especially on a fresh, clean install.
Second Suggestion:- I would also propose a semi-permanent history. If Autopatcher was to keep a small history / log file in its folder, it could then remember that module X has been hash checked, passed and is ready for installation.
Third Suggestion:- A completely verbose installation routine, as opposed to the default "quiet" install procedure. If I can at least see what the updates are doing when they try to install, I would have a better chance of figuring out why they all freeze at 98%.
Combine these suggestions with another suggestion I read earlier (to not load incompatible modules) Autopatcher would be outstanding.
To further illustrate my frustration, I have spent the better part of three days trying to get this MSI "Leader" laptop back up to date. Between Autopatchers unavoidable loading times, certain updates freezing at 98% (always 98%) and having to reboot between certain updates, only to have to re-attempt certain updates because they have prerequisite updates that must be installed first, I've had to reboot approximately 20 times, recover from hash-checked updates that caused reboot loops (sometimes without BSOD) and other random Autopatcher crashes. Not to mention having to completely erase corrupted SoftwareDistribution and CatRoot folders (which I apparently have to do again right now, after a boot-loop, followed by system restore, and yes, I have chkdsk /F /X /R several times AND I've run memtest multiple times).
BUT, I do have to offer my greatest thanks and appreciation for Autopatcher, it has saved me a lot of time and bandwith.