Command line utilities (BRC and NConvert, for example) read source files without leading zeros in the filename in non-numeric (alphanumeric or ASCII) sort order, 1 - 10 - 11 - 2 for example. As a result, when a multi-page output file is produced some pages are in the wrong order.
I don't see any way to simply pad existing file numbers so that they are read in the correct numeric sequence? So that files with an arbitrary alphanumeric prefix and number such as abcd1 are renamed abcd001, etc.
Padding with leading zeros is a basic function in any Windows renaming utility, but the /AUTONUMBER parameter reads the source files, in non-numeric order, and renumbers them adding padding if specified, so the order will still be incorrect... If the file numbers were only padded, the order in which files were read wouldn't matter.
So is there a way of just adding padding? Or a simple workaround that could be included in a batch file?