[comp.protocols.nfs] PC-NFS Install Help Needed

jgr@cbnewsb.cb.att.com (jefferson.g.risner) (03/08/91)

   Can anyone tell me what I'm doing wrong trying to install PC-NFS
on an AT&T 6312 WGS (286 pc) using an AT&T Starlan board?  I'm trying
to use the at&t.com and pktd.sys files downloaded from Clarkson U.
and I'm getting an error like "Bad or missing CON" when I boot the
PC.  My config.sys and autoexec.bat files are listed below along with
the screen messages displayed when I boot.

   Please respond by E-Mail.


                             Thanks in Advance,

                                   Jeff Risner
                                   AT&T Bell Labs
                                   jgr@cbnewsb.cb.att.com


HERE'S MY CONFIG.SYS FILE:

   device=c:\dos3_3\ansi.sys
   SHELL=c:\command.com /E:1024 /P
   BUFFERS=20
   FILES=20
   DEVICE=C:\NFS\PCNFS.SYS 
   DEVICE=C:\NFS\SOCKDRV.SYS
   device=c:\nfs\pktd.sys
   LASTDRIVE=V


HERE'S MY AUTOEXEC.BAT FILE:

   @echo off
   SET TZ=CST6CDT
   prompt $p$g
   path=c:\;c:\bat;c:\bin;c:\cmds;c:\dos3_3;c:\nfs
   c:

   SET NFSDRIVE=C
   PRT *
   c:\nfs\at&t.com 0x60 0x3 0x368 0xd000
   NFSRUN


HERE'S WHAT HAPPENS WHEN I BOOT THE PC:  (condensed version)

   Primary Boot Strap
   AT&T Personal Computer MS-DOS 3.30a Release 1.0
   Copyright ....

   Sun Microsystems PC-NFS Network File System
   Version 3.01
   Serial # ....
   Copyright .....

   Bad or missing CON

   Packet Driver for the AT&T Starlan/Ethernet boards version 7.1.1
   Portions Copyright ....
   Packet driver skeleton copyright ....
   This program is free .....
   NO WARRANTY ....

   Packet driver loaded at segment 2131
   This board is an AT&T Starlan 10 R3 NAU
   TDR ok
   Interrupt number 0x3 (3)
   I/O port 0x368 (872)
   Memory address 0xd000 (53248)
   My Ethernet address is 08:00:6A:82:46:C3

   C:\>NET YPDOMAIN intl_lan
   [PC-NFS Installed]

   C:\>NET START RDR jeff *

   C:\>NET YPSET intl0
   Could not open socket - SOCKDRV.SYS may not be configured

****at this point the computer reboots itself, reloads the packet 
****driver at a different segment and then hangs up after the NET YPDOMAIN
****command