codepage

  • Thread starter Thread starter sali
  • Start date Start date
S

sali

xp, set up for national language, language/keyboard functions properly,
there is lang icon on taskbar, etc ...

problem is that cmd starts with 437 code page, instead of oem regional,
usualy belonging to this local/regional settings.

there is no entry either in autoexec.nt nor config.nt nor cmd's pif file
found to change codepage with "chcp" or "mode con" at cmd starting.

is there some other place where 437 codepage may be forces instead of
regional?
any idea what else to check to solve the problem?

thnx.
 
In said:
xp, set up for national language, language/keyboard functions
properly, there is lang icon on taskbar, etc ...

problem is that cmd starts with 437 code page, instead of oem
regional, usualy belonging to this local/regional settings.

there is no entry either in autoexec.nt nor config.nt nor cmd's
pif file found to change codepage with "chcp" or "mode con" at
cmd starting.

is there some other place where 437 codepage may be forces
instead of regional?
any idea what else to check to solve the problem?
Click to expand...

One might make use of "Autorun" for CMD ("Command Processor")
HKEY_CURRENT_USER\Software\Microsoft\Command Processor\
and/or
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\
perhaps, and would be my first choice using the CHCP command.

There is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage\
OEMCP=437
but I do not know if changing this is safe or effective off-hand.
Probably researchable from your end.

There is good chance you will have issues with Copy/Paste to and
from CMD and the GUI parts of Windows. And filenames might be
effected too.

W2K
 
You did not state what language/codepage you should have.

In addition to what Mark V has posted.

437 codepage is United States.

codepage select= yyy

yyy value from table.
Value Country/Region
------------------------------
437 United States
850 Multilingual (Latin I)
852 Slavic (Latin II)
855 Cyrillic (Russian)
857 Turkish
860 Portuguese
861 Icelandic
863 Canadian-French
865 Nordic
866 Russian
869 Modern Greek

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Control\Nls\CodePage

Here's some info from various sources.

ACP is the default ANSI code page; OEMCP is the default OEM code page; and
MACCP is the default Macintosh code page.

The OEMCP value controls to which OEM code page to translate ANSI, and the
OEMHAL value controls the display of extended characters at a command
prompt.

the default OEM code page in Windows NT is the DOS 437 code page

The computer's ANSI code page is stored in the following registry value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage\ACP

For U.S. English versions of Windows NT, Windows 95, and Windows 98, the
default OEM code page is 437 (U.S. English). The computer's OEM code page is
stored in the following registry value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage\OEMCP

To verify the client OEM code page on Windows NT, Windows 95 and Windows 98
computers, run chcp from the command line. To verify that data in a file is
stored in the proper code page, you must use the appropriate editor. ANSI
data should look correct in any GUI editor (such as Notepad, WordPad, or
Microsoft Word). OEM data should look correct in a command-line tool (such
as type or edit).

This may be of some interest...
INFO: Windows, Code Pages, and Character Sets
http://support.microsoft.com/kb/75435

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
[mark, wesley]

yes, thnx, this oemcp registry solved the direct problem, now cmd starts
with desired codepage [regarding chcp and mode con commands], but, there is
still mess with cmd prompt displaying characters.

since computer is on client's location, i need more time to investigate what
char code is realy read from kbd and what is sent to display, and maybe just
raster font [vgaoem] is wrongly rendering, and what is the relation between
gui and txt programs.

i'll be back [when collect more data] ...
 
You're welcome.

I always manage to learn something myself when doing a little research. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Mark V said:
In said:
You did not state what language/codepage you should have.

In addition to what Mark V has posted.

437 codepage is United States.
Click to expand...
[ ... ]
This may be of some interest...
INFO: Windows, Code Pages, and Character Sets
http://support.microsoft.com/kb/75435
Click to expand...

Great info, thanks.
Click to expand...
 
Have fun. :-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
sali said:
[mark, wesley]

yes, thnx, this oemcp registry solved the direct problem, now cmd starts
with desired codepage [regarding chcp and mode con commands], but, there
is still mess with cmd prompt displaying characters.

since computer is on client's location, i need more time to investigate
what char code is realy read from kbd and what is sent to display, and
maybe just raster font [vgaoem] is wrongly rendering, and what is the
relation between gui and txt programs.

i'll be back [when collect more data] ...



Wesley Vogel said:
You did not state what language/codepage you should have.

In addition to what Mark V has posted.


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage\OEMCP

In
Click to expand...
Click to expand...
 
In said:
[mark, wesley]

yes, thnx, this oemcp registry solved the direct problem, now
cmd starts with desired codepage [regarding chcp and mode con
commands], but, there is still mess with cmd prompt displaying
characters.
Click to expand...
[ ]

Remember that (NTFS) the filename are actually stored in UNICODE...
It is all really a mess when working between GUI processes and a CMD
based interface. Or it can be anyway. <sigh>
 
Back
Top