[MenuTitle] NetWare DOS ODI Driver
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > NetWare DOS ODI Workstation *
***********************************************
The NetWare DOS ODI workstation driver file is stored in the \DOS_ODI
subdirectory of the PowerNIC diskette.
1. Power on the workstation, and execute Novell's LSL program.
2. At the DOS prompt type the following command to execute the NetWare 4.x
workstation driver --
[drive]:\DOS_ODI\E200P
where [drive] is the floppy disk drive that this diskete is in.
3. After executing the driver, run NetWare's IPXODI.COM & NETX.EXE
(or VLM.EXE) files.
4. Please refer to Novell's Installation Manual for more details.
[MenuTitle] NetWare IPX Driver
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > NetWare IPX Workstation *
***********************************************
The NetWare IPX workstation driver file is stored in the \IPX
subdirectory of the PowerNIC diskette.
1. At the DOS prompt, type the following command to execute the IPX
workstation driver --
[drive]:\IPX\IPX.COM
2. After executing the driver, run NETX.EXE.
3. The following example is to change IPX setting according to hardware
configuration.
a) Display help screen.
[drive]:\IPX\IPX.COM /?
Novell IPX/SPX v3.10 (911121)
(C) Copyright 1985, 1991 Novell Inc. All Rights Reserved.
LAN Option: CNet PowerNIC CN200Eplus Series v2.20 (960227)
Hardware Configuration: Auto Configuration
Usage: IPX [options]
valid options:
-I or /I Display version information
-D or /D Display hardware options
-O or /O<num> Load using hardware option <num>
-C or /C=[path]<filename> Use an alternate configuration file
-? or /? Display this help screen
b) Display hardware options.
[drive]:\IPX\IPX.COM /D
Novell IPX/SPX v3.10 (911121)
(C) Copyright 1985, 1991 Novell Inc. All Rights Reserved.
LAN Option: CNet PowerNIC CN200Eplus Series v2.20 (960227)
Hardware options available:
* 0. Auto Configuration
1. IRQ = 3, I/O Base = 300H, no DMA or RAM
2. IRQ = 2 or 9, I/O Base = 320H, no DMA or RAM
3. IRQ = 4, I/O Base = 340H, no DMA or RAM
4. IRQ = 5, I/O Base = 360H, no DMA or RAM
5. IRQ = 2 or 9, I/O Base = 300H, no DMA or RAM
6. IRQ = 3, I/O Base = 240H, no DMA or RAM
7. IRQ = 5, I/O Base = 280H, no DMA or RAM
8. IRQ = 4, I/O Base = 2C0H, no DMA or RAM
9. IRQ = 4, I/O Base = 300H, no DMA or RAM
10. IRQ = 5, I/O Base = 320H, no DMA or RAM
11. IRQ =15, I/O Base = 340H, no DMA or RAM
12. IRQ =15, I/O Base = 360H, no DMA or RAM
13. IRQ = 5, I/O Base = 300H, no DMA or RAM
14. IRQ =10, I/O Base = 320H, no DMA or RAM
15. IRQ =11, I/O Base = 340H, no DMA or RAM
16. IRQ =12, I/O Base = 360H, no DMA or RAM
c) Change IPX hardware options.
For example:
[drive]:\IPX\IPX.COM /O4
[MenuTitle] Personal NetWare
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > Personal NetWare *
***********************************************
The driver for Personal NetWare 1.x is stored in the \DOS_ODI subdirectory
of the PowerNIC diskette.
1. First install Personal NetWare in the PC.
2. Copy the driver file to the Personal NetWare subdirectory.
At the DOS prompt, type the following commands:
COPY A:\DOS_ODI\E200P.INS C:\NWCLIENT
COPY A:\DOS_ODI\E200P.COM C:\NWCLIENT
NOTE: This assumes the diskette is in drive A.
3. a) Run Personal NetWare's SETUP.EXE to enter the main menu.
b) Choose the "Primary Network Interface Card" item, and press ENTER to
select "CN200/600/650Eplus Ethernet Adapter".
c) Return to the main menu and choose "Configure Primary Interface Card"
to configure the "INT", "PORT" and "Media Frame Type(s)".
d) At the main menu, press "Save Changes and Exit".
4. Execute STARTNET.BAT.
[MenuTitle] NetWare OS/2 ODI Driver
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > NetWare OS/2 ODI Workstation *
***********************************************
The NetWare ODI driver for OS/2 is stored in the OS2_ODI subdirectory
of the PowerNIC diskette.
1. First, install NetWare Requester for OS/2 in the PC.
2. Copy E200P driver to the subdirectory of NetWare.
At the OS/2 prompt, type the following commands:
COPY A:\OS2_ODI\E200P.SYS C:\NETWARE\
NOTE: This assumes the diskette is in drive A.
3. Use a text editor to modify C:\CONFIG.SYS as follows:
...
...
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
>> DEVICE=C:\NETWARE\NE2000.SYS << --- change NE2000.SYS to E200P.SYS
...
...
4. Use a text editor to create the file NET.CFG in the C:\NETWARE subdirectory.
The following is an example of the C:\NETWARE\NET.CFG file:
Link driver E200P
INT 3
PORT 300
FRAME Ethernet_802.3
5. Shut down and reboot the computer.
NOTE: There is a text editor named E.EXE to use under OS/2 full screen.
To edit the two files above, at the OS/2 prompt, type:
E C:\CONFIG.SYS
or
E C:\NETWARE\NET.CFG
[MenuTitle] NetWare v3.1x ODI Server Driver
This section provides two installation procedures: the first is for
NetWare 3.11. The procedure for 3.12 follows.
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > NetWare 3.11 ODI Server *
***********************************************
The NetWare 3.11 ODI server driver file is stored in the \NW_31X
subdirectory of the PowerNIC diskette.
1. Power on the file server, and execute Novell's SERVER.EXE program.
2. Load LSLENH.NLM first (this also automatically loads PATCHMAN.NLM).
At the server's prompt, type:
LOAD A:\NW_31X\LSLENH.NLM
3. Load LAN driver E200P.LAN and bind it. This will automatically load
MSM31X.NLM and ETHERTSM.NLM. The general way of using these parameters
is:
LOAD <driver name> <PARAMETER NAME>
Example:
LOAD A:\NW_31X\E200P.LAN PORT=300 INT=3 FRAME=Ethernet_802.2 NAME=E200P_802.2
BIND IPX TO E200P_802.2 NET=2
LOAD A:\NW_31X\E200P.LAN PORT=300 INT=3 FRAME=Ethernet_802.3 NAME=E200P_802.3
BIND IPX TO E200P_802.3 NET=3
NOTE: This assumes that this diskette is in drive "A:".
4. The server program will load and execute the E200P.LAN driver module.
Please refer to the NetWare 386 V3.11 Installation Manual for more
information to make an auto-execution batch file to load the E200P.LAN
module.
NOTE: If you use the MONITOR.NLM shipped with NetWare 3.11, your server could
abend when viewing LAN statistics in MONITOR.NLM with E200P.LAN driver.
We have provided the newer Novell MONITOR.NLM program in the driver
diskette to correct this problem.
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > NetWare 3.12 ODI Server *
***********************************************
The NetWare 3.12 ODI server driver file is stored in the \NW_31X
subdirectory of the PowerNIC diskette.
1. Power on the file server, and execute Novell's SERVER.EXE program.
2. Load the LAN driver E200P.LAN and bind it (this also automatically loads
MSM31X.NLM and ETHERTSM.NLM). The general way of using these parameters
is:
LOAD <driver name> <PARAMETER NAME>
Example:
LOAD A:\NW_31X\E200P.LAN PORT=300 INT=3 FRAME=Ethernet_802.2 NAME=E200P_802.2
BIND IPX TO E200P_802.2 NET=2
LOAD A:\NW_31X\E200P.LAN PORT=300 INT=3 FRAME=Ethernet_802.3 NAME=E200P_802.3
BIND IPX TO E200P_802.3 NET=3
NOTE: This assumes that this diskette is in drive A.
3. The server program will load and execute the E200P.LAN driver module.
Please refer to the NetWare 3.12 Installation Manual for more
information on how to make an auto-execution batch file to load the
E200P.LAN module.
[MenuTitle] NetWare v4.x ODI Server Driver
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > NetWare 4.x ODI Server *
***********************************************
The NetWare 4.x ODI server driver file is stored in the \NW_4
subdirectory of the PowerNIC diskette.
1. Power on the file server, and execute Novell's SERVER.EXE program.
2. Load the LAN driver E200P.LAN. (Two different methods are shown here.)
METHOD 1 --
At the server's prompt, load the driver E200P.LAN and bind it
(this also automatically loads MSM.NLM and ETHERTSM.NLM). The general
way of using these parameters is:
LOAD <driver name> <PARAMETER NAME>
Example:
LOAD A:\NW_4\E200P.LAN PORT=300 INT=3 FRAME=Ethernet_802.2 NAME=E200P_802.2
BIND IPX TO E200P_802.2 NET=2
LOAD A:\NW_4\E200P.LAN PORT=300 INT=3 FRAME=Ethernet_802.3 NAME=E200P_802.3
BIND IPX TO E200P_802.3 NET=3
NOTE: This assumes that this diskette is in drive A.
METHOD 2 --
a) At the server's prompt type: LOAD INSTALL
b) When the install menu appears, choose the menu item.
c) Install the LAN driver E200P.LAN according to the NetWare manual,
or use the on-line instructions.
3. The server program will load and execute the E200P.LAN driver module.
Please refer to the NetWare 4.x Installation Manual for more information
on making an auto-execution batch file to load the E200P.LAN module.
[MenuTitle] PC/TCP
This section provides three installation procedures: the first describes
how to install the packet driver for FTP's PC/TCP in DOS. Following this is
the procedure for installing the NDIS DOS driver. Last is the procedure
for the NDIS OS/2 driver.
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > Packet Driver *
***********************************************
The packet driver for PC/TCP is located in the \PCTCP subdirectory
of the PowerNIC diskette.
1. Run the 200EPD.COM program by entering the following
at the DOS command line --
A:>\PCTCP\200EPD <Packet_INT#> [IRQ#] [IO_Addr#]
(NOTE: This assumes the driver diskette is in drive A.)
where --
<Packet_INT#>: interrupt vector number, which can be
decimal, hexadecimal or octal format.
if:
decimal format -- from 96 to 128
hexadecimal ----- from 0x60 to 0x80
octal format ---- from 0140 to 0200
[IRQ#]: interrupt setting.
The following settings can be selected 3, 4, 5, 9,
10, 11, 12, 15.
[IO_ADDR#]: I/O Base Address setting.
The following settings can be selected:
0x300 0x320 0x340 0x360 0x380 0x3A0 0x3C0 0x3E0
0x200 0x220 0x240 0x260 0x280 0x2A0 0x2C0 0x2E0
EXAMPLE: 200EPD 0x60 3 0x300
(manual selection)
--> Packet_INT# = 0x60, IRQ# = 3, IO_Addr# = 0x300
200EPD 0x60
(automatic selection)
--> Packet_INT# = 0x60, IRQ# & IO_Addr# = automatic selection
2. Execute the ETHDRV.EXE device program, which is included with the
FTP PC/TCP software package.
The Ethernet adapter should now work with FTP PC/TCP.
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > NDIS 2.0.1 DOS Driver *
***********************************************
The DOS NDIS driver for PC/TCP is located in the \NDIS_20 subdirectory
of the PowerNIC diskette.
1. Create the subdirectory named LANMAN in the hard disk which consists of
relevant files from the NDIS directory of "PC Network Software
Unsupported Network Software, Diskette A".
2. Run INSTALL.EXE in PCTCP directory.
3. From the "Network Interface Card Driver Selection" window, choose
the item "NDIS Driver". Then, press F10.
4. In the "Interface Driver" window, enter the driver pathname
"A:\NDIS_20\E200P.DOS" (assuming this diskette is in drive A).
5. Key in complete pathname with file of "C:\LANMAN\PROTMAN.DOS".
6. Enter complete pathname with file of "C:\LANMAN\NETBIND.EXE".
7. Modify the contents of PROTOCOL.INI:
Change [E200P] To [E200P_NIF]
8. Append the contents of CONFIG.INS file in the PCTCP directory to
C:\CONFIG.SYS. Add one more option in the following statement.
Change:
DEVICE=C:\LANMAN\PROTMAN.DOS
To:
DEVICE=C:\LANMAN\PROTMAN.DOS /I:C:\LANMAN
9. Copy the PCTCP\AEXECFTP.BAT file to AUTOEXEC.BAT.
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > NDIS 2.0.1 OS/2 Driver *
***********************************************
The OS/2 NDIS driver for PC/TCP is located in the \NDIS_20 subdirectory
of the PowerNIC diskette.
1. Copy A:\NDIS_20\E200P.OS2 to C:\PCTCP\DRV
(where "A:" is the drive this diskette is in)
2. Add the following line to the CONFIG.SYS file --
DEVICE=C:\PCTCP\DRV\E200P.OS2
Example:
DEVICE=C:\PCTCP\DRV\PROTMAN.OS2 /I:C:\PCTCP\DRV
DEVICE=C:\PCTCP\DRV\E200P.OS2
DEVICE=C:\PCTCP\DRV\SOCKET.OS2
3. Edit the C:\PCTCP\DRV\PROTOCOL.INI file to add the correct adapter
and protocol information.
Example:
;========================
;++ ADAPTERS ++
;========================
; 200E Plus Series cards
;
[E200P_NIF]
DRIVERNAME = E200P$
INTERRUPT = 3
IOBASE = 0x300
;========================
;++ PROTOCOLS ++
;========================
;FTP PC/TCP for OS/2
[SOCKET]
drivername = $SOCKET
bindings = E200P_NIF
[MenuTitle] Microsoft LAN Manager
This section contains two driver installation procedures: the first is for
the DOS version of LAN Manager. The OS/2 LAN Manager driver installation
procedure follows.
The driver for LAN Manager for DOS is located within the \MSLANMAN.DOS
subdirectory, and the OS/2 driver is in the \MSLANMAN.OS2 subdirectory
of the PowerNIC diskette.
NOTE: LAN Manager >REQUIRES< the subdirectory structure which is on this
diskette. If users want to copy the LAN Manager driver to another diskette,
the subdirectory and file structure must be the same.
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > LAN Manager for DOS *
***********************************************
1. Insert this driver diskette into the appropriate drive.
2. From the LAN Manager subdirectory (\LANMAN) on the hard disk,
run the SETUP program to begin installation.
3. Press the ALT+C keys to pull down the Configuration menu.
4. From the Network Adapter Drivers dialog box, select "CNet CN200Eplus
Series Ethernet adapter" from the menu, if shown (skip to step 7).
Otherwise, select "Other Driver" to import the driver.
5. Enter the disk drive letter for the driver diskette. No
path is required.
6. Select "CNet CN200Eplus Series Ethernet adapter" and click OK.
7. Select the desired protocol from the Network Protocol dialog box
and click OK.
8. Save the Configuration and Installation settings. LAN Manager will
automatically make modifications to CONFIG.SYS, AUTOEXEC.BAT, and
PROTOCOL.INI files.
9. Reboot.
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > LAN Manager for OS/2 *
***********************************************
1. Insert this driver diskette into the appropriate drive.
2. In the Group Main window, click the OS/2 Full Screen icon.
The full screen shell prompt will appear.
3. Change the hard disk directory from the root to subdirectory \LANMAN.
4. Key in the SETUP command (SETUP.EXE).
5. In the "Configuration" menu, choose "Network Drivers", the
Workstation Configuration window will appear.
6. Click the Add New Config button.
7. To select the driver for installation, click "Other Driver" in
the Network Adapter Drivers field
8. Assign the drive this diskette is in, without path. The driver will be
copied to the hard disk. Then, click the OK button.
9. In the "CNet CN200Eplus Series Ethernet adapter" window, set the
network protocol to be NetBeui (or other desired protocol) and
click OK.
10. Save the Configuration and Installation settings.
11. Reboot.
[MenuTitle] LAN Server
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > LAN Server OS/2 NDIS *
***********************************************
The OS/2 NDIS driver for LAN Server is located in the \NDIS_20 subdirectory
of the PowerNIC diskette.
1. Copy A:\NDIS_20\E200P.OS2 to C:\IBMCOM\MACS
(NOTE: This assumes that this diskette is in drive A.)
2. Copy A:\NDIS_20\IBMLANSE\E200P.NIF to C:\IBMCOM\MACS\E200P.NIF
3. Invoke C:\IBMCOM\LAPS.EXE to install the network driver.
[MenuTitle] Windows for WorkGroups 3.1
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > Windows for Workgroups 3.1 *
***********************************************
The DOS NDIS driver for Windows for Workgroups is located in the
\NDIS_20 subdirectory of the PowerNIC diskette.
1. From the Control Panel, click on the "Network" icon.
2. If there is no 200E NDIS driver installed on the hard disk, select
"Unlisted or Updated Network Adapter". Specify "A:\NDIS_20" as the path
(assuming this diskette is in drive A). Skip to Step 4.
3. Otherwise, select "CNet CN200E Series Ethernet Adapters" in
the network adapter list.
4. Specify the correct configurations of NIC, including I/O Base
and INTERRUPT (IRQ). I/O Base and IRQ values should be set to
zero's for autosense or to the same values specified in the
PowerNIC SETUP program.
5. Save the configurations.
6. Exit and reboot PC to put the change into effect.
NOTE: If you had previously installed the driver in WFW and want to install
it from the diskette again, you must first delete the related OEM?.INF
file from the \WINDOWS\SYSTEM subdirectory.
[MenuTitle] Windows for WorkGroups 3.11
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > Windows for Workgroups 3.11 *
***********************************************
The driver for Windows for Workgroups 3.11 is located in the \WFW311
subdirectory of the PowerNIC diskette.
1. Start Windows for Workgroups. From the "Network" group, choose
the Network Setup icon.
2. In the Network Setup window, click on "Drivers".
3. From the Drivers window, choose "Add Adapter...".
4. When the new menu is displayed, choose the "Unlisted or Updated Network
Adapter" item for the new driver.
5. There is a box for entering the directory path. Key in A:\WFW311 (assuming
this diskette is in drive A). Click "OK".
The next step inputs the IRQ channel and the I/O address. For NDIS
drivers, the IO Base and IRQ should be zero's for autosense. Users can
also set the values retrieved from the PowerNIC SETUP program.
6. In the driver type box, highlight the "Real Mode and Enhanced Mode
NDIS Driver", "Enhanced Mode Driver", "Real mode NDIS driver" or "ODI
Driver".
This procedure assumes that an NDIS driver is used. To use the ODI driver,
copy A:\DOS_ODI\E200P.COM to the hard disk and append the E200P.COM
statement in the AUTOEXEC.BAT file.
7. Save all settings, exit Windows for Workgroups and reboot.
[MenuTitle] Windows NT 3.1
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > Windows NT 3.1 *
***********************************************
The Windows NT 3.1 driver is located in the \WINNT\31 subdirectory
of the PowerNIC diskette.
1. Start Windows NT 3.1 and logon as Administrator. From the Control
Panel select the "Network" icon.
2. From the Netowrk window, click on the "Add Adapter..." button and
then choose "<Other> Requires disk from manufacturer".
3. Insert this driver diskette into the appropriate diskette drive.
4. Follow the instructions appearing on the screen and select the
appropriate drive name when required to give the location for the
driver and the OEMSETUP.INF file. Example:
A:\WINNT\31 <--- Directory of CNet 200Eplus Series Ethernet Driver
5. After pressing the "Continue" botton, confirm the driver diskette,
key in "0" for the IO Address, and click on the OK button.
(The IO Address can also be set to the value specified in the
PowerNIC SETUP program.)
6. Now, the driver has been installed. Select the OK button from
the Network window. The protocols and driver will bind together.
7. Reboot
[MenuTitle] Windows NT 3.5/3.51
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > Windows NT 3.5/3.51 *
***********************************************
The driver for Windows NT 3.5/3.51 is located in the \WINNT\35 subdirectory
of the PowerNIC diskette.
1. Start Windows NT and logon as Administrator. From the Control Panel
select the "Network" icon.
2. From the Network window, click on the "Add Adapter..." button and choose
the item "<Other> Requires disk from manufacturer".
3. Insert this driver diskette into the appropriate drive.
4. Follow the instructions appearing on the screen and select the
appropriate drive name when required to give the location for the driver
and the OEMSETUP.INF file. Example:
A:\WINNT\35 <--- Directory of CNet 200E Plus Series Ethernet Driver
5. After pressing the "Continue" button, the message "CNet CN200Eplus Series
Ethernet Adapter" should be displayed. Set the value for IRQ and
I/O Addresses to zero. Click on the OK button.
6. Now, the driver has been installed. Select the OK button from
the Network window. The protocols and driver will bind together.
7. Reboot
[MenuTitle] Windows 95
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > Windows 95 *
***********************************************
The driver for Windows 95 is located in the \WIN95 subdirectory
of the PowerNIC diskette.
PnP MODE --
Windows 95 has three versions so far. Version 0, A and B. You can select
the "System" icon in "Control Panel" box. On the System dialogue box,
the "40.00.950" message is version 0, "40.00.950 A" is version A and
"40.00.950 B" is version B. For version 0 and A, please follow the
"New Hardware Found" installation procedures. For version B (OSR2), go
to "Update Device Driver Wizard" installation procedures.
1. Insert CNet's CN200/600/650Eplus PwerNIC(tm) PC Card Ethernet adapter
into your computer's ISA-bus slot.
2. Connect the network cable to the RJ-45 or BNC connector.
3. Turn on the computer to run Windows 95.
"New Hardware Found" installation procedures:
4. When "New Hardware Found" window shows up, move mouse pointer to "Driver
from disk provided by hardware manufacturer", and then push "OK".
5. When "Install From Disk" window shows up, type "A:\WIN95" or "B:\WIN95"
in the input drive and path box where the driver is stored.
6. After the driver information shows up, select (highlight)
the "CNet PowerNIC CN200E/600/650Eplus PnP Ethernet Adapter" and click "OK".
7. When "Insert disk" window shows up, push "OK" button and then choose
a correct path to load *.dll files, i.e. D:\WIN95.
8. After "System Setting Change" window shows up, the installation is done.
Remove your installation disk, push "YES" to restart Windows 95,
and the driver will function.
9. Installation is completed for Windows 95 version 0 and A.
"Update Device Driver Wizard" installation procedures:
If your Windows 95 is version B (OSR2), you must CAREFULLY install
PowerNIC LAN card drivers from the release diskette, due to that
this version's "Update Device Driver Wizard" utility has poor error
recovery ability. (If you make mistakes during the installation,
refer to Appendix A for the error recovery). Please follow the
installation steps in details below.
4. When the "Update Device Driver Wizard" dialogue box shows up, and
in it, it says "This wizard will complete the installation of
"NE2000 Compatible", put this PowerNIC LAN card's release
diskette to floppy drives and make sure the the drive's door is
CLOSED. Then click "Next" button ONE TIME only. (Don't rush to push the
"Next" button again. The rush "Next" button clicked would be assumed as
"Finished" and may cause error installations (Appendix A for error
recovery). It is going to take 30 seconds for Windows 95 to search the
card's driver. Then, another message "Windows found the following updated
driver for this device: CNet PowerNIC CN200/600/650Eplus Ethernet Adapter",
shows up, then click "Finish" button to complete the driver installation.
(If it shows "Windows was unable to locate a driver for this device.",
You may also click "Other Locations" and type A:, A:\WIN95, B:, or
B:\WIN95, then click "OK" button). After the "Finish" button id clicked,
Windows starts to copy files from Windows 95 CD-ROM to your hard
disk. This is going to take around two minutes, please wait.
5. When the "Copying Files" dialogue shows up to request the directory
for the "E200P.SYS" file. Type "A:\WIN95" or "B:\WIN95" where A:
or B: drive is the place you put the release dskette in, then click "OK".
Windows 95 also request Windows95 CD directory to copy network-
related files. Please type the your Windows 95 CD directory name.
(Traditionally, it is D:\WIN95 or D:\WINDOWS).
6. Restart your PC to complete the installation.
Appendix A: (Valid only for WIndows 95 version B installation)
No matter what mistakes you made in the version B's installtion procedures
above and can not install the card to Windows 95. The "Update Device Driver
Wizard" utility still REGISTERS to Windows 95 that the card is installed
(with incoomplete error info., of sourse). Even though you carefully follow
the installation procudures above for the second time to successfully install
the driver, Windows 95 still treats the card as bad because the error data
was already REGISTERED. Therefore, you have to remove the REGISTERED errors,
before you try to install the driver again. The following describes the
details to remove the registered errors.
1. Click "Network" icon in the "Control Panel" box and remove the
PowerNIC Ethernet card you just successfully installed if any.
2. Select "Start" button (left-down corner) and select "Run" item.
Type REGEDIT, the registry edidor utility , then click "OK" button to
execute it.
3. In the Registry Editor dialogue, double-click "HKEY_LOCAL_MACHINE" item,
double-click "Enum", then double-click ISAPNP item. Select the
"JQE9008", then delete it, which is the error registered.
Close Register Editor dialogue.
4. Reboot Windows 95 again to carefully follow the installtion procedures
above again.
-------------------------------------------------------------------------------
JUMPERLESS MODE --
1. From the Windows 95 main screen, click on the "My Computer" icon.
Choose the "Control Panel" subwindow, and then the "Network"
icon to install the network driver.
2. In the Network box, select the "Add" button.
3. Now, the "Select Network Component Type" window shows four options:
"Client", "Adapter", "Protocol", and "Service".
Choose "Adapter". The "Select Network Adapter" window appears.
4. In the "Manufacturers" box, highlight "[detect net driver]".
Then click the "Have Disk ..." button.
5. There is a box to input the drive and path the driver is located.
Key in "A:\WIN95" (assuming this diskette is in drive A).
6. After the driver information appears, select
"CNet PowerNIC CN200/600/650Eplus PnP Ethernet Adapter".
7. Return to the "Network" window. Highlight the selected driver, and
press the "Properties ..." button which includes "Driver Type",
"Bindings", and "Resources". Choose "Resources" and enter the
correct values for "Interrupt [IRQ]" and "I/O address range". (These
values can be found from the "Adapter Configuration" feature of the
PowerNIC SETUP program.
8. Push the "OK" button in the "Network" window and Windows 95 will
construct the driver configuration. When the "Insert disk" window appears,
push the OK button and then choose a correct path to restore *.dll
files, i.e. C:\WIN95.
9. After the "System settings change" window appears, the installation
is done. Select "YES" to restart Windows 95, and the driver will
be functional.
[MenuTitle] PC/NFS
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > PC/NFS *
***********************************************
The driver for PC/NFS is located in the \NDIS_20 subdirectory
of the PowerNIC diskette.
1. Prepare the "QuickNDIS with drivers for PC-NFS" diskette and insert
it into the appropriate drive.
2. Run the QUICKNDIS command.
3. After the "NDIS Driver" menu appears, choose "zero" for the third
party driver.
4. Next, input path and make sure the driver, filename with extension NIF,
and PROTOCOL.INI are in the diskette drive with path "A:\NDIS_20\".
5. Confirm that the driver name is correct. The message "CNet CN200E Series
Ethernet Adapters" should be displayed.
6. When the driver is installed, user must configure the IRQ, I/O address,
and driver name in the PROTOCOL.INI file. Default values are 0, 0x0, and
E200P$.
7. Add the network device driver in the CONFIG.SYS file and the
'NETBIND' command in the AUTOEXEC.BAT file. Example:
DEVICE=C:\LANMAN\E200P.DOS <----- in CONFIG.SYS file
C:\LANMAN\NETBIND <----- in AUTOEXEC.BAT file
When done, reboot the workstation. The network card driver will be
loaded into memory.
[MenuTitle] LAN Support Program
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > LAN Support Program *
***********************************************
The driver for LAN Support Program is located in the \NDIS_20 subdirectory
of the PowerNIC diskette.
1. Copy A:\NDIS_20\E200P.DOS to a LAN Support Program directory.
2. Add DEVICE=\PATH\E200P.DOS to the CONFIG.SYS file.
3. Modify the PROTOCOL.INI file under the LAN Support Program
directory as follows:
BINDINGS = E200P
:
:
[E200P]
DRIVERNAME = E200P$ ; The values should be set to '0' for
IOBASE = 0X300 ; automatic configuration or the same
INTERRUPT = 3 ; as the values fixed in the adapter.
[MenuTitle] Banyan VINES
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > Banyan VINES 4.10 *
***********************************************
The driver for Banyan VINES is located in the \NDIS_20 subdirectory
of the PowerNIC diskette.
1. Copy the E200P.DOS driver from this diskette (\NDIS_20\E200P.DOS) to the
VINES directory on the hard disk which contains the file BAN.EXE.
2. Create a LANMAN subdirectory under the root, and copy the PROTOCOL.INI file
from the \NDIS_20 subdirectory of the PowerNIC diskette to this directory.
3. Add the following two lines to your CONFIG.SYS file:
DEVICE=<VINES directory>\PROTMAN.DOS
DEVICE=<VINES directory>\E200P.DOS
4. Check the PROTOCOL.INI file to make sure that the values in the INTERRUPT
and IOBASE fields agree with the settings on the LAN card (choose zero's
to autosense). The adapter settings can be found in the "Adapter
Configuration" feature of the PowerNIC SETUP program.
5. Run PCCONFIG and configure the NDIS Ethernet driver. Enter the interrupt
level and fill in the Section Name "E200P_NIF" in the "BINDINGS =" field.
[MenuTitle] Wollongong
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > Wollongong Pathway *
***********************************************
The driver for Wollongong Pathway is located in the \NDIS_20 subdirectory
of the PowerNIC diskette.
1. Make a directory called NDIS on your hard disk.
2. Copy E200P.DOS and PROTOCOL.INI from the \NDIS_20 subdirectory of this
PowerNIC diskette to the C:\NDIS directory.
3. Change diskettes and run the Pathway Setup Program, PWSETUP
4. After the "Pathway Setup Program for DOS" window appears, choose
"Installation".
5. In "Installation", select "Pathway Run Time". From "Pathway Run Time",
choose "Quick Setup for NDIS".
6. In the "Pathway Runtime Quick Installation for NDIS" window
input the appropriate floppy disk drive letter as the source drive.
The destination should be "C:\PATHWAY".
Also, set the IP address and the number of subnet mask bits.
7. In the "Driver NDIS and Kernel Configuation" window, enter the path
"C:\NDIS" to the device driver and the PROTOCOL.INI file
8. There is a screen editor for modifying the configuations with
respect to I0BASE, Hardware Interrupt, and Driver Name. To exit
the editor press the F4 key. Zero values of IRQ and IO address
are used to autodetect the CN200/600/650Eplus adapter.
9. Next, use the select bar to change the software interrupt and
network frame type.
10. The Pathway Setup program will copy all relevant files and modify
the CONFIG.SYS file as well as the AUTOEXEC.BAT file automatically.
11. Reboot.
[MenuTitle] DEC PathWorks
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > DEC PathWorks *
***********************************************
The driver for DEC PathWorks is located in the \NDIS_20 subdirectory
of the PowerNIC diskette.
1. Run the "NETSETUP.EXE" program from the "Client Setup" diskette.
2. Choose the default value "Non-LK250 keyboard" as the keyboard type.
3. Select "DECNET" in "Network Transport" screen.
4. Insert the "PWRKS V4.1 DNET TRNSPRT" diskette into the appropriate
drive.
5. Assign the destination drive (default is C:).
6. The following are the questions & answers for the installation dialog.
<1> Create an initial workstation diskette with default "NO".
<2> Input workstation node name and address.
<3> Use asynchronous DECNET (ASYNC) with default "NO".
<4> Use only DECNET DOS components with default "NO".
<5> Input server node name and address.
<6> Append LK250 keyboard setup info to the AUTOEXEC.BAT file with default
"NO".
<7> Select network adapter type with "ETHERNET".
<8> Choose the "Other NDIS" item and input the NDIS driver path to be
A:\ or B:\ plus "NDIS_20\E200P.DOS".
<9> Input the path of PROTOCOL.INI as the same as in step <8>.
<10> Add the system service DOS subdirectory to the DOS search path with
default "NO".
7. In the CONFIG.SYS file, modify the statement
"SHELL=C:\COMMAND.COM C:\DOS\ /P" to be
"SHELL=C:\COMMAND.COM C:\DOS\ /P /E:319" .
The value of the "/E" option should not be less than 319.
8. The PROTOCOL.INI file may need to be revised. Make sure the
IRQ, NI_IRQ variable, is in agreement with the adapter card's IRQ.
[MenuTitle] UNIX Stream Driver
***********************************************
* CNet ISA-Bus PowerNIC Driver Installation *
* > SCO UNIX Open System 5 *
***********************************************
The ISA-Bus PowerNIC adapters are fully NE2000 compatible. Use the NE2000
driver bundled with Open System 5.
METHOD 1 --
1. From the 'SINGLE USER MODE', enter the root password in order to
have 'System Maintenance Mode'.
2. Enter 'netconfig' after '#'.
3. The 'Network Configuration Manager' window will appear, choose 'Hardware'
and select 'Add new LAN adapter'.
4. When the 'Add new LAN adapter' window appears, select 'NOVELL NE2000' and
[ENTER] to continue.
5. The 'Search for network adapter' box will be displayed. Choose 'no'.
6. After the "Network Driver Configuration" window appears, enter the I/O
address and the interrupt vector and press 'ok'.
7. In the "Add protocol" window, there are two items: "SCO IPX/SPX" or
"SCO TCP/IP". Choose "SCO TCP/IP".
8. After the "SCO TCP/IP configuration" window appears, enter the proper
values for "Local Host name", "IP address", "Netmask", and so on.
9. When the message box shows "the following products were successfully
configured into the system", installation is done. Exit the "Network
Driver Configuration" window.
10. After the 'Question' box appears, push the OK button to re-link the Kernel.
11. Enter 'haltsys' to reboot the UNIX system.
METHOD 2 --
1. From the 'X window' mode, click 'System Adaministration' icon.
2. In the 'System Adaministration' window, choose 'Networks'.
3. A window will appear, choose 'Network Configuration Manager'.
4. After the 'Network Configuration Manager' window appears, the installation
procedure is the same as Method 1, beginning at Step 3.
[MenuTitle] Remote BootROM
*************************************************
* CNet ISA-Bus PowerNIC Boot ROM Installation *
* *
*************************************************
A boot ROM socket is provided on each adapter card. The purpose of
the boot ROM is for use in diskless workstations or other machines
where a standardized boot configuration is desirable.
To install a remote boot ROM:
1. Position the ROM chip above the socket of the Ethernet adapter card.
Align the notch on the ROM with the notch on the socket.
2. Slowly but firmly push the ROM into the socket. Be careful not
to bend any of the pins.
3. Plug the LAN adapter card into the machine, turn on the computer, and
then connect the computer to the server.
4. Run the SETUP.EXE program to enable the boot ROM by assigning it an address.
5. Save the address when prompted. Exit the SETUP program.
6. When exiting the SETUP program, you will be prompted to power off the
system to implement the change in Boot ROM setting. Power off and reboot.
Below are three procedures for installing IPX, RPL, and NDIS Boot ROMs.
IPX Boot ROM Installation for NetWare v3.11 and v4.x
-------------------------------------------------------------------------------
1. Prepare a bootable diskette, which includes AUTOEXEC.BAT, LSL.COM,
RPLODI.COM, Driver, IPXODI.COM, and NETX.EXE (or VLM.EXE for NetWare
v4.x), and insert the diskette in the appropriate floppy disk drive.
2. Execute DOSGEN.EXE in the F:\SYSTEM directory to transfer the
diskette contents to the image file NET$DOS.SYS, and locate the
image file to the F:\LOGIN directory. Then copy A:\AUTOEXEC.BAT to
the F:\LOGIN directory.
3. At the server, load the server driver (in NetWare v3.11, frame
type set to 802.3, and in NetWare v4.x frame type set to 802.2 and 802.3),
and bind IPX to the server driver.
4. Remove the diskette and reboot the computer. This computer will
automatically boot and connect to the server.
RPL Boot ROM Installation for NetWare v3.11 and v4.x
-------------------------------------------------------------------------------
1. Prepare a bootable diskette which includes AUTOEXEC.BAT, LSL.COM,
Driver, IPXODI.COM, and NETX.EXE (or VLM.EXE for NetWare v4.x), and
insert this diskette in the appropriate disk drive.
2. Execute DOSGEN.EXE in the F:\SYSTEM directory to transfer the
diskette contents to the image file NET$DOS.SYS, and locate the
image file to the F:\LOGIN directory. Then copy A:\AUTOEXEC.BAT to the
F:\LOGIN directory.
3. On the server site, load RPL.NLM and bind RPL to the server driver.
4. Remove the diskette and reboot the computer. This computer will
automatically boot and connect to the server.
NDIS Boot ROM Installation for MS LAN Manager
-------------------------------------------------------------------------------
1. Execute SETUP program to install the LAN Manager server with remote boot
service (in LAN Manager v2.1, select "REMOTEBOOT" protocol, and in MS LAN
Manager v2.2, select DLC protocol).
2. Execute RPLSETUP program to install LAN Manager Enhanced for MS-DOS
workstations or LAN Manager for OS/2 workstations.
3. Log on as an administrator, execute RPLINST program, and then invoke NET
START REMOTEBOOT.
Note: For MS OS/2 workstations, the hardware interrupt of the adapter
card must be set as IRQ=2. This does not apply to MS-DOS
workstations.