infidel wrote:Thanks for the suggestions HT1, and discourse/treatise on all things 'batch'
.
Likewise my friend
, it's good to find some smart people who actually don't take offense when someone takes an interest in their baby. Who knows it may yield some interesting results if one tries to come up with a different way of achieving the same result. not everyone is a serious pro dev but people can still surprise you with what they come up on their own time.
i saw your batch, yes it is quite complexe, kudos on the work. i remember writing a big one back in my college days (but i did not inhale, lol)
it had an actual user interface with ansi escape codes back in the old dos days, for colors and borders and keyboard input by user for various options. At one point it was up over 20k and that was back in the days of windows 95/98. i had to reduce it but mostly it was huge due to the various interfaces it showed on screen according to user input.
it looked like the old dos Norton Utilities (which i used extensivelly to defrag my old rig, ah youth, no amount of defraging was ever going to make it faster lol), same colors and characters on screen as Norton. it called Speedisk and NDD with various command line switches and more tools, it was my main dos interface at one point, a personnal program library basically. it was a fun personnal project of mine to code it.
infidel wrote:The problem with windows shortpaths
yes, i digress... lol
Question: just so i'm clear on the issue, why exactly do you need short paths, don't the tools work with long paths if you put quotes around it ?
i'm sure anything programmed in the last 5 or 6 years has got to be able to handle long paths. Maybe there's another tool that does the same and handles long paths.
infidel wrote:, e.g. %~s is that it isn't guaranteed to result in a short path. It will only yield a short path if 8dot3 was enabled at the time the given file/folder was created. So if a user turns off 8dot3 at some point, %~s will give long paths for those files that were created during the 'off' period.
i just whiped up a small batch and checked my c: drive with fsutil:
Code: Select all
fsutil 8dot3name scan "C:\Program Files (x86)\Universal Media Server"
fsutil 8dot3name query c:
pause
Ran it as admin, and this is the result window if you need to see it.
- fsutilanalyse.PNG (25.77 KiB) Viewed 21578 times
Translating for you, basically the status i get for volume c: is 0 (8.3 creation is activated) and registry is 2 (default value, per volume). Are those the values you seek ?
Fsutil says after testing "According to the 2 values above, 8.3 creation will work on this volume".
i understand you need to know if the ums folder has an 8.3 path but the creation of 8.3 isn't turned off on my system, never has, yet i still get the yellow warning from your batch file when i install jumpy.
i didn't change any registry value pertaining to this setting, so yes like you said "if the user turns it off" i agree, but i didn't turn it off.
So i'm puzzled why i still see the 8.3 warning during install... Must be a lost in translation thing maybe, i seem to recall you mentioning it only works with english systems.
On that note, If you feel like expanding the setup's understanding of fsutil in other languages, i attached a text file containing the same results from the command line, notice the vowels with accents don't look right in the text file compared with the screenshot above. Taking this into account might help in detection of the fsutil values in french and maybe spanish systems if you use redirection operators in your batch file. it is in simple dos text, not unicode or utf-8.
Maybe some further testing needs to be done on win10 systems, it is still (relativelly) a new beast and M$ can change things at any point. But by all accounts fsutil gives a greenlight for 8.3 paths by default.
But if i may,i'd be willing to try a beta setup if you whip one up for this problem.
Cheers,