Quicky Computerbox question

[narzy]

cliff notes:
trying to copy files from one windows XP box to another over the network, windows file transfer sucks and keeps dropping the following error:

"Cannot Copy <Filename>

The resulting file name is too long, specify a different file name"

Windows then aborts the file transfer and I have to start it all over again, there are many many files in this directory and I have been chasing my tail tracking them down and re-naming them by hand, I have been doing this for the past 2 hours and have made no head way, I thought of mass-renaming the files or truncating the file names but have come to the conclusion that is not a viable solution.

what I am going to try is to set up an FTP server on the reciving machine and FTP the files over I'm thinking that FTP won't give a sh!t about file name length (am I right in that assumption) or is there a better way? if this were linux I'd rsync them but rsync on windows is more complicated than it needs to be.

 

[MisterJackson]

Hmmmmm.....

Use Ycopy....and WRONG FORUM!!!

 

[AbsolutDealage]

This is the wrong forum, but....

Why don't you just zip up all the files first?

 

[BKLounger]

just set them up on a network neighborhood and transfer

 

[narzy]

Originally posted by: AbsolutDealage
This is the wrong forum, but....

Why don't you just zip up all the files first?

Off topic gets by far the most traffic so that is why it is posted here...

Zip would take HOURS if not days we are talking something like 100 gigs of data...again if this were linux I'd have tar.gz'd them but it's not...

 

[narzy]

Originally posted by: BKLounger
just set them up on a network neighborhood and transfer

that is exactly what I've done and it's not working...What you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone in this room is now dumber for having listened to it. I award you no points, and may God have mercy on your soul.

 

[FoBoT]

what kind of hard drive are they on? can you remove the drive from the original system and plug it up on the destination system temporily

 

[AbsolutDealage]

Originally posted by: narzy

Originally posted by: AbsolutDealage
This is the wrong forum, but....

Why don't you just zip up all the files first?

Off topic gets by far the most traffic so that is why it is posted here...

That's no excuse. It still doesn't belong here.

Zip would take HOURS if not days we are talking something like 100 gigs of data...again if this were linux I'd have tar.gz'd them but it's not...

You can zip with no compression, and it wouldn't take any longer than tar'ing them. 100 gig is still a lot though... why don't you just pull the hard drive and do a local transfer?

Originally posted by: narzy

Originally posted by: BKLounger
just set them up on a network neighborhood and transfer

that is exactly what I've done and it's not working...What you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone in this room is now dumber for having listened to it. I award you no points, and may God have mercy on your soul.

Don't come in to the wrong forum asking for help and then act like a d!ck.

 

[narzy]

Originally posted by: FoBoT
what kind of hard drive are they on? can you remove the drive from the original system and plug it up on the destination system temporily

SATA drive, original machine only has PATA...could get a converter but don't want to...

 

[spidey07]

Just use FTP.

If that gives same problem then something is different between the two files systems.

 

[narzy]

Originally posted by: AbsolutDealage

Originally posted by: narzy

Originally posted by: AbsolutDealage
This is the wrong forum, but....

Why don't you just zip up all the files first?

Off topic gets by far the most traffic so that is why it is posted here...

That's no excuse. It still doesn't belong here.

Zip would take HOURS if not days we are talking something like 100 gigs of data...again if this were linux I'd have tar.gz'd them but it's not...

You can zip with no compression, and it wouldn't take any longer than tar'ing them. 100 gig is still a lot though... why don't you just pull the hard drive and do a local transfer?

Originally posted by: narzy

Originally posted by: BKLounger
just set them up on a network neighborhood and transfer

that is exactly what I've done and it's not working...What you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone in this room is now dumber for having listened to it. I award you no points, and may God have mercy on your soul.

Don't come in to the wrong forum asking for help and then act like a d!ck.

Don't post stupid useless sh!t and you'll have nothing to worry about .

 

[narzy]

Originally posted by: spidey07
Just use FTP.

If that gives same problem then something is different between the two files systems.

kk thanks spidey...

 

[narzy]

son of a *)(#$89 FTP is throwing errors...I HATE computers...time to find another career...

 

[MercenaryForHire]

Zombie thread resurrected, get the shotgun.

Sounds like you're hitting the path+filename length wall of 255 characters.

FTP will at least copy all the non-offending files, then you can truncate/rename the lengthly buggers later.

- M4H

 

[MisterJackson]

Originally posted by: narzy

Originally posted by: AbsolutDealage

Originally posted by: narzy

Originally posted by: AbsolutDealage
This is the wrong forum, but....

Why don't you just zip up all the files first?

Off topic gets by far the most traffic so that is why it is posted here...

That's no excuse. It still doesn't belong here.

Zip would take HOURS if not days we are talking something like 100 gigs of data...again if this were linux I'd have tar.gz'd them but it's not...

You can zip with no compression, and it wouldn't take any longer than tar'ing them. 100 gig is still a lot though... why don't you just pull the hard drive and do a local transfer?

Originally posted by: narzy

Originally posted by: BKLounger
just set them up on a network neighborhood and transfer

that is exactly what I've done and it's not working...What you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone in this room is now dumber for having listened to it. I award you no points, and may God have mercy on your soul.

Don't come in to the wrong forum asking for help and then act like a d!ck.

Don't post stupid useless sh!t and you'll have nothing to worry about .

Kinda like you did with this thread? You truly are a cock gobbler.

 

[narzy]

Originally posted by: MercenaryForHire
Zombie thread resurrected, get the shotgun.

Sounds like you're hitting the path+filename length wall of 255 characters.

FTP will at least copy all the non-offending files, then you can truncate/rename the lengthly buggers later.

- M4H

there seem to be a lot of them...If the filesystem is going to have such a hard time with long file names why in the WORLD would it let people create them, this is just idiocy...another bang up job MSFT! woot. :roll:

 

[narzy]

Originally posted by: MisterJackson



Kinda like you did with this thread? You truly are a cock gobbler.

do the world a favor, choke on a loaded shotgun barrel and pull the trigger...

 

[mugs]

The path is too long. Shorten the path that you're copying the files to.

Edit: And use robocopy to do the copying (it's free from MS)

 

[MisterJackson]

Originally posted by: narzy

Originally posted by: MisterJackson



Kinda like you did with this thread? You truly are a cock gobbler.

do the world a favor, choke on a loaded shotgun barrel and pull the trigger...

Internet E-thug....are you Icy Hot too? I'm willing to bet you are bitch boy.

I leave a big steaming pile on your thread....and I'm out.

 

[narzy]

Originally posted by: MisterJackson

Originally posted by: narzy

Originally posted by: MisterJackson



Kinda like you did with this thread? You truly are a cock gobbler.

do the world a favor, choke on a loaded shotgun barrel and pull the trigger...

Internet E-thug....are you Icy Hot too? I'm willing to bet you are bitch boy.

I leave a big steaming pile on your thread....and I'm out.

you attack me first and I'm somehow the e-thug/bitch when I tell you were to stick it...LMAO!

Originally posted by: mugs
The path is too long. Shorten the path that you're copying the files to.

Edit: And use robocopy to do the copying (it's free from MS)

Thanks mugs, do you know of any program that will allow me to check and shorten offending file names or will I need to write a perl script?

 

[MercenaryForHire]

Originally posted by: narzy

Originally posted by: MercenaryForHire
Zombie thread resurrected, get the shotgun.

Sounds like you're hitting the path+filename length wall of 255 characters.

FTP will at least copy all the non-offending files, then you can truncate/rename the lengthly buggers later.

- M4H

there seem to be a lot of them...If the filesystem is going to have such a hard time with long file names why in the WORLD would it let people create them, this is just idiocy...another bang up job MSFT! woot. :roll:

The problem is the destination filename.

Source could be C:\Folder\File.ext, but if you're saving it to C:\Backup from other people's computers\Archive of their C drive\Stuff I'm keeping for my personal collection\Folder To Sort\2007-01-29\Porn\Video.avi then that's too long.

Try dumping it to C:\X\Folder\File.ext

- M4H

 

[narzy]

Originally posted by: MercenaryForHire

Originally posted by: narzy

Originally posted by: MercenaryForHire
Zombie thread resurrected, get the shotgun.

Sounds like you're hitting the path+filename length wall of 255 characters.

FTP will at least copy all the non-offending files, then you can truncate/rename the lengthly buggers later.

- M4H

there seem to be a lot of them...If the filesystem is going to have such a hard time with long file names why in the WORLD would it let people create them, this is just idiocy...another bang up job MSFT! woot. :roll:

The problem is the destination filename.

Source could be C:\Folder\File.ext, but if you're saving it to C:\Backup from other people's computers\Archive of their C drive\Stuff I'm keeping for my personal collection\Folder To Sort\2007-01-29\Porn\Video.avi then that's too long.

Try dumping it to C:\X\Folder\File.ext

- M4H

OHHH okay, I understand the problem now, I thought it was a file name that was < 255 that had been created and now the system wouldn't let me move it...this is beginning to make sense.

 

[MagnusTheBrewer]

So, who's in charge of the narzy scroll anyways? :disgust:

 

[narzy]

Originally posted by: MagnusTheBrewer
So, who's in charge of the narzy scroll anyways? :disgust:

that doesn't even make any sense!