No, because as above the update feature will no longer work (when bizarre downloaded filename and folder name from Github). However I can try with a backup named properly UUPDL.v0.05.28 - will do so now.
@s1ave77 you can use tags on GitLab to mark releases, add changelogs and upload release archives. Git repositories use LF line endings that may cause problems with cmd scripts, so I would recommend to add some kind of converter from LF line endings to CR+LF for cmd scipts.
Downloaded filename uupdl-master-758f8314866e3f3e752a39efa7166ec152582208.zip unpacks to folder named uupdl-master-758f8314866e3f3e752a39efa7166ec152582208 - Run v0.06.01 - Run manual update (as I have been doing successfully all day/night) unpack.... replace... update.... Code: 'D:\Archives\Unpacks\uupdl-master-758f8314866e3f3e752a39efa7166ec152582208\uup.downloader.cmd' is not recognized as an internal or external command, operable program or batch file. Still as I nave been saying for last few posts, Github filename/folder name has completely shot things for me! To re-assure me I've not gone bonkers can anyone confirm plz?
In my previous reply the script says "mismatch found" i manually copied over the files to the folder with the correct foldername: "uupdl.v0.06.01" instead of the one with "master..." in it and still the mismatch found message.
I don't know, but the update process is shakey. Had to go to github to get it. Update through 05.8 said nothing available. Then I downloaded, extracted, and pasted. It is my personal opinion that an update should just download, and run with no user intervention other than where the program is installed. Usually it might be C:\Program Files (x86)\UUPDownloader, but if I have it elsewhere I just change the path.
I can only repeat and have proven it by using a backup (not the Github download) that the bizarre Github filename/unpacked folder name has completely broken it (the manual update feature) for me.
The files downloaded from GitLab have LF line endings which obviously have another checksum than local files on Windows which have CR+LF line endings.
Dumped the lot. Started afresh with Github download, same situation exists for me now. Manual update will not work now, been working fine today/tonight. Replace.... Nil files copied to D:\Archives\Unpacks\uupdl-master-41c27e27bb3432d82985ea7670c001647e6beb6e Only since the weird filename/unpacked folder name were introduced with Github download, prior to that always been fine.
@Enthousiast - unpacked folder name uupdl-master-41c27e27bb3432d82985ea7670c001647e6beb6e and you ran manual update and chose to download anyway, then replace? Let me know of your results with that procedure plz.
No clue what's gone wrong here, been meticulous in checking, dumped the lot and just will not manually update for me since Github was introduced. Ah well, catch up tomorrow. Why/what is folder.txt at root of my D: drive and left there? Code: 17/09/2017 22:35 <DIR> uupdl-master-41c27e27bb3432d82985ea7670c001647e6beb6e Directory of d:\downloads\uupdl.v0.06.01\uupdl-master-41c27e27bb3432d82985ea7670c001647e6beb6e