3 ms·

You are right, it's likely to be the conversion from OEM to ANSI. In that case, NT wouldn't have the same bug, since it uses Unicode internally (and the tables

You are right, it's likely to be the conversion from OEM to ANSI. In that case, NT wouldn't have the same bug, since it uses Unicode internally (and the tables translate OEM character 255 to U+00A0). The forum post seems to be about this directory in the leaked 3.5 source: https://github.com/Hengle/windows_nt_3_5_source_code/tree/master/windows_nt_3_5_source_code/NT-782/PRIVATE/MVDM/WOW16/KERNEL31 https://github.com/Hengle/windows_nt_3_5_source_code/tree/ma...

ale42 2y ago
Great question, what would happen if NT sees a FAT filesystem (therefore with 8.3 names stored in OEM charset) with a filename containing a Alt+255 (0xFF) character? Anybody with a ready VM around to test this?
ale42 2y ago
Quickly had a look in the KERNEL31 source. The LDOPEN.ASM file contains calls to a routine called MyOemToAnsi, which does the character set conversion. In turn, that function either calls the actual conversion routine in the keyboard driver, or does nothing if there's no keyboard driver yet (boot phase). Didn't find the keyboard driver part, probably not part of the actual kernel so it makes sense that it's not there. Anyone knows where to find one?