MSINPUT Device Settings Not Read After Second Device Is Added

 Last reviewed: October 25, 1996
Article ID: Q120939
The information in this article applies to:
  • Microsoft Natural Keyboard with IntelliType software version 1.0
  • Microsoft IntelliPoint software version 1.0

SYMPTOMS

When you install a Windows-level MSINPUT device (IntelliType or IntelliPoint) on a system with an existing installation of the Microsoft IntelliType software or Microsoft IntelliPoint software with the MS-DOS level components only, the settings for IntelliType or IntelliPoint are not read correctly.

CAUSE

When you install IntelliPoint or IntelliType, the following additional line is added to the AUTOEXEC.BAT file: 

   SET MSINPUT=C:\MSINPUT
This environment variable sets the location of the MSINPUT.INI file where the settings for both IntelliType and IntelliPoint are located.

If IntelliType or IntelliPoint is installed with only MS-DOS-level components to a drive or directory other than the default (C:\MSINPUT), a second installation with Windows-level components overrides the first installation settings by changing the SET environment variable path for the MSINPUT.INI file. Functionality of either IntelliType or IntelliPoint may appear to be lost.

The settings for both IntelliType and IntelliPoint must reside in the same MSINPUT.INI file.

RESOLUTION

Make sure that both IntelliType and IntelliPoint are installed to the same drive and directory. If it is not possible to reinstall the second MSINPUT device to the same directory and path as the first, use the following steps:

  1. Edit the MSINPUT.INI file to reflect both IntelliType and IntelliPoint settings.

  2. Edit the AUTOEXEC.BAT file to reflect the correct drive and path for the SET MSINPUT=<drive>:\<path> environment variable.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Natural Keyboard with IntelliType and Microsoft Home and Standard Mouse with IntelliPoint versions 1.00. We are researching this problem and will post new information here in the as it becomes available.

MORE INFORMATION

You do not receive a warning message when installing a second MSINPUT device at the Windows level when the first MSINPUT device was installed with only MS-DOS-level components on a drive or directory other than C:\MSINPUT. However, the second installation does change the SET MSINPUT=<drive>:\<path> statement found in the AUTOEXEC.BAT file, leaving two separate incomplete MSINPUT.INI files, only one of which is actually read.

KBCategory: kbhw KBHW kbprb
KBSubcategory: mnk
Additional reference words: 1.00 MNK mouse mous natural natrl naturl
natral intelipnt intellipont intellityp intellitpe

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.

Last reviewed: October 25, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.