I have one system where I can scan this long path correctly as shown below. It converts it to the DOS short name successfully since the path is really long

Path converted from [\\?\C:\Documents and Settings\myname\Local Settings\Temporary Internet Files\Content.IE5\UJW3A5ID\1027eed543b58578e6e3b824071758d9bdeafd1265a7b24402f7551e927c3acb81cdbfa67bfd3446b42706edbe6b0608936758c58f0c7d1f68b5cd4c42f5e53570bdeeee23870722b7d8b04c5[1].htm] to [\\?\C:\Documents and Settings\fw_release\Local Settings\Temporary Internet Files\Content.IE5\UJW3A5ID\1027EE~1.HTM]

But I have another system where the exact same path crashes:

Path converted from [\\?\C:\Documents and Settings\myname\Local Settings\Temporary Internet Files\Content.IE5\UJW3A5ID\1027eed543b58578e6e3b824071758d9bdeafd1265a7b24402f7551e927c3acb81cdbfa67bfd3446b42706edbe6b0608936758c58f0c7d1f68b5cd4c42f5e53570bdeeee23870722b7d8b04c5[1].htm] to [\\?\C:\Documents and Settings\fw_release\Local Settings\Temporary Internet Files\Content.IE5\UJW3A5ID\ tC:\Documents and Settings\fw_release\Local Settings\Temporary Internet Files\Content.IE5\UJW3A5ID\LibClamAV Warning: Filename too long, please report


If you look at it really carefully you'll notice the difference is the following:

GOOD: UJW3A5ID\1027EE~1.HTM
BAD: UJW3A5ID\ tC:\Documents and Settings

Notice how when the second one tries to convert it to short name, it actually puts in a weird space and t character instead of making it the dos short name like the good one.

Do you guys know what would cause this?

Strange! Are both computers 64 bit or 32 bit or one of each?

Regards,

Both are xp pro 32-bit

8dot3 filename creation may be disabled, check https://technet.microsoft.com/en-us/library/ff621566%28v=ws.10%29.aspx https://technet.microsoft.com/en-us/library/ff621566%28v=ws.10%29.aspx

Didn't seem to help. This time I get a smiley face icon instead of the space t.

Content.IE5\UJW3A5IDOA?C:\Docu

I actually changed the registry value on my xp box to 0. It's called:
NtfsDisable8dot3NameCreation