Separate/Break Up My English Collection of...
Simon00
25 Dec 2008
It was not smart of me to d/l everything from a single apup directory. There appears to be conflicts as newer versions over write older and the deletion/re-downloads happens over and over and over again.
Can I rebuild/separate my update collection without re-download everything?
If it's not possible, can someone POST a regular MD5SUM file for each of the platforms, separately, so that I can break up my collection manually? My Internet connection isn't so fast....
I'm also curious as to why not use a program such as ClrMamePro (using subdirectory mode & force packing unzip)? And create a simple dat (xml or listinfo) and it'll tell you what your missing and automatically delete/backup/rename files you have and rebuild to your hearts content along w/ the entire file directory structure. Missing files can be found from a # of sources. Rom collectors have been using it for about a decade now.... Dat files would be easy to maintain AND be less than a hundred kilobytes, depending on the # of hashes used. The Dir2Dat program is very well written. And it's astronomically impossible to simultaneous fool all three hashes+file size. Can choose from any or all of the three most popular, sha1, md5, crc32...
Thanks...
Edited by Simon00, 25 December 2008 - 03:32 AM.
Can I rebuild/separate my update collection without re-download everything?
If it's not possible, can someone POST a regular MD5SUM file for each of the platforms, separately, so that I can break up my collection manually? My Internet connection isn't so fast....
I'm also curious as to why not use a program such as ClrMamePro (using subdirectory mode & force packing unzip)? And create a simple dat (xml or listinfo) and it'll tell you what your missing and automatically delete/backup/rename files you have and rebuild to your hearts content along w/ the entire file directory structure. Missing files can be found from a # of sources. Rom collectors have been using it for about a decade now.... Dat files would be easy to maintain AND be less than a hundred kilobytes, depending on the # of hashes used. The Dir2Dat program is very well written. And it's astronomically impossible to simultaneous fool all three hashes+file size. Can choose from any or all of the three most popular, sha1, md5, crc32...
Thanks...
Edited by Simon00, 25 December 2008 - 03:32 AM.
_def_x_
25 Dec 2008
Hi Simon and Merry Christmas Eve...
I'll offer my opinion before I take off for a few days.
I've been through this myself a few times and have come to the conclusion, if you use AutoPatcher
on multiple OSs - it is best to separate the OS releases. There were issues with XP SP2 and XP SP3
sharing the same folder and we are seeing similar problems again - this is due to like file names but
with different hashs and the result becomes an endless cycle of download-delete-re download, the
"FIX" is to put the OS release in its own folder.
I have decided as well to have "one" folder that includes the "Addons", "Java", "Dotnet" and "DirectX"
that way I can simply copy to my thumb drive the update release I need depending on the situation -
without having 3 Addon Packs, 3 Java, and 3 DirectX - one for each AutoPatcher OS release.
You will want to select "AutoPatcher Updater" and "AutoPatcher Engine" with each release to have it
be functional, as well keep "apup.exe" and "autopatcher.exe" up-to-date.
You can "rebuild" from looking at the scripts, paying close attention to the details of where each file
belongs (everything is in the script - file name, size, hash, where it came from and where it needs to
go). Run "apup.exe", select the items you want, let apup retrieve the scripts, and before you hit the
"Finish" tab look for the scripts in the "temp_bin" folder (in the AutoPatcher/APUP folder) and "copy"
the files out - you can open them in notepad. Part of the clean-up process is to delete temp_bin and
its contents.
When you think you got it, I would "verify" your work by running "apup.exe /log", checking only the items
you put in each folder - (AutoPatcher Updater-AutoPatcher Engine-XP SP3 x86), let apup.exe scan the
folder. If you see "Finish" without any errors this is good. If you should get an error message, check the
log file.
This should get you started.
Mike
I'll offer my opinion before I take off for a few days.
I've been through this myself a few times and have come to the conclusion, if you use AutoPatcher
on multiple OSs - it is best to separate the OS releases. There were issues with XP SP2 and XP SP3
sharing the same folder and we are seeing similar problems again - this is due to like file names but
with different hashs and the result becomes an endless cycle of download-delete-re download, the
"FIX" is to put the OS release in its own folder.
I have decided as well to have "one" folder that includes the "Addons", "Java", "Dotnet" and "DirectX"
that way I can simply copy to my thumb drive the update release I need depending on the situation -
without having 3 Addon Packs, 3 Java, and 3 DirectX - one for each AutoPatcher OS release.
You will want to select "AutoPatcher Updater" and "AutoPatcher Engine" with each release to have it
be functional, as well keep "apup.exe" and "autopatcher.exe" up-to-date.
You can "rebuild" from looking at the scripts, paying close attention to the details of where each file
belongs (everything is in the script - file name, size, hash, where it came from and where it needs to
go). Run "apup.exe", select the items you want, let apup retrieve the scripts, and before you hit the
"Finish" tab look for the scripts in the "temp_bin" folder (in the AutoPatcher/APUP folder) and "copy"
the files out - you can open them in notepad. Part of the clean-up process is to delete temp_bin and
its contents.
When you think you got it, I would "verify" your work by running "apup.exe /log", checking only the items
you put in each folder - (AutoPatcher Updater-AutoPatcher Engine-XP SP3 x86), let apup.exe scan the
folder. If you see "Finish" without any errors this is good. If you should get an error message, check the
log file.
This should get you started.
Mike
Simon00
25 Dec 2008
Hi Mike,
It would have been nice if we were warned by the updater about this issue beforehand.... I'll try your suggestion next week and see how it goes.... Many thanks!
Merry Christmas you also... and a safe and HAPPY NEW YEAR!!!..
-Simon
It would have been nice if we were warned by the updater about this issue beforehand.... I'll try your suggestion next week and see how it goes.... Many thanks!
Merry Christmas you also... and a safe and HAPPY NEW YEAR!!!..
-Simon
