Deleting files with VERY long file names

In message <>, Gene E. Bloch
<> writes:
>On 3/08/2012, Joerg Jaeger posted:
>> On 3/8/2012 5:37 PM, Stan Brown wrote:
>>> On Thu, 08 Mar 2012 06:57:30 -0600, danielfird wrote:
>>>> Hi all, I have been suffering from accessing, managing and even
>>>>renaming files
>>>> that have more than 255 characters over a long time. I have tried
>>>>various ways
>>>> but failed. Then I have searched this problem in internet. Then I
>>>>have found a
>>>> solution. This software is very easy to use. Named Long path Tool.
>>>
>>> Really not necessary, though I'm glad it worked for you.
>>>
>>> Find the folder in question in Explorer, Shift-Right-click and select
>>> Open Command Prompt here. Type "dir /x" (no quotes) to reveal the
>>> short file names next to the long file names. Then "del" (no quotes)
>>> and the short file name.
>>>
>
>> That seems to work well. I think you can most likely solve most
>>problems with the shell.
>> Just like in Linux.
>> From what i tried it looks like Windows names the first 6 letters,
>>then a ~ and a counting number with extension.

Variations in that appear when you get past the counting number of 9, or
the first few characters include some not allowed in an 8.3 name (fewer
characters are allowed than in long names - spaces for example), or if
the extension has more than three characters, or ...
>
>Yes, that's correct or close to correct, AFAIK. Still, the safest thing
>is to use dir /x in a command window, so as not to accidentally use the
>wrong name. Dir /x shows both names, which makes correct identification
>easy.
>
Agreed.
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf

Abandon hope, all ye who <ENTER> here.

On 3/09/2012, J. P. Gilliver (John) posted:
> In message <yac6r.13400$>, Bob I <>
> writes:
>>Another method is to map a drive letter to a folder just above the problem
>> file. To do this share the folder to everyone and then map the folder as a
>> network share. Disconnect the drive when done and remove sharing
>> permission. Saves a lot of messing about with renaming
> []
> Does SUBST no longer work in 7? (It works in XP; I think XP tries to dissuade
> you from using it, but I haven't experienced any ill-effects, provided you
> know you're using it.)

> Mapping drive letters - and SUBST if available - are (possible) solutions to
> the problem of too long a name including the path; if the path is not
> involved, then use of the short name is better.

On this Windows 7 computer, subst /? in a command window gives a brief
help message. I would guess that means it works in Win 7.

Subst /help gives an error message :-)

--
Gene E. Bloch (Stumbling Bloch)

In article <>,
d says...
>
> On 3/09/2012, J. P. Gilliver (John) posted:
> > In message <yac6r.13400$>, Bob I <>
> > writes:
> >>Another method is to map a drive letter to a folder just above the problem
> >> file. To do this share the folder to everyone and then map the folder as a
> >> network share. Disconnect the drive when done and remove sharing
> >> permission. Saves a lot of messing about with renaming
> > []
> > Does SUBST no longer work in 7? (It works in XP; I think XP tries to dissuade
> > you from using it, but I haven't experienced any ill-effects, provided you
> > know you're using it.)
>
> > Mapping drive letters - and SUBST if available - are (possible) solutions to
> > the problem of too long a name including the path; if the path is not
> > involved, then use of the short name is better.
>
> On this Windows 7 computer, subst /? in a command window gives a brief
> help message. I would guess that means it works in Win 7.
>
> Subst /help gives an error message :-)

(-;

--
Zaphod

Adventurer, ex-hippie, good-timer (crook? quite possibly),
manic self-publicist, terrible bad at personal relationships,
often thought to be completely out to lunch.

On 3/9/2012 3:44 PM, Zaphod Beeblebrox wrote:
> In article<>,
> d says...
>>
>> On 3/09/2012, J. P. Gilliver (John) posted:
>>> In message<yac6r.13400$>, Bob I<>
>>> writes:
>>>> Another method is to map a drive letter to a folder just above the problem
>>>> file. To do this share the folder to everyone and then map the folder as a
>>>> network share. Disconnect the drive when done and remove sharing
>>>> permission. Saves a lot of messing about with renaming
>>> []
>>> Does SUBST no longer work in 7? (It works in XP; I think XP tries to dissuade
>>> you from using it, but I haven't experienced any ill-effects, provided you
>>> know you're using it.)
>>
>>> Mapping drive letters - and SUBST if available - are (possible) solutions to
>>> the problem of too long a name including the path; if the path is not
>>> involved, then use of the short name is better.
>>
>> On this Windows 7 computer, subst /? in a command window gives a brief
>> help message. I would guess that means it works in Win 7.
>>
>> Subst /help gives an error message :-)
>
> (-;
>
subst /? works but /help gives an error on my Win7 64bit

--
Zaidy036

On 3/09/2012, Zaidy036 posted:
> On 3/9/2012 3:44 PM, Zaphod Beeblebrox wrote:
>> In article<>,
>> d says...
>>>
>>> On 3/09/2012, J. P. Gilliver (John) posted:
>>>> In message<yac6r.13400$>, Bob I<>
>>>> writes:
>>>>> Another method is to map a drive letter to a folder just above the
>>>>> problem
>>>>> file. To do this share the folder to everyone and then map the folder as
>>>>> a
>>>>> network share. Disconnect the drive when done and remove sharing
>>>>> permission. Saves a lot of messing about with renaming
>>>> []
>>>> Does SUBST no longer work in 7? (It works in XP; I think XP tries to
>>>> dissuade
>>>> you from using it, but I haven't experienced any ill-effects, provided
>>>> you
>>>> know you're using it.)
>>>
>>>> Mapping drive letters - and SUBST if available - are (possible) solutions
>>>> to
>>>> the problem of too long a name including the path; if the path is not
>>>> involved, then use of the short name is better.
>>>
>>> On this Windows 7 computer, subst /? in a command window gives a brief
>>> help message. I would guess that means it works in Win 7.
>>>
>>> Subst /help gives an error message :-)
>>
>> (-;
>>
> subst /? works but /help gives an error on my Win7 64bit

That's no surprise to me, since that's what I just reported two posts
up...

In this post, that's 4 and 6 lines above your comment.

--
Gene E. Bloch (Stumbling Bloch)

In message <jje43l$914$>, Zaidy036 <>
writes:
>On 3/9/2012 3:44 PM, Zaphod Beeblebrox wrote:
>> In article<>,
>> d says...
>>>
>>> On 3/09/2012, J. P. Gilliver (John) posted:
>>>> In message<yac6r.13400$>, Bob I<>
>>>> writes:
>>>>> Another method is to map a drive letter to a folder just above the problem
>>>>> file. To do this share the folder to everyone and then map the folder as a
>>>>> network share. Disconnect the drive when done and remove sharing
>>>>> permission. Saves a lot of messing about with renaming
>>>> []
>>>> Does SUBST no longer work in 7? (It works in XP; I think XP tries
>>>>to dissuade
>>>> you from using it, but I haven't experienced any ill-effects, provided you
>>>> know you're using it.)
>>>
>>>> Mapping drive letters - and SUBST if available - are (possible)
>>>>solutions to
>>>> the problem of too long a name including the path; if the path is not
>>>> involved, then use of the short name is better.
>>>
>>> On this Windows 7 computer, subst /? in a command window gives a brief
>>> help message. I would guess that means it works in Win 7.
>>>
>>> Subst /help gives an error message :-)
>>
>> (-;
>>
>subst /? works but /help gives an error on my Win7 64bit
>
Before we get too far down this road: I mentioned subst because I find
it a lot easier to use, when just working within existing drives, than
using the mapping network drive method.
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf

People wear anoraks because it's cold outside and it rains, not to annoy the
editors of style magazines. - Ben Elton, Radio Times 18-24 April 1998

Alf wrote on 02/13/2011 05:20 ET
> I have picked up a few files with very long names that Windows 7 will no
> delete (error message indicating that file names are too long). So far I hav
> tried (1) rebooting, (2) moving or changing th
> files names--will not work because I get a Windows error sound by jus
clickin
> on the files, and (3) using CMD to try to delete the files with old DO
> commands--still get an error message re lengt
> of the files
>
> I would appreciate any suggestions. TIA. --Al
>
>
> Posted with NewsLeecher v5.0 Beta
> Web @ http://www.newsleecher.com/?usene
>
After days of searching I finally found solution for unlocking, managing an
renaming long named files. Get your problem solved fro
http://longpathtool.com/

On 3/29/2012, atillarist posted:
> Alf wrote on 02/13/2011 05:20 ET :
>> I have picked up a few files with very long names that Windows 7 will not
>> delete (error message indicating that file names are too long). So far I
>> have tried (1) rebooting, (2) moving or changing the
>> files names--will not work because I get a Windows error sound by just
>> clicking on the files, and (3) using CMD to try to delete the files with old
>> DOS commands--still get an error message re length
>> of the files.
>>
>> I would appreciate any suggestions. TIA. --Alf
>>
>>
>> Posted with NewsLeecher v5.0 Beta 1
>> Web @ http://www.newsleecher.com/?usenet
>>
> After days of searching I finally found solution for unlocking, managing and
> renaming long named files. Get your problem solved from
> http://something.something/

It looks to me like an old spammer is back with a new nym.

Any other opinions?

--
Gene E. Bloch (Stumbling Bloch)

On Thu, 29 Mar 2012 16:08:56 -0700, Gene E. Bloch
<> wrote:

>On 3/29/2012, atillarist posted:
>> Alf wrote on 02/13/2011 05:20 ET :
>>> I have picked up a few files with very long names that Windows 7 will not
>>> delete (error message indicating that file names are too long). So far I
>>> have tried (1) rebooting, (2) moving or changing the
>>> files names--will not work because I get a Windows error sound by just
>>> clicking on the files, and (3) using CMD to try to delete the files with old
>>> DOS commands--still get an error message re length
>>> of the files.
>>>
>>> I would appreciate any suggestions. TIA. --Alf
>>>
>>>
>>> Posted with NewsLeecher v5.0 Beta 1
>>> Web @ http://www.newsleecher.com/?usenet
>>>
>> After days of searching I finally found solution for unlocking, managing and
>> renaming long named files. Get your problem solved from
>> http://something.something/
>
>It looks to me like an old spammer is back with a new nym.
>
>Any other opinions?

I randomly see 'helpful' posts like the one above, all pointing to the
same utility, in most of my subscribed text groups. Like the one
above, they are usually replies to posts that are 1-4 years old.

--

Char Jackson

On 30/03/2012 2:28 am, Char Jackson wrote:
> On Thu, 29 Mar 2012 16:08:56 -0700, Gene E. Bloch
> <> wrote:
>
>> On 3/29/2012, atillarist posted:
>>> Alf wrote on 02/13/2011 05:20 ET :
>>>> I have picked up a few files with very long names that Windows 7 will not
>>>> delete (error message indicating that file names are too long). So far I
>>>> have tried (1) rebooting, (2) moving or changing the
>>>> files names--will not work because I get a Windows error sound by just
>>>> clicking on the files, and (3) using CMD to try to delete the files with old
>>>> DOS commands--still get an error message re length
>>>> of the files.
>>>>
>>>> I would appreciate any suggestions. TIA. --Alf
>>>>
>>>>
>>>> Posted with NewsLeecher v5.0 Beta 1
>>>> Web @ http://www.newsleecher.com/?usenet
>>>>
>>> After days of searching I finally found solution for unlocking, managing and
>>> renaming long named files. Get your problem solved from
>>> http://something.something/
>> It looks to me like an old spammer is back with a new nym.
>>
>> Any other opinions?
> I randomly see 'helpful' posts like the one above, all pointing to the
> same utility, in most of my subscribed text groups. Like the one
> above, they are usually replies to posts that are 1-4 years old.
>
So what? People might still want the information, even if it's been
answered before in a post that's long been deleted from the server.