I'd like to delete already installed patches from /modules/ to free some disk space
how can it be done so that next time apup.exe doesn't download them again?
thanks.
deleting old patches
Started by orange, Dec 27 2012 09:47 AM
4 replies to this topic
#1
Posted 27 December 2012 - 09:47 AM
#2
Posted 27 December 2012 - 10:17 AM
Instead of deleting the already installed patches from your apup/ap an easy solution is to copy current apup to a external source such as flash drive, external hdd or even burn the contents to optical media.
If you delete them from your apup, the next time you update with apup it will detect that files are missing and redownload them. There is nothing worse than to have re-download a release...take it from me...it's a pain
I strongly advise that if you don't want to keep apup/ap on your hard drive then purchase an extra flash drive and keep apup on it.
Hope that helps
If you delete them from your apup, the next time you update with apup it will detect that files are missing and redownload them. There is nothing worse than to have re-download a release...take it from me...it's a pain
I strongly advise that if you don't want to keep apup/ap on your hard drive then purchase an extra flash drive and keep apup on it.
Hope that helps
#3
Posted 27 December 2012 - 10:30 AM
thanks.
I'm using autopatcher for several windows guests in virtualbox. some of those are more 'secure' than others. therefore, I want those to update autopatcher, while others update windows only. making iso is time consuming. unfortunately, it seems autopatcher cant work in SMB mapped network drive.
I'm using autopatcher for several windows guests in virtualbox. some of those are more 'secure' than others. therefore, I want those to update autopatcher, while others update windows only. making iso is time consuming. unfortunately, it seems autopatcher cant work in SMB mapped network drive.
#4
Posted 28 December 2012 - 01:30 AM
Well.. IF you map a network location to a drive letter... it "should" work. Nothing can be guaranteed though. Some people have had no problems... Me for example. However... IF you want to use autopatcher over network.... please please please delete the rti files before running autopatcher. Same thing before burning to iso. You have already verified contents of files no need to verify them on CD/DVD or read Only Network Access. It takes a long time.
Have you tried SMB mapping and it failed? What kind of errors were reported, I am interested. Since it works for me, I can't detect where it fails so I can fix/change it.
Have you tried SMB mapping and it failed? What kind of errors were reported, I am interested. Since it works for me, I can't detect where it fails so I can fix/change it.
#5
Posted 11 January 2013 - 08:51 AM
thanks for replies.
it seems the problem is in Kerio firewall. it can't create md5 of CURL.exe when doing update on mapped drive (each time its different).
but I think I found another way, using virtualbox immutable option.
it seems the problem is in Kerio firewall. it can't create md5 of CURL.exe when doing update on mapped drive (each time its different).
but I think I found another way, using virtualbox immutable option.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











