This article was previously published under Q90970
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
This article contains questions and answers about Windows for WorkgroupsSetup, network card settings, and important preliminary troubleshootingsteps.
The following information applies to Microsoft Windows(TM) forWorkgroups version 3.1.
Q. What are the memory and disk space system requirements for Microsoft Windows for Workgroups?
A. Windows for Workgroups must be run in 386 enhanced mode in order to share resources. 386 enhanced mode requires a minimum of 3 megabytes (MB) of memory; however, 4 MB is recommended. Standard mode operation requires a minimum of 2 MB of memory. These memory requirements refer to total conventional and extended memory only. Windows for Workgroups requires a minimum of 9.5 MB and a maximum of 14.5 MB of free disk space. Upgrading over Microsoft Windows operating system version 3.1 reduces these free disk space requirements to a minimum of 3.5 MB and a maximum of 8.5 MB. Workgroup Connections require 320 kilobytes (K) of free conventional memory and 1 MB of free disk space.
Windows for Workgroups must be installed on a workstation that has a hard disk drive. Windows for Workgroups and Workgroup Connections are supported on MS-DOS-based systems.
Q. I'm having difficulty installing Microsoft Windows for Workgroups. What should I do?
A. Complete information on installing Windows for Workgroups is contained in the "Getting Started" manual. The following are five general setup tips:
Before you run the Setup program, start your machine with a minimal configuration. For more information, please refer to the section titled "Streamline the CONFIG.SYS and AUTOEXEC.BAT Files" in Chapter 6 of the "Getting Started" manual. The examples provided in this manual refer to a minimum configuration after Windows for Workgroups is loaded. The last three lines in the CONFIG.SYS file and the first line in the AUTOEXEC.BAT file that relate to the network are not loaded before installation.
Windows for Workgroups installations are most successful when installed to a newly created and empty subdirectory. This applies to all packages of Windows for Workgroups, including upgrade packages. Upgrading over a Windows 3.x environment configured for a network other than Microsoft LAN Manager or Novell(R) NetWare(R) may cause incompatibility issues. If Windows 3.x is currently installed on your computer for a network, choose the Windows Setup icon, choose Change Systems Settings from the Options menu, and select the No Network Installed option before you run the Windows for Workgroups upgrade.
If your Windows 3.x environment is not installed for a network and you are using any third-party drivers, font software, desktop shells, or utilities, consider installing Windows for Workgroups to a different directory. If you choose to upgrade over the Windows 3.x directories, at least disable any third-party products from the Windows 3.x environment before you run Setup.
Workgroup Connections should be installed to a different subdirectory; do not upgrade over Windows. If you do so, a new SYSTEM.INI file is created.
During Setup, if your machine locks up, reboots itself, or displays corrupt images on the screen, Setup may have incorrectly recognized your hardware. For solutions to these problems, please refer to the section titled "Setting Up Windows for Workgroups" in Chapter 6 of the "Getting Started" manual.
Q. Where can I find more information about setup entries and the setup of supported network adapter cards?
A. To properly configure your network card, please refer to the complete instructions in the section titled "Setting Up a Network Card" in Chapter 6 of the "Getting Started" manual. The following are four general tips:
Entries referring to Workgroup and ComputerName should be limited to 15 characters. All other share names should conform to the MS-DOS file-naming convention, which consists of an eight-character maximum filename and an optional extension limited to three characters.
The Windows for Workgroups Setup may not always detect yournetwork card and its configuration accurately. For thisreason, you may want to choose Custom Setup so that you canmodify the network card configuration. This configurationcan also be changed in the Windows for Workgroups ControlPanel after Setup is complete.
Some cards, such as the Intel(R) EtherExpress(TM), may besoftware configurable; therefore, there may not be anyjumpers and/or switches on the card to configure the IRQ,I/O port, and RAM addresses. The Windows for Workgroupsnetwork card installation software configures these cards.
Windows for Workgroups supports only the NetBEUI protocol.The MSIPX protocol is available only after you install theoptional network functionality for Novell NetWare. Theprotocols conform to the Network Driver InterfaceSpecification (NDIS). If you want to use another protocol,obtain the NDIS-compliant protocol driver and anOEMSETUP.INF file from the software company that providesthe protocol.
Q. Where can I find information on installing unlistednetwork protocols and adapters?
A. Information on installing third-party networks and protocolscan be found on pages 152 and 204 of the "User's Guide." Thefollowing are six general tips:
For information about using the Microsoft LAN Manager TCP/IPprotocol with Microsoft Windows for Workgroups, please referto the Windows for Workgroups Resource Kit. For information onpurchasing Microsoft Data Link Control (DLC) and MicrosoftTCP/IP for Windows for Workgroups, Call Microsoft ConsumerSales at (800) 426-9400. Both TCP/IP and MSDLC are supportedby Microsoft LAN Manager support.
The MSIPX protocol is available only after you add NovellNetWare connectivity to Windows for Workgroups.
If you have an Ethernet adapter that can emulate either anNE1000 or an NE2000 network card, choose the NE1000-compatible adapter for an 8-bit card or the NE2000-compatible adapter for a 16-bit card in the Network Adapterdialog box.
If you have an ArcNet(R) adapter that conforms to theNetwork Driver Interface Specification (NDIS), select ArcNetCompatible in the Network Adapter dialog box.
If your network card is not listed in the Network AdapterCompatibility List, you must obtain the NDIS driver specificto your network card and the OEMSETUP.INF file from thevendor of your network card.
Q. I'm receiving the error message, "The Protocol Manager hasreported an incomplete binding." What is causing this error?
A. The error "The Protocol Manager has reported an incompletebinding" is most often caused by a conflict in the upper memoryarea or an incorrect setting in the PROTOCOL.INI file. Tocorrect the error, use the following two steps:
If the memory manager EMM386.EXE is loaded in the CONFIG.SYSfile, modify the line to read as follows:
Save this file and restart the computer. If the
error message continues after you modify theCONFIG.SYS file, the answers to the next two questions mayhelp you correct this problem.
Q. I'm still receiving the "incomplete binding" error messageafter I exclude the upper memory area with EMM386 in theCONFIG.SYS file. What should I try next?
A. If you still receive the "incomplete binding" error messageafter you have excluded the upper memory area, use thefollowing four steps to check for possible PROTOCOL.INI settingerrors:
In the Control Panel window, choose the Network icon.
Choose the Adapters button and note the brand name and modelof the network card listed under Network Adapter In Use. Ifthe network adapter is incorrect, choose the Remove button,then choose the Add button to select the correct driver.
Note the IRQ, I/O Port, and Base Memory addressconfigurations. If any of these settings is incorrect,change the entry to its correct setting. This configurationinformation can also be found by choosing the Setup buttonin the Network Adapter dialog box.
The last item to check is the protocol. You must have atleast one protocol selected in the dialog box titledProtocols In Use. Windows for Workgroups supports theNetBEUI protocol. MSIPX is only available after NovellNetWare connectivity is added to Windows for Workgroups.
Q. I'm still receiving the "incomplete binding" error messageeven after I have confirmed and corrected all the settings inthe PROTOCOL.INI file. What should I do now?
A. If you continue to receive the "incomplete binding" errormessage after you verify that all the settings in thePROTOCOL.INI file are correct, and if you are using the IntelEtherExpress adapter card, use the following three steps:
Turn off the computer and disconnect any cables from the card.
Attach a T connector to the card with two terminators on theT.
Restart the computer. If the message
The Protocol Manager has reported an incomplete binding
no longer displays, there is a problem with the cable.
Q. I'm running Microsoft Windows for Workgroups on a NovellToken Ring network and am receiving the error message
File server cannot be found.
What is causing this error?
A. If you are running on a Novell Token Ring network, the error
File server cannot be found
may be caused by loading ROUTE.COM in the AUTOEXEC.BAT file. Edit the AUTOEXEC.BAT fileand remove the line that loads ROUTE.COM. After you save thefile, restart your machine.
Q. I'm running on a Novell Ethernet network and am receivingthe error message
File server cannot be found.
What is causing this error?
A. If you are running on a Novell Ethernet network, the errormessage
File server cannot be found
may be caused by exceeding the user limit of the Novell software or by an entryin the PROTOCOL.INI file referring to the incorrect Ethernetframe type. If you have not exceeded your user limit on theNovell network, try correcting this problem by using thefollowing four steps:
In the Control Panel window, choose the Network icon, thenchoose the Adapters button.
Select the adapter that is bound to MSIPX, choose the Setupbutton, then choose the Advanced button.
Select Novell IPX from the Protocols In Use box, then choosethe Settings button.
In the Adapter Media Type Value box, you will see eitherNovell/Ethernet or Ethernet_II(DIX). Note which parameter isindicated, and then select the other Media Type parameter.
Q. I'm receiving the error message
NetBIOS session limit exceeded.
What is causing this error?
A. "NetBIOS session limit exceeded" refers to the number ofconnections that can be made to your server at any one time.This limit is affected by the number of sessions set in the[MS$NetBEUI] section of the PROTOCOL.INI file. Other protocolsrefer to variables other than SESSIONS. Please refer to yournetwork protocol documentation for more information. Use thefollowing four steps to increase the number of sessions:
Open the PROTOCOL.INI file from the WINDOWS directory in anASCII text editor, such as Microsoft Windows Notepad.
Locate the section titled [MS$NetBEUI].
Double the value following SESSIONS=. When you increase thevalue following SESSIONS=, you must also increase the valuefollowing NCBS=. The NCBS value should be double the valueof SESSIONS.