When you ran chkdsk you were running DOS or Windows. This means that a
code-page is set for the operating system at that time. When you insert
a USB disk, it is also running under that code-page. When you then run
chkdsk it checks characters based on the current code-page.
It has just occurred to
The chkdsk command is running with a specified code-page because it's
running within DOS or Windows. I strongly suspect that you'll find that
if you change the code-page, all kinds of nasty things will happen.
Again, if you can provide an actual specification that indicates that
these characters a
I don't doubt that you can use a bad character in a Linux
implementation. Also, the vfat module and dosfsck are not the same piece
of software and both read from the drive in completely different ways.
My point is that dosfsck is checking a FAT file system. The problem is
not that these characters
Uhm, both these characters, '\' and '|' *are* bad characters as a
non-Chinese (Big5) FAT filename AFAIK.
If you have a reference that says otherwise, let me know and I'll have a
look at it.
--
Problem in FSCK checking Chinese filename (Big5)
https://bugs.launchpad.net/bugs/49217
You received thi
Determining the code page number has been the largest issue. It is as
far as I've been able to investigate not detectable on the file-system
itself, which means that the end user is expected to supply it. That
really doesn't work.
Whilst investigating this I toyed with the idea of reading the
conf
Hi, just got your message. I'm currently away from my computer but I'm
still working on this. I expect to do some more when I return next
week. Would you be able to test versions if I release them? Or could
you create a tiny FAT file system that shows the problem so I can test
stuff as I'm fixing i
