🚀 go-pugleaf

I had a few questions regarding National Language Support features 
of DOS/Windows;

-What is the structure of country.sys ? does one need device driver 
 documentation, since there in no information in the DOS programmer 
 manuals. The country.sys file provided with DOS only covers generic
 languages. I was interested in doing a brand new one.

-If thats too hard, can one grab the pointer to conversion table routines

 Get Uppercase Table
 Get filename Uppercase Table
 Get Filename char Table
 Get Collate-Sequence Table 

 and modify the current pointer to some TSR area with my own tables?
 This would basically bypass an existing setup.

-The reason I am doing all this hard work, is because of Windows/DOS
problem regarding ANSI vs OEM character sets. (yuk yuk). To correctly
create DOS files  from Windows, Windows only allows you enter "legal"
DOS OEM characters. The conversion between the two is determined at
Install time. Per documentation, Windows looks at the code page info
of DOS and builds appropriate tables.  (Is this what the oemansi.bin
file is all about?)  So one needs to have the DOS in appropriate state
before installing Windows in order to get the appropriate functionality
at Windows level.

Any advice on any of this would be appreciated.


-anoosh
-- 
-----------------------------------------------------------------------
| Silicon Graphics Inc./MIPS Technology Inc.   	| anoosh@mti.sgi.com  | 
| 2011 N. Shoreline Blvd. M/S 10U-178           | anoosh@sgi.com      |
| Mountain View, CA  94039 USA.               	| 415-390-4497	      |