///////// ///////// ///////// ///////// ///////// ///////// /////////  

NVIDIA Installation Guide for DOS NDIS and
	 NetWare DOS ODI Client Drivers
Version 1.11 
NVIDIA Corporation

///////// ///////// ///////// ///////// ///////// ///////// /////////  
 
Published by
NVIDIA Corporation
2701 San Tomas Expressway
Santa Clara, CA 95050
Copyright (c) 2001, 2005 NVIDIA Corporation. All rights reserved.

This software may not, in whole or in part, be copied through any means, 
mechanical, electromechanical, or otherwise, without the express permission 
of NVIDIA Corporation. Information furnished is believed to be accurate and 
reliable. However, NVIDIA assumes no responsibility for the consequences of 
use of such information nor for any infringement of patents or other rights 
of third parties, which may result from its use. No License is granted by 
implication or otherwise under any patent or patent rights of NVIDIA Corporation.

Specifications mentioned in the software are subject to change without notice.

NVIDIA Corporation products are not authorized for use as critical components 
in life support devices or systems without express written approval of NVIDIA
Corporation.

NVIDIA, the NVIDIA logo, and nForce are registered trademarks or trademarks 
of NVIDIA Corporation in the United States and/or other countries. 

Intel is a registered trademark of Intel. Microsoft, Windows, Windows NT are 
registered trademarks of Microsoft Corporation. Novell, NetWare, and ODI are 
registered trademarks of Novell. Other company and product names may be trademarks 
or registered trademarks of the respective owners with which they are associated.


\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\  
Table of Contents 
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\  

Chapter 1: Overview and System Requirements

	I.   About This Guide 
	II.  About the NVIDIA DOS NDIS Ethernet Driver 
	III. About the NVIDIA NetWare DOS ODI Client Driver
	IV.  System Requirements for NVIDIA DOS NDIS Ethernet Driver
 		- Hardware
     		- Operating System  
	V.  System Requirements for NVIDIA NetWare DOS ODI Client Driver
 		- Hardware
     		- Operating System  

Chapter 2: Installing the NVIDIA DOS NDIS Ethernet Driver

	I.   Using Norton Ghost Enterprise 
  		- Creating a Network Startup Disk Using the Template Method 
 	   	- Creating a Network Startup Disk Without Using the Template  
	II.  Using Microsoft Network Client  
     		- Creating a Network Startup Disk with OEMSETUP.INF
     		- Creating a Network Startup Disk Manually
	III. Using Microsoft/3Com LANMAN 
     		- Creating a Network Startup Disk with OEMSETUP.INF
    		- Creating a Network Startup Disk Manually

Chapter 3: Installing the NVIDIA Netware DOS ODI Client Driver

	I.   NetWare Client 16 Installations 
	II.  NetWare Client 32 Installations  

Appendix:   Glossary


\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ 
Chapter 1:	 OVERVIEW AND SYSTEM REQUIREMENTS
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ 

I.	About This Guide
	====================  

	Chapter 1 (this chapter) discusses the following topics:
		I.   About This Guide 
		II.  About the NVIDIA DOS NDIS Ethernet Driver 
		III. About the NVIDIA NetWare DOS ODI Client Driver
		IV.  System Requirements for NVIDIA DOS NDIS Ethernet Driver
 			- Hardware
     			- Operating System  
		V.   System Requirements for NVIDIA NetWare DOS ODI Client Driver
 			- Hardware
     			- Operating System  

	Chapter 2: "Installing the NVIDIA DOS NDIS Ethernet Driver" 	explains the 
		procedures to modify configuration files that will become part of
		your NVIDIA(R) DOS NDIS Ethernet startup disk for an
		 NVIDIA nForce(tm) MCP system.

	Chapter 3: "Installing the NVIDIA NetWare DOS ODI Client Driver" provides
		instructions for installing your NVIDIA NetWare DOS ODI Client 
		Driver on Novell Client 16 and Client 32 for DOS.

	Appendix A is a short Glossary.


II.	About the NVIDIA DOS NDIS Ethernet Driver
	=================================== 
	The NVIDIA DOS NDIS Ethernet Driver is an NDIS2 device driver for
	DOS. Two different system files are used in the driver architecture,
	NDIS.DOS and NVNDIS2.DOS.

	NDIS.DOS is the upper layer of the architecture and communicates with 
		higher level protocols such as TCP.
	
	NVNDIS2.DOS is the lower layer of the architecture and contains the 
		hardware-specific code.


III.	About the NVIDIA NetWare DOS ODI Client Driver
	=============================================== 
	The NVIDIA NetWare DOS ODI Client Driver is suitable for both NetWare 
	Client 16 and Client 32 for DOS. 

        The system file, NVODI.COM, is compliant with the Novell ODI Specification 
        for 16-bit DOS Client HSMs (Hardware Specific Modules).		


IV.	System Requirements for NVIDIA DOS NDIS Ethernet Driver
	=======================================================

	Before you install and use the NVIDIA DOS NDIS Ethernet driver, be sure 
	that you have met the following software, hardware, and operating system 
	requirements.
	
	A.  NVIDIA DOS NDIS Ethernet Driver Software
	------------------------------------------------------------
	Verify that you have the files that comprise the NVIDIA DOS NDIS Ethernet
	Driver set as listed below.

	Note: 	These files are supplied online or on disk, depending on the
		requirements of your organization.
 
	File Name 	Description
	============================================
	NDIS.DOS	NDIS2 wrapper
	NVNDIS2.DOS 	NVIDIA DOS NDIS Ethernet driver in DOS device driver format
	PROTOCOL.INI 	[Norton Ghost Enterprise] Protocol configuration file
	MCASSIST.CFG 	[Norton Ghost Enterprise] Template used to add NVIDIA
			Ethernet to supported adapter list
	MODIFY.EXE 	[Microsoft Network Client and Microsoft/3Com LANMAN] 
			Utility that adds NVNDIS2.DOS to the CONFIG.SYS file and
			copies NVNDIS2.DOS to the disk in the A: drive.
	OEMSETUP.INF 	[Microsoft Network Client and Microsoft/3Com LANMAN]
			Driver installation file for NVIDIA DOS NDIS Ethernet driver
        MSPROT.INI      [Microsoft Network Client] Sample Protocol.ini for Microsoft DOS 
                        Network Client provided for reference purposes. File is 
                        created from Windows NT 4.0 Server CD. TCPIP is the main 
                        network protocol. User needs to rename the file from 
                        MSPRTO.INI to PROTOCOL.INI.
        NVNDIS2.EXE     NVIDIA DOS NDIS Ethernet driver as a TSR program. This driver
                        provides the same functionality as NVNDIS2 except that it 
                        is an executable that can be loaded in a batch file or 
                        entered on the command prompt.
        
        

	B. Hardware
	------------------- 
	You need an NVIDIA nForce MCP system in order to install the NVIDIA DOS NDIS
	Ethernet driver software.

	C. Operating System
	----------------------------
	The NVIDIA DOS NDIS Ethernet driver can be installed and run on MS DOS, 
	PC DOS, and compatible DOS-based operating systems, as shown below.

	Examples of supported operating systems:

	Name				Operating System / Version
	============================================== 
	Norton Ghost Enterprise 	PC DOS 7.1 Revision 0
	Microsoft Network Client 	Windows 98 DOS version 4.10.2222
	Microsoft/3Com LANMAN 		DOS 6.22

V.	System Requirements for NVIDIA NetWare DOS ODI Client Driver
	=============================================================

	Before you install and use the NVIDIA NetWare DOS ODI Client Driver, 
	be sure that you have met the following software, hardware, and operating 
	system requirements.
	
	A.  NVIDIA NetWare DOS ODI Client Driver Software
	----------------------------------------------------
	Verify that you have the files that comprise the NVIDIA NetWare DOS ODI 
	Client Driver set as listed below.

	Note: 	These files are supplied online or on disk, depending on the
		requirements of your organization.
 
	File Name 	Description
	============================================
	NVODI.COM	ODI Client Driver
	DRIVER16.LST	Package installation file
	NVODI.INS	Driver installation file

	B. Hardware
	------------------- 
	You need an NVIDIA nForce MCP system in order to install the NVIDIA 
	NetWare DOS ODI Client Driver software.

	C. Operating System
	----------------------------
	NetWare Client 16 and Client 32 for DOS software require that MS DOS 5.x 
	or PC DOS 5.x (or later versions of the software) is running on your computer.



/////////////////////////////////////////////////////////////////////// 
Chapter 2   INSTALLING THE NVIDIA DOS NDIS ETHERNET DRIVER
///////////////////////////////////////////////////////////////////////

This chapter explains the procedures you will use to modify configuration files
that will become part of your NVIDIA DOS NDIS Ethernet startup disk for
an NVIDIA nForce MCP system. The following major topics are discussed:

I.	Using Norton Ghost Enterprise  
II.	Using Microsoft Network Client  
III.	Using Microsoft/3Com LANMAN   
IV.     Forcing Speed/Duplex

The applications listed above can incorporate the NVIDIA DOS NDIS Ethernet 
device driver as you prepare the configuration file contents of the network startup
disk. In order to integrate the NVIDIA DOS NDIS Ethernet driver and ensure proper 
functionality, follow the instructions under the application you plan to use.

I. 	Using Norton Ghost Enterprise
	============================= 
	
	The following topics are discussed:

	A. Creating a Network Startup Disk Using the Template Method
	B. Creating a Network Startup Disk Without Using the Template 


	A. Creating a Network Startup Disk Using the Template Method
	=========================================
	NVIDIA has supplied a template for the Norton Ghost Enterprise boot wizard. 
	This template can create the NVIDIA DOS NDIS Ethernet driver as an item in the 
	adapter list. Follow these steps to use the template:

	1. 	Copy the NVIDIA directory "NVIDIA DOS NDIS Ethernet" to the 
		Template directory of Norton Ghost.

		--------------------------------------------------------------------------------------- 
		For Windows 2000, the template directory is:

		C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template
		------------------------------------------------------------------------------ 

	2.	Run the Norton Ghost Boot Wizard to create a network startup disk.
		The NVIDIA DOS NDIS Ethernet driver appears as a choice in
		the adapter list.

	3. 	Modify only the memory configuration lines in the CONFIG.SYS file,
		as shown here:
 
		device=a:\himem.sys
		dos=high,umb
		device=a:\emm386.exe noems (optional)


	B. Creating a Network Startup Disk Without Using the Template
	=========================================
	To create a network startup disk without the template method explained above, 
	follow these steps:

	1. 	Run the Norton Ghost Boot Wizard to create a network startup disk.

	2.	Choose any adapter from the list that appears; for example,
		"Intel EtherExpress Pro 100".

	3.	Copy the NDIS.DOS and NVNDIS2.DOS driver files to A:\NET.

	4. 	Modify the CONFIG.SYS file to use both the driver files in step 3. 
		The following is an excerpt from a sample CONFIG.SYS file:

		device=a:\net\NVNDIS2.DOS 
		devicehigh=a:\himem.sys
		dos=high,umb
		lastdrive=z
		devicehigh=a:\net\protman.dos /i:a:\net
		rem devicehigh=a:\net\e100b.dos
		devicehigh=a:\net\NDIS.DOS
		devicehigh=a:\net\ntsts.dos
		devicehigh=a:\net\dlshelp.sys

		----------------------------------------------------------------- 
		Notes:	The NVNDIS2.DOS driver must be loaded before any
			other drivers and must not be loaded "high". 

			You "must" include the following lines to address memory
			requirements:
				device=a:\himem.sys
				dos=high,umb
				device=a:\emm386.exe noems (optional)
		--------------------------------------------------------------- 

	5.	Modify PROTOCOL.INI as shown in the following excerpt from a 
		sample PROTOCOL.INI file:

		[nic]
		drivername = UNDIS$
		;drivername = E100B$
		;Speed = Auto-Speed
		;ForceDuplex = Auto


II.	Using Microsoft Network Client
	============================== 
	
	The following topics are discussed:

	A.  Creating a Network Startup Disk with OEMSETUP.INF
	B.  Creating a Network Startup Disk Manually


	A. Creating a Network Startup Disk with OEMSETUP.INF
	======================================

	Thee two versions of the Microsoft Network Client are: 

	* Microsoft Network Client (MS DOS) can be obtained from:
		ftp://ftp.microsoft.com/bussys/clients/msclient/

	* Microsoft Network Client (Windows XP/2000/NT) is located on the 
		Windows NT Server 4.0 CD-ROM.
		-----------------------------------------------
		NOTE: See Microsoft article Q252448.
		-----------------------------------------------

	Follow these steps to create the NVIDIA DOS NDIS Ethernet startup disk:
	 
	1. 	If you are using Microsoft Network Client 	(Windows XP/2000/NT),  
		follow the procedure in the Microsoft article Q128800.
	 
	2.	If you are using Microsoft Network Client (MS DOS), 
		select the option "Network adapter not shown on list below...". 

	3. 	Enter the path of the OEMSETUP.INF file when prompted for the
			location of the driver. 
		 
	4. 	Once either of the above procedures (step 1 or 2) has been completed, 
		you can use MODIFY.EXE to modify the CONFIG.SYS to include the 
		NVNDIS2.DOS driver file.

	5. 	Modify only the memory configuration lines in the CONFIG.SYS file,
		as shown here:

		device=a:\himem.sys
		dos=high,umb
		device=a:\emm386.exe noems


	B. Creating a Network Startup Disk Manually
	=========================== 
	If you don't plan to use the OEMSETUP.INF data to create your network
	startup disk, follow these steps:

	1. 	Run Microsoft Network Client to create a network startup disk. 

	2.	Choose any adapter from the list that appears; for example, 
		"Intel EtherExpress Pro 100".

	3. 	Copy the NDIS.DOS and NVNDIS2.DOS driver files to  A:\NET.

	4. 	Modify CONFIG.SYS file to use the NVIDIA DOS NDIS Ethernet
		driver as shown in the following excerpt from a sample CONFIG.SYS file:

		files=30
		stacks=9,216
		lastdrive=z
		device=a:\himem.sys
		dos=high,umb
		device=a:\emm386.exe noems
		device=a:\net\NVNDIS2.DOS
		device=a:\net\ifshlp.sys
		-------------------------------------------------------- 
		Notes:	The NVNDIS2.DOS driver must not be loaded "high".

			You must include the following lines to address memory
			 requirements:

			device=a:\himem.sys
			dos=high,umb
			device=a:\emm386.exe noems
			
			This ensures that there is enough available memory to use
			 the "Full Redirector".
		----------------------------------------------------------- 

	5.	Modify PROTOCOL.INI as shown in the following excerpt from a 
		sample PROTOCOL.INI file:

			[nic]
			DriverName=UNDIS$
			;INTERRUPT=3
			;IOADDRESS=0x300
			;DMACHANNEL=none
			;DMAMODE=burst
			;MAXTRANSMITS=12

	6.	Modify SYSTEM.INI to use NDIS.DOS as shown in the following 
		excerpt from a sample SYSTEM.INI file:

			[network drivers]
			netcard=NDIS.DOS


III.	Using Microsoft/3Com LANMAN 
	===================================== 

	The following topics are discussed:

	A. Creating a Network Startup Disk with OEMSETUP.INF
	B. Creating a Network Startup Disk Manually 


  	A.  Creating a Network Startup Disk with OEMSETUP.INF
	=======================================
	----------------------------------------------------------------- 
	Microsoft/3Com LANMAN can be obtained from: 
		ftp://ftp.microsoft.com/bussys/clients/lanman/
	------------------------------------------------------------------ 

	Follow these steps:

	1.	To install the NDIS.DOS driver using the OEMSETUP.INF, select
		the option that allows you to select a network adapter that is not in 
		the list.

	2. 	Once you have completed this installation process, use the MODIFY.EXE
		utility to modify the CONFIG.SYS file to include the NVNDIS2.DOS driver
		file.

	3.	Modify only the memory configuration lines in the CONFIG.SYS file,
		as shown here:

 		device=a:\himem.sys
		dos=high,umb
		device=a:\emm386.exe noems


	B.  Creating a Network Startup Disk Manually
	============================
 	If you don't plan to use the OEMSETUP.INF data to create your network 
	startup disk, follow these steps:

	1.	Run LANMAN to create a network startup disk.

	2.	Choose any adapter from the list that appears. For example,
		 "Intel EtherExpress Pro 100".

	3.	Copy the NDIS.DOS and NVNDIS2.DOS driver files to  A:\NET.

	4.	Modify CONFIG.SYS file to use both of the files in step 3 as shown 
		in the following excerpt from a sample CONFIG.SYS file:

			device=a:\himem.sys
			dos=high,umb
			device=a:\emm386.exe noems
			files=30
			lastdrive=z
			device=a:\net\NVNDIS2.DOS
			device=a:\lanman.dos\drivers\protman\protman.dos /i:a:\lanman.dos
			device=a:\net\NDIS.DOS
			device=a:\lanman.dos\drivers\protocol\tcpip\tcpdrv.dos /i:a:\
			lanman.dos
			device=a:\lanman.dos\drivers\protocol\tcpip\nemm.dos

	 	--------------------------------------------------------------------------- 
		Notes:	The NVNDIS2.DOS driver must not be loaded "high".

			You must include the following lines to address memory 
			requirements:

			device=a:\himem.sys
			dos=high,umb
			device=a:\emm386.exe noems
			
			EMM386.EXE provided with LANMAN causes the
			startup sequence to hang. Therefore, use the EMM386.EXE
			that's provided with DOS.
		------------------------------------------------------------------------------ 


	5. 	Modify PROTOCOL.INI as shown in the following excerpt from a 
		sample PROTOCOL.INI file:

			[nic]
			DriverName=UNDIS$
			;INTERRUPT=3
			;IOADDRESS=0x300
			;DMACHANNEL=1


IV.	Forcing Speed/Duplex 
	===================================== 

	The default for establishing the link speed/duplex is
	auto-negotiation.  The user may override the default
	by specifying the "/FORCED" option to the nvndis2.dos driver.

	The syntax for the /FORCED option is:
	
		/FORCED <mode> 

		where <mode> is one of the following: 
		
			"10H"  - for 10mb half duplex
			"10F"  - for 10mb full duplex
			"100H" - for 100mb half duplex
			"100F" - for 100mb full duplex

	Note that all characters must be uppercase.

	An example of forcing the speed to 100mb full duplex is
 	provided below:

		device=a:\net\NVNDIS2.DOS /FORCED=100F
	


/////////////////////////////////////////////////////////////// 
Chapter 3   INSTALLING THE NVIDIA NETWARE DOS ODI CLIENT DRIVER
///////////////////////////////////////////////////////////////

This chapter explains the procedures for installing the NVIDIA NetWare
DOS ODI Client Driver for NetWare Client 32 and Client 16 for DOS.

I.	Installing NVIDIA NetWare DOS ODI Client Driver on NetWare Client 32 for DOS

	The following steps guide you through installing the NVIDIA NetWare DOS ODI 
	Client 	Driver on a computer running NetWare Client 32 for DOS. 

	1.	Insert a blank disk in drive A: of your computer.

	2.	Copy the NVIDIA NetWare DOS ODI Client Driver files to the disk. The 
		driver files are: 

		nvodi.com
		driver16.lst
		nvodi.ins

	3.	Run the installation program for NetWare Client 32 for DOS.

	4. 	Select the products you want to install.  

		a) Confirm that the "NetWare Client 32 for DOS" box is checked.

		b) Select any other product you want to install.

		c) When you are done, press F10.

	5. 	From the menu "Select a LAN drive type", select "16-bit LAN drivers" 
		and press F10.

	6.	From the menu "16-bit Network Board Drivers", select 
		"USER SPECIFIED 16-BIT DRIVER" and press F10.

	7.	Insert the disk containg the NVIDIA NetWare DOS ODI Client Driver 
		software in drive A:.

	8.	Press ENTER.
	
	9.	From the menu "16-bit Network Board Drivers", select "NVIDIA
		Ethernet Driver" and press F10.

		Note: 	The disk containing the NVIDIA NetWare DOS ODI Client 
			Driver software should still be inserted in drive A.  

	10.	Press ENTER and then press F10.

	11.	Specify the Frame type and press F10.

		The "Menu Installation Configuration Summary" now displays 
		"16-bit LAN drivers" in the "LAN driver type" box and 
		"NVIDIA Ethernet PCI Driver" in the "LAN driver" box.  

	12. 	Press F10.
	
	13.	Continue installing Client 32.  

		Note: At some later point during the installation process, you 
		may be prompted to insert the disk containing the NVIDIA driver 
		software in the A: drive of your computer.

		Below is a sample startnet.bat file after the installation program has 
		been run:

		SET NWLANGUAGE=ENGLISH
		C:\NOVELL\CLIENT32\NIOS.EXE
		C:\NOVELL\CLIENT32\LSL.COM
		C:\NOVELL\CLIENT32\N16ODI.COM
		C:\NOVELL\CLIENT32\NESL.COM
		C:\NOVELL\CLIENT32\NVODI.COM
		LOAD C:\NOVELL\CLIENT32\LSLC32.NLM
		LOAD C:\NOVELL\CLIENT32\PC32MLID.LAN
		LOAD C:\NOVELL\CLIENT32\IPX.NLM
		LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM

		Below is a sample net.cfg file after the installation program 
		has been run:

		Link Driver NVODI
			FRAME Ethernet_II

		NetWare DOS Requester
			FIRST NETWORK DRIVE F
			NETWARE PROTOCOL NDS BIND

		Protocol IPX
			IPX SOCKETS 40


II.	Installing NVIDIA NetWare DOS ODI Client Driver on NetWare Client 16 for DOS

	The following steps guide you through installing the NVIDIA NetWare DOS ODI Client 
	driver software on a computer running NetWare Client 16 for DOS.  

	1.	Insert a blank disk in drive A: of your computer.

	2.	Copy the NVIDIA NetWare DOS ODI Client Driver files to the disk. The 
		driver files are: 

		nvodi.com
		driver16.lst
		nvodi.ins

	3.	Run the installation program for NetWare Client 16 for DOS.

	4. 	Highlight the line under "Select the driver for your network board", 
		and press ENTER.

	5.	From the menu "Network Board", select "OTHER DRIVERS" and
		press ENTER.
		
	6.	Insert the floppy containing the NVIDIA NetWare DOS ODI Client 
		Driver software and press ENTER.

	7.	From the menu "Network Board", select "NVIDIA  Ethernet Driver" 
		and press ENTER.
		
	8.	Specify the Frame type and press F10.

	9.	Continue installing Client 16. 

		Below is a sample startnet.bat file after the installation program has 
		been run:

		SET NWLANGUAGE=ENGLISH
		C:\NWCLIENT\LSL.COM
		C:\NWCLIENT\NVODI.COM
		C:\NWCLIENT\IPXODI.COM
		C:\NWCLIENT\VLM.EXE


		Below is a sample net.cfg file after the installation program has 
		been run:

		Link Driver NVODI
			FRAME Ethernet_II

		NetWare DOS Requester
			FIRST NETWORK DRIVE = F
			NETWARE PROTOCOL = NDS BIND



\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ 
APPENDIX A:  GLOSSARY
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

HSM
Hardware Specific Modules (HSM) is a Novell term for a device driver.

MCP
Media and Communications Processor (MCP) is used in reference to the 
NVIDIA product called nForce. nForce comprises the MCP and the Integrated 
Graphics Processor (IGP).

NDIS
Network Driver Interface Specification is a Microsoft specification
for how communication protocol programs (such as TCP/IP) and network
device drivers should communicate with each other.

NetWare
Novell network operating system

nForce
NVIDIA product that consists of both the Integrated Graphics Processor (IGP) 
and the Media and Communications Processor (MCP) architectures. 

ODI
Open Data-Link Interface (ODI) is the Novell interface specification for 
LAN drivers.

SDK
software development kit

UNDI
Universal Network Driver Interface


---------------------------------------------------------------------------

For detailed information on the complete range of NVIDIA products and
terminology, see the NVIDIA Web site at www.nvidia.com.
