Re: Too long filenames wrongly handled by Windows
- From: Mikhail Zhilin <mwz@xxxxxxxxxxxxxxxx>
- Date: Tue, 19 Apr 2005 18:02:31 +0400
Assuming there is no Y: drive (in the other case use the letter that is
free), you can create Y: fictive drive:
Start -- Run...
subst Y: "H:\PC8_bakup\Documents and Settings\User4\Local
Settings\Temporary Internet Files\Content.IE5"
(it is one long line). Then you can copy all the subfolders from the
root of Y:\ to the main "Content.IE5" folder.
BUT... No need to backup this ...\Temporary Internet
Files\ folder at all: all the files in it are temporary files, which can
be deleted at any time. If it is possible -- simply exclude it from the
Backup set.
As well as the content of \Windows\TEMP and
"\Documents and Settings\User4\Local Settings\Temp"
(with any name instead of \User4\ in this line) folders.
--
Mikhail Zhilin
http://www.aha.ru/~mwz
Sorry, no technical support by e-mail.
Please reply to the newsgroups only.
======
On Tue, 19 Apr 2005 14:39:19 +0200, "Michel Merlin"
<michel.merlin@xxxxxxxxxxx> wrote:
>Too long filenames wrongly handled by Windows
>
>As part of a routine backup, I copy (using an appropriate
>program) an entire main HD, say HD1, onto another HD2, then I
>"forward-copy" HD2 onto HD3. Initial backup can use up to 2
>hours, but next backups, copying only the new or changed files,
>use only 2 to 10 minutes (depending on PC and its use).
>
>After doing this for some times, the backup, while performing OK
>for all files in first stage (HD1 to HD2) and for most files in
>forwarding stage (HD2 to HD3), fails in that 2nd stage for a
>dozen files, with errors like this one:
>
>« Unable to rename temp file from H:\PC8_bakup\Documents
>and Settings\User4\Local Settings\Temporary Internet
>Files\Content.IE5\W1IN4HUB\~PGTEMP.TMP to H:\PC8_bakup\Documents
>and Settings\User4\Local Settings\Temporary Internet
>Files\Content.IE5\W1IN4HUB\the_style1-%23FFFFFF-%23F3F2FB-%23003
>399-%23C2C3F4-%23003399-%23FFFFFF-%23FFFFFF-%23000000-%230033AA-
>%23000000-%230033AA-%23F3F2FB-%23E9E6EF-%23FFFF[1].css (The
>system cannot find the path specified) »
>
>Those files with extraordinary long names are all TIF
>(Temporary Internet Files), and among the less important of
>them, so I try to delete them by hand.
>
>I can easily delete by hand the other ~10 files that return the
>same error, but this one won't be deleted, returning:
> ____________________________________________________________
> | Error Deleting File or Folder
> |____________________________________________________________
> | Cannot delete file: The filename you specified is
> | X invalid or too long.
> | Specify a different filename.
> |
> | | OK |
> |____________________________________________________________
>
>That file exists in HD1 and HD2, but not in HD3 (since renaming
>failed and the ~PGTEMP.TMP file, being temporary, has been
>deleted).
>
>As a result, I have the main disk of one of my PCs, HD1, that
>contains a file that can't be read, or moved, or deleted;
>however, and oddly, no message or error is issued when
>defragging that HD1 disk.
>
>But it remains that this HD1 disk is vulnerable; I don't dare
>doing ScanDisk on it (I lost 2 entire HDs with all their data a
>few years ago with this same error or very similar, when Windows
>decided on its own to perform a ScanDisk - with a gentle message
>saying something like, from my memory, "to protect integrity of
>your data"...).
>
>I want to make clear that:
>
>1. the real problem is not with the failed renaming or copying
> in HD3 (curiously the problem never comes in HD2), but with
> the initial file (in HD1) being unable to be read or moved or
> deleted, with all the expected grave failures that this may
> cause;
>2. my backup is not contributing to that real problem, it only
> unveils it.
>3. the faulty files are TIFs made by some sites (mostly forums)
> that seem to store data on my computer in file *names* (and
> sometimes in file *types* BTW) instead of in file *contents*.
> But, the data in those filenames (and contents when it can be
> read) is unreadable for me and doesn't help me guess the
> faulty sites.
>
>So the only solution I have to get rid of that dangerous wrong
>file, is to reformat HD1, with all the time loss (and risks)
>involved in the implied backup and restore.
>
>So I would like 2 things:
>
>1) Anyone can tell me how to avoid such problem in the future,
> or to work around it more simply and time efficiently?
>
>2) Can Microsoft cure its software to remove that problem?
> (which most probably comes from some Windows components
> used in Windows Explorer and in 3rd-party programs like
> backup programs)?
>
>Paris, Tue 19 Apr 2005 14:39:20 +0200
.
- Follow-Ups:
- Cache is often underestimated and poorly managed
- From: Michel Merlin
- Cache is often underestimated and poorly managed
- References:
- Too long filenames wrongly handled by Windows
- From: Michel Merlin
- Too long filenames wrongly handled by Windows
- Prev by Date: Autorun on shutdown
- Next by Date: Re: Video Card question
- Previous by thread: Re: Clear cache will use same components - backups must restore!
- Next by thread: Cache is often underestimated and poorly managed
- Index(es):
Relevant Pages
|
