× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Doesn't work.

Philipp

Philipp Rusch schrieb:

Hello Vern,

I will give it a try ...

Thank you, Philipp

Vern Hamberg schrieb:

Philipp

I have a fix for some Remote Access stuff that affected OpsConsole when installed on Win2K-SP4. Is Remote Access related to Terminal Server? Let me know if you'd like me to send it.

Vern

At 04:05 PM 4/23/2004, you wrote:

Hi all,

we have a strange effect when installing Client Access Express
V 5.2.0 (with or without the latest serv pack, doasn't matter)
on a W2K Terminalserver with SP4 and all latest Hotfixes:
when starting a 5250 session (pcsws.exe) in a windows terminal
session (RDP-connection) an error comes up saying "PCSKBD110"
and something like unsupported/unrecognized keyboard.
When you go further to connect to the AS/400 system you get a
signon screen, but you cannot enter data, because the keys don't
work. Change language / keyboard settings does't change a thing.
When using this installation of CA directly from the console of
the terminalserver itself, there is no problem at all.
IBM has nothing in its PTF-database on this topic, Microsoft
*has* some knowledge base entries, stating that there is a
confirmed error in the "GetKeyboardType" function which causes
several applications to malfunction, e.g. IBM Personal Comm.
Microsoft only has a fix in conjunction with SMS-Server and
recommends a 202 MB huge patch to install as a cure.
But: we don't use SMS-Server and I see no way to install this
"Patch" without SMS being installed.
There *must* be another solution to this problem, if at all.

I hope somebody has an idea.

Philipp




_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.