edmund@qualcomm.com (The Silver Surfer) (06/18/91)
Hello out there. I've just downloaded the NOVELL.EXE file that contains all the Novell drivers for the packet driver interface, and I'm having problems configuring the server. When I configured IPX.COM to use the packet driver interface, I had no problems, but when I wanted to use ECONFIG to configure the os and bridge files, I found that they didn't exist. I have netware v3.11 and some things have changed since April 1989 (The date on the README file). The utilities book explains how to use ECONFIG with IPX.COM, but that doesn't work either. The two files the README file wants are NET$OS.EXE and BRIDGE.EXE, neither of which I can find. Have these files changed names, or am I doing something drastically wrong? -- edmund@qualcomm.com (Ed Villavert) "It's a question of mind over matter. Qualcomm Incorporated We no longer mind, cause you no longer San Diego, Ca matter." -- Stitch Jones (619) 587-1121 x-5192
trier@cwlim.INS.CWRU.Edu (Stephen C. Trier) (06/18/91)
Edit your AUTOEXEC.NCF file (in SYS:SYSTEM) and add the option
"frame=ethernet_ii" to the command line where you load your network
card driver. (If there is already a frame= command, remove it.)
That will econfig the server.
If you would like to run supporting both protocols, duplicate your
current load line, add the frame=ethernet_ii command to the second,
use "name=" to rename one of them, and bind IPX to both. For example:
...
load 3c503 memory=c8000 port=300 int=3 name=ETH_802.3
load 3c503 memory=c8000 port=300 int=3 frame=ethernet_ii name=ETH_II
bind ipx to ETH_802.3
bind ipx to ETH_II
...
This example loads the 3c503 driver once for each frame type, using a
single network card for both. It then tells the server to use the
IPX protocol for both. This lets you use both packet driver and non-
packet driver computers to speak to the server at once.
For your other question, you don't need to econfig the packet driver
version of IPX. The econfigging is implicit. You only need to econfig
the IPX file if it is a non-packet driver IPX. With what I describe
above, you don't even need to do that.
--
Stephen Trier "48 61 70 70 69 6e 65 73 73 20 69 73 20 61
Small Systems Guy 20 77 61 72 6d 20 68 65 78 20 64 75 6d 70
Information Network Services 21 20 20 3b 2d 29" - Me
Case Western Reserve University Mail: trier@ins.cwru.edu