home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Mother of All Windows Books
/
CD-MOM.iso
/
cd_mom
/
drivers
/
netcard
/
ub
/
readme.txt
< prev
next >
Wrap
Text File
|
1991-08-28
|
10KB
|
178 lines
; Sample PROTOCOL.INI for UBNEI
; -----------------------------
; This is a sample PROTOCOL.INI file for the UBNEI Ungermann-Bass NDIS MAC
; driver. The [UBNEI] section shows examples of UBNEI configuration parameter
; settings. Comments at the end of the file explain these parameters and give
; their default, minimum and maximum values. The [protocol manager] and
; [netbeui] sections aren't meant to be complete or realistic examples, except
; for the "BINDINGS = UBNEI" line in the [netbeui] section.
[protocol manager]
DRIVERNAME = PROTMAN$
[netbeui]
DRIVERNAME = NETBEUI$
BINDINGS = UBNEI
SESSIONS = 32
NCBS = 100
[UBNEI]
; Note that many of these parameters have default values (which are
; given below under "Comments about UBNEI parameters"). A parameter need not
; be specified in your PROTOCOL.INI if its default value is satisfactory.
DriverName = UBNEI$
AdapterType = NIUpc
MemoryWindow = 0xD8000
IO_Port = 0x368
IRQ_Level = 3
SlotNumber = 4
MaxRequests = 6
MaxTransmits = 6
ReceiveBufSize = 600
MaxMulticast = 16
ReceiveMethod = ReceiveLookahead
ReceiveBuffers = 64
; Comments about UBNEI parameters:
; --------------------------------
; DriverName:
; This parameter's value must be UBNEI$, or, in the case where
; multiple adapters are installed, UBNEI$ for the first adapter's
; DriverName, UBNEI2$ for the second one, UBNEI3$ for the third, and
; so on.
; AdapterType:
; This specifies the type of Ungermann-Bass adapter. The possible
; values are shown below. You should use:
;
; AdapterType = NIUpc for the NIUpc or 3270 NIUpc adapter;
; AdapterType = Personal NIU for the 128K Personal NIU adapter;
; AdapterType = Personal NIU/ex for the 512K Personal NIU/ex adapter;
; AdapterType = NIUps for the NIUps or NIUps/EOTP adapter;
; AdapterType = NIUpc/EOTP for the adapter which is known variously
; as NIUpc/EOTP, NIUpc Plus, and GPCNIU.
; Some Ungermann-Bass adapter types are called by various names in
; special contexts and in older documentation. To support these other
; naming conventions, the driver will accept the following synonyms for
; AdapterType.
; Synonyms Meaning
; -------- -------
; PCNIU Personal NIU
; PCNIUex, Personal NIUex Personal NIU/ex
; NIUps/EOTP NIUps
; GPCNIU, NIUpc PLUS, NIUpcPLUS NIUpc/EOTP
; MemoryWindow:
; This specifies the physical base address in the PC memory address
; space of the "window" through which the adapter's RAM will be refer-
; enced. This parameter's value must agree with the jumpered configur-
; ation of the adapter. (For the NIUps, "MemoryWindow" is not needed and
; will be ignored.)
; IO_Port:
; This specifies the base address in the PC I/O address space of the
; adapter's I/O ports. Its value must agree with the jumpered configur-
; ation of the adapter. (For the NIUps, "IO_Port" is not needed and
; will be ignored.)
; IRQ_Level:
; This specifies the IRQ level that will be used by the adapter-to-
; PC interrupt. Its value must agree with the jumpered configuration of
; the adapter. (For the NIUps, "IRQ_Level" is not needed and will be
; ignored.)
; MaxRequests: (Default = 6; Min = 1; Max = 10.)
; This specifies the maximum number of "GeneralRequest"s that can be
; simultaneously outstanding.
; MaxTransmits: (Default = 6; Min = 1; Max = around 400.)
; This specifies the number of "TransmitChain"s that the MAC driver
; guarantees to accept without giving an "OUT_OF_RESOURCE" response.
; MaxMulticast: (Default = 16; Min = 0; Max = 255.)
; This specifies the maximum number of multicast addresses that can
; be in effect simultaneously. (NOTE that there's no 's' on the end of
; this keyword.)
; ReceiveBufSize: (Default = 600; Min = 256; Max = 1514.)
; This specifies the size of the receive buffers the MAC driver will
; use. This should be large enough to hold the normal expected received
; frame. It need not be large enough to hold the largest expected frame.
; The MAC driver will handle large frames in multiple receive buffers.
; The value of ReceiveBufSize must be even.
; ReceiveMethod: (Default = ReceiveLookahead;
; other choices: ReceiveChain, AdapterBuffered
; and ReceiveChain, HostBuffered
; This determines the method of received frame delivery the MAC
; driver will use. The possibilities are described below. Which one
; is best to use depends mainly on how the Protocol driver you're using
; works. Use number (1) if you don't know anything about the Protocol
; driver.
; (1) ReceiveMethod = ReceiveLookahead
; When a received frame is available and Indications are On, the
; MAC driver will call the Protocol driver's "ReceiveLookahead" routine.
; "ReceiveLookahead" will be given the total length of the frame and a
; pointer to the "lookahead" data in a receive buffer in the adapter's
; RAM. The Protocol driver must copy the frame (possibly using the MAC's
; "TransferData" routine) before returning from "ReceiveLookahead". When
; "ReceiveLookahead" returns, the MAC driver frees the receive buffers
; in the adapter's RAM for use in receiving more frames.
; This method works well if the Protocol driver is able to copy the
; frame to the Protocol driver's client's buffers at the time "Receive-
; Lookahead" is called. It is also a good method if the Protocol driver
; always copies frames into internal buffers of its own.
; (2) ReceiveMethod = ReceiveChain, AdapterBuffered
; When a received frame is available and Indications are On, the MAC
; driver will call the Protocol driver's "ReceiveChain" routine, passing
; it an "RxBufDescr" which points to the frame in the receive buffers in
; the adapter's RAM. The Protocol driver can either (a) immediately copy
; the frame or (b) save a copy of the "RxBufDescr" and leave the frame
; in the buffers in the adapter's RAM, to be copied at a later time. In
; case (b), the Protocol driver must copy the frame as soon as possible
; and call the MAC's "ReceiveRelease" function to make the buffers in
; the adapter's RAM available for receiving more frames.
; This method of operation can be the most efficient. It's a little
; better than the "ReceiveLookahead" method if the Protocol driver can
; copy the frame immediately, because the overhead of calling "Transfer-
; Data" is avoided. Also, it has the advantage over "ReceiveLookahead"
; that the Protocol driver doesn't have to copy the frame immediately --
; the frame can be left for a short time in the adapter's buffers. But
; if frames are left in the adapter's buffers long, it will run out of
; buffers and start losing frames. Also, there's the overhead of calling
; "ReceiveRelease" to consider.
; (3) ReceiveMethod = ReceiveChain, HostBuffered
; When a received frame is available and Indications are On, the MAC
; driver will copy the frame from the receive buffers in the adapter's
; RAM into receive buffers in the Host memory and call the Protocol
; driver's "ReceiveChain" routine, passing it an "RxBufDescr" which
; points to the Host-memory buffers. The Protocol driver can copy the
; frame immediately or leave it in the Host-memory buffers. It must
; eventually call the MAC driver's "ReceiveRelease" routine to free the
; Host-memory buffers for reuse. The buffers in the adapter's RAM are
; made available for receiving more frames as soon as "ReceiveChain"
; returns.
; In this mode, the MAC driver allocates receive buffers in the Host
; memory. These buffers are allocated at driver INIT time. Their number
; and size are determined by the "ReceiveBuffers" and "RcvBufSize" para-
; meters. The only advantage of this mode is that in it the MAC driver
; provides a possibly large amount of long-term frame buffering in which
; a Protocol driver can leave received frames until it can deliver them
; to its clients. This advantage comes at the cost of the space devoted
; to the Host-memory buffers. This is an inefficient mode if the
; Protocol driver always copies frames into its own internal receive
; buffers or if it can quickly copy frames from the adapter's buffers to
; its client's buffers.
; ReceiveBuffers: (Default = 64; Min = 16; Max = 512.)
; This specifies the number of receive buffers that the MAC driver
; will allocate in the Host memory. This parameter is meaningful only
; if "ReceiveMethod = ReceiveChain, HostBuffered" is specified. For
; other values of "ReceiveMethod", no receive buffers will be allocated
; in the Host memory -- the "ReceiveBuffers" parameter will be ignored.
; SlotNumber: (Min = 1; Max = 8.)
; This parameter is needed only when multiple NIUps adapters, and
; multiple instances of the UBNEI driver, are installed. Even then, this
; parameter is required only if it is necessary to override the default
; association between driver instances and adapters. By default, the
; UBNEI driver instance that comes first in PROTOCOL.INI will be associ-
; ated with the NIUps adapter in the lowest numbered slot, the UBNEI
; driver instance that comes second will be associated with the NIUps
; adapter in the second lowest numbered slot, and so on.
; PermanentAddr: The value is a string of 12 ASCII hexadecimal digits,
; for example: PermanentAddr = "00DD01AABBCC"
; This parameter provides a way to override the "Permanent Station
; Address" that's built into the adapter's ROM. Note that this parameter
; is normally not needed, and shouldn't be used. The NDIS specification
; strongly discourages configuring the "Permanent Station Address".