INSTALLING NDIS DRIVERS. 7.1. INSTALLATION NDIS DRIVER 7.1.1. Mic
|
|
|
Top Searches for this datasheet
Installing NDIS Drivers
INSTALLING NDIS DRIVERS.
7.1. INSTALLATION NDIS DRIVER 7.1.1. Microsoft Windows 7.1.2. Microsoft Windows Workgroups 3.11 7.1.3. Installation NDIS Driver. 7.1.4. NDIS Driver Installation When Controller Detected System Boot. 7.1.5. Installation WINNT 3.51 NDIS Driver 7.2. INSTALLATION NDIS DRIVER 7.2.1. Microsoft Windows 8.1. 8.2. 9.1. INSTALLING UNIX DRIVER (ODT BELOW).
DRIVER INSTALLATION FROM COMMAND LINE PROMPT. UNIX DRIVER KEYWORDS INSTALLING UNIX DRIVER (SCO OPENSERVER ABOVE)
UNIX DRIVER KEYWORDS
INSTALLING DRIVER (RELEASE 4.0). 10.1. SOFTWARE RELEASE DRIVER KEYWORDS 10.1.1. Keywords. INSTALLING UNIXWARE DLPI DRIVER. 11.1. 11.2. 11.3. DRIVER INSTALLATION USING DESKTOP DRIVER INSTALLATION FROM COMMAND LINE PROMPT UNIXWARE DLPI DRIVER KEYWORDS
INSTALLING UNIXWARE DLPI DRIVER 12.1. UNIXWARE DLPI DRIVER KEYWORDS
INSTALLING VXWORKS DRIVER 13.1. 13.2. INTRODUCTION. INSTALLATION PROCEDURE
INSTALLING SUNSOFT SOLARIS DRIVER. 14.1. SUNSOFT SOLARIS DRIVER KEYWORDS.
INSTALLING PACKET DRIVER. 15.1. 15.2. 15.3. 15.4. DRIVER INSTALLATION USING AMINSTAL UTILITY DRIVER INSTALLATION FROM COMMAND LINE PROMPT KEYWORD EXAMPLE PACKET DRIVER KEYWORDS
INSTALLING COMPONENT INTERFACE (CI) 16.1. DESKTOP MANAGEMENT INTERFACE (DMI) 16.1.1. Service Layer. 16.1.2. Component Interface (CI). 16.2. INSTALLATION PROGRAM (DMI VERSION 1.1) 16.2.1. Invoking DMINSTL. 16.2.2. Editing Input. 16.2.3. Starting Installation Program 16.2.4. Exiting Installation Program. 16.3. INSTALLATION PROCEDURE (DMI VERSION 2.0). INSTALLING UNIVERSAL BOOT
Installing NDIS Drivers
Installing NDIS Drivers
7.1.
Installation NDIS Driver
Network Driver Interface Specification (NDIS) driver specification developed Microsoft offer standard driver interface adapter cards. AMD's NDIS driver supports following environments: Microsoft Windows 3.1, 3.5, 3.51 Microsoft Windows Workgroups 3.11 Microsoft Windows Installation AMD's NDIS driver environments listed above described below. 7.1.1. Microsoft Windows Support provided Microsoft Windows (Versions 3.1, 3.5, 3.51) environment.
Notes: directory structure provided NDIS driver diskette been automatic installation. Also, more information found Microsoft Windows User's Guide. Only x86-based Windows platforms supported.
Follow steps listed below: Insert NDIS driver diskette into floppy drive. From Control Panel Windows Main window, double click Network icon install PCnet adapter card. Network Settings dialog box, choose Adapter. Network Adapter dialog box, pull down adapter card list menu select <Other> Requires disk from manufacturer from list continue. next window, enter:
A:\WINNT350
Then, select PCnet Family Ethernet Adapter from dialog
PCnet Family Network Driver Installation Guide install PCnet adapter card.
PCnet Family Ethernet Adapter Card Setup dialog box, select type (defaults nothing selected). more than network adapter card used, select type.
Note: Sometimes will work PCI-based systems. this case, selecting PCI1 PCI2 depending type.
_7.1 PCnet-ISA adapter card: Enter correct port, IRQ, channel values correspond with what card jumpers. values selected, default values will chosen driver. _7.2 PCnet-ISA+, PCnet-ISA PCnet-32, PCnet-PCI adapter cards: channel values auto-detected. However, values must specified multiple network cards. values using AMINSTAL Utility (see Express Installation section more details). Shutdown Windows AMINSTAL Utility from DOS.
Note: using PCnet-PCI adapter card, need AMINSTAL Utility.
Reboot your system complete driver installation process.
additional information, refer your Microsoft Windows documentation. addition, user review README.TXT file WINNT directory NDIS driver diskette. 7.1.1.1. Keyword Example
keyword, into PCnet Family Ethernet Adapter Card Setup dialog (see instructions above access this dialog box), activate button keyword described Software Keywords section (Appendix
Installing NDIS Drivers 7.1.2. Microsoft Windows Workgroups 3.11 Support provided Microsoft Windows Workgroups (Version 3.11) environment. Microsoft Windows Workgroups 3.11 supports both NDIS 2.01 NDIS drivers. provides both these NDIS drivers.
Notes: format procedure install NDIS drivers Windows Workgroups 3.11 different from that Windows Workgroups 3.1. directory structure that provided NDIS driver diskette been setup automatic installation. Installation section this manual provides more details regarding driver installation. Also, more information found Microsoft Windows Workgroups 3.11 User's Guide.
Follow steps listed below: Insert NDIS driver diskette into floppy drive. Windows Workgroups 3.11 Program Manager, double click Windows Setup icon. From Options Menu, select Change Network Settings. From Network Setup dialog box, select Drivers. button install PCnet NDIS 2.01 NDIS drivers. Network Drivers dialog box, select Adapter button install PCnet device drivers. Network Adapter window, choose Unlisted Updated Network Adapter from menu then select
Note: Detect button, Am2100/Am1500T, PCnet Family selections from menu standard drivers uses previous release driver software.
Install Driver dialog will appear. Enter floppy drive containing NDIS driver diskette specify Windows Workgroups 3.11 path install PCnet drivers. example, enter:
A:\WFW311\ISA cards A:\WFW311\PCI cards
Then select Advanced Micro Devices PCnet Family selection will appear under Network Adapters list. Select continue. Answer series questions correct base port, channel, channel.
PCnet Family Network Driver Installation Guide Network Drivers dialog box, select Setup. PCnet Family dialog box: _9.1 PCnet-ISA adapter card: Specify IRQ, base port, channel correspond jumper settings adapter card. _9.2 PCnet-ISA+, PCnet-ISA PCnet-32, PCnet-PCI adapter cards: interrupt (IRQ) Auto_scan base port Select Network Drivers dialog box, select Close. Network Setup dialog box, select Microsoftspecific dialog boxes, select Skip. Install Driver dialog box, enter:
\WFW311 Note: Auto_scan selected PCnet-ISA+, PCnet-ISA PCnet-32, PCnet-PCI, then value need specified; however, Windows Workgroups 3.11 will issue warning message regarding possible interrupt conflict. This temporary configuring interrupt channel until real value according EEPROM configuration.
Select exit. Windows Workgroups 3.11 will user reboot machine once installation completed. installation NDIS driver Windows Workgroups 3.11 complete. 7.1.2.1. Keyword Example
LED0 keyword value, follow instructions given above access advanced settings PCnet adapter card. dialog will appear keyword options. LED0 setting, enter value desired from list given Software Keywords section (Appendix Table NDIS Driver Keywords.
Installing NDIS Drivers 7.1.3. Installation NDIS Driver This installation assumes that there PCnet controller driver installed system that this upgrade. install driver from distribution floppy, follow these instructions: Click Start button, choose Settings, then choose Control Panel. Choose Network icon from menu. Then delete already installed network card. From distribution diskette copy file Netamd.inf from <drive>:\WIN95\MAC\NDIS3 c:\WINDOWS\INF Then shut down system. reboot, Win95 detects PCnet controller installed system prompts user path distribution floppy. example, a:\WIN95\MAC\NDIS3 Note: case, Win95 does detect controller system, then skip following next installation procedure. rest network files copied from Win95 Distribution disks. completion installation, user will prompted Shutdown system. When System comes again, network should running. Highlight PCnet Adapter Network Control Panel select File Sharing Box. Choose appropriate here. experienced user choose advanced button Network Control panel Settings appropriate parameters.
PCnet Family Network Driver Installation Guide
7.1.4. NDIS Driver Installation When Controller
Detected System Boot
Click Start button, choose Settings, then choose Control Panel. Choose Network icon then click Add. Select PCnet Family Adapters, from which appropriate adapter type chosen. user prompted choose resources. Select resources without conflicts. experienced user choose advanced button Network Control panel Settings appropriate parameters. Highlight PCnet Adapter Network Control Panel select File Sharing Box. Choose appropriate here. completion, shutdown system then reboot. NDIS driver should running now.
Installing NDIS Drivers
7.1.5. Installation WINNT 3.51 NDIS Driver This installation procedure same procedure WINNT 3.1/3.5 driver. Refer Section 7.1. WINNT 3.51 NDIS driver distribution diskette under WINNT 3.51 subdirectory. There only difference. WINNT 3.51 will detect PCnet-PCI controller system PCI-only dialog will appear. This means user does have select Scan controllers. there non-PCI controller system, then PCnet VL/ISA dialog appears, appropriate parameters chosen WINNT 3.1/3.5 driver case. there ISA/VL controller same system, then controller detected first, dialog appears. Then, when user adds next adapter, PCnet VL/ISA dialog appears appropriate parameters chosen WINNT 3.1/3.5 driver case.
Note: This driver will work WINNT 3.51 onwards only compatible with 3.1/3.5. name driver changed AMDPCN.SYS.
7.1.5.1.
NDIS Driver Keywords
Table NDIS Driver Keywords. Table NDIS Driver Keywords Keyword Keyword Name Description Address IOADDRESS Interrupt type designation INTERRUPT DMACHANNEL BUS_TO_SCAN Additional Keyword Details Common Keywords. Common Keywords. Common Keywords. Driver Specific Keywords. Range Default
PCnet Family Network Driver Installation Guide Address NETADDRESS This keyword allows user specify overwrite IEEE Mfr. address. This must edited PROTOCOL.INI registry. Present valid IEEE address Present
Full Duplex
FDUP
Supported PCnetISA only
FDUP keyword used enable disable full duplex 10BaseT ports. Common Keywords.
Present
(What EEPROM)
Note:
keywords available NDIS driver activated selecting options through dialog appropriate operating system.
Installing NDIS Drivers
7.2.
Installation NDIS Driver
Network Driver Interface Specification (NDIS 4.x) developed Microsoft offer standard driver interface adapter cards. AMD's NDIS driver supports following environments: Microsoft Windows Microsoft Windows OSR2 above (Memphis, etc.) Installation details AMD's NDIS driver described below. 7.2.1. Microsoft Windows Support provided Microsoft Window (Version 4.0) environment. Notes: directory structure that provided NDIX driver diskette been automatic installation. Also, more information found Microsoft Windows User' Guide. Only x86-based Windows platforms supported. Follow steps listed below: Insert NDIS driver diskette into floppy drive. From Control Panel Windows Main window, double click Network icon install PCnet adapter card. From Network Settings dialog box, choose Adapter click Add. From Select Network Adapter dialog box, click Have Disk button. From Insert Disk window, enter: A:\WINNT\MINIPORT\NDIS4 completion installation, user will prompted shut down system. When system comes again, network should running. Highlight PCnet adapter Network Control Panel select File Sharing box. Choose appropriate here. experienced user choose Advanced button Network Control Panel settings appropriate parameters.
PCnet Family Network Driver Installation Guide
Installing UNIX Driver
Installing Unix Driver
(ODT below)
Support provided UNIX (Version 3.2.4) environment. UNIX stream-based driver should installed from command line prompt.
Notes: Support Version 3.2.2 longer provided AMD. directory structure that provided Unix driver diskette been automatic installation. Installation section this manual provides more details regarding driver installation. Also, more information found UNIX User's Guide.
8.1.
Driver Installation From Command Line Prompt
currently have older UNIX driver installed your system, should remove prior installing newer version. netconfig custom utilities remove older driver version. Refer your UNIX documentation needed. After removing your existing driver, then proceed with installing newer UNIX driver.
Note: custom netconfig utilities provided SCO.
Follow steps listed below: Login root. Insert UNIX driver diskette into floppy drive Make sure floppy drive which this diskette inserted fd0. This default floppy drive where UNIX custom utility will look driver corresponding installation script. custom utility typing:
custom
Then press <Enter>
Note: using drive custom utility with option specify correct drive where UNIX driver diskette located.
custom utility main menu, will four main options upper left hand corner screen (Install, Remove, List, Quit). right/left arrow keys select Install option then press <Enter>. Next, up/down arrow keys select product press <Enter>. Three options will displayed (Entire Product, Packages, Files). Select Entire
PCnet Family Network Driver Installation Guide Product press <Enter>. following message will displayed:
Insert requested volume press <Return> continue installation Insert: Continue Distribution Floppy Volume Quit
Press <Enter> continue. following message will displayed:
Installing custom data files. Insert requested volume press <Return> continue installation Insert: Continue PCnet Family Driver Floppy Volume Quit
Press <Enter> continue. following message will displayed:
Extracting files. Checking file permissions.
will then returned custom utility main screen. Select Quit from custom utility main options. Answer want exit from custom utility. will then returned Unix prompt. Next, netconfig utility typing: netconfig Then press <Enter>. netconfig utility used configure UNIX driver different INT, DMA, address values. This utility also used driver protocol chain.
Note: netconfig utility modifies space.c file automatically must used order proper support BIOS calls.
Installing UNIX Driver
following will displayed:
Available options: chain Remove chain Reconfigure element chain Quit Select Option:
Select option (Add chain) typing: Then press <Enter>. following will displayed:
Select level chain quit:
Select appropriate level chain your system entering appropriate number (Num) value pressing <Enter>. Next, select appropriate number (Num) value PCnet Ethernet driver press <Enter>. Answer questions asked netconfig appropriate your system. Refer your UNIX documentation needed. Also, Software Keyword section this manual more details keyword settings.
Note: need modify keyword values, should edit space.c file needed. path this file /etc/conf/pack.d/pnt0/space.c
Select Quit from netconfig utility typing then press <Enter>. this point, should relink your kernel reboot system. Refer your UNIX documentation needed. installation UNIX driver complete.
PCnet Family Network Driver Installation Guide 8.2.
Unix Driver Keywords
Keywords added, deleted, and/or modified manually editing appropriate #define values space.c file. Appendix (Software Keywords) your UNIX Manuals more details. sample version this file listed below:
Copyright 1993 Advanced Micro devices, Inc. File: /etc/conf/pack.d/pnt0/space.c Version: Description: Unix System V/386 Config. file PCnet family Author: Leonid Grossman Created: 08/20/93 #include config.h defined(PNT3_UNITS) #define TOT_UNITS #elif defined(PNT2_UNITS) #define TOT_UNITS #elif defined(PNT1_UNITS) #define TOT_UNITS (PNT1_UNITS+PNT_UNITS) #else #define TOT_UNITS (PNT_UNITS) #endif #define MAX_MINORS Please modify #define TX_BUFFERS_0 Must power (1,2,4,8,.512) #define TX_BUFFERS_1 #define TX_BUFFERS_2 #define TX_BUFFERS_3 #define RX_BUFFERS_0 #define RX_BUFFERS_1 #define RX_BUFFERS_2 #define RX_BUFFERS_3 #define SCAN_TYPE_0 0-all, 1-PCI, 2-PnP, 3-VESA, 4-ISA, 5-PCI1, 6-PCI2 #define SCAN_TYPE_1 #define SCAN_TYPE_2 #define SCAN_TYPE_3 #define LED0_0 0xffffffff 0xffffffff defaults #define LED0_1 0xffffffff #define LED0_2 0xffffffff #define LED0_3 0xffffffff #define LED1_0 0xffffffff #define LED1_1 0xffffffff #define LED1_2 0xffffffff #define LED1_3 0xffffffff #define LED2_0 0xffffffff #define LED2_1 0xffffffff #define LED2_2 0xffffffff #define LED2_3 0xffffffff #define LED3_0 0xffffffff #define LED3_1 0xffffffff #define LED3_2 0xffffffff #define LED3_3 0xffffffff #define dmarotate_0 normal priority, rotate priority #define dmarotate_1 #define dmarotate_2 #define dmarotate_3 #define tp_0 autoselect mode, mode #define tp_1 #define tp_2 #define tp_3 #define fdup_0 default, AUI, 10BaseT,
Installing UNIX Driver
#define fdup_1 #define fdup_2 #define fdup_3 Please modify ACCESS_TYPE LAST_BUS parameters unless sure that values provided 'netconfig' wrong #define ACCESS_TYPE_0 #define ACCESS_TYPE_1 #define ACCESS_TYPE_2 #define ACCESS_TYPE_3 #define LAST_BUS_0 #define LAST_BUS_1 #define LAST_BUS_2 #define LAST_BUS_3 pnt_MaxStreams MAX_MINORS; pnt_TotalDevCount TOT_UNITS;
Structure used space.c pass configuration driver. This information copied pnt_DeviceStruct structure. struct pnt_ConfigStruct short index; short minors; short vec; short iobase; short ioend; short dma; short tx_buffers; short rx_buffers; long bus_scan; long led0; long led1; long led2; long led3; long dmarotate; long long fdup; long access_type; long last_bus; board index minor devices configured interrupt vector boards base memory address Ending base address channel used board Number Transmit buffers*/ Number Receive buffers*/ type search value value value value
struct pnt_ConfigStruct pnt_ConfigArray[TOT_UNITS] defined PNT_UNITS MAX_MINORS, PNT_0_VECT, PNT_0_SIOA, PNT_0_EIOA, PNT_CHAN, TX_BUFFERS_0, RX_BUFFERS_0, SCAN_TYPE_0, LED0_0, LED1_0, LED2_0, LED3_0, dmarotate_0, tp_0, fdup_0, ACCESS_TYPE_0, LAST_BUS_0
PCnet Family Network Driver Installation Guide
#endif defined PNT1_UNITS ,{1, MAX_MINORS, PNT1_0_VECT, PNT1_0_SIOA, PNT1_0_EIOA, PNT1_CHAN, TX_BUFFERS_1, RX_BUFFERS_1, SCAN_TYPE_1, LED0_1, LED1_1, LED2_1, LED3_1, dmarotate_1, tp_1, fdup_1, ACCESS_TYPE_1, LAST_BUS_1 #endif defined PNT2_UNITS ,{2, MAX_MINORS, PNT2_0_VECT, PNT2_0_SIOA, PNT2_0_EIOA, PNT2_CHAN, TX_BUFFERS_2, RX_BUFFERS_2, SCAN_TYPE_2, LED0_2, LED1_2, LED2_2, LED3_2, dmarotate_2, tp_2, fdup_2, ACCESS_TYPE_2, LAST_BUS_2 #endif defined PNT3_UNITS ,{3, MAX_MINORS, PNT3_0_VECT, PNT3_0_SIOA, PNT3_0_EIOA, PNT3_CHAN, TX_BUFFERS_3, RX_BUFFERS_3, SCAN_TYPE_3, LED0_3, LED1_3, LED2_3, LED3_3, dmarotate_3, tp_3, fdup_3, ACCESS_TYPE_3, LAST_BUS_3 #endif
Installing Unix Driver
(SCO OpenServer above)
Note: PCnet Software Release only. OpenServer built-in support PCnet driver. documentation network driver installation directions. upgrade PCnet driver Version, follow steps below: Copy install file from SCOUNIX.50 directory diskette file format. copied with doscp command from MERGE session. install command upgrade PCnet driver package.
9.1.
Unix Driver Keywords
Keywords added, deleted, and/or modified using ADVANCED button PCnet driver during netconfig installation. Appendix (Software Keywords) your UNIX Manuals more details. driver additional keyword, pcnet2 non-zero value, pcnet2 keyword enables advanced features PCnet-PCI2 chip.
PCnet Family Network Driver Installation Guide
Installing Driver (Release 4.0)
Open Server 5.0.4 have driver their installation CD-ROMs. After operating system installed, updated driver installed following steps below: Boot system after inserting network card. Install older driver that comes with 5.0.4 with netconfig bind with TCPIP. Relink reboot. make sure that works, follow these steps: _2.1 Start NETCONFIG. _2.2 Click select following options: Hardware, Adapter, Adapter, Protocol other Options. Copy following four files from updated driver files from software Release files: driver.o space.c space.h pnt.h Link kernel with command: /etc/conf/cf.d/link_unix then reboot. Make sure following values correct /etc/conf/pack.d/space.h file: PNT_0_PCI_BUS PNT_0_PCI_DEV PNT_0_PCI_FUNC
above values PCI; those will different. Make sure they Note: exists during driver removal when using netconfig file. Manually remove directory under /etc/conf/pack.d, otherwise next installation driver will work.
PCnet Family Network Driver Installation Guide
10.1.
Software Release Driver Keywords
Software Release driver additional keywords added user's convenience. user access space.c file /etc/conf/pack.d/pnt/ directory edit file following keywords requirement: FULLDUP Speed100 MII_EXT_PHY 10BaseT Auto-Negotiation overrides when AUI, MII_EXT_PHY, 10BaseT keywords Care should taken that only interface none enabled. none enabled, then Auto-Negotiation overrides. Also FULLDUP Speed100 enabled disabled setting values respectively. Note: Speed100 controllers that support only Mbps data transfer, ignored driver/controller Mbps speed effective. 10.1.1.
Keywords
/etc/conf/pack.d/space.h file edited reflect desired values LEDs controllers. user uses default LEDs, LEDs reflect specifications. user changes values, drivers reprogram LEDs reflect desired value. These values edited changed space.h file reflect user's desired values. Note: After making keyword changes Unix kernel must linked with command /etc/conf/cf.d/link_unix rebooted changes effective. space.c space.h files provided below reference.
space.c #include #include #include #include #include sys/types.h sys/stream.h sys/mdi.h sys/pci.h pnt.h
#include #include
config.h space.h
#define MAX_MINORS pnt_MaxStrepnt MAX_MINORS; pnt_TotalDevCount PNT_CNTLS;
kathyp Fulldup=0; Speed100=0; Aui=0; TenBaseT=0; MII_ExtPhy=1; struct pnt_ConfigStruct pnt_ConfigArray[PNT_CNTLS] defined PNT_0 MAX_MINORS, PNT_0_VECT, PNT_0_SIOA, PNT_0_EIOA, PNT_0_DMA, PNT_0_TX_BUFFERS, PNT_0_RX_BUFFERS, PNT_0_LED0, PNT_0_LED1, PNT_0_LED2, PNT_0_LED3, PNT_0_DMAROTATE, PNT_0_TP, PNT_0_FDUP, PNT_0_PCNET2, PNT_0_PCI_BUS, PNT_0_PCI_DEV, PNT_0_PCI_FUNC #endif defined PNT_1 ,{1, MAX_MINORS, PNT_1_VECT, PNT_1_SIOA, PNT_1_EIOA, PNT_1_DMA, PNT_1_TX_BUFFERS, PNT_1_RX_BUFFERS, PNT_1_LED0, PNT_1_LED1, PNT_1_LED2, PNT_1_LED3, PNT_1_DMAROTATE, PNT_1_TP, PNT_1_FDUP, PNT_1_PCNET2, PNT_1_PCI_BUS, PNT_1_PCI_DEV, PNT_1_PCI_FUNC #endif defined PNT_2 ,{2, MAX_MINORS, PNT_2_VECT, PNT_2_SIOA,
PCnet Family Network Driver Installation Guide
PNT_2_EIOA, PNT_2_DMA, PNT_2_TX_BUFFERS, PNT_2_RX_BUFFERS, PNT_2_LED0, PNT_2_LED1, PNT_2_LED2, PNT_2_LED3, PNT_2_DMAROTATE, PNT_2_TP, PNT_2_FDUP, PNT_2_PCNET2, PNT_2_PCI_BUS, PNT_2_PCI_DEV, PNT_2_PCI_FUNC #endif defined PNT_3 ,{3, MAX_MINORS, PNT_3_VECT, PNT_3_SIOA, PNT_3_EIOA, PNT_3_DMA, PNT_3_TX_BUFFERS, PNT_3_RX_BUFFERS, PNT_3_LED0, PNT_3_LED1, PNT_3_LED2, PNT_3_LED3, PNT_3_DMAROTATE, PNT_3_TP, PNT_3_FDUP, PNT_3_PCNET2, PNT_3_PCI_BUS, PNT_3_PCI_DEV, PNT_3_PCI_FUNC #endif extern pntopen(), pntclose(), pntuwput(); extern nulldev(); struct module_info pnt_minfo 1514, 16*1514, 12*1514 struct qinit pnturinit pntopen, pntclose, nulldev, &pnt_minfo, struct qinit pntuwinit pntuwput, pntopen, pntclose, nulldev, &pnt_minfo, struct streamtab pntinfo &pnturinit, &pntuwinit, @(#) space.h 94/12/19 SCOINC channel modified jumpered adapters #define PNT_0_DMA #define PNT_1_DMA #define PNT_2_DMA #define PNT_3_DMA Number transmit buffers #define PNT_0_TX_BUFFERS #define PNT_1_TX_BUFFERS
#define PNT_2_TX_BUFFERS #define PNT_3_TX_BUFFERS Number receive buffers #define PNT_0_RX_BUFFERS #define PNT_1_RX_BUFFERS #define PNT_2_RX_BUFFERS #define PNT_3_RX_BUFFERS 10-BaseT enforced non-zero #define PNT_0_TP #define PNT_1_TP #define PNT_2_TP #define PNT_3_TP LED0 #define #define #define #define LED1 #define #define #define #define LED2 #define #define #define #define LED3 #define #define #define #define FULL #define #define #define #define value PNT_0_LED0 PNT_1_LED0 PNT_2_LED0 PNT_3_LED0 value PNT_0_LED1 PNT_1_LED1 PNT_2_LED1 PNT_3_LED1 value PNT_0_LED2 PNT_1_LED2 PNT_2_LED2 PNT_3_LED2 value PNT_0_LED3 PNT_1_LED3 PNT_2_LED3 PNT_3_LED3 0xc0 0xc0 0xc0 0xc0 0xb0 0xb0 0xb0 0xb0 0x4088 0x4088 0x4088 0x4088 0x81 0x81 0x81 0x81
DUPLEX enabled PNT_0_FDUP PNT_1_FDUP PNT_2_FDUP PNT_3_FDUP
controller rotate priority mode #define PNT_0_DMAROTATE #define PNT_1_DMAROTATE #define PNT_2_DMAROTATE #define PNT_3_DMAROTATE Advanced PCnet features #define PNT_0_PCNET2 #define PNT_1_PCNET2 #define PNT_2_PCNET2 #define PNT_3_PCNET2 number #define PNT_0_PCI_BUS #define PNT_1_PCI_BUS #define PNT_2_PCI_BUS #define PNT_3_PCI_BUS device number #define PNT_0_PCI_DEV #define PNT_1_PCI_DEV #define PNT_2_PCI_DEV
PCnet Family Network Driver Installation Guide
#define PNT_3_PCI_DEV adapter function number #define PNT_0_PCI_FUNC #define PNT_1_PCI_FUNC #define PNT_2_PCI_FUNC #define PNT_3_PCI_FUNC
Installing Unixware DLPI
Driver
Support provided Unixware (Version 1.1) environment. AMD's Unixware driver compliant with AT&T's Data Link Provider Interface (DLPI) specification. Unixware driver installed using Unixware Desktop Graphical User Interface (GUI) from Unixware command line prompt. Both methods explained below. 11.1.
Driver Installation Using Desktop
currently have older Unixware driver installed your system, should remove prior installing newer version. After removing your existing driver, then proceed with installing newer Unixware driver. Follow steps listed below: Unixware Desktop window, double click System_Setup icon. System Setup window, double click Appl-n_Setup icon. following message will displayed:
Cataloging applications your system; Please wait
Wait system catalog existing Applications/Sets currently installed. Insert Unixware DLPI driver diskette into drive From Application Setup menu bar, select View. From View drop down menu, select Uninstalled Appl'ns. From Uninstalled Appl'ns drop down menu, select Disk_A. following message will displayed:
Cataloging applications Disk_A; Please wait
Wait system catalog existing Applications/Sets currently Disk Select icon clicking From Application Setup menu bar, select Application. From Application drop down menu, select Install.
PCnet Family Network Driver Installation Guide window will then open entitled, Application: pnt. following message will displayed:
PROCESSING: Package: Advanced Micro Devices PCnet Family driver (pnt) from <diskette1>.
Wait system process Unixware driver. Next, within Application: window, will Adapter Selection Menu with following:
PCnet (PNT):
Replace typing:
press <Enter>.
Note: this time AMD's Unixware driver only supports adapter.
Apply then highlighted. Press <Enter> continue. Next, within Application: window, will Parameter Selection menu with following:
Interrupt vector: address: DMA:
using PCnet-ISA adapter card, then step 14.1 below. using PCnet-ISA+, PCnet-ISA PCnet-32, PCnet-PCI adapter card, then step 12.2 below. _12.1 PCnet-ISA adapter card: must know what your card's (interrupt vector), base address, values are. right arrow select appropriate value your card then down arrow move next field. After filling each field, press down arrow highlight Apply then press <Enter>. step below continue.
_12.2 PCnet-ISA+, PCnet-ISA PCnet-32, PCnet-PCI adapter cards: Leave base address values auto scan will performed detect proper base address values automatically. However, note that (interrupt vector) value will also automatically detected, cannot installed dynamically. know correct value, enter interrupt vector field, press down arrow highlight Apply box, then press <Enter>. step below continue. know correct value, enter guess (e.g., press down arrow highlight Apply box, then press <Enter>. happen guess correct value, will mismatch message installation process will continue. step below continue. Most likely, will mismatch. this case, need reboot system restart installation process. system comes during reboot will WARNING message instructing your setup again with specified value. Write this value down restart installation process from step above. When reach step 12.2 again, value wrote down fill interrupt vector field leaving other fields Press down arrow highlight Apply box, then press <Enter>. step below continue. following message will displayed:
Installing part
Wait system install Unixware driver. following message will displayed:
Click Exit terminate pkgadd
Click Exit button.
PCnet Family Network Driver Installation Guide following message will displayed bottom Application Setup window:
Software installation succeeded
installation Unixware DLPI driver complete.
Note: should attach network driver running: /etc/confnet.d/configure Refer your Unixware documentation needed.
11.2.
Driver Installation From Command Line Prompt
currently have older Unixware driver installed your system, should remove prior installing newer Version. After removing your existing driver, then proceed with installing newer Unixware driver. Follow steps listed below: Unixware prompt, type following:
pkgadd diskette1
Then press <Enter>. following message will displayed:
Insert diskette into Floppy Drive Type [go] when ready, (default: quit:
Insert Unixware DLPI driver diskette into drive Then press <Enter> accept default value start installation process. following message will displayed:
Installation progress. remove diskette. following packages available: Advanced Micro Devices PCnet Family driver (i386) Select package(s) wish process `all' process packages). (default: all) [?,??,q]
Type following:
Then press <Enter> select package. following message will displayed:
PROCESSING: Package: Advanced Micro Devices PCnet Family driver (pnt) from <diskette1>.
Wait system process package. Next, will Adapter Selection Menu with following:
PCnet (PNT):
Type following:
Then press <Enter>.
Note: this time AMD's Unixware driver only supports adapter.
Apply then highlighted. Press <Enter> continue. Next, will Parameter Selection menu with following:
Interrupt vector: address: DMA:
using PCnet-ISA adapter card, then step below. using PCnet-ISA+, PCnet-ISA PCnet-32, PCnet-PCI adapter card, then step below. _6.1 PCnet-ISA adapter card: must know what your card's (interrupt vector), base address, values are. right arrow select appropriate value your card then down arrow move next field. After filling each field, press down arrow highlight Apply then press <Enter>. step below continue. _6.2 PCnet-ISA+, PCnet-ISA PCnet-32, PCnet-PCI adapter cards: Leave base address values
PCnet Family Network Driver Installation Guide auto scan will performed detect proper base address values automatically. However, please note that (interrupt vector) value will also automatically detected, cannot installed dynamically. know correct value, enter interrupt vector field, press down arrow highlight Apply box, then press <Enter>. step below continue. know correct value, enter guess (e.g., press down arrow highlight Apply box, then press <Enter>. happen guess correct value, will mismatch message installation process will continue. step below continue. Most likely, will mismatch. this case, need reboot system restart installation process. system comes during reboot will WARNING message instructing your setup again with specified value. Write this value down restart installation process from step above. When reach step again, value wrote down interrupt vector field leaving other fields Press down arrow highlight Apply box, then press <Enter>. step below continue. following message will displayed:
Processing package information Processing system information Verifying package dependencies
Followed
Installing part
Followed
following loadable modules will configured now: Module configuration completed.
Unix Operating System kernel will rebuilt include your configuration changes during next system reboot.
Followed
Installation Advanced Micro Devices PCnet Family driver (pnt) successful.
following message will displayed:
Insert diskette into Floppy Drive Type [go] when ready, (default: quit:
Type then press <Enter> quit installation. will then returned Unix prompt. installation Unixware DLPI driver complete.
Note: should attach network driver running: /etc/confnet.d/configure Refer your Unixware documentation needed.
PCnet Family Network Driver Installation Guide 11.3.
Unixware DLPI Driver Keywords
Keywords added, deleted, and/or modified manually editing appropriate #define values space.c file. Appendix (Software Keywords) your Unixware Manual more details. sample version this file listed below:
#ident #ident $Header: #include #include #include #include #define #define #define #define #define #define #define <sys/types.h> <sys/stream.h> <sys/dlpi_ether.h> <config.h> NSAPS MAXMULTI INETSTATS STREAMS_LOG IFNAME PNT_CNTLS; NSAPS; PNT_CNTLS; STREAMS_LOG; IFNAME;
PNT_TX_BUF PNT_RX_BUF
pnt_TotalDevCount pnt_MaxStreams pntboards pntstrlog char *pnt_ifname
DL_bdconfig_t pntconfig[ PNT_CNTLS #ifdef PNT_0 PNT_CMAJOR_0, PNT_0_SIOA, PNT_0_EIOA, PNT_0_SCMA, PNT_0_ECMA, PNT_0_VECT, NSAPS, #endif };struct pnt_ConfigStruct short index; short minors; short vec; ushort iobase; ushort ioend; short dma; short tx_buffers; short rx_buffers; long bus_scan; long led0; long led1; long led2; long led3; long dmarotate; long long fdup; long fast_isa;
struct pnt_ConfigStruct pnt_ConfigArray[PNT_CNTLS] #ifdef PNT_0 NSAPS, PNT_0_VECT, PNT_0_SIOA, PNT_0_EIOA, PNT_CHAN, PNT_TX_BUF, PNT_RX_BUF, scan, MUST (PCI1) machines dmarotate full duplex fast isa*/ #endif
PCnet Family Network Driver Installation Guide
Installing Unixware DLPI
Driver
Unixware built-in support PCnet driver. Unixware utility install built-in PCnet driver. help, Unixware manual. upgrade version driver, copy Driver.o space.c from Disk drivers /etc/conf/pack.d/pnt directory. Note: These files format Unixware directory diskette copied using doscp command from MERGES session. Rebuild kernel with /etc/conf/bin/idbuild command.
12.1.
Unixware DLPI Driver Keywords
Keywords added, deleted, and/or modified manually editing appropriate #define values space.c file. Appendix (Software Keywords) your Unixware Manuals more details. sample version this file, Unixware section. PCnet driver Unixware additional keyword, pcnet2 non-zero value, this keyword enables advanced features PCnet-PCI2 chip.
PCnet Family Network Driver Installation Guide
Installing VxWorks Driver
Installing VxWorks Driver
13.1.
Introduction
VxWorks Ethernet Device driver compatible with PCnet-PCI PCnet-FAST network controllers. source code driver integrated compiled VxWorks operating system, boot image standalone VxWorks (Vxworks.st) loaded onto floppy diskette. This diskette used boot diskette load VxWorks operating system. 13.2.
Installation Procedure
install, follow steps listed below: Insert floppy diskette into floppy drive boot system with VxWorks operating system. Refer VxWorks 5.3.1 Programmer's Guide mount hard disk also attach network interface card. command attach network card usrNetInit() initial network address host address obtained from boot parameters. change network interface address, command: ifAddrSet. ifAddrSet( InPci 139.95.95.1 order other hosts connect VxWorks system, user command: hostadd() with appropriate parameters.
PCnet Family Network Driver Installation Guide
Installing SunSoft Solaris Driver
Installing SunSoft Solaris Driver
Support provided SunSoft Solaris (Version 2.1) environment. install AMD's Solaris driver, follow steps listed below: Login root. prompt, type:
pkgadd <devname>
Where <devname> floppy drive (/dev/fd0). That above line should look like following:
pkgadd /dev/fd0
more information, page pkgadd (enter pkgadd help). Then press <Enter>. Insert Solaris driver diskette into floppy drive. Enter path package base directory (/kernel/drv). Enter path where want driver object installed (/kernel/drv). pkgadd application installs:
/kernel/drv/pnt /kernel/drv/pnt.conf
Wait process complete. Change into directory where installed driver object /kernel/drv). Edit pnt.conf file pnt.conf). more information, page driver.conf help (man driver.conf). Make following changes: Change name indicate driver name (name Change class indicate system type (class sysbus Change dmachan indicate channel dmachan PCnet-ISA). Change intr indicate interrupt handle line (intr PCnet-ISA). Delete additional entries table reflect number PCnet cards
PCnet Family Network Driver Installation Guide system. Example (for PCnet-ISA):
name= class= sysbus dmachan=5 intr=5,5 reg=0,0,0;
prompt, type following:
add_drv
Then press <Enter>. more information, page add_drv help (man add_drv). Edit hosts file /etc/hosts). Make following changes: address, hostname, entry loghost.
Note: Remove default local host entries.
example,
IPaddress 77.0.12.4 hostname Solaris-24-1 127.0.0.1 77.0.12.4 localhost loghost #loghost #Solaris-24-1 Solaris-24-1
Edit hostname.pcn0 file /etc/hostname.pnt0). Enter hostname file. example,
hostname Solaris-24-1 Solaris-24-1
Edit netmasks file /etc/netmasks). entry conform network requirements. example,
IPaddress 77.0.12.4
wish limit access local segment
77.0.12.4 255.255.255
This will permit system recognize stations with addresses between 77.0.12.0 77.0.12.255. Reboot system (shutdown -g0). following message displayed during reboot phase:
configuring network interfaces: pnt0
installation SunSoft Solaris driver complete.
Installing SunSoft Solaris Driver
14.1.
SunSoft Solaris Driver Keywords
Table SunSoft Solaris Driver Keywords. Table SunSoft Solaris Driver Keywords Keyword Description Driver name Driver class Interrupt Address Full Duplex Keyword Name name= class= sysbus [intr=5,x] [ioaddr= io_addr] [dmachan= dma_no] FDUP Additional Keyword Details This required. Range Default
This indicates system device type. Common Keywords. Common Keywords. Common Keywords. (ISA only) FDUP keyword used enable disable full duplex 10BaseT ports. Common Keywords.
Present
(What EEPROM)
PCnet Family Network Driver Installation Guide
Installing Packet Driver
Installing Packet Driver
Packet driver PCnet architecture (backward compatible Am2100/Am1500T) based packet driver from Clarkson University. 15.1.
Driver Installation Using AMINSTAL Utility
Follow steps listed below: AMINSTAL Utility configure your PCnet adapter card's base address, channel, channel.
AMINSTAL Utility section more information configuring your PCnet adapter card.
Once have completed configuration your PCnet adapter card using AMINSTAL, step below continue. Select Continue button Configuration dialog box. Installation dialog will appear. Select desired PCnet adapter card highlighting dialog box. Highlight Packet driver install driver. Change default path necessary. default directory C:\PKTDRV. Press Continue button complete installation. AMINSTAL will copy selected driver file into specified directory create sample AUTOEXEC.NET file specified directory. AUTOEXEC.NET file contains following:
PCNTPK INT=0x60 IOADDRESS=<ioaddress> IRQ=<irq> DMA=<dma> Note: Packet driver uses software interrupt provide handle driver automatically scan. software interrupt range 0x60-66. AMINSTAL utility uses default value 0x60. there conflict with other software settings, please change this setting editing AUTOEXEC.NET file.
Exit AMINSTAL when installation been completed. user need make modifications system files, using sample files reference.
installation Packet driver complete.
PCnet Family Network Driver Installation Guide 15.2.
Driver Installation From Command Line Prompt
Source executable code version packet driver provided. number other utilities (including source) which above packet driver also provided, well number documentation files. recommended that read information available. most important file start reading install.doc. Utilities also described this file. Copy Packet driver (PCNTPK.COM) into directory. packet driver loaded from prompt from AUTOEXEC.BAT file. command line format packet driver
PCNTPK [-n] [-d] [-w] <INT=packet_int_no> [IRQ=int_no] [IOADDR=io_addr] [DMA=dma_no] [BUSTYPE=bus] [DMAROTATE] [TP] [LED0=xx] [LED1=xx] [LED2=xx] [LED3=xx] [FDUP=xx]
When using Windows, either option WINPKT Utility (see install.doc [IRQ=int_no], [IOADDR=io_addr], [DMA=dma_no] specified PCnet-ISA adapter card, default values assumed packet driver.
Note: following: INT=packet_int_no handle upper layer interface (normally 0x60-66). This optional. upper layer application such scans handle between 0x60-66.
Additional common keywords specified. Please refer Software Keywords section (Appendix this manual more information. 15.3.
Keyword Example
example command line follows:
PCNTPK INT=0x60 IRQ=3 IOADDR=0x300 DMA=5
15.4.
Packet Driver Keywords
Table Packet Driver Keywords.
Installing Packet Driver Table Packet Driver Keywords Keyword Description Packet converter Keyword Name [-n] Additional Keyword Details option converts Ethernet type 8137 Novell PSO-like packets. This required standard boot from Packet driver included Packet Driver package drivers load from boot image file. option delays initialization. option will keep initialization code after loading. This required boot support. switch used Windows. Install Packet Driver before running MS-Windows. This switch does prevent Windows from swapping network application memory, simply detects when that happened, drops packet. WINPKT Utility enhanced mode applications. This software interrupt used communicate with packet driver. Appendix install.doc file more details. Range Default Enabled
Initialization delay
[-d]
Enabled
Windows option
[-w]
Enabled
Software Interrupt
<INT= packet_int_no
0x60-0x66
0x60
PCnet Family Network Driver Installation Guide
Keyword Description Address Full Duplex
Keyword Name [IOADDR= io_addr] [DMA= dma_no] FDUP
Supported PCnet-ISA only
Additional Keyword Details Common Keywords Common Keywords.
Range
Default
FDUP keyword used enable disable full duplex 10BaseT ports. Common Keywords.
Present
(What EEPROM)
Note: Keyword options Packet driver activated loading driver command line loading driver from batch file like AUTOEXEC.BAT.
Installing Component Interface (CI)
Installing Component Interface (CI)
16.1.
Desktop Management Interface (DMI)
brings manageability intelligence computer systems such desktop servers, allowing vendors easily manageability their products. works synergistically with existing standards such Plug Play Simple Network Management Protocol (SNMP). Specifically, AMD's support (MIF file Instrumentation) extends following drivers: NDIS driver NDIS OS/2 driver NDIS Windows Workgroups driver client driver OS/2 client driver
local interface used within single system. provides means which component instrumentation developed multiple vendors interplay within single system uniformly provide management information. Desktop Management Task Force's (DMTF) interface consists following elements: Service Layer (SL), local program that collects information from components, manages that information through database, passes information management applications requested. controls communication between itself management applications means Management Interface (MI), between itself manageable products means Component Interface (CI). Specification detailed information. database, which contains information about products installed attached system. Service Layer manages information database. information comes from files provided with each manageable product. Specification detailed information. Management applications, remote local programs interrogating, changing, controlling, tracking, listing elements desktop system. management application graphical user interface program, network management agent, installer program, diagnostics program, remote procedure call. Specification detailed information. Manageable products, also called components, hardware, software, peripherals that occupy attached desktop computer, such hard disks, word processors, CD-ROMs, printers, motherboards, operating systems,
PCnet Family Network Driver Installation Guide spreadsheets, graphics cards, sound cards, modems. Each product provides information database means file that contains pertinent management information that product. Specification detailed information. structure shown Figure below. 16.1.1.
Service Layer
Service Layer (SL) system-resident program that manages activities. background task process that always ready request from management application managed components. There specific implementations Service Layer different operating systems environments. Refer Specification installation procedures. 16.1.2.
Component Interface (CI)
integral part handles communication between component instrumentation shields vendors from complexity management information encoding minimizes responsibilities instrumentation.
Management Applications Management Interface (MI)
Service Layer (SL) Component Interface (CI) Database
General Instrumentation Driver Hardware Software Components
Figure Desktop Management Interface Structure
Installing Component Interface (CI) 16.2.
Installation Program (DMI Version 1.1)
Installation program edits PCNET.MIF file copies instrumentation files file follows: Source File PCNET.MIF PCNET.OVL PCNET.EXE Destination Directory C:\DMI\DOS\MIFS\BACKUP C:\DMI\DOS\BIN C:\DMI\WIN16\BIN
installation program performs following edits PCNET.MIF file: Chooses comment uncomment path string overlay instrumentation, depending whether target driver (the driver that going used system) Windows Workgroups v3.11 NDIS driver drivers: NDIS (comment former uncomment latter). Inserts serial number `Value' section `Serial number' attribute field. Inserts installation date `Value' section `Installation' attribute field. Inserts connector type `Value' section `Connector type' attribute field. These edits done manually desired. properly edited file installed with management application that supports install feature such browser provided with SDK. 16.2.1.
Invoking DMINSTL
invoke installation utility from distribution diskettes, insert diskette into drive. Issue following commands (assuming diskette writeprotect feature disabled): A:>CD \DMI A:\DMI>DMINSTL installation program copied directory target system executed from there. only limitation that files installed reside same directory installation program proper (this true installation from floppy drive well). Note: When performing installation using Installation Utility (DMINSTL), remove TSRs that essential installation. example, installing MS-DOS V6.2 system, pressing while message, "Starting MS-DOS." displayed will bypass system startup files boot clean system
PCnet Family Network Driver Installation Guide startup. using earlier version (e.g., V3.3), booting from floppy without CONFIG.SYS AUTOEXEC.BAT file will achieve same result. Once system been started using this method, installation program used install support PCnet drivers. 16.2.1.1. Directory Structure DMINSTL expects following directory structure exist target environment. directory structure does exist, installation program will create Figure
WIN1
Figure Directory Structure 16.2.1.2. DMINSTL Interaction With DMINSTL interacts with service layer ways. loaded, installation program invokes required perform installation. loaded, DMINSTL loads before continuing. Once installation completes, unloaded DMINSTL loaded available target system, DMINSTL copies PCNET.MIF file both C:\DMI\DOS\MIFS C:\DMI\DOS\MIFS\BACKUP directories. 16.2.1.3. Moving Between Fields Once installation program been invoked, presents forms based interface with text input fields pull-down menu fields. move between fields, pressed repeatedly until cursor enters desired text input field, until desired pull down menu field highlighted.
Installing Component Interface (CI)
16.2.2.
Editing Input
16.2.2.1. Text Edit Fields When cursor enters text input field, three actions effected field itself. cursor advanced character position each press rightarrow except rightmost position field where cursor ceases advance. pressing left-arrow key, cursor moved left character position same manner when moving right. Finally, characters entered into field placed current cursor position cursor advanced position right. Again, field, character inserted cursor advanced. 16.2.2.2. Pull Down List When cursor placed pull down menu field, field highlighted. display pull down list, press down-arrow while holding down key. Once displayed, items list highlighted using down arrow keys. Pressing Enter selects highlighted item hides pull down list. hide pull down list without making selection, press key. 16.2.3.
Starting Installation Program
used instruct DMINSTL begin actual installation process. After filling fields desired, press F10. subparagraphs below description fields. DMINSTL will display progress dialog center screen. dialog will alternately draw erase blue center screen demonstrate that installation progressing. Once installation completes, actions will occur. installation succeeded, dialog appears indicating success operation Component assigned driver. installation fails, message appears indicating source failure. Again, must pressed clear message. 16.2.3.1. Serial Number Serial Number field used enter serial number network adapter card package. number usually found outside package distribution media. purpose this field allow serial number package readily retrieved case required purpose such technical assistance. Serial Number field straight text field. This means that will accept text (letters numbers) that typed into
PCnet Family Network Driver Installation Guide
16.2.3.2. Installation Date Installation Date field initialized system date time. field uses following format. HH:MM:SS yyyy `mmm' portion represents month. following values accepted:
`dd' subfield represents month legal value between HH:MM:SS subfield used denote current time. symbols represent hours, minutes, seconds, respectively. Finally, `yyyy' field represents year. errors detected format time date field will cause value rejected error message displaying required format displayed. 16.2.3.3. Connector Type Connector Type field identifies three possible connectors that used with network interface controller. three connector types currently supported follows: 10BaseT (RJ45) 10Base2 (BNC) Connector Type field pull down menu field. display choices, press ALTDownArrow. 16.2.3.4. Target Driver Target Driver field identifies driver used with software. select desired driver, pull down (ALT-DownArrow) menu select either: NDIS NDIS 2/ODI
Installing Component Interface (CI) first selection with Windows Workgroups Version 3.11. second with network operating system that uses either NDIS drivers (e.g. Server Netware, respectively).
16.2.4.
Exiting Installation Program
installation program terminated time prior pressing begin actual installation process. exit program, press while holding down key. Once pressed, installation process must continue until complete. 16.3.
Installation Procedure (DMI Version 2.0)
install, follow steps listed below: Copy PCNET.MIF PCNET.EXE files directory (for instance, PCNET). Install Intel's Explorer. Reboot system. Make sure that service layer (WIN32SL.EXE) program running. Launch Explorer program. Click Component option under File menu. Specify path PCNET.MIF file click button. From Start menu, PCNET.EXE program. Explorer window, double click Computer icon. will item, PCnet Ethernet Controller Component. Expanding this item will show groups under examine attributes their corresponding values expanding group interested running PermaNet Server Software driver have configured adapters pair, will pop-up message each time primary fails recovers. This demonstrated causing link failure primary pulling Primary adapter's cable.
PCnet Family Network Driver Installation Guide
Installing Universal Boot
Installing Universal Boot
Located BOOTROM directory driver diskette file called netrom.hex. Boot support provided PCnet-ISA devices, PCnet device, PCnet-PCI devices. Remote boot allowed from following servers: Novell Server Microsoft Manager (Server)
Boot based protocol. install universal Boot ROM, follow steps listed below: Obtain Boot from borrow PROM with netrom.hex file. This file Intel MCS-86 format.
Note: Currently, EEPROM greater than equal size used. Also, this EEPROM should faster
Insert Boot into 28-pin socket. using PCnet-ISA adapter card, then step below. Otherwise, step below. _3.1 PCnet-ISA adapter card: Install Boot jumper enable Boot ROM. Next, jumpers base address, channel, channel. PCnet-ISA, must four configurations listed below when setting jumpers:
Config Option Addr 300h 320h 340h 360h Boot Addr C80000h CC000h D0000h D4000h
Note: Boot Addresses listed above jumper settings.
step below continue. _3.2 PCnet adapter cards: Using AMINSTAL, configure PCnet adapter cards with available Boot address.
PCnet Family Network Driver Installation Guide step continue. Notes: Refer AMINSTAL section AMINSTAL utility. PCnet adapter card configured Plug Play mode, Boot address will selected automatically (which same PCnet device PCnet devices). Follow Boot installation procedure outlined Novell Installation Manual, Microsoft Manager Server Manual, Server Manual prepare server support RPL. going remote boot OS/2 workstation Microsoft Manager, follow steps listed below prior performing remote boot from server. Otherwise, step below continue. Edit file os213bb.cnf. path this file follows:
Notes: file os213bb.cnf remote boot configuration file OS/2 Version 1.3. running different version OS/2 your workstation, file name slightly different. path os213bb.cnf file, NETBEUI different depending which protocol using.
Edit following line os213bb.cnf file:
BBLOCK\NDIS\pcntnd.DOS Note: line shown above default. tildes represent parameter fields. default tilde means
Change second tilde value line should look like:
BBLOCK\NDIS\pcntnd.DOS
Save os213bb.cnf file. step continue. Next, perform remote boot from server. diskless workstation will display some sign-on messages followed
boot from Novell Server, press boot from Server press boot from Server press boot from Microsoft Manager, press boot from first available server, press selection within seconds, will choice Please, make your choice now!
Installing Universal Boot
make selection pressing appropriate number. nothing selected within seconds, appropriate server will selected auto detect. This also used support workstations without keyboard monitor. After selection made, remote boot process started.
Note: This version Boot does display Boot from Network (Y/N) message. Make sure have bootable device system (i.e., drive). diskless system without bootable device, this Boot will take over boot process.
PCnet Family Network Driver Installation Guide
Other recent searches
uPD98408 - uPD98408 uPD98408 Datasheet
SNC21501A - SNC21501A SNC21501A Datasheet
DSP1N5D5 - DSP1N5D5 DSP1N5D5 Datasheet
DSP1N5D7 - DSP1N5D7 DSP1N5D7 Datasheet
DSP1N5D12 - DSP1N5D12 DSP1N5D12 Datasheet
DSP1N5D14 - DSP1N5D14 DSP1N5D14 Datasheet
DSP1N5D15 - DSP1N5D15 DSP1N5D15 Datasheet
DSP1N5D17 - DSP1N5D17 DSP1N5D17 Datasheet
CAT37 - CAT37 CAT37 Datasheet
374624B00035 - 374624B00035 374624B00035 Datasheet
2SD1624 - 2SD1624 2SD1624 Datasheet
Privacy Policy | Disclaimer
© 2012 Datasheet Archive
