Short Filename problem Netware to Windows Server

[bernie321]

Hi

We are copying huge quantity of word documents to a Windows 2003 server from our Netware 4 Server.

The files were created by a semi-bespoke software package that stores the dos short filename in its database for compatibility.

We need to be able to access the files from the windows server through the semi-bespoke software, but the software throws an error because it is looking for the file using netware short filename.

EG:
The filename it is looking for is: 1603LETT.DOC
But the new filename on the windows server is: 1603LE~1.DOC

Is there any way of copying this data to the windows server keeping the short filename. Or alternatively is there a way of comparing the files whilst and returning the filename so that i can develop a script to change the database.

Many thanks B

 

[TheLad]

Don't think so as the Windows file system stores the short filenames different to the NetWare file system. The NetWare system does not bother with the ~1 etc... whereas the Windows file system does. Just differencies in the two file systems which I guess you will have to overcome.

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[MarkhP]

Bernie,
Unless the files on the Netware server actually have more that 8.3 character filenames, you shouldn't have a problem copying them to your windows machine.

Have you got long filenames enabled on the Netware server?. Assuming that you are running NW411/SP9, you (admin) can go to the console and type "LOAD LONG.NAM <enter>" then "ADD NAME SPACE LONG TO VOLUME {volumename} <enter>".

 

[TheLad]

That won't make any difference since Bernie is copying FROM the NetWare box to the Windows box so making any namespace change on the NetWare box will not help in this situation.

As I have already mentioned, the NetWare file system stores the files differently to a Windows server hence the different short filename.

-----------------------------------------------------
&quot;It's true, its damn true!&quot;
-----------------------------------------------------

 

[MarkhP]

I am only suggesting that having Long filenames enabled could give him a more compatible match between filenames during the transfer. The filenames using LONG.NAM (latest) are presented in a similar way that Windows does (ie using the tilde symbol to abbreviate names). Novell used to hold filenames longer than 8 characters and only display the first 8 in a directory listing under dos for example. I have no problem copying from Netware servers to Windows servers and we have long filenames enabled. It is only a suggestion.

 

[TheLad]

NetWare 4.x handles files differently to NetWare 5.x or 6.x and all of them handle files differently to Windows servers.

The problem highlighted is not a problem copying the files but that the file gets "renamed" on the Windows server to the Windows standard which includes ~1 etc.. at the end of the filename. Having long filenames on the NetWare 4.x server is irrelevant as the files on the NetWare server will still keep their original names which do not include the ~1 etc.. in the filename.

The TID below is old but explains why this occurs and a possible fix (which will not rename existing files so probably will not be of use in this instance):

http://support.novell.com/cgi-bin/search/searchtid.cgi?/2922642.htm

-----------------------------------------------------
&quot;It's true, its damn true!&quot;
-----------------------------------------------------

 

[marvhuffaker]

One of the many limitations of a Winblows system. My best recommendation is not use Windows. Keep your Netware system and never consider changing.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com