Undeletable Files (PMV1026; CHCP 850 may cure)

Still trying to rebuild my system after a hardware
problem, I ran into some files containing accented
characters. These files did contain data but couldn't
be typed, edited, viewed, or accessed in any way. I
couldn't rename them with the CLI or PMShell. The
CLI said file not found, the PMShell said PMV1026,
filename too long (it wasn't). I couldn't even erase
the stubborn files with *.*, or shred their parent
directory. I tried using exact character matches
using ALT-xxx and so forth as well.

There is an old Newgroup message from Bruce B.
Kitchen, 'Undeletable files' (Oct. 15, 1997) which
sounds exactly like this problem. But at that time
the only thing anyone found that worked was to back
up and reformat the partition to purge the stubborn
files.

Well, I just tumbled to a different solution. I
used CHCP 850 to change the code page from 437 to 850,
and was immediately able to access and purge the
unwanted files. Apparently, using ALT-this and that
to enter unusual filename characters is not always
effective. In at least some cases, you have to set
the code page to the same page in which a file was
originally created before you can get rid of it.

Just thought I'd post this in case anyone else ever
runs into the undeletable file problem again. Try
changing the code page (e.g. CHCP 850). If you are
lucky that might be sufficient and you won't have to
reformat your partition.

I'm also sort of curious as to why it could possibly
matter what code page is set, when you *can* enter the
exact filename using ALT codes. If anybody can explain
that it might be worth passing on.

Bye!

--
Walt Gregg (walt at w-gregg dot juneau.ak.us)

.

Relevant Pages

  • Re: Undeletable Files (PMV1026; CHCP 850 may cure)
    ... I got it solved using DFSee ... containing the wierd characters and edit them with DFSee. ... filename too long. ... Walt Gregg ...
    (comp.os.os2.misc)
  • Re: determine default filename encoding
    ... > Suse tech support for the way filename characters are represented, ... Characters are characters - just bytes. ... Then if that coding differed from the LANG coding ... filenames that were written in encoding X as they were written, ...
    (comp.os.linux.setup)
  • Re: unix filename restriction
    ... underscore _ and the dot. ... You could use other characters, ... never met a *human* defined path of more than 80 chars (most of the ... If you want to be very sure, limit your filename to the DOS limit of 8 ...
    (comp.os.linux.development.apps)
  • Re: Error Message: "The File Name is Not Valid or Too Long...."
    ... I, then, proceed to name that file using only valid characters. ... the destination folder. ... That is not counting the drive letter and slashes or the filename itself. ... (Again - not counting the extension/dot.) ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Cannot delete files
    ... There HAS to be an 8.3 filename! ... I've not been brave enough to tell it Yes on THIS folder, ... characters don't look quite the same in this email font; ... but the SFN was "NOD~1.EE". ...
    (microsoft.public.windowsxp.perform_maintain)