Moving long filenames from Windows2000 machine -is there a scan?

[clennox]

Hello:
Dealing with two machines - one has XP and the other has Windows 2000.
When I tried to copy files fomr the old Windows 2000 machine to the new directory on XP, I had continued failures because XP will not accept long file names (over 255 characters).
I was using the XP machine and logging in to the 2000 machine.

Is there a script/program out there that I could run on my Windows 2000 machine to identify all filenames over 255 characters?

I could then re-name them and copy them over to the XP machine. From what I can tell, the XP machine can't be logged into from a 2000 one, but I am still researching that...so I will have to browse to the files from the XP machine.

 

[bcastner]

. a "Path too deep" error is not always because the actual path is too deep. It is reported on fundamental hardware issues as well. See:

http://dotnetjunkies.com/WebLog/sahilmalik/archive/2004/08/30/23742.aspx

. consider modifying the script's directory path. It seems little appreciated that you can map a share from its root to any subfolder

If I have a share name for C:\shared_information, I can net use drive letter any of the subfolders in a mapping command.

. Create a new share at the level \subfolder_1p\ or whatever and adjust the script to begin there.

C:\shared_information\subfolder1\subfolder_1a\subfolder_1b\subfolder_1c\...etc up to the 255 limit:

Then map to that. To XP it appears as drive_letter:\

. consider using SUBST
subst m: \\remote_share_server\entire path as long as you can

Again, the lengthy path appears to XP as drive_letter:\

I also encourage you to use Robocopy instead of Xcopy if doing this transfer.

 

[linney]

For what it is worth 2000 ought to be able to talk to XP it sounds as if you may be having other network problems besides long file names.

Simple File Sharing- enabled

http://www.practicallynetworked.com/sharing/xp/filesharing.htm

Simple File Sharing - disabled

http://www.practicallynetworked.com/sharing/xp_filesharing/index.htm

http://www.michna.com/kb/wxnet.htm

I also believe that Windows 2000 is limited to a 255 character filename length. Running ChkDsk on your 2000 system might be interesting just to check those filenames.

 

[clennox]

Hello:
I will look into the path too deep issue. My XP version (Home) doesn't tell me what the errors are...which is frustrating...it just says 'cannot copy file' with no filename or explanation.
Thank you for your help so far.
Any suggestions on why I'm not getting more intelligient error messages?

 

[bcastner]

I am less concerned about the error message details than whether you tried the various steps to reduce the enumerated path; or used alternatives to the Copy or Xcopy commands.

 

[linney]

On your 2000 machine copy the file to a floppy (or CD). Try copying the file from floppy (or CD) to XP Home. Does this procedure work without copy errors?

I wonder if you are having file permission or sharing errors rather than data reading errors?

What error message mentioned 255 Characters?