Damon Caskey: Don't use names over 8 characters. You are asking for problems.
To be perfectly honest, I don't know exactly where you can and can't use more than 8 characters. It's just good practice not to do it.
Part of the reason I don't know is that I just never do it. Leaves one less issue to worry about when debugging.
BaritonoMarchetto77: I am around since borgeneration open, and I can say that the fact that using more than 8 characters could be hazardous was emphasized in different topics.
It is also probable that it applies only to the line commands (classic bor commands) and not to scripts...
I agree that it's probably better to stick to 8 characters, but all of the mods I've posted here use more and I've never had a problem with it.
It may lead to more problems later, but I'm willing to take that risk. With the way the engine is growing, it would seem a bit backwards if a new version introduced more DOS-like limitations.
BaritonoMarchetto77: Anyhow, I am not inclined to risk, so if there's a way to individuate non-8.3 pattern file names please report
Did you try one of the 3 methods I posted earlier?
1. Add " | more" to the end of the command line
ex "program.exe | more"
2. Add " > log.txt" to the end of the command line
ex "program.exe > log.txt"
3. Type "dir /s /b > dir.txt"
Open dir.txt in Notepad2 and hit Alt Z (Strip First Character) 8 times
#3 is a bit of a roundabout method, but the first two are simple and should work just fine. Vista might not support the "pipe" symbol ( | ) but I'd be very surprised if "redirect output" ( > ) didn't work.
Since you're using packer.exe instead of borpak.exe you can type:
packer.exe mymod.pak data | more
or
packer.exe mymod.pak data > log.txt
The first one will pause the screen while it displays the output and the second one won't display the output on the screen at all but will instead create a text file called log.txt with the output in it.
