home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!sgigate!odin!mips!anoosh
- From: anoosh@mips.com (Anoosh Hosseini)
- Newsgroups: comp.os.msdos.programmer,comp.os.ms-windows.programmer
- Subject: country.sys and more
- Message-ID: <1hm203INNn7k@spim.mti.sgi.com>
- Date: 28 Dec 92 05:06:11 GMT
- Organization: SGI/MIPS
- Lines: 37
- NNTP-Posting-Host: wildcat.mti.sgi.com
- Originator: anoosh@wildcat.mti.sgi.com
-
- 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 |
-