KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q47254: SideKick 1.56x Causes Problems with Keyboard Input

Article: Q47254
Product(s): See article
Version(s): 2.01
Operating System(s): MS-DOS
Keyword(s): ENDUSER | S_QuickASM | mspl13_c
Last Modified: 10-OCT-1989

Borland's SideKick Version 1.56x has been found to cause problems
with keyboard input in QuickC and QuickAssembler.

The following routines have been observed to show the problem with
SideKick loaded: gets, getch, getche, cgets, cscanf, scanf, and kbhit.

In all cases, when a program requiring keyboard input is run with one
of these routines, input does not occur as expected. The first 15 keys
pressed during a call to one of these run-time library functions do
not appear on the run screen. The 16th and all following keys are
received by the input function/procedure. Upon termination of the
program being run under the QuickC environment, the 15 keys pressed
during run time appear on the QuickC editing screen.

To alleviate this problem, either do not load SideKick after booting,
or use the Hot-Key combination to remove it from memory. The key
combination should be used at the DOS command prompt, as follows:

   CTRL+ALT (To call up the main selection window), then
   CTRL+HOME+END

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.