> Recently, mount has been telling me it can't find the NLS code page
> for my /msdos partition. I ignored the problem, but apparently that
> was a bad idea. I thought scandisk had gone bananas, until I realized
> that a) I haven't run scandisk or even booted into Win/DOS for a week or
> two, and b) scandisk doesn't use names like FSCK0000.BIN.
I don't have an fsck that works on FAT or VFAT file systems. It seems you
have one, but it doesn't work too well. It might be safer to stick with
DOS' own chkdsk and scandisk. If you put "0 0" for the dump and pass
fields (the last two) in your /etc/fstab, that should stop fsck from
messing with your DOS files.
Not to be the "Ugly American," I hope, but the answer to CONFIG_NLS seems
to be be a mandatory "yes." There isn't even a question about it.
Perhaps the configuration option should be eliminated.
___
Trevor Johnson