Re: Cut Long Names

de Terry Russell 05/09/2006 01:31

"shadow" <shadow.crossbones@gmail.com> wrote in message
news:rr1v52t3ofg8iiovtkn2p8ccmi484nauk2@4ax.com...
>
> Cut Long Names 1.6b - my impressions
> ------------------------------------------------------
>
> Only works under Windows NT/XP

> Pre-set to scan *.xls;*.doc;*.rtf;*.txt;*.html;*.htm files, can easily
> add your own extensions.
>
> Pre-set for 150 characters length, can easily change the length to
> search for.
>
> A simply check mark allows searching system files as well.
>
> It is fast and searches a 10G partition in seconds. it would take
> somewhat longer when searching through a full hard drive of the chosen
> extensions I am sure.

> One can choose which files to rename and which not to from the found
> file names listing.

Usually, for some reason , and I am sure I only checked one, it
cropped a whole drive.

> The utility allows saving the listing of the file names (with full
> paths) after renaming.
>
> I do not like the auto rename feature when one clicks on start rename,
> as one is not given a choice as to how to rename. I would recommend
> testing it on a few files first.

click-select and edit button , you can change the rename

no undo , no foldback 'now go back and do some more' once
completed you have to run the app again
the save feature could be used to undo
paths are ahrd to resolve

> One can use it to locate long file names, and manually rename the
> files oneself. I would be a more confortable and a lot safer doing
> that anyway. It would have been handy to include the ability to click
> on a file name and change it to your name of preference from within
> the utility but that it doesn't do this is more than likely one of the
> reasons its freeware.

>
> It does what it claims to do, doesn't have any bad side effects, and
> uses very little memory (3.1m when running) or system resources.

I couldn't move or delete renamed files without a reboot.
I have several installed filesystems, perhaps one or the other aren't
playing well together. Long paths will do that to you.

The docs are not entirely correct about paths, but close enough.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/fs/naming_a_file.asp

The problem with renamers is that often the long filenames are from
webpages and the like that depend on other files.
Truncating at depth for a reparented tree should do a lot more than
truncate filenames, otherwise it will just break the logic.
Excessively long paths will need to be shortened in the directory.

> One gets what one pays for.
>
> Useful in checking for long files names before creating ISO's and
> burning backups to CD/DVD disc's, or any other removable media for
> that matter.

I little inattention, maybe a glitch, but inattention is the default state
so
cannot be discounted, and it clearfelled the directory tree.
It defaults to an industrial buzzsaw, there are other tools that are a
little more subtle

It does exactly what it says and I can't fault that .. cut long names.

[ the real problem here is that after 25 years, hundreds of
billions of dollars spent on machines with memory in gigabytes
and drives reaching for terrabytes we still have to worry,
I mean WORRY, about a couple of hundred bytes ,
it is those few hundred bytes in a file system architecture
designed for floppies that breaks most backups
and causes so many admin headaches ]