System File Changes Installing Xircom CE10 Ethernet Adapter

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

SUMMARY

This article lists the changes made to your SYSTEM.INI, AUTOEXEC.BAT, and CONFIG.SYS files when you install the Xircom CE10 Credit Card Ethernet adapter. It also discusses the PROTOCOL.INI file that Setup creates for this adapter.

MORE INFORMATION

AUTOEXEC.BAT

C:\WINDOWS DIRECTORY\NET START

CONFIG.SYS

Device=C:\WINDOWS DIRECTORY\IFSHLP.SYS

SYSTEM.INI

[BOOT] network.drv=WFWNET.DRV

[BOOT.DESCRIPTION] network.drv=Microsoft Windows Network (version 3.11)

[386ENH] network=*vnetbios, *vwc, vnetsup.386, vredir.386, vserver.386 netheapsize=20 netmisc=ndis.386, ndis2sup.386 transport=nwlink.386, nwnblink.386, netbeui.386 InDOSPolling=FALSE

[NETWORK] winnet=wfwnet/00025100 Username=username Workgroup=workgroup ComputerName=computername

[NETWORK DRIVERS] devdir=C:\windows directory LoadRMDrivers=YES netcard=cendis.exe transport=ndishlp.sys,*netbeui

[NWBLINK] lanabase=1

PROTOCOL.INI File

[NETWORK SETUP] version=0x3110 netcard=cendis,1,CENDIS,1 transport=ms$nwlinknb,NWLINK transport=ms$ndishlp,MSNDISHLP transport=ms$netbeui,NETBEUI lana0=cendis,1,ms$netbeui lana1=cendis,1,ms$nwlinknb lana2=cendis,1,ms$ndishlp

[PROTMAN] Drivername=Protman$ Priority=MS$NDISHLP

[CENDIS] Drivername=XIRCOM$ INT=10 (or other IRQ adapter configured for) IOADDRESS=0x300 (or other address configured for) MEM=0xC800 (or other starting memory address configured for) IOWORDSIZE=16 SOCKET=1 (socket that lan adapter installed in)

[NWLINK] Bindings=CENDIS

[MS$NDISHLP] Drivername=ndishlp$ BINDINGS=CENDIS

[NETBEUI] Drivername=netbeui$ SESSIONS=10 NCBS=12 BINDINGS=CENDIS Lanabase=0

PROTOCOL.INI

Setup also creates a PROTOCOL.INI file when you install the Xircom adapter.(If PROTOCOL.INI already exists, Setup modifies it.) Sometimes the PROTOCOL.INI settings do not match the CONFIG.SYS settings for the Credit Card adapter, which causes it to fail. If this happens, compare your PROTOCOL.INI settings with the relevant CONFIG.SYS lines and modify any inconsistent settings.


KBCategory: kbnetwork kbsetup kbhw kb3rdparty
KBSubcategory: wfw wfwg
Additional reference words: 1.00 3.11 Xircom PCMCIA CE10 creditcard


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.