site  contact  subhomenews

VFAT codepage fixed

May 21, 2009 — BarryK
There has been some discussion recently on this blog and feedback on the Woof alphas on the forum, about the on-going problem with non-English characters and the vfat filesystem.

The advice given to me, that has been applied to some other puplets, to change the default codepage from 437 to 850 and the iocharset from iso8859-1 to utf8, seems to be not such a good idea -- see my recent post explaining why.

So, I configured the kernel with 437 and iso8859-1, as per all previous official puppies.

Instead, it is better to modify the codepage and iocharset when mounting the vfat partition. This can be done by appropriate parameters to the 'mount' command. Here is explanation from the 'mount' manpage:

Sets the codepage for converting to shortname characters on FAT and VFAT filesystems. By default, codepage 437 is used.
Character set to use for converting between 8 bit characters and 16 bit Unicode characters. The default is iso8859-1. Long filenames are stored on disk in Unicode format.

What I have done is put some code into /usr/sbin/pmount and /usr/local/bin/drive_all that provides the codepage parameter. I should really have placed this common code elsewhere, but for now it is duplicated in both scripts:


#w476 modify codepage and iocharset...
#note, could also set iocharset=iso8859-2 (default: codepage=437, iocharset=iso8859-1)
if [ -f /etc/keymap ];then #set in /etc/rc.d/
KEYMAP="`cat /etc/keymap | cut -f 1 -d '.'`"
case $KEYMAP in
mount -t vfat -o shortname=mixed,quiet${CODEPAGE_PARAM} $DODEV /mnt/$DEVNAME #v411 added quiet.

It is not necessary to create an entry in /etc/fstab, the above code should take care of the situation automatically.

However, I need help. As you can see, it only tests for "de", which is fine for MU. For anyone interested in this topic, could you look at the Keyboard Wizard in the Setup menu and figure out what codepages are appropriate for the other keyboard layouts?

The default is 437, which is fine for USA/Canada/Australia. I think 850 is fine for Western European countries? Eastern European keyboard layout need a different codepage?

If I can get some help on this, I can flesh out that case statement. For example, if Denmark and France keyboards are to also have codepage 850:

case $KEYMAP in


Problem mounting vfat partition with upupsave.2fs file
Username: Leon
I modified /usr/sbin/pmount and /usr/local/bin/drive_all and this code works for sl_SI locale: [i]case $KEYMAP in slovene) CODEPAGE_PARAM=',codepage=852,iocharset=iso8859-2'[/i] It works in Puppy 4.1.2 and upup-473. [b]Problem mounting vfat partition with upupsave.2fs[/b] My upupsave.2fs is located on vfat partition and I modified the init script and initrd.gz file to properly mount it. I changed the line 687 from: [i]mntfunc -t $PUPSAVEFS -o noatime /dev/$PUPSAVEDEV /mnt/dev_save[/i] to: [i]mntfunc -t $PUPSAVEFS -o noatime,shortname=mixed,codepage=852,iocharset=iso8859-2 /dev/$PUPSAVEDEV /mnt/dev_save[/i] When rebooted the boot process ended with syncing error and kernel panic after [i]Loading the upup_473.sfs main file...[/i] boot information message was displayed. [b]Information that you search for[/b] National language keyboard types and SBCS code pages See the last column: IBM Personal Computer SBCS code page ISO/IEC 8859 See: The Parts of ISO/IEC 8859

iso8859-2 iocharset
Username: BarryK
"Leon, Thanks for your feedback. I think the problem at bootup is because the nls_iso8859-2.ko module is not there. I'll see if I can get that fixed for alpha9.

Good 'ol OS/2 handbook for keyboards and code pages
Username: pakt
"This little booklet for IBM's OS/2 Warp (remember that :n_n:) sums up international keyboards and code pages. It may not be up-to-date though :worried:

init and vfat
Username: BarryK
"Leon, I have just done a quick thing for alpha9, as I don't have much time. The 'init' script will recognise the 'pkeys' kernel boot parameter, so if you put "pkeys=slovene" then vfat partition will mount with the correct codepage and iocharset. It needs further attention though, that I will look at later. For example, 'pkeys' was only intended for the "old 2-letter" keyboard layout system, which has less choices. Perhaps the time has come to dump that old system. For alpha9, if you use "pkeys=slovene", which is not one of the old 2-letter codes, then it doesn't work later on in the script.

'pkeys' kernel boot parameter
Username: Leon
"Barry, Thanks for fixing the 'init' script. Boot parameter seems to be a good choice to keep the filenames display settings independent of other locale settings. Someone that not use locale specific character in filenames might want to keep default kernel settings. Properly displayed filenames are important for me because I share my data files among Windows 98 SE, Windows Vista and Puppy. The final solution is near and it's worth the efforts.

Tags: woof