VINES Err Msg: BAN: Unable to Read 'PCCONFIG.DB' with WFWG

 Last reviewed: November 21, 1994
Article ID: Q95879
The information in this article applies to:
  • Microsoft Windows for Workgroups versions 3.1, 3.11

SYMPTOMS

If Banyan VINES connectivity is installed and Windows for Workgroups has been installed on a drive other than drive C, the following error message may appear during startup when the BAN.EXE driver executes from the AUTOEXEC.BAT file: 

   BAN: Unable to read 'PCCONFIG.DB' configuration database.
In addition, this may cause the ARSWAIT.EXE terminate-and-stay- resident (TSR) program to stop the system.

CAUSE

This problem occurs because the Banyan VINES Setup program inserts the following line in the AUTOEXEC.BAT file 

   CD X:\WINDOWS
where X is the drive on which Windows for Workgroups is installed. This command changes the working directory on drive X but does not actually change to drive X. Because the BAN.EXE TSR must be executed from the same directory where the PCCONFIG.DB file is located, the drivers fail to load and the above error message occurs during startup.

WORKAROUND

To work around the error message, use any text editor to insert the following command line in the AUTOEXEC.BAT file prior to the CD X:\WINDOWS line (where X is the drive on which Windows for Workgroups is installed): 

   X:
Banyan VINES is manufactured by Banyan Systems, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

KBCategory: kbnetwork kb3rdparty kberrmsg
KBSubcategory: wfw wfwg winboot
Additional reference words: 3.10 3.11 3rdparty boot up lockup lock up hang
crash

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: November 21, 1994
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.