Issues with Windows 98 on Other Third-Party Networks

Both protected-mode, 32-bit, and real-mode, 16-bit network clients are available for most network clients. You should use 32-bit, protected mode network clients whenever possible. Protected-mode, 32-bit clients offer the following benefits:

• Easy installation and configuration using built-in Windows 98 tools.
• Performance enhancements, such as Plug and Play networking support, long file names, client-side caching, and automatic reconnections.
• Greater stability than with real-mode clients.
• Ability to run additional 32-bit, protected-mode clients simultaneously.
• Integration with the Windows 98 environment, including the Windows 98 unified logon, Network Neighborhood, and Windows 98 network management tools.

You should install 32-bit clients after you have finished Windows 98 Setup. If you have a 16-bit client on your computer before Windows 98 Setup, contact your network vendor for information about how to upgrade to the 32-bit clients.

Contact your network vendor for their latest installation INF file.

Note

Be sure to read the Windows 98 Readme.txt, Setup.txt, and Network.txt notes on networking. Also check the Microsoft WinNews forums on online services for specific information about your network and about particular adapters.

Overview of Installing Support for Other Networks

This section gives an overview of installing both 32-bit clients and 16-bit clients, and it describes how to install Microsoft Client for Microsoft Networks after another network client has been installed.

Installing 32-bit Clients

You should install 32-bit clients after you have run Windows 98 Setup. For installation details related to your specific network, see the section for that network.

Installing 16-bit Clients

This section describes how to install Windows 98 16-bit clients from another vendor. For installation details related to your specific network, see the section for that network or contact your network vendor.

You can add real-mode, third-party support to Windows 98 in one of two ways:

• Add network support before upgrading to Windows 98. In most cases, Setup retains networking components. (One exception is Novell NETX. For more information about upgrading Novell NETX, see "Installing or Upgrading a Real-Mode Novell Client" earlier in this chapter.) You should be sure that the network client is installed correctly under MS-DOS, Windows 3.1, Windows for Workgroups, or Windows 95.
• Add network support after upgrading to Windows 98.

On most computers running multiple clients, Windows 98 Setup stores all real-mode networking components, including Protocol.ini, in the \Windows directory. (For computers running Novell’s VLM, Windows 98 Setup stores these components in the Nwclient directory.) On computers running a real-mode client as the primary network, the networking components are left in place. The settings in Protocol.ini affect only real-mode NDIS drivers. Changing these values has no effect on protected-mode NDIS drivers. If you need to change settings in Protocol.ini, use the Network option in Control Panel whenever possible. For information about Protocol.ini entries, see Chapter 16, "Windows 98 on Microsoft Networks."

Note

Microsoft does not support upgrading over any real-mode clients other than NETX, VLM, and Banyan VINES 7.1 or later. Consult the Network.txt file for more information about support boundaries for real-mode clients.

Installing Client for Microsoft Networks with Other Networks

If you want to install the 32-bit, protected-mode Client for Microsoft Networks in addition to a network client from another vendor, and if the client is not already installed, follow these steps. For more information about configuring and using Client for Microsoft Networks, see Chapter 16, "Windows 98 on Microsoft Networks."

To install Client for Microsoft Networks after another client has been installed

1. After Windows 98 Setup, in Control Panel double-click Network.
2. In the Network dialog box, click Add. In the Select Network Component Type dialog box, double-click Client.
3. In the Select Network Client dialog box, click Microsoft in the Manufacturers list, and click Client for Microsoft Networks in the Network Clients list. Click OK.
4. Usually hardware detection detects the correct network adapter and selects the corresponding driver. If you must add a network adapter, follow the steps in Chapter 14, "Introduction to Networking Configuration."
5. In the Network dialog box, double-click the network adapter in the list of components. Verify the settings in the properties for the network adapter. Then click OK. For information, see Chapter 15, "Network Adapters and Protocols." See also the documentation for your network adapter to verify its software settings.

   Setup automatically installs a protected-mode version of any protocol that the installed network clients are using. If you need to install another protocol, follow the steps in Chapter 14, "Introduction to Networking Configuration."

6. Shut down and restart the computer.

Using Real-Mode WinNet16 Drivers

In addition to multiple 32-bit Windows 98 network providers, Windows 98 can also support a single 16-bit WinNet driver. This is the basic configuration that must be used for a network product that does not offer a 32-bit network provider.

If the 16-bit network provider from another network vendor does not provide a browsing scheme, Network Neighborhood will be empty. This indicates that it is not a browsable network. You must use the Map Network Drive dialog box for network access. Also, notice that a drive connected through the Windows 98 user interface is accessible in all command prompt boxes. (However, it is accessible only from Windows 98 command prompt boxes, not when you reboot in MS-DOS mode.) A connection made at a command prompt, however, will be available in that command prompt box only and will not be available throughout the Windows 98 user interface.

Table 17.19 summarizes the components for the 16-bit, real-mode network drivers.

Table 17.19 Components for real-mode network drivers