Technical Information Document
386 NLM Allows Remote Boot for 3com 3station - TID2 (last modified 25JAN1999)
2 2
associated file

Click filename to download:
3cboot.exe; 33111 bytes; Date/Time: 09-17-1993/03:43PM

abstract

This file contains an NLM that allows you to do a remote boot from a 3COM workstation using NetWare v3.1x. The file 3C1100.COM is a certified DOSODI driver for 3COM 3STATIONS. For information about implementing DOSODI drivers refer to the NetWare ODI Shell for DOS manual (NetWare 3.11), or the Installation manual (NetWare 3.10).

installation

issue

Self-Extracting File Name: 3CBOOT.EXE Revision: A

Files Included Size Date Time

\
  3CBOOT.TXT (This File)
  3C1100.COM 12288 11-12-91 10:42a
  3CBOOT.NLM 11897 9-30-91 2:32p

INSTALLATION INSTRUCTIONS

This README file of 3CBOOT.EXE is for NetWare v3.10 or v3.11.

3CBOOT.NLM - FILE SERVER DRIVER
3C1100.COM - WORKSTATION DRIVER

** 3C1100.COM is a CERTIFIED DOSODI driver for 3COM 3STATIONS. For information regarding the implementation of DOSODI drivers refer to the NETWARE ODI Shell for DOS manual (Netware 3.11) or the Installation manual (Netware 3.10). The following files are also needed:

       LSL.COM
       IPXODI.COM
       NETX.COM

REQUIREMENTS:

1. Server running NetWare v3.10 or NetWare v3.11.

2. NetWare Installation manuals.

SERVER INSTALLATION:

1. Copy the 3cboot.nlm to the server's SYS:SYSTEM directory.

2. Edit the Autoexec.ncf to include the following:

     "load <landriver> frame=ethernet_ii name=net1"
     "bind ipx to net1 net=<net1number>"
     "load 3cboot"
     "bind 3cboot net1"

     Where <landriver> = lan driver for server. eg. NE2000
           <net1number> = net number for that cabel segment.
            e.g 5678.

     For a more complete example of an AUTOEXEC.NCF please
     refer to the example section at the end of this document.

WORKSTATION INSTALLATION:

3. Format a bootable diskette and copy the following files to the newly created diskette:

    Config.sys**
    Netx.com
    Autoexec.bat**
    Rplodi.com
    Lsl.com
    3c1100.com
    Ipxodi.com

    ***NOTE: If you are using a NET.CFG, you must delete it.

     **See the EXAMPLES section for examples of these files

4. Create Boot Image:

 1. Connect to server with a machine containing a floppy drive.
 2. Login as supervisor
 3. Change directories to SYS:LOGIN (e.g cd SYS:LOGIN)
 4. MAP S3:=SYS:SYSTEM (optional)
 5. Place the boot diskette (the one you created in Step 3) into
    drive A:
 6. Run DOSGEN (eg. "\system\dosgen")
    (See NetWare Installation manual for details on creating
     a DOS boot image.)
 7. Copy a:\autoexec.bat to sys:\login\autoexec.bat

5. Connect 3Station to ethernet wire and power it on.

EXAMPLES

Example Config.sys:
     shell = command.com /e:1024 /p
     files = 20
     buffers = 20

Example Autoexec.bat:

     break on
     prompt = $p$g
     Lsl
     Rplodi
     3c1100
     Ipxodi
     netx
     f:
     login

Example Autoexec.ncf:

    file server name Example
    IPX internal net=123456
    load ne2000 port=300 int=3 frame=Ethernet_ii name=net1
    load ne2000 port=300 int=3 frame=Ethernet_802.3 name=net2
    bind IPX to net1 net=3456
    bind IPX to net2 net=5678
    load 3cboot
    bind 3cboot net1
    load remote bigshot
    load rspx
    mount all

contents

Self-Extracting File Name:  3cboot.exe

Files Included       Size   Date         Time    Version   Checksum

\
    3C1100.COM      12288   11-12-1991   09:42AM
    3CBOOT.NLM      11897   09-30-1991   01:32PM
    3CBOOT.TXT       3992   09-17-1993   01:07AM
Document Title: 386 NLM Allows Remote Boot for 3com 3station
Document ID: 2
Creation Date: 01JUL1993
Modified Date: 25JAN1999
Document Revision: 1
Novell Product Class: NetWare
Novell Product and Version: NetWare 3.11

Disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.

Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.