T
tom
Guest
Re: Deleting undeletable files
hi i know how to basically delete files but the files i am trying to delete
keep saying acess denied it dosent let me do system restores and i cant even
view the folder the folder contains world of warcraft > wtf > user names >
characters. in that order i managed to delete most of them but there are
about 5 undeletable character files.? is there a way i can delete these?
"Cal" wrote:
> I managed to figure this out on my own...
>
> "Cal" wrote:
>
> > "Dave Patrick" wrote:
> >
> > > From a command prompt try;
> > >
> > > dir /x
> > > and try deleting them using their 8.3 short names.
> >
> > This helps me in most cases. There is a situation where the file name has a
> > "%" in it: TYPE%3~1
> >
> > When I try to delete this name (the 8.3 name for a much longer filename),
> > it comes back with File Not Found.
>
> It turns out the full path to the file was too long (not just the filename itself, since the 8.3 name still resulted in the problem).
>
> The file was about a dozen or more folders deep, with some of the folder names rather wordy. The solution was to rename the folders to something short, like "a".
>
> Cal.
hi i know how to basically delete files but the files i am trying to delete
keep saying acess denied it dosent let me do system restores and i cant even
view the folder the folder contains world of warcraft > wtf > user names >
characters. in that order i managed to delete most of them but there are
about 5 undeletable character files.? is there a way i can delete these?
"Cal" wrote:
> I managed to figure this out on my own...
>
> "Cal" wrote:
>
> > "Dave Patrick" wrote:
> >
> > > From a command prompt try;
> > >
> > > dir /x
> > > and try deleting them using their 8.3 short names.
> >
> > This helps me in most cases. There is a situation where the file name has a
> > "%" in it: TYPE%3~1
> >
> > When I try to delete this name (the 8.3 name for a much longer filename),
> > it comes back with File Not Found.
>
> It turns out the full path to the file was too long (not just the filename itself, since the 8.3 name still resulted in the problem).
>
> The file was about a dozen or more folders deep, with some of the folder names rather wordy. The solution was to rename the folders to something short, like "a".
>
> Cal.