Mailer: Elm [revision: 66.36.1.1]
Newsgroups: bit.listserv.novell
Date:         Wed, 27 Jan 1993 18:59:25 MET
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Partner Support Group <psg@HPUAMSC.NETH.HP.COM>
Subject:      Re: your mail
              "hrizuk@MAX.MUHLBERG.EDU" at Jan 26, 93 1:36 pm

>
> To: Any Remote Boot Gurus
>
> I'm having problem getting a boot image diskette file I've
> created to work. The boot image file is intended to allow me
> to remotely boot a PC from the fileserver and load the
> necessary drivers (NDIS card drivers) to be able to login to
> a Netware server and Unix server simultaneously. The problem
> is I keep getting an error message "Error reading boot image
> disk file" everytime I boot the PC which uses the boot image
> disk file. If I create a generic boot image file, just to
> load DOS and login, it works fine.  As soon as I include all
> the drivers, etc. needed to use AIR for DOS (the product I'm
> using to connect to the UNIX server over the LAN) I get the
> error.  They suggest in the Netware manuals booting the PC
> from the diskette used to generate the boot image disk file.
> When I do this it boots fine; I'm able to use AIR for DOS
> and logon to the Unix server while being logged into a
> Netware server without any trouble. Below I've included a
> copy of my CONFIG.SYS, AUTOEXEC.BAT and CLASSRM.BAT files
> used to boot the PC and create the boot image file along
> with some other pertinent information.
>
> [CONFIG.SYS]
> FILES=30
> BUFFERS=25
> DEVICE=PROTMAN.DOS /I:A:\
> DEVICE=MACWD.DOS
>
> [AUTOEXEC.BAT]
> CLASSRM.BAT
>
> [CLASSRM.BAT]
> PROMPT $P$G
> IPX
> TCPNDIS
> NETBIND
> NETX
> F:
> LOGIN ETTINGER/
>
>
> All the files needed are located in the root directory of
> drive A: (there are no subdirectories).
>
> The files contained on the diskette are:
>
> AUTOEXEC.BAT
> CLASSRM.BAT
> COMMAND.COM
> CONFIG.SYS
> IPX.COM*
> MACWD.DOS*
> NETBIND.EXE*
> NETX.COM
> PROTMAN.DOS*
> PROTOCOL.INI*
> TCPNDIS.EXE*
>
> (* These files came with the AIR for DOS software package)
>
> My PROTOCOL.INI file is as follows:
>
> [PROTOCOL MANAGER]
>      DRIVERNAME    = PROTMAN$
>      DYNAMIC       = YES
>
> ; - MAC Drivers
> ---------------------------------------------------------
>
> [MACWD_NIF]
>      DRIVERNAME    = MACWD$
>      IRQ           = 5
>      RAMADDRESS    = 0xC800
>      IOBASE        = 0X2C0
>
> ; - Protocol Drivers
> ----------------------------------------------------
>
> [SPRY CONCURRENT]
>      DRIVERNAME    = SPRY$CONCURRENT
>      BINDINGS      = MACWD_NIF
>
> [SPRY TCP]
>      DRIVERNAME    = SPRY$TCP
>      BINDINGS      = MACWD_NIF
>      INTVEC        = 0x62
>
> The hardware and software we are using is a follows:
>
> PC:  AT&T 6386SX/EL WGS Personal Computer
> NIC: Western Digital 8003W 10 BASE-T Ethernet NIC
> Boot ROM: Western Digital Boot Rom v2.02 NVL (62-000372-000)
> MS-DOS: Version 3.3 (AT&T)
> NOS: NetWare 3.11, 2.15 and 2.11
> Connectivity Software: AIR for DOS
>                        Spry Inc.
>                        1319 DEXTER AVE N
>                        SUITE 150
>                        SEATTLE, WA 98109
>
>                        PHONE: 206 286-1412
>                        FAX  : 206 286-1722
>                        MODEM: 206 286-1405
>                        INTERNET:  techs@spry.com
>
>
> I've made sure I copied the boot image diskette file
> (CLASSRM.SYS) and the batch file called by AUTOEXEC.BAT
> (CLASSRM.BAT) to all the file servers (in the LOGIN
> directory) connected to the network.  In addition I've
> ammended the BOOTCONF.SYS file to reflect the PCs network,
> address, and boot image filename. I copied this new
> BOOTCONF.SYS to all servers connected to the network.
>
> When I boot the PC the Protocol Manager loads displaying the
> card info on the screen and then stops. Eventually I get the
> error message mentioned above. Then the message
> "Initializing Adapter" appears again, followed by "A
> software configurable adapter was found", followed by
> "Initialization Complete", then just a cursor and that's all
> she wrote.
>
> These machines work with these NICs and Boot ROMs because
> we've had them remotely booting from the server for the past
> 2 years. But now we'd like to also connect to our UNIX
> server via the network instead of direct wiring.
>
> I've been using the AIR for DOS product on other PCs
> (Booting from Hard Drives) around campus, that need this
> kind of connectivity, without any difficulties.  I need to
> be able to get this to work in the not too distant future
> because boot diskettes will never work in our
> classroom/labs.
>
> Any and all help anyone can give me will be appreciated.
> Thanks in advance.
> ------------------------------------------------------------
> John Hrizuk                Internet:hrizuk@max.muhlberg.edu
> Muhlenberg College         Compuserve: 71756,2225
> 2400 Chew St.              Phone: (215) 821-3309
> Allentown, PA 18104        Fax: (215) 821-3534
> ------------------------------------------------------------
>
>
We had a similar problem. From diskette it worked fine, but after creating
the boot-image file there was no way to boot remotely.
It seemed that the NETBIND did a reset of the network board and couldn't
establish neither an IPX connection or TCP/IP connection.
When we created a RAM-Disk on the PC and ran the NETBIND from there we could
we could established the connections.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU