LANMAN.TXT Driver File Contents (en1657-a.zip)

		 Accton Technology Corporation
     Ethernet Remote Boot Rom for Lan Manager operation System
     =========================================================

Remote Boot Installation for LAN Manager 2.1
--------------------------------------------
Remote Boot installation on LAN Manager 2.1 may be complex.
Also, be aware that the Accton Generic Boot ROM does
not provide remote boot capability on a Microsoft OS/2 system.

There are two ways to install the remote boot software on
the LAN Manager server. You can either use Accton's
configuration utility (on the Accton Driver diskette
or download it from Accton's BBS), or edit the RPL
files manually.

Generic Boot Installation for LAN Manager 2.1
Using Accton's Configuration Utility
----------------------------------------------

1. Refer to the Microsoft LAN Manager Administrator's Guide
	Chapter 13: Booting Workstations Remotely for more
	detailed information.

	Follow the steps to setup the remote boot environment,
	but do not use the RPLMGR.EXE program to create
	the remote boot profile.

2. Select an OS/2 full screen, and change to the
	RPL subdirectory. For example, C:\LANMAN\RPL

3. Copy the RPLCFG.CMD, RPL.ACC, RPLMGR.ACC and the ETHNE.DOS
	from the \RPL\LANMAN subdirectory of the Accton Driver
	diskette, or from Accton's BBS to C:\LANMAN\RPL.

4. Run RPLCFG to install the remote boot software.

5. Refer to the Chapter 13 of LAN Manager Administrator's Guide.
	Follow the steps in "Managing Remote Boot".

Generic Boot Installation for LAN Manager 2.1
by Manually Editing the RPL File
---------------------------------------------

1. Refer to the Microsoft LAN Manager Administrator's Guide
	Chapter 13: Booting Workstations Remotely.  Follow the
	steps to setup the remote boot environment, but do not
	use the RPLMGR.EXE program to create a remote boot profile.
2. Select an OS/2 full screen. Make C:\LANMAN\RPL the default
	directory.
3. Copy ETHNE.DOS to BBLOCK\NDIS
4. Create a subdirectory BBLOCK\NETBEUI\ETHNE
5. Create DOSBB.CNF and PROTOCOL.INI files in
	BBLOCK\NETBEUI\ETHNE as shown below:
-----------------------------------------------------------
	BBLOCK\NETBEUI\ETHNE\DOSBB.CNF:

	; DOS on Accton Ethernet Adapter
	RPL BBLOCK\RPLBOOT.SYS
	LDR BBLOCK\RPLSTART.COM ~
	DAT BBLOCK\NETBEUI\ETHNE\PROTOCOL.INI
	DRV BBLOCK\RPLDISK.SYS ~ 4 M
	EXE BBLOCK\RPLPRO1.COM ~ 2 ~
	EXE BBLOCK\RPLBIND2.EXE ~ ~
	EXE BBLOCK\PROTMAN.EXE ~ ~
	EXE BBLOCK\RPLBIND1.EXE ~ ~
	DRV BBLOCK\TCPDRV.DOS /I:C:\LANMAN.DOS ~ ~
	EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~
	DRV BBLOCK\NDIS\ETHNE.DOS ~ ~ ~
	DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M

	BBLOCK\NETBEUI\ETHNE\PROTOCOL.INI:

	[protman]
	drivername = protman$
	dynamic = yes
	priority = netbeui
	[netbeui]
	drivername = netbeui$
	bindings = ethne
	names = 5
	ncbs = 8
	packets = 20
	pipeline = 10
	sessions = 4
	stacksize = 512
	lanabase = 0
	[xnsnb]
	DRIVERNAME = XNSNB$
	BINDINGS = ethne
	MAXPROCESSES = 12
	FGTICKS = 2
	BGTICKS = 2
	MAXROUTES =
	MAXSOCKETS =
	MAXXMITDESCS =
	NONGROUPS =
	SHAREGROUPS =
	LOGINLIBRARY =
	COURIERLIBRARY =
	NETBIOSGROUPS =
	lanabase = 1
	[xnstp]
	DRIVERNAME = XNSTP$
	LOAD = XNSTP[CB]
	BINDINGS = ethne
	MAXPROCESSES = 12
	FGTICKS = 2
	BGTICKS = 2
	MAXROUTES =
	MAXSOCKETS =
	MAXXMITDESCS =
	NONGROUPS =
	SHAREGROUPS =
	LOGINLIBRARY =
	COURIERLIBRARY =
	NETBIOSGROUPS =
	lanabase = 1
	[tcpip]
	DRIVERNAME = TCPIP$
	IPADDRESS0 = (TCPIP_ADDRESS)
	SUBNETMASK0 = (TCPIP_SUBMASK)
	DEFAULTGATEWAY0 = (TCPIP_GATEWAY)
	NBSESSIONS = 6
	LOAD = tcptsr[c],tinyrfc[c],emsbfr[cr]
	UNLOAD = "unloadt /notsr[dc]"
	bindings = ethne
	lanabase = 1
	[ethne]
	drivername = ethne$
	;iobase = 0x300
	;irq = 0x3
---------------------------------------------------------------

6. Edit the RPL.MAP in the current directory.

  a. Add the lines below the description of "boot block records"

  yyyyyyyyyyyy BBLOCK\NETBEUI\ETHNE\DOSBB.CNF 2 6 A ~ DOS
  ~Accton~EtherPair  0000E8 ~ ,,, ~ RDOSA ~ ~ ~ ~ ~ ~

  b. Insert the lines before the description of "profile and
	  workstation records added by rplmgr"

 0000E8?????? ???????? D FITS\DEFAULT (RPL_SERVER_NAME)
 S ~ ~ ~,,, ~ RDOSA ~ DEFAULT *~New~Accton~EtherPair~* ~ ~ ~

7. Edit the RPLMGR.INI in the current directory.
	Insert the following section before the OS/2 description block.

	[configuration]
	name = DOS330A
	os = DOS330
	dirname = DOS
	dirname2 = DOS330
	bblink = RDOSA
	fitfileshared = fits\dos330
	fitfilepersonal = fits\dos330p
	comment = DOS 3.30 Accton EtherPair
	adapter = 0000E8??????
	[configuration]
	name = DOS401A
	os = DOS401
	dirname = DOS
	dirname2 = DOS401
	bblink = RDOSA
	fitfileshared = fits\dos401
	fitfilepersonal = fits\dos401p
	comment = DOS 4.01 Accton EtherPair
	adapter = 0000E8??????
  [configuration]
			  name = DOS500A
			  os = DOS500
			  dirname = DOS
			  dirname2 = DOS500
			  bblink = RDOSA
			  fitfileshared = fits\dos500
			  fitfilepersonal = fits\dos500p
			  comment = DOS 5.00 Accton EtherPair
			  adapter = 0000E8??????

			 And append the following line to RPLMGR.INI
			 ; 0000E8 = Accton (Ethernet)

 8. Log onto the network as an administrator.
	 Stop the remote boot service. Run RPLINST.
	 Then restart remote boot service.

 9. Refer to the Chapter 13 of LAN Manager
	 Administrator's Guide. Follow "Managing Remote Boot"
	 to generate a workstation profile.

All trademarks or brand names mentioned are properties of
their respective owners.

===End===


Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web3, load: 0.46