NetWare Boot ROM V4.1 (1) Introduction Highlight Computer Systems, Inc. has contributed her efforts in networkings research and development for years. Accumulated many years' experience in networks, Highlight has implemented a new version Boot ROM in NetWare environment. This version provides full-function help which will enable the end user to do hardware configuration, diagnostic network status, debug network topology in remote boot environment. The software will auto-detect I/O base address and IRQ level (and program the memory buffer address for memory mapping ethernet card like WD compatible card). The final execution function is a simple diagnosis, which tell the workstation user about the LAN adaptor's working condition. The new version boot ROM has many advantages in booting procedure over the earlier old Boot ROM. For example : 1. Never suffer from booting failure in mixed environment with NetWare v2.xx, NetWare v3.xx and NetWare v4.xx. 2. There will be no confused LAN hardware configuration with LAN device-driver's configuration any more. 3. Debuging network topology becomes easy for most user. 4. The earlier Boot ROM was booting up with fixed hardware config- urations, users couldn't check what's going wrong, but it's clear while using our Boot ROM that supports auto-detected hardware configuration and networking diagnosis, the time and money spent on technical support can be saved. 5. There will be no trouble in communication with file server. With this Boot ROM supporting automatic on line connection in networking, the NetWare Watchdog function and NetWare console clear station function will not affect the on line processing once it successfully boots. 6. The critical problems, Workstation locking up or unable to reattach, will not occur as follow situations, * After fixed the fault cabling system. * Reboot File Server. * Transmitting by disturbing with thousands packets from other nodes. * Mixed RPLFIX's and non-RPLFIX's boot image file environment. (2) BOOT ROM Specifications for NetWare General function: * Boot without disk. * Support IPX protocol for NetWare. (note: Ethernet frame type: ETHERNET_802.3 ) * Support SAP services ( Nearest Server Request ). (note: Watch the Router Tracking Screen on file server console after enter TRACK ON command.) * Protocol Support for DOSODI Specification: . Schedule AES Event . Register Stack . Bind Stack to MLID . De-register Stack . Register Prescan Stack . De-register Prescan Stack (note: The DOSODI protocol is bound to logical board #1 in this ROM routine, user can exchange protocol in modify NET.CFG file.) * General opening file : 1. BOOTCONF.SYS, text file, describes multiple remote booting. 2. NET$DOS.SYS, the first default boot image file. 3. IBM$DOS.SYS, the second default boot image file. (note: refer to command line utility at DOSGEN part, see Workstation in the Netware Installation manual.) * Boot trap vector : INT 19h Improvement: NetWare Network: * Boot no failure in mixed environment with NetWare v2.xx, v3.xx, v4.xx * No transmit fail by disturbing with thousands packets from others. * No fail in mixed RPLFIX's and non-RPLFIX's boot image file environment. * Support DOSODI driver without execute RPLODI. * Support DOSODI driver UNLOAD function for alter another DOSODI driver. * Support DOSODI driver UNLOAD function for alter protocol stack. * Automatic enable NIC active after DOSODI driver unload. * Dynamic detectable network status. * Automatic attachment in networking, 1. Will not be affected by NetWare Watchdog function. 2. Will not be affected by NetWare console clear station function. * Automatic Resume connection after being interrupted. * Friendly interface with screen message. * Avoid power-on again as network error retried. Hardware Specification: * Full range IO (with base I/O, base memory, IRQ) could be setting. * Automatic interface with network card hardware configuration. * Diagnosis of network status. * No failure in setting IRQ 7. Environment: Operation system : NetWare v2.xx, NetWare v3.xx, NetWare v4.xx DOS version : v3.xx, v4.xx, v5.xx, v6.xx, v7.xx Computer System : with IBM PC/AT/386/x86 (3) Ethernet IPX BOOT ROM Comparison with other brand 旼컴컴컴컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴컴컴컴컫컴컴컴컴컴컴컴컴컴컴컴컴컴커 � Function \ Brand � Highlight Boot ROM � Other brand Boot ROM � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 쿓ardware Configuration � Full Base I/O range 쿽nly *IO=300, IRQ=3 � � 쿔O from 200H to FFFFH� *IO=320, IRQ=5 � 쿞upported � Full IRQ level range� *IO=340, IRQ=4 � � � IRQ from 2 to 15 � *IO=360, IRQ=2 or few � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 쿝AM buffer work with � Yes � No, only 16KB in 16 bit, � � 6 KBytes upto 16KBytes �(Auto-detected range)� 8 KB in normal 8 bit slot � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 � Configuration setup � Not necessary � Yes � � with user's manual � � � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 쿑riendly error message � Yes � No � 쿞upport Troubleshooting � � � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 � Network diagnosis � Yes � No � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 쿎ontinue work perfectly � � � � * After fixed the fault� Yes � Workstation could be � � cabling system. � � hardware reset � � * Reboot File Server. � User can abort net- � or � � * Disturbing with thou-� work and skip to lo-� Workstation could be � � sands of packets from� cal driver(B:-C:,..)� locking up � � other nodes � ; can return to net-� or � � * Station was cleared � work operation after� Display "Error reading bo-� � by Watchdog or File � network fixed. � ot image file" error mess-� � Server console. � � age. � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 쿞upport DOS v3.xx, v4.xx� Yes � Yes � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 쿞upport DOS v5.xx, v6.xx� Yes 쿘ust be fixed by using RPL-� � v7.xx 쿏o not care RPLFIX 쿑IX, But can't run DOSODI � � � or Non-RPLFIX � � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 � Support NetWare v3.12, � Yes � No � � NetWare v4.xx � 쿽r after RPLFIX will locked� 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 쿌ll local disk, but disk� Yes � No, only hard disk c: can � � A:, can be used. � (driver B:-C:,...) � be used. � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 � Support Driver unload � Yes � No � � and reload for DOSODI 쿙o need RPLODI.COM 쿝eboot will cause lock up � 쳐컴컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컵컴컴컴컴컴컴컴컴컴컴컴컴컴캑 쿟he TIME and MONEY spent� � � 쿽n technical support can� Yes � No � 쿫e saved. � � � 읕컴컴컴컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴컴컴컴컨컴컴컴컴컴컴컴컴컴컴컴컴컴켸 Message of ROM procedure 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽 (A) Booting message 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿗oading from Network (Y or N) ?� 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� : If your computer has a hard disk, then the monitor will show this message for selecting which way to boot. otherwise Boot ROM will skip to (B) display title. 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽 (B) Display title �袴袴� Booting title of ROM 袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴敲 � PC/LANSTATION Remote Program V4.1 for NetWare � � LAN Option : HE-x00 / HE-206 ' HE-320R (960125) � � (C) Copyright Highlight computer systems, Inc. 1991-1996 � � NetWare is a registered trademark of Novell, Inc. � 훤袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴暠 Lan_Board type : HE-x00 Boot ROM Segment : 0x???? Node Address : 0x???????????? IRQ Level : ? I/O Base : 0x??? Buffer Size : ?? KByte Data Width : ?? bit Network Transmit Status ..... : This is the title and hardware configuration for remote booting. 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽 (C) AUTOMATIC LAN ADAPTOR INITIAL : This procedure process adaptor automatic hardware configuration and network diagnosis. (see Hardware Configuration and Diagnosis) If there is no error returned, then GOTO procedure (D), else it will display message on screen, as follows : 旼컴컴 Error message 컴컴컴컴컴컴컴컴컴컴컴커 � � 쿛ress any key to continue ..... � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� : It must be wrong with LAN interface board or wrong with cabling system during hardware initialization. 旼컴컴 Error message 컴컴컴컴컴컴컴컴커旼컴컴 Error message 컴컴컴컴컴컴컴커 쿙etwork error for Receiving packet. 납Network error for Sending packet. � 쿌bort, Retry? 납Abort, Retry? � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴牡컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : (After pass the hardware initialization and network diagnosis, it will get into the dynamic detectable network routine until you have released the boot ROM routine with NETx.COM command or VLM.EXE command for NetWare 4.x.) * It may be wrong with the cabling system. (as sending) * During the process of network, the following events may cause above situation: 1. the boot ROM routine may be damaged.(e.g. ODI driver not using RPLODI) 2. the network address may be changed. (as receiving) 3. the node address may be changed. (as receiving) 4. the packet data frame may be changed. (as receiving) 5. Unload driver or unbind protocol at file server. (as receiving) 6. If other LANstation has been set with same node address.(as receiving) :Normal life time before error message displayed, Receiving = 20 sec- onds, sending = 2 seconds. After error retry life time before error message displayed, Receiving = 6 seconds, sending = 2 seconds. 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽 (D) Nearest File Server Request : This procedure broadcast the Service Query Packet (Nearest File Server Request) to get server name and network address. If there is no packet returned with file server information, then it will display error message on screen(as follows), else GOTO procedure (E). 旼컴컴 Error message 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿑ile server could not be found. � �=> Check file server has booted or not. � �=> Check file server's cabling system. � �=> Must set reply to get nearest server=on in file server console. � �=> Check the SYS volume is mounted or not. � �=> Check file server has loaded LAN driver & bound proper protocol or not.� �=> Check LAN station's cabling system or File Server's LAN card. � �=> Check file server shut down or not. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 旼컴컴 Error message 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿑ile server could not be found. � �=> Check current station's cabling system. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : (Above message displayed, after abort network error retry) * Use TRACK ON at the file server console and watch for GET NEAREST SERVER REQUESTS from the workstation. (as receiving) * Use CONFIG at the file server console and check the LAN driver load or not, check the LAN protocol assigned or not, check the Frame type is correct or not (example: ethernet's frame type is ETHERNET_802.3), check the Interrupt level setting is correct or not. (as receiving) * Check file server's cabling system : (as receiving) 1. Check connection between adaptor connector and cable connector. 2. Check connection between HUB's connector and cable connector. 3. Check the cable's wire is cut off or not. 4. In BUS topology, check the terminator's connection or check the terminator's resistor value is correct or not. * As NetWare 386 OS, check SET communications status, must SET Reply to Get Nearest Server=ON 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽 (E) ATTACH THE FILE SERVER : This procedure process attachment of file server and the file server will reserve a connection space in server's memory. If there is no error returned, then GOTO procedure (F), else it will display the error message on screen, as follows : 旼컴컴 Error message 컴컴컴컴컴컴컴컴커 쿐rror attaching the file server. � 쿛ress any key to continue ..... � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 旼컴컴 Error message 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿐rror attaching the file server. � �=> Check file server has loaded LAN driver & bound proper protocol or not.� �=> Check LAN station's cabling system or File Server's LAN card. � �=> Check file server shut down or not. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 旼컴컴 Error message 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿐rror attaching the file server. � �=> Check current station's cabling system. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : This message told you that the file server has no room for additional user to login into the file server. There may be too many user in connection with file server, or no more memory(RAM) space for works. : NetWare V3.11 for 20-user has limit of connections in network operation. If the 21th connection request is processed, then this message will be displyed on screen. If you want to login normally, then you must ask the supervisor to clear the NOT-LOGGED-IN connection, and then you will has the rights to attach file server. 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽 (F) PROCESS BOOT FILE : (1) OPEN BOOTCONF.SYS : This procedure open the BOOTCONF.SYS file for get multiple Remote Boot image file. The BOOTCONF.SYS is a text file which describe the expression of LAN station's Boot image file. The format of BOOTCONF.SYS is described as follows : 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 쿑ormat: {0x[[space or 0][network_address][space],[space or 0][node][space]� � = [space]} � � or {0x[network_address],=} � � or {0x,[node]=} � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 For more detail see (a) NetWare 2.1x supervisor guide in chapter 9 ( Preparing the Network for Use). (b) Netware 386 Installion in Appendix D : Use DOSGEN to Add Remote Reset. (c) See DOSGEN in Utilities reference. IF the file open success, THEN GOTO read the BOOTCONF.SYS file, IF the file read error THEN display error message. ELSE IF there is no network address matched THEN GOTO (2). ELSE GOTO open the match image file, then GOTO (3). ENDIF ENDIF ELSE GOTO (2). ENDIF 旼컴컴 Error message 컴컴컴컴컴컴� 쿐rror reading BOOTCONF.SYS file.� 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : When the error message is displayed on screen, you may say that the network is unstable. * Check if other LAN station has been set with same node address. * Check your LAN station's cabling system, then boot your LAN station again. * Check if file server's hard disk failure, get it for repair. (2) OPEN NET$DOS.SYS or IBM$DOS.SYS : This procedure open the Remote Boot image file for loading DOS in remote LAN station. If the file open successfully, then GOTO (3), else it will display the error message on screen as follows : 旼컴컴 Error message 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿐rror opening boot image file. � �1) Check NET$DOS.SYS file must exist in directory SYS:LOGIN. � �2) You must DOSGEN the boot image file in SYS:LOGIN. � 쿛ress any key to continue ..... � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : * Login into file server with disk's LAN driver, change directory in SYS:LOGIN and check NET$DOS.SYS with DIR instruction. In NetWare 386 server console, using MONITOR's File Open / Lock Activity item option to check SYS.:LOGIN.:NET$DOS.SYS. * If there is no NET$DOS.SYS exist in SYS:LOGIN directioy, please make DOSGEN(See DOSGEN in Utilities reference). * Check if other LAN station has been set with same node address. * Check your LAN station's cabling system, then boot your LAN station again. * Check if file server's hard disk failure, get it for repair. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿟he has been opened for writing by others. � �bort or Wait until it closed then etry ? � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿐rror opening file : � 쿟he SYS volume has been dismounted. � �bort or let it re-mounted then etry ? � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� (3) READ BOOT IMAGE FILE : ( executing like locate A:> ) This procedure read the Remote Boot image file for loading DOS in remote LAN station. If the DOS has loaded successfully, then GOTO (4), else it will display the error message on screen as follows : 旼컴컴 Error message for ETHERNET 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 쿐rror reading boot image file : � �=> Check file server has loaded LAN driver & bound proper protocol or not.� �=> Check LAN station's cabling system or File Server's LAN card. � �=> Check file server shut down or not. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 旼컴컴 Error message for ETHERNET 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 쿐rror reading boot image file : � �=> Check current station's cabling system. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : (It may be lose data packet) * Check file server's cabling system : 1. Check connection between adaptor connector and cable connector. 2. Check connection between HUB's connector and cable connector. 3. Check the cable's wire is cut off or not. 4. In BUS topology, check the terminator's connection or check the terminator's resistor value is correct or not. * Change File Server's LAN card with another one. * Check if file server's hard disk failure, get it for repair. (4) SUCCESS READ : This procedure simulate the DOS procedure which has been treated like booting from locate drive A, it will load IO file, DOS file, COMMAND shell into memory. If you want to login into Netware, you must execute next two steps(as follows): 旼컴컴컴� 퀂tep 1.� 읕컴컴컴� A:>IPX (loading IPX/SPX device driver) or { A:>LSL A:>PCIODI ;run LAN driver with NET.CFG ;HE200 is NE1000/NE2000 compatible driver ;HE205 is NE2000 plus compatible driver A:>IPXODI ;protocol assign for IPX note: set FRAME name(in NET.CFG) same to file server. } 旼컴컴컴� 퀂tep 2.� 읕컴컴컴� A:>NETx ;loading NetWare transpotation or { A:>VLM ;command for NetWare 3.12 or 4.x } note: VLM.EXE v1.01 (930402) has a bug that can't run large progarm from drive A:, if workstation boots from remote boot ROM. If it could not login successfully, then the following message will be displayed on the screen. 旼컴컴 Error message 컴컴컴컴컴컴컴컴커旼컴컴 Error message 컴컴컴컴컴컴컴커 쿙etwork error for Receiving packet. 납Network error for Sending packet. � 쿌bort, Retry? 납Abort, Retry? � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴牡컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : * It may be wrong with the cabling system. (as sending) * During the process of network, the following events may cause above situation: 1. the boot ROM routine may be damaged. 2. the network address may be changed. (as receiving) 3. the node address may be changed. (as receiving) 4. the packet data frame may be changed. (as receiving) 5. Unload driver or unbind protocol at file server. (as receiving) 6. If other LAN station has been set with same node address. (as receiving) 旼컴컴 Error message for ETHERNET 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 쿐rror reading boot image file : � �=> Check file server has loaded LAN driver & bound proper protocol or not.� �=> Check LAN station's cabling system or File Server's LAN card. � �=> Check file server shut down or not. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 旼컴컴 Error message for ETHERNET 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 쿐rror reading boot image file : � �=> Check current station's cabling system. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : (It may be lose data packet) * Check file server's cabling system : 1. Check connection between adaptor connector and cable connector. 2. Check connection between HUB's connector and cable connector. 3. Check the cable's wire is cut off or not. 4. In BUS topology, check the terminator's connection or check the terminator's resistor value is correct or not. * Change File Server's LAN card with another one. * Check if file server's hard disk failure, get it for repair. 栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢 栢 栢 栢 ETHERNET(HE-x00/HE-320R) Configuration and Diagnosis 栢 栢 栢 栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢栢 Specification of ROM The Boot ROM can automatically do hardware configuration, but it has a limit of range described as follows : 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 � Chips : DP8390, DP83901, DP83902 or RTL8029 compatible chip.� � Auto IRQ : 3, 4, 5, 7, 9(2), 10, 11, 12, 15. � � Base Memory : � � ETHERNIC-8 : 2000h-3FFFh � � ETHERNIC-16 : 4000h-5FFFh ( 8 bit slot mode) � � ETHERNIC-16 : 4000h-7FFFh (16 bit slot mode) � � Base I/O : 200h, 220h, 240h, 260h, 280h, 2A0h, 2C0h, 2E0h. � � 300h, 320h, 340h, 360h, 380h, ... , 0FFE0h. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 Automatic Configuration and Diagnosis 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽� A) SEARCH BASE I/O PROCEDURE : This procedure is testing the function of internal loopback transmit. If no failure during testing, then the IRQ controller will return the correct IRQ level, else it will display error message on screen as follows : 旼컴컴 Error message 컴컴컴컴컴� 쿐thernet Base I/O not found ! � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : 1. If the Base I/O setting is not match(200h, 220h, 240h, 260h, 280h, 2A0h, 2C0h, 2E0h, 300h, 320h, 340h, 360h, 380h, 3A0h, 3C0h, 3E0h,... , 0FFE0h) 2. If I/O base conflict with other interface I/O address. 3. ISA BUS on motherboard is damage. >> Change to next slot. 4. May be Ethernet controller failure. 旼컴컴 Error message 컴컴� � Ethernet IRQ error ! � 읕컴컴컴컴컴컴컴컴컴컴컴켸 : 1. IRQ jumper is not setting. 2. IRQ wire is cut off or short with other wire. 3. Network controller is damage. 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽� B) SEARCH BASE MEMORY for distinguish between HE-x00 and HE-320R This procedure is testing the ETHERNET Base memory by simple write /read. If no memory write/read error, then it will be setting correct type of ethernet adaptor, else it will return the error message, displayed on screen as follows : 旼컴컴 Error message 컴컴컴컴컴컴컴컴컴컴� 쿓E-x00 or HE-206 or HE-320R not found ! � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : If your interface board is not compatible with HE-x00 or HE-320R. 旼컴컴 Error message 컴컴컴컴커 쿐thernet Memory failure ! � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴� : 1. Check your interface board's AT type switch (or jumper), was it setting correct AT type. 2. May be wrong with interface board's memory buffer circuit. 3. ISA address BUS on motherboard is damage. 4. Memory electronic circuit is damage. 5. It must be at least 6 K Bytes memory range OK. 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽� C) INITIAL THE ETHERNET RESET and READ NODE ID PROCEDURE This procedure will initial the ETHERNET interface board and display the ETHERNET hardware configuration(as follows). 旼컴컴 ETHERNET configuration 컴컴컴커 쿗an_Board type : HE-x00 � 쿍oot ROM Segment : 0x???? � 쿙ode Address : 0x???????????? � 쿔RQ Level : ? � 쿔/O Base : 0x??? � 쿍uffer Size : ?? KByte � 쿏ata Width : ?? bit � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : 1. This is an Ethernet configuration information message. 2. Lan_Board type : there are three type of adaptor, HE-100, HE-200W(plug into 16 bit slot), HE-200B(plug into 8 bit slot). 16K is the range of activity memory buffer. 3. The I/O Base range: (200h, 220h, 240h, 260h, 280h, 2A0h, 2C0h, 2E0h, 300h, 320h, 340h, 360h, 380h, 3A0h, 3C0h, 3E0h,... , 0FFE0h) : IRQ = interrupt level, wrong IRQ level may cause reveiving error in network; I/O Base = I/O base address in 32 sequence address range, NodeID = current adaptor node address. 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽� D) AUTOMATIC DIAGNOSTIC TRANSMISSION PROCEDURE : After completion of hardware configuration, it will execute the network diagnosis. The following is the executive message, 旼컴컴 Execute message 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 쿙etwork Transmit Status ..... Pass ! � � or � 쿙etwork Transmit Status ..... Transmit collided on the network ! � � or � 쿙etwork Transmit Status ..... Carrier sense lost, check the terminator ! � � or � 쿙etwork Transmit Status ..... Offline, check cabling system ! � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� : [pass !] : The transportation of packet has worked well. [Transmit collided, check cabling system ! ] : . Check the terminator. . Number of packets are transmitting in same time so that transmission is difficult or impossible. It happen as follow condition, 1. Too mush network traffic. 2. The cable is not connect properly. 3. Too mush noise in cable system. 4. Wrong cable type. [Carrier sense lost, check the terminator !] : May be cable's length is too long. It happen as follow condition, 1. One end of cable is not connect to terminator. (only BNC) 2. Terminator is not a 50 ohm resistor. (only BNC) 3. Too long of cable length. 4. Wrong cable type. [Offline, check cabling system !] : The interface board has be disconnected from ethernet cable. It happen as follow condition, (only BNC mode) 1. The cable is not connect to BNC. 2. The cable's wire is cut off. 3. The ethernet transceiver is damage. [NODE] : Other message during ethernet work error 旼컴컴 Error message 컴컴컴컴컴컴컴컴컴컴컴커 �*** Ethernet Hardware Could not Active *** � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� : The controller can not initial to activate. 旼컴컴 Error message 컴컴컴컴컴컴컴컴컴컴커 �*** Ethernet Hardware Fails to Stop *** � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� : The controller can not initial to stop. 旼컴컴 Error message 컴컴컴컴컴컴컴컴� 쿐thernet Base I/O conflict occured. � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : The other interface board conflicts with current Base I/O. NetWare RPL Boot ROM V1.0 (1) Introduction The Boot ROM we create uses the IBM Find/Found RPL Protocol to allow a hardware independent Boot Strap Program to boot a diskless workstation. The IBM RPL Protocol is used because it is generic and allows the board manufacturer to provide a single Boot ROM that will boot from any network supporting the protocol. Currently, this includes Novell NetWare, Microsoft LAN Manager, and IBM LAN Server. (2) BOOT ROM Specifications General function: * Boot without disk. (note: Must without hard disk.) * Support IBM Find/Founf RPL protocol. (note: Ethernet frame type: ETHERNET_802.2 ) * Calls Loader Application by using Interrupt Vector 18h. * Copies the image of boot file, Executes the Boot Strap Program. * Registers as a protocol stack with the LSL. * To download a DOS, OS/2, UNIX or any other operating system image that might be required. Hardware Specification: * Full range IO (with base I/O, base memory, IRQ) could be setting. * No failure in setting IRQ 7. * It will avoid conflict with other address setting on the Memory mapping type of Ethernet cards, like ROM BIOS, SRAM, UMB, EMS frame, and program step by 16 KB offset range. * Automatic interface with network card hardware configuration. * Diagnosis of network status. NetWare Environment: * Automatic attachment in networking, 1. Will not be affected by NetWare Watchdog function. 2. Will not be affected by NetWare console clear station function. * Automatic Resume connection after being interrupted. Environment: Operation system : Novell NetWare, Microsoft LAN Manager, and IBM LAN Server. DOS version : 3.xx, 4.xx, 5.xx, 6.xx Computer System : with IBM PC/AT/386/x86 Remote Program Load on NetWare 3.x Introducing RPL.nlm RPL.nlm is a NetWare v3.11(or v4.x) Loadable Module that acts as a Protocol Stack and responds to the IBM architected Remote Program Load (RPL) frames as defined in the "IBM Remote Program Load User's Guide". It is used in networks that have diskless workstations installed with the RPL BIOS Module. Installing RPL.nlm on the File Server The following BOOTSTRAP programs come with RPL.nlm and should be installed in the SYS:\LOGIN directory of the file server: ETHER.rpl For IBM MCA Ethernet Adapters F1ETH.rpl For IBM Model 25SX Ethernet Adapters PCN2L.rpl For IBM PC Network Adapters RBOOT.rpl For Adapters using the Novell Generic Boot TOKEN.rpl For IBM Token-Ring Network Adapters An appropriate BOOTSTRAP program gets download to the workstation in response to a SEND.FILE.REQUEST from the Boot ROM RPL Module. RPL.nlm should be installed in the SYS:\SYSTEM directory of the file server. Loading RPL.nlm on the File Server RPL.nlm is loaded the same as any NetWare NLM: LOAD RPL at the file server command prompt. there are no parameters associated with loading RPL.nlm. Binding RPL.nlm to the 802.2 Board Since RPL.nlm is a protocol Stack, it must be found to any and all Boards that have RPL clients attached to them: BIND RPL to board [ACK],[FRAME=ff],[GNS],[NODEFAULT], [PROTECT],[PS=server],[TRO] where board is the name of any NetWare LAN driver that is configured for IEEE 802.2 frame type. NOTE: About all special nouns and parameters, see "Remote Program Load on NetWare 3.x" The RPL Display Screen When the Boot ROM gets control through INT 18h, it will clear the Video display and present pertinent message as the information becomes available. An example display screen illustration shows as follows, 旼컴컴 Booting title of RPL BootROM 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿙ovell RPL BootROM v1.00 (920626) � 쿓ighlight HE200 Ethernet MLID v1.43 (940218) � 쿎opyright Highlight Computer Systems 1993-1994, All Rights Reserved. � � � 쿝PL-ROM-ADR: 484C 0000 4AA7 � 쿝PL-ROM-IRQ: 3 � 쿝PL-ROM-PIO: 300 � � � 쿝PL-ROM-FFC: 1 � 쿝PL-ROM-SFC: 15 � 쿝PL-ROM-SEQ: 5 � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� : This is a remote booting screen message for new RPL Boot ROM. * RPL-ROM-ADR: Node Address * RPL-ROM-DMA: DMA Channel * RPL-ROM-IRQ: Interrupt Level * RPL-ROM-PIO: Programmed I/O address * RPL-ROM-MM1: Memory Address 1 * RPL-ROM-ERR: The prefix of a FATAL error. * RPL-ROM-HSM: The prefix given to a driver-generated message. * RPL-ROM-FFC: The number of Find Frames sent by the Boot ROM. * RPL-ROM-SFC: The number of Send File Request Frames sent by the Boot ROM. * RPL-ROM-SEQ: The number specifying the last valid sequence number received. Message of Hardware Initialization RPL-ROM-ERR: 201 Ethernet Base I/O not found ! RPL-ROM-ERR: 202 Ethernet IRQ error ! RPL-ROM-ERR: 203 Ethernet Memory failure ! RPL-ROM-ERR: 204 Ethernet Memory not found ! RPL-ROM-ERR: 205 LAN adapter is not compatible with Highlight LAN adapter ! RPL-ROM-ERR: 206 Ethernet Base I/O conflict occured. RPL-ROM-HSM: 207 Ethernet is not compatible with WD Ethernet ! RPL-ROM-HSM: 210 Offline, check cabling system ! RPL-ROM-HSM: 211 Carrier sense lost, check the terminator ! RPL-ROM-HSM: 213 Transmit collided, check cabling system ! RPL-ROM-HSM: 222 Select Memory base out of range 旼컴컴 BooStrap title of RPL BootROM 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 쿙ovell NetWare RPL Generic BootStrap Program v4.04 (930205) � �(C) Copyright Novell, Inc., 1993 � � � � RBOOT-RPL-106: Place CURSOR on DISK IMAGE file; Hit ENTER when Ready:� � � � NET$DOS.SYS � � MS$dos.sys � � TCPIP � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 : This is a Generic BootStrap Program download screen for multiple disk image files option. There are three boot image files for option, these file name has been assigned in SYS:LOGIN\BOOTCONF.SYS text file. The content of SYS:LOGIN\BOOTCONF.SYS : { 0x484C00004AA7 = NET$DOS.SYS MS$dos.sys TCPIP 0x10005a460025 = NET$DOS.sys FRED.sys : JOE.sys } Message of BootStrap RBOOT-RPL-100: Unable to CONNECT to File Server RBOOT-RPL-101: File Server is DOWN RBOOT-RPL-102: CCB Command 00 Returned ERROR Code 00 RBOOT-RPL-103: BAD Return Code from ODI Send RBOOT-RPL-104: Unable to OPEN RBOOT-RPL-105: Attempt to WRITE OVER Disk Emulator RBOOT-RPL-106: Place CURSOR on DISK IMAGE file; Hit ENTER when Ready: RBOOT-RPL-107: Unable to READ RBOOT-RPL-108: Unable to Register IPX ODI Stack RBOOT-RPL-109: Unable to OPEN Socket 5342h RBOOT-RPL-110: Send ECB was Re-Used RBOOT-RPL-111: IML Update in Process; Computer will RE-BOOT Features of RPL.nlm * BOOTCONF.SYS is parsed by RPL.nlm at the File Server to minimize the amount of Network Traffic. * RPLFIX and RPLODI are not required when booting a workstation. * You may now boot across a Source Routing Bridge.