There is another way to obtain these files.
This is done using the updater itself. Upon updating, the updater downloads each file individually, except so much of a set has changed that it downloads the entire zip. We all know that the zips stay in the PS folder to be unzipped manually.
However, the remaining files also get downloaded before the updater hangs. They are downloaded to a temporary file in the PS folder, which is called \"download.tmp\". This file is the most recently downloaded file, i.e., just what we\'re looking for. The only things the DOS-window does is:
- copy the current file to the folder \"updatertemp\" in the PS folder
- rename the \"download.tmp\" file to whatever the filename needs to be.
Now let\'s finish the theory and dive right in!
Start the updater in --auto mode (this is for convenience, the normal mode will also work, but you need to restart the updater for each file)
It\'ll update happily until it encounters one of the dreaded hangs. Now it asks what to do.
Don\'t respond just yet! Instead, take note of the file it is currently updating (the last filename before the error message).
Now have a file manager handy (explorer will do) and copy the file \"download.tmp\" to a temporary folder. Now rename the copy to what you took note of (or look at the updater\'s window).
It is important that you copy this file anew each time, and immediately once the error message is displayed, because otherwise you\'ll not get the correct file! Verify that the filesize that the updater shows is the same as the actual size of \"download.tmp\" (this may require to refresh the view in the file manager), at least approximately (due to the byte / Kbyte conversion factor of 1024 and rounding of the filemanager).
Afterwards, hit either \"Error\" or \"Abort\". The neat thing is that the updater will continue in --auto mode.
It\'ll likely encounter this issue on some other files as well, just repeat the process above and you\'ll get them all.
Once the updater is finished, simply copy all the files from the temporary folder into the PS folder, and you\'re done.
Note that it might happen that a file needs to be placed somewhere else: copy them one by one and see whether it asks \"overwrite?\": if it does ask, say \"Yes\", but if it doesn\'t ask, look where this file actually needs to be placed (use the search function of the file manager you\'re using). Also delete the file you just placed in the PS folder so that it won\'t interfere with later updates! However, this should be very rare.
Edit: Maybe you devs could make the updater do this automatically if a file couldn\'t be replaced, so that we just need to move them? Like creating a \"failedupdate\" folder and placing all files there, with the correct directory structure for easy movement? Just a thought.
