Micro Channel Digiboard PC/XEM Fails Under Windows NT

Last reviewed: September 5, 1995
Article ID: Q132554

The information in this article applies to:

Microsoft Windows NT Workstation versions 3.5 SP2 and 3.51
Microsoft Windows NT Server versions 3.5 SP2 and 3.51

SYMPTOMS

After you install Windows NT 3.5 Server Pack 2 or Windows NT 3.51, your asynchronous Digiboard PC/XEM micro channel adapter stops working. The following messages are written to the event log:

   Source: SCM
   Event ID: 7000
   Description: Digi fep 5 driver service failed to start due to the
                following error:

                   No mapping between account names and security id's was
                   done.

   Source: DIGIFEP5
   Event ID: 5
   Description: The description for event id %5% in source digifep5 could
                not be located. It contains the following insertion
                string(s),NTXEM2.

CAUSE

Windows NT does not correctly save the slot number in the registry on MCA computers. The slot number is incorrectly saved as 0.

Also, the Digiboard driver downloads its configuration information to the board during initialization. If the computer is not cold booted (turned off) between configuration changes, the driver will not reinitialize the board on the next boot.

WORKAROUND

To work around this problem, run Registry Editor (REGEDT32.EXE) and modify the following key in the HKEY_LOCAL_MACHINE hive to manually change the slot number:

   \System\CurrentControlSet\Services\NTXEM2\Parameters\Slot Number

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

If you have already installed the Digiboard driver, unistall it and reboot (cold boot) the computer.
Use the Microchannel Reference floppy disk that was supplied with the computer to confirm that the Digiboard has been configured properly and the reboot (cold boot) the computer.
Boot Windows NT and install the Digiboard driver. Do not reboot the computer.
Run Registry Editor (REGEDT32.EXE).

From the HKEY_LOCAL_MACHINE subtree, go to the following key:

      SYSTEM\CurrentControlSet\Services\NTXALL[1-n]\Parameters

Change the value for SlotNumber to the correct slot number.
Run Control Panel, choose Network, and configure the Digiboard. The correct slot number will appear and Setup will reconfigure the other values correctly. Quit Control Panel, but choose not to reboot the computer.
Shutdown the computer and then reboot (cold boot) it again:
a. From the Program Manager File menu choose Shutdown.
b. Choose Shutdown and then choose OK.
This allows any configuration currently saved in the Digiboard to be cleared, allowing Windows NT to reinitialize it during the next boot process.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5 SP2 and 3.51. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbother kbbug3.50.sp2 kbbug3.51
KBSubcategory: ntdriver ntsetup ntras
Additional reference words: 3.50 3.51 prodnt ras zero micro channel

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: September 5, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.