Consultor Eletrônico

CapsLock problem on Win95/98/ME WinChar character client

If you have CapsLock on when running the 8.2C and above character client (_progres.exe) on Windows95, 98 or ME, keys other than the
letter keys will act like the shift key is pressed.

For example, if you type 2 with CapsLock on, you'll get
the @ symbol. This problem is caused by a bug in Windows. Microsoft's console implementation on Win95/98 and ME does not always translate keys properly. This is not a problem on NT.

Progress includes a dll which can be used for a workaround to this problem. The name of the dll is prokey32.dll.
When this dll is used, we process keystrokes with different function calls which avoid the problem with CapsLock.

To make Progress use prokey32.dll, you need to put an empty file called prokey32.txt on your system. When we see that file, we know we should use the prokey32.dll. It needs to be put in one of the following locations:
- in the dlc\bin directory
(advantage: only one copy needed in a network scenario)
- in your working directory
(advantage: can enable on a per user basis)
- anywhere along your windows PATH
(if you don't like the above)

In earlier versions of 8.2 (8.2A and 8.2B), we used prokey32.dll in interpreting keystrokes by default. In 8.2C and above we do not automatically use that DLL. One of the reasons we decided to change the default behavior is that prokey32.dll adds extra processing for reading the keystrokes. Another reason is that Microsoft may fix this problem in a future release or servicepack for these Operating Systems, and we wanted to give users control over whether the dll is used.