Thanks Neil, I passed this on to our PC technician and as we were
chewing on it, I found an IBM APAR that reflects our problem precisely.
That said, it's still no slam dunk as we're using a PC with a Japanese
OS so image START-PROGRAMS and everything else in Japanese.
The SE33915 APAR says:
In previous releases, System i Access for Windows included support for
installing secondary languages. Secondary languages allow users to
configure System i Access for Windows to display System i Access
features in different languages.
In V6R1, GA code of System i Access for Windows does not have secondary
language support.
The APAR does have several solutions so I'm confident this is just what
we need.
Bryan
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Neill Harper
Sent: Tuesday, January 11, 2011 1:00 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Invalid Host Code-Page with Windows 7
We had problems like this on XP.
Client access is not a Unicode enabled app. So it uses the non Unicode
language system setting to map code points to glyphs.
The below might help. You need to set your Language for non Unicode
programs to something more appropriate, but be warned this will affect
all of the non Unicode programs that the workstation user uses.
http://windows.microsoft.com/en-us/windows7/Change-the-system-locale
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Burns, Bryan
Sent: 11 January 2011 17:21
To: Midrange Systems Technical Discussion
Subject: RE: Invalid Host Code-Page with Windows 7
Thanks Steve but it's more complicated than that, Using:
- Windows 7 Professional - Japanese
- Office 2007 Professional suite - Japanese
- System I Access for Windows V6R1
Code page 037 (US) works, but code page 930 doesn't. In the past, we
could always get both code pages working with Japanese versions of
Windows (e.g. XP and 2000). Now with the combination of Windows 7,
system I Access for Windows V6R1 and system I 0S V5R4m5; it's not
working.
Bryan
midrange.com
