Moving dos scripts to Windows 2003 server

I have just been given the task to move a batch process to a windows 2003 server from a windows 98 box. Seems simple but under 2003. All the path names and file names are being cut off.

for example:

CALL c:\BAT\FILSET%4

the %4 here is 99E when the call is made it translates this to

CALL c:\BAT\FILSET99

if I use echo c:\BAT\FILSET%4 I get c:\BAT\FILSET99E.

Any reason why this works on 98 box and not the 2003 box?

 

I am writing this from Win98SE. I don't have 2003server, but I have heard of problems like yours. The file names are getting cut off after 8 characters. The extensions get cut off after 3. This is because of DOS using the 8.3 file format. Windows hacks longer file names in, but support for those names seems wavering when doing DOS stuff. The reason it works on 98, I presume, is that 98 is based on DOS, while 2003 is based on NT instead, I believe. I usually just use filenames of 8 characters or less to circumvent the problems, but there are some tools available--I have WinOne, an alternative DOS environment for Windows, but I haven't tried long filenames in it much. Alternatively, I translate batch files into either JScript or VBScript for Windows Scripting Host, which is the Windows successor to batch files.

 

Powershell
http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx