Method '~' of object '~' f...
bizzybody
19 Apr 2012
Trying to just download the Autopatcher components. Unzipped the file ran apup and checked just the top three boxes.
I get these error messages.
Method '~' of object '~' failed in prjUpdater.mdlGeneral.createPath at line 114
Path not found in prjUpdater.mdlGeneral.createPath at line 114
Here's the log, there's another error message that pops up many times when logging is used.
apuplog.zip (1.86K)
downloads: 2
Does anyone have a full direct download of everything required by Autopatcher itself? I deleted my Autopatcher Addons folder to download it all fresh to ensure there wasn't anything old in it, but now apup can't download Autopatcher.
Edit: Or how about fixing the error reporting of apup to say "Hey, the drive you're trying to download to is full!". After deleting some other stuff off the USB stick it downloaded. Simply running out of room shouldn't cause error messages about incorrect MD5 hashes, it should pop up Windows' own not enough space error message.
Edited by bizzybody, 19 April 2012 - 07:11 PM.
I get these error messages.
Method '~' of object '~' failed in prjUpdater.mdlGeneral.createPath at line 114
Path not found in prjUpdater.mdlGeneral.createPath at line 114
Here's the log, there's another error message that pops up many times when logging is used.
apuplog.zip (1.86K)
downloads: 2
Does anyone have a full direct download of everything required by Autopatcher itself? I deleted my Autopatcher Addons folder to download it all fresh to ensure there wasn't anything old in it, but now apup can't download Autopatcher.
Edit: Or how about fixing the error reporting of apup to say "Hey, the drive you're trying to download to is full!". After deleting some other stuff off the USB stick it downloaded. Simply running out of room shouldn't cause error messages about incorrect MD5 hashes, it should pop up Windows' own not enough space error message.
Edited by bizzybody, 19 April 2012 - 07:11 PM.
_def_x_
19 Apr 2012
Download to a local connected drive (C:, E:, etc) first, when the packages are downloaded and Official then move (or copy) EVERYTHING from (C:\apup) to external media, USB stick, or make your CD.
Also, I would suggest copying the package to the local drive (C:\) of any computer to be updated, don't run AutoPatcher from connected drives or the CD - very slow and can fail in some instances.
Moral - Create & Update from a local drive when creating or updating!
The next incarnation of the software should work much better with non local drives, until then this seems to works best.
Just MO
Also, I would suggest copying the package to the local drive (C:\) of any computer to be updated, don't run AutoPatcher from connected drives or the CD - very slow and can fail in some instances.
Moral - Create & Update from a local drive when creating or updating!
The next incarnation of the software should work much better with non local drives, until then this seems to works best.
Just MO
ViroMan
19 Apr 2012
The version of apup you are using is very old and lacks allot of error reporting functions. I won't suggest the newer apup2 because click-clicks new scripts are not compatible with it.(mostly not his fault) The newer application I am making will be much more verbose about issues and how to correct them. Also yes... don't run APUP from USB drives. AP is OK to run from USB drives IF you delete the RTI files so that it won't take forever to md5 the files although this makes AP think the set is not official. It is still recommended to copy to the local drive first though... much faster.
Im thinking I should write up a batch file for people to use when they have AP on a remote location. Moves the RTI files then runs AP then puts the RTI files back.
Edited by ViroMan, 19 April 2012 - 09:22 PM.
Im thinking I should write up a batch file for people to use when they have AP on a remote location. Moves the RTI files then runs AP then puts the RTI files back.
Edited by ViroMan, 19 April 2012 - 09:22 PM.
