DGindex CLI doesn't like "&"...

[Mug Funky]

hey yo.

noticed a week or so ago that DGindex's CLI doesn't like certain input paths...

it seems to not input files with an ampersand in them, and (i'm not sure on this one) doesn't appear to like paths over a certain length in characters (this may be the ampersand thing again though... not sure).

this is not at all a big deal... i'm happy using it as it is, it just means a little renaming every now and then.

i like to use shell extensions and batch files to get stuff done quicker - like right-click an m2v and go "make d2v"... :)

[Guest]

it seems to not input files with an ampersand in them No, it handles them fine. The DOS shell is intercepting the & because it is a special character.

and it doesn't appear to like paths over a certain length in characters I was unsuccessful in trying to implement infinite length support. :)

Seriously though, the limit was 1024 characters. I'm increasing it to 4096, but again, you may be limited by what the DOS shell can support.

[Mug Funky]

aaah. that makes sense...

hehe. i'd love to see a path that's 4096 chars long (haven't seen much over 200)

the strange thing is, that using the same batch commands to create an avs file there's no problem - the avs comes out with the correct text in it. although no programs are being run when i auto-generate an avs file - it's all just "ECHO blah >> %1blah.avs" style commands.

tried changing "%1" to "%~d1%~p1%~n1.m2v" after -IF, but that seems to crash DGindex (this is with a short path). when i get rid of the "&" it works.

crash message is just the standard "DGIndex.exe has encountered a problem and needs to close. We are sorry for the inconvenience." with the "don't send" box.

it probably is windows that's to blame - i trust your software more than i trust MS's

[Guest]

If you can give me a batch file that crashes DGIndex, I will fix it.