- Insert the disk that came with your card in the disk drive. That is
probably your machine's A: drive but it may be the B: drive. This
example uses A:.
- Enter a: to change to the A: Drive. Then enter dir /w to see the
contents of the disk as shown below Do not type the "C:\>"; that is
the prompt.
C:\> a: (and press return)
A:\> dir/w (and press return)
- EXE, COM, and BAT files are executibles (if you enter their name at
a prompt, without the extension, , the files will do something). Look for
a file or directory that says "Setup or Diag" or something of that
nature. Once the setup program is found, run it by typing it's name.
A:\> setuppgm (enter your setup program's name)
- If the setup program has an "Auto Configure" option, choose that
option and record the IRQ (the interrupt request number is usually one
of 5, 10, 11, or 15) and I/O address (This may look like 300h but is
entered as 0x300. The I/O addresses will be in the range of
0x220-0x380, but the usual one is 0x300.). See the example in the next
panel. You will need these numbers later. If you do not see these
during the setup, you should be able to view the information with one
of the other setup program options.
- If the Setup Menu has a "Card Test" option, run that option. If
there are no problems, exit the Setup Menu. If there were problems,
the Setup program may suggest things for you to try. Do those and
retest before preceding.
- Once you have the defined IRQ and I/O address, you are ready to try
loading the packet driver. First you must find the driver. At the A:
prompt, enter
A:\> dir /w
- Look for a directory (directories are in square brackets), that has
the word, or an abbreviation of the word, "packet" in it. For example,
one 3COM card calls that directory "PKTDVR" which is short-hand for
packet driver. You need to change to the packet driver directory now.
A:\> cd packet_directory (use your directory name)
- 8. To see the files in this directory, enter the dir/w command.
A:\packet_directory> dir/w
- Look for a file with a filetype of COM. COM files are typically
used to load packet drivers. If several COM files exist, or you want
additional information, look for a DOC or README file (often if you
view the README file it will tell you what driver to use for what
system, i.e., Window 3.1, Windows for Workgroups 3.11, Windows NT,
Novell, etc.). You need to copy this file to your hard drive and then
switch back to the C: drive.
A:\packet_directory> copy driver.com c: (use your driver name)
A:\packet_directory> c:
- To see the syntax the packet driver COM file expects, type the
command:
C:\> driver (use your driver name)
* You will see something similar to this:
exp16 [IRQ]
Items in < > are required.
At a minimum the Packet Vector, also known as the interrupt number(Int_Num),
is required. The first interrupt number to try is 0x60. Your card
may also require the IRQ and/or the I/O address that you recorded during
setup. Now try loading your packet driver:
C:\> driver 0x60 (include all fields required by your card
For example: ne2000 0x60 15 0x300 )
* Problems that could occur include IRQ conflict (from the C:\> prompt
enter: msd. Look at the IRQ section and find an available IRQ before
preceeding. Then go back to the setup program and choose another IRQ
(5,10,11, or 15).) If there is a interrupt number conflict, re-enter
the driver command and try 0x61,0x62, and then 0x63.
- You now need to load Winpkt with the same interrupt number (you
must have the WNET software installed before entering this command).
C:\> c:\wnet30\winsock\wnpkt 0x60
where the 0x60 should be the first number you entered when you loaded
the packet driver. No other arguments are used. If there are no
errors, you are ready to try the WNET software.
- Enter win to start Windows.
C:\> win
- Open the WNET group; start the WNET 3.0.4 application by
double-clicking. The text should read:
Ethernet disconnected
Your Name Logged On
- Click Connect on the WNET menu bar. TCPMAN should launch.
* If it does not, exit Windows, and enter the following to unload the
packet drivers:
C:\> driver -u (use your driver name)
C:\> c:\wnet30\winsock\ winpkt -u
Then reenter the load commands to make sure you didn't make a typo. If
you still get errors, call 231-HELP for assistance.
- When connected, click on Clients and launch Gopher. If you get to
the Virginia Tech gopher, your card is correctly installed, loaded,
and working.
* If you do not get to the gopher menu, Disconnect and follow the
instructions above to unload and then reload your packet drivers and
try gopher again. Call 231-HELP for assistance if you still have a
problem.
- If you successfully got the gopher menu, it is time to make the
loading of your packet drivers automatic. Quit Gopher, Disconnect and
Quit WNET. Then quit Windows. Change to the C: directory and edit your
autoexec.bat file.
C:\> edit autoexec.bat
- Using your arrow keys, move your cursor to the end of the last
line, press return and enter the following two lines. (If autoexec.bat loads
Windows, i.e. you have win in it, these lines must be entered before
the line that loads Windows.)
c:\exp16 0x60 0x300 (where exp16 is used for illustration
only, use your packet driver filename
and the values you used earlier)
c:\wnet30\winsock\winpkt 0x60 (use your interrupt number)
- From the File menu, choose SAVE. Then choose EXIT. (If your mouse
doesn't work, use the keystrokes:
Alt+f, s
Alt+f, x to exit autoexec.bat)
- Eject the floppy from drive A:. Now everytime you start your
machine those two commands will be executed. All you need to do is
start Windows, open WNET, and Connect.