Using DLC for Connectivity

For direct connection and communication with a mainframe computer that uses DLC, the DLC protocol must be installed on the client computer that is running Windows 95. The Microsoft DLC protocol works with either token-ring or Ethernet network adapter drivers.

Microsoft DLC is also used to provide connectivity to local area printers connected directly to the network. For example, DLC can be used for printing to a printer such as a Hewlett-Packard HP® LaserJet® 4Si that uses an HP JetDirect® network adapter to connect directly to the network (rather than to a port on a print server). The DLC protocol must be installed and running on the print server for the printer. Computers sending print jobs to a print server for a DLC network printer do not need the DLC protocol — only the print server requires DLC. To take advantage of the DLC protocol device driver, you must create a network printer in the Printers folder.

The following sections describe how to install the Microsoft DLC protocol and how to configure it with Novell NetWare ODI drivers and IBM LanSupport.

Note Windows 95 contains the most up-to-date Microsoft DLC protocol. Make sure you are running the latest version, which is also available from Microsoft Download Service (MSDL) and CompuServe. For more information about MSDL, see Appendix J, "Windows 95 Resource Directory."

Installing and Configuring Real-Mode Microsoft DLC

Architecture for real-mode DLC with NDIS 2 network adapter drivers

This section describes how to install the real-mode NDIS 2 Microsoft DLC protocol to bind with an NDIS 2 network adapter driver. This is an NDIS 2 protocol that, when installed, is bound to an NDIS 2 network adapter driver. The Windows 95 protected-mode protocols use the NDIS2SUP.VXD module to coexist with and run over the real-mode NDIS 2 network adapter drivers.

When you install Windows 95, Windows 95 Setup detects whether the computer already has the Microsoft DLC protocol installed; if so, Setup migrates the protocol and its settings to Windows 95. Otherwise, you can add Microsoft DLC as a protocol after Windows 95 is installed.

Note

You must install the version of Microsoft DLC provided with Windows 95. You cannot use the Microsoft DLC INF file from Windows for Workgroups 3.x to install this protocol; Windows 95 uses a new INF file format.

You can also install Microsoft DLC using setup scripts, as described in Appendix D, "MSBATCH.INF Parameters."

To install the Microsoft DLC protocol on a computer running Windows 95

In the Network option in Control Panel, click Add.
In the Select Network Component Type dialog box, double-click Protocol.
In the Select Network Protocol dialog box, click Microsoft in the Manufacturers list, and then click Microsoft DLC in the Network Protocols list. Then click OK.
Shut down and restart the computer for the changes to take effect.
Make sure that there is only one net start entry in AUTOEXEC.BAT, because Setup automatically adds an entry to support DLC, even if such an entry already exists.

The properties in the following table are set by default for real-mode Microsoft DLC. You can use the Network option in Control Panel to change these default values, or to set values for other parameters that you might use, in the Advanced properties for Microsoft DLC protocol.

Value	Description
Saps	Indicates the number of SAPs that can be opened simultaneously. The range for SAPs is 1 to 255 inclusive. The default is 3. For a description of SAPs, see the IBM Local Area Network Technical Reference. For more information about adjusting the SAPs value, see the entry for Stations.
Stations	Indicates the number of link stations that can be opened simultaneously. The range for stations is 1 to 255 inclusive. The default is 20. Each application requires a certain number of SAPs and stations. Because each SAP or station takes up memory, you should provide only enough for your application to run.
Swap	Turns on address bit-swapping when it is enabled and Microsoft DLC is bound to an Ethernet driver. The default is 1 (enabled).
Usedix	Sets the frame format. By default, this value is 0 (disabled), which is the correct value for 802.3 Ethernet format. Set this value to 1 for Ethernet DIX 2.0 (Ethertype 0x80D5) format. Ethernet DIX frames have an extra type-field.

The default values for Swap and Usedix are appropriate for most token-ring LAN environments. If the computer has an Ethernet adapter, then you should set the correct values for these parameters in the Advanced properties for Microsoft DLC. If you previously used the IBM DXME0MOD.SYS driver, use the following table to map the XMIT_SWAP parameter to set values for the two Microsoft DLC parameters.

DXME0MOD.SYS	Microsoft DLC Parameters
xmit_swap	Swap	Usedix
0	1	0
1	1	1
2	0	0
3	0	1

The following example shows some typical settings in AUTOEXEC.BAT and PROTOCOL.INI for Microsoft DLC with an Intel EtherExpress PRO LAN NDIS 2 network adapter driver on an Ethernet network. Notice that the [Msdlc$] section is added automatically by Windows 95 when the protocol is installed.

Sample Configuration File Settings for Microsoft DLC with NDIS 2 Adapters

Filename

Required settings

AUTOEXEC.BAT

net init
msdlc.exe
net start

PROTOCOL.INI

[netbeui$]
DriverName=NETBEUI$
Lanabase=0
sessions=10
ncbs=12
Bindings=EPRO$

[nwlink$]
DriverName=nwlink$
Frame_Type=4
cachesize=0
Bindings=EPRO$

[epro$]
DriverName=EPRO$
INTERRUPT=10
ioaddress=0x300

[protman$]
priority=ndishlp$
DriverName=protman$

[ndishlp$]
DriverName=ndishlp$
Bindings=EPRO$

[data]
version=v4.00.000
netcards=EPRO$,*PNP8132

[msdlc$]
DriverName=msdlc$
stations=20
saps=3
swap=0
usedix=1
Bindings=EPRO$

Configuring Microsoft DLC with ODI Drivers

Architecture for real-mode DLC with ODI network adapter drivers

For computers that are running Microsoft DLC with ODI drivers using the Novell-supplied ODINSUP.EXE file, Windows 95 Setup installs over this configuration and leaves entries for ODINSUP and MSDLC in AUTOEXEC.BAT. Microsoft does not provide direct support for Microsoft DLC used with ODINSUP.EXE.

If you must run a real-mode network redirector or TSR (NETX.EXE, VLM.EXE, and so on), you need to configure Microsoft DLC by binding the Microsoft DLC protocol to an ODI network adapter driver, as shown in the illustration. Otherwise, install Microsoft DLC over NDIS 2 with the protected-mode Microsoft Client for NetWare Networks.

The following table shows settings used to configure Microsoft DLC with ODI drivers.

Configuration File Settings for Real-Mode Microsoft DLC over ODI Drivers

Filename	Required settings
AUTOEXEC.BAT	lsl ;Novell-supplied component mlid_driver.com ;Novell-supplied component odinhlp.exe ;Windows 95 component odinsup.exe ;Novell-supplied component msdlc.exe ;Windows 95 component net start netbind ;Windows 95 component
NET.CFG	Protocol ODINSUP Bind EPROODI BUFFERED Link Driver EPROODI Port 300 Frame Ethernet_802.2 Frame Ethernet_802.3 Frame Ethernet_II Frame Ethernet_Snap
PROTOCOL.INI	[protman$] priority=ndishlp$ DriverName=protman$ [ndishlp$] DriverName=ndishlp$ Bindings= [data] version=v4.00.000 netcards= [nwlink$] Frame_Type=4 cachesize=0 DriverName=nwlink$ [msdlc$] DriverName=msdlc$ xstations0=0 xstations1=0 stations=20 saps=3 xsaps0=1 xsaps1=1 swap=0 usedix=1 Bindings=EPROODI [EPROODI] Drivername=EPROODI INTERRUPT=10 ioaddress=0x300

Upgrading Existing IBM LanSupport Installations

If you are using DLC support supplied by IBM to connect to host computers, Windows 95 Setup can detect IBM DLC; it leaves the installation intact and configures Windows 95 to run over that configuration. Although support for IBM DLC can be installed using the Network option in Control Panel, the required components must be provided by your network vendor.

This section describes two typical IBM LanSupport configurations, using DXMC0MOD.SYS and DXME0MOD.SYS.

DXMC0MOD.SYS, the monolithic IBM DLC driver.

For this configuration, Windows 95 Setup does one of two things:

If the computer is running NetWare, Setup keeps the DXMC0MOD.SYS driver and related settings, and installs the Generic ODI driver plus Microsoft Client for NetWare Networks, or keeps the real-mode client, as described in Chapter 9, "Windows 95 on NetWare Networks."
If the computer is running DXMC0MOD.SYS and no other networking components, Setups keeps the DXMC0MOD.SYS driver and does not install any Windows 95 networking components.

The following shows a sample configuration for IBM DXMC0MOD.SYS with Microsoft Client for NetWare Networks.

Example of Configuration Settings for DXMC0MOD.SYS with ODI Drivers

Filename	Required settings
AUTOEXEC.BAT	lsl ; Novell-supplied component lansup ; Novell-supplied component odihlp.exe ; Microsoft component
CONFIG.SYS	device=path\dxmaood.sys ;IBM-supplied component device=path\dxmcomod.sys ;IBM-supplied component

DXME0MOD.SYS, the NDIS driver for IBM DLC.

For this configuration, Windows 95 Setup does one of three things:

Architecture for real-mode DLC with NDIS 2 network adapter and IBM LanSupport

If the computer is running DXME0MOD.SYS and no other networking components, Setup keeps the DXME0MOD.SYS driver and does not install any Windows 95 networking components.
If the computer is running DXME0MOD.SYS and Novell NetWare, Setup installs an NDIS network adapter driver plus Microsoft Client for NetWare Networks, and leaves the DXME0MOD.SYS driver intact.
If the computer is running DXME0MOD.SYS with the IBM DOS LAN Requestor, Setup installs an NDIS 2 adapter driver, keeps the DXME0MOD.SYS driver, installs Client for Microsoft Networks, and removes the IBM DOS LAN Requestor redirector components.

The following shows a sample configuration for IBM DXME0MOD.SYS with Client for Microsoft Networks using an NDIS 2 adapter driver. The same basic kinds of settings are used for a computer running Microsoft Client for NetWare Networks with an NDIS 2 adapter driver.

Example of Settings for DXMCE0MOD.SYS with Client for Microsoft Networks

Filename	Required settings
AUTOEXEC.BAT	net start netbind
CONFIG.SYS	device=c:\windows\protman.dos /i:c:\windows device=c:\windows\epro.dos ;ndis2 driver device=c:\lsp\dxma0mod.sys ;IBM-supplied device=c:\lsp\dxme0mod.sys ,,3 ;IBM-supplied device=c:\windows\ndishlp.sys ;Windows 95
PROTOCOL.INI	[protman$] priority=ndishlp$ DriverName=protman$ [ndishlp$] DriverName=ndishlp$ Bindings=EPRO$ [data] version=v4.00.000 netcards=EPRO$,*pnp8132 [netbeui$] DriverName=NETBEUI$ Lanabase=0 sessions=10 ncbs=12 Bindings=EPRO$ [nwlink$] DriverName=nwlink$ Frame_Type=4 cachesize=0 Bindings=EPRO$ [EPRO$] DriverName=EPRO$ INTERRUPT=10 ioaddress=0x300 [DXMAIDXCFG] dxme0_nif=dxme0.nif dxmj0mod_nif=dxmj0mod.nif smcdosjp_nif=smcdosjp.nif smcdosjp2_nif=smcdosjp.nif smcdosat_nif=smcdosat.nif smcdosat2_nif=smcdosat.nif smcdosmc_nif=smcdosmc.nif smcdosmc2_nif=smcdosmc.nif [ETHERAND] DriverName=DXME0$ Bindings=EPRO$