Here's something I can't figure out:

I bought a new laptop and am transferring files from the old one, through a
USB external drive.

For some of the files, the new machine says "The filename is too long or
filename isn't valid" so the transfer is aborted.

They're both XP machines (well, the old one is XP Home and the new one is XP
Pro).

If the name was fine on the old machine, why isn't it fine on the new one?
Especially since in these cases the names aren't even that long.

I'm guessing I have to set something on the new machine.

Anybody offer any insights?

Thanks!

John

"JMF" <jfavaro@tin.it> wrote in message
news:u%23oPvOX%23IHA.3392@TK2MSFTNGP03.phx.gbl...
> Here's something I can't figure out:
>
> I bought a new laptop and am transferring files from the old one, through
> a USB external drive.
>
> For some of the files, the new machine says "The filename is too long or
> filename isn't valid" so the transfer is aborted.
>
> They're both XP machines (well, the old one is XP Home and the new one is
> XP Pro).
>
> If the name was fine on the old machine, why isn't it fine on the new one?
> Especially since in these cases the names aren't even that long.
>
> I'm guessing I have to set something on the new machine.
>
> Anybody offer any insights?
>
> Thanks!
>
> John

Discussed in this very newsgroup only two days ago in the thread
"Will XP Backup copy files Uncompressed to another disk" - see here:
http://groups.google.fr/group/micros...e07bed0c56a3b0
The problem lies with your old PC. You chose to place much
of the information into your file & folder ***names***, thus
exceeding the combined maximum of 260 characters. To solve
the problem permanently you need to put the information into
your ***files***, then shorten the file/folder names.

Many thanks! I'll review all the information in that thread now.

John

"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:eEvC8TX%23IHA.5040@TK2MSFTNGP04.phx.gbl...
>
> "JMF" <jfavaro@tin.it> wrote in message
> news:u%23oPvOX%23IHA.3392@TK2MSFTNGP03.phx.gbl...
>> Here's something I can't figure out:
>>
>> I bought a new laptop and am transferring files from the old one, through
>> a USB external drive.
>>
>> For some of the files, the new machine says "The filename is too long or
>> filename isn't valid" so the transfer is aborted.
>>
>> They're both XP machines (well, the old one is XP Home and the new one is
>> XP Pro).
>>
>> If the name was fine on the old machine, why isn't it fine on the new
>> one? Especially since in these cases the names aren't even that long.
>>
>> I'm guessing I have to set something on the new machine.
>>
>> Anybody offer any insights?
>>
>> Thanks!
>>
>> John
>
> Discussed in this very newsgroup only two days ago in the thread
> "Will XP Backup copy files Uncompressed to another disk" - see here:
> http://groups.google.fr/group/micros...e07bed0c56a3b0
> The problem lies with your old PC. You chose to place much
> of the information into your file & folder ***names***, thus
> exceeding the combined maximum of 260 characters. To solve
> the problem permanently you need to put the information into
> your ***files***, then shorten the file/folder names.
>

JMF wrote:
> Here's something I can't figure out:
>
> I bought a new laptop and am transferring files from the old one,
> through a USB external drive.
>
> For some of the files, the new machine says "The filename is too long
> or filename isn't valid" so the transfer is aborted.
>
> They're both XP machines (well, the old one is XP Home and the new
> one is XP Pro).
>
> If the name was fine on the old machine, why isn't it fine on the new
> one? Especially since in these cases the names aren't even that long.
>
> I'm guessing I have to set something on the new machine.
>
> Anybody offer any insights?

You said "transfer" but didn't name the mechanism.

If you're using the command prompt COPY or XCOPY commands, be aware that any
imbedded spaces in folders or filenames bother the command something fierce.
To circumvent this problem, surround the source and destination addresses
with double-quotes, viz:

COPY "C:\Source Folder\Source File.TXT" "F:\Destination Folder\"

"HeyBub" <heybub******.com> wrote in message
news:egr7M1Y%23IHA.1180@TK2MSFTNGP04.phx.gbl...
> JMF wrote:
>> Here's something I can't figure out:
>>
>> I bought a new laptop and am transferring files from the old one,
>> through a USB external drive.
>>
>> For some of the files, the new machine says "The filename is too long
>> or filename isn't valid" so the transfer is aborted.
>>
>> They're both XP machines (well, the old one is XP Home and the new
>> one is XP Pro).
>>
>> If the name was fine on the old machine, why isn't it fine on the new
>> one? Especially since in these cases the names aren't even that long.
>>
>> I'm guessing I have to set something on the new machine.
>>
>> Anybody offer any insights?
>
> You said "transfer" but didn't name the mechanism.
>
> If you're using the command prompt COPY or XCOPY commands, be aware that
> any imbedded spaces in folders or filenames bother the command something
> fierce. To circumvent this problem, surround the source and destination
> addresses with double-quotes, viz:
>
> COPY "C:\Source Folder\Source File.TXT" "F:\Destination Folder\"

This is the second time today that you push this line. While you are
certainly correct in saying that file/folder names with embedded
spaces must be surrounded by double quotes, this has nothing at
all to do with the problem of having excessively long file+folder
names. Mentioning it to the OP will only cause confusion. Note
also that the double-quote requirement is not limited to the copy/
xcopy commands. It applies to ALL console commands, with one
tiny exception (which I won't mention for fear of adding to your
confusion).

Pegasus (MVP) wrote:
> "HeyBub" <heybub******.com> wrote in message
> news:egr7M1Y%23IHA.1180@TK2MSFTNGP04.phx.gbl...
>> JMF wrote:
>>> Here's something I can't figure out:
>>>
>>> I bought a new laptop and am transferring files from the old one,
>>> through a USB external drive.
>>>
>>> For some of the files, the new machine says "The filename is too
>>> long or filename isn't valid" so the transfer is aborted.
>>>
>>> They're both XP machines (well, the old one is XP Home and the new
>>> one is XP Pro).
>>>
>>> If the name was fine on the old machine, why isn't it fine on the
>>> new one? Especially since in these cases the names aren't even that
>>> long. I'm guessing I have to set something on the new machine.
>>>
>>> Anybody offer any insights?
>>
>> You said "transfer" but didn't name the mechanism.
>>
>> If you're using the command prompt COPY or XCOPY commands, be aware
>> that any imbedded spaces in folders or filenames bother the command
>> something fierce. To circumvent this problem, surround the source
>> and destination addresses with double-quotes, viz:
>>
>> COPY "C:\Source Folder\Source File.TXT" "F:\Destination Folder\"
>
> This is the second time today that you push this line. While you are
> certainly correct in saying that file/folder names with embedded
> spaces must be surrounded by double quotes, this has nothing at
> all to do with the problem of having excessively long file+folder
> names. Mentioning it to the OP will only cause confusion. Note
> also that the double-quote requirement is not limited to the copy/
> xcopy commands. It applies to ALL console commands, with one
> tiny exception (which I won't mention for fear of adding to your
> confusion).

I mentioned it because the OP said "... the filenames aren't even that
long..."

I deduced from that long filenames were not the actual problem.

As for generating confusion, that's simply not possible. If the OP does not
have any imbedded spaces in his his file\folder names, adding double-quotes
won't matter. If he does have imbedded spaces, adding double-quotes may very
well solve his problem.

I recall a situation from the days of the Yiddish theater. An actor
collapses on the stage. A doctor from the audience runs up and examines him.
From the balcony a Yiddishi-momma voice calls out: "Give him an enema!"

The doctor stands and shouts: "Madam, the actor is dead!"

The voice from the balcony shouts back, "So... It can't hurt!"

>
> I mentioned it because the OP said "... the filenames aren't even that
> long..."
>
> I deduced from that long filenames were not the actual problem.
*** If the OP had omitted double quotes then he would get a
*** completely different error message. Give it a try yourself!

> As for generating confusion, that's simply not possible. If the OP does
> not have any imbedded spaces in his his file\folder names, adding
> double-quotes won't matter. If he does have imbedded spaces, adding
> double-quotes may very well solve his problem.
*** No, adding double quotes will never resolve a problem of
*** excessively long file names. Again - give it a try!

> I recall a situation from the days of the Yiddish theater. An actor
> collapses on the stage. A doctor from the audience runs up and examines
> him. From the balcony a Yiddishi-momma voice calls out: "Give him an
> enema!"
>
> The doctor stands and shouts: "Madam, the actor is dead!"
>
> The voice from the balcony shouts back, "So... It can't hurt!"
*** This is a newsgroup, not a slap-stick comedy. We're meant
*** to assist the OP, not to entertain him with funny jokes.

Pegasus (MVP) wrote:

> *** This is a newsgroup, not a slap-stick comedy. We're meant
> *** to assist the OP, not to entertain him with funny jokes.
>
>

Personally, I rather liked the joke...

Bill

"Bill Sharpe" <wfsnopam@adelphia.net> wrote in message
news:OVwvygJ$IHA.5192@TK2MSFTNGP04.phx.gbl...
> Pegasus (MVP) wrote:
>
>> *** This is a newsgroup, not a slap-stick comedy. We're meant
>> *** to assist the OP, not to entertain him with funny jokes.
>
> Personally, I rather liked the joke...
>
> Bill

So do I, if only it came with something that would assist the OP . . .