Jan. 1995 Readme for the DE-254 boot ROM =============================== Product name : DE-254 Feature : 8K Boot ROM for DE-250 series adapter Function : 1. Machine detected : 1> Auto detected 2> PC compatibles ( INT 19h ) 3> IBM PS/2 ( INT 18h ) 1.1 For further details, see the following: 1.1-1> Auto detected : . Auto detect bootstrap vector . One is for PC compatible machines, the other is for PS/2 and PS/VP model compatible machines. Note: User can specify which vector will be replaced. If user selected INT18h for IBM PS/2, PS/VP model or compatible machine, it would skip the confirmation message, "Boot from network (Y/N)" . Otherwise, all processes would be the same as the PC compatibles. 1.1-2> PC Compatibles (INT 19h) . If user selected item 2:" PC Compatibles (INT 19h)" , boot ROM will work by the following rules: - Check if driver A has floppy diskette with diskette in A and ON, boot from drive A. - No floppy diskette in A , check if user has hard disk. No hard disk , boot from network . - With hard disk , it will confirm "Boot from network (Y/N) ?" Yes, boot from the network. No , boot from the hard disk. 1.1-3> IBM PS/2 (INT 18h) . This is for IBM PS/2, PS/VP machine or compatible that supports the system startup procedure function. 2. Server detected Supported server are as follows: 1> Netware RPL Server 2> IBM LAN Server 3.0 3> IBM LAN Server 4.0 4> MS LAN MAN Server 5> The first available server 2.1 For further details, see the following: 2.1-1> Netware RPL Server . Boot from Netware RPL Server 2.1-2> IBM LAN Server 3.0 . Boot from IBM LAN Server 3.0 2.1-3> IBM LAN Server 4.0 . Boot from IBM LAN Server 4.0 2.1-4> MS LAN MAN Server . Boot from MS LAN MAN Server 2.1-5> The first available server . It will find the server in the network which responds first. Troubleshooting: 1. Remote boot function doesn't work ? Ans. . Check if boot ROM has been plugged in correctly. . Check if NIC's remote boot function is enabled. . Select ROM address that does NOT conflict with another device. . Select 8K bytes ROM size. . Cold start your system again. . If still doesn't work, have system service. 2. Finding IBM LAN SERVER failure ? Ans. . Check if LAN SERVER net started successfully. . Check if LAN SERVER support remoteboot function. . Check if machine ID has been created. . Check if IPL server has been created. . Please refer to the IBM LAN SERVER manual. 3. Finding Netware RPL boot server failure ? 3-1. Ans. . Check if Netware server is on-line . Make sure adapter is working properly. . Check if Netware server support RPL and IPX interface. . Check if Netware server support ETHERNET_802.2 frame type. . Load drivers as follows: :LOAD xxx.LAN frame=ethernet_802.2 :LOAD RPL.NLM :LOAD IPX.NLM (default initial) :BIND IPX to xxx.LAN net=100 :BIND RPL to xxx.LAN . If still doesn't work, have system service. 3-2. Remote boot from server failure Ans. Check if boot volume support bootable function. 4. Finding MS LAN MAN failure ? Ans. . Check if LAN MAN net started successfully. . Check if LAN MAN support remote boot function. . Check if remoteboot configurations for new adapters have been created correctly. . Check if machine ID has been created. . Check if IPL server has been created. . Please refer to the MS LAN MAN manual. Note: 1. RPL (RIPL) : Remote Initialization Program Loader. 2. Netware RPL server, IBM LAN Server 3.0, IBM LAN Server 4.0, and MS LAN MAN server all follow the RPL specifications.