Conference netcad::hub_mgnt

    
    Try putting a /n after SCHK. This will stop it from looking at the
    interrupt and everything will probably work. I've seen this on other
    NICs.
    
    Dennis Faust
    

	As Dennis suggested...

	Add /NDIS to the SCHK.exe line in the STRTNDIS.BAT file.
	This command loads the scheduler for the network operating
	system. The /NDIS qualifier bypasses some NDIS error checking
	during loading. Excerpt from PW documentation... This switch
	may be necessary for a few thrid-party NDIS drivers.

	We have found this to be a problem in some cases and will be
	adding this line as the default in the next release version.    
Barb

Has anyone gotten HUBwatch to run on a DECpc XL with a DE435?  I haven't gotten
any useful responses from this notesfile or the Pathworks or Etherworks notes
files.  I am really very frustrated with this whole mess and noone seems to have
any answers.

Bill

    
    I have a customer who has a DEC Celebris PC with a DEC DE435 PCI
    Ethernet card... will the the DE435 work with HUBwatch V3.1 ...
    the base note indicates that there may be a problem...
    
    
    

    I've got a Celebris XL590 that I'm trying to get HUBwatch working on
    with a DE435 interface on it as well.  With some help from Barb, I was
    able to locate new drivers for it... V2.40 and have managed to get the
    IPSTACK up and running without any errors.  It was rather painful and I
    found that the HUBwatch installer didn't deal with the PROTOCOL.INI
    file properly.  I had to edit it by hand.
    
    I've run a few tests with PING and such so I know that the stack is
    running fine.
    
    When I startup V4.1.1 and specify the address of the DEChub 900 I get
    an error after a few moments "system error."  Nothing more to indicate
    what the problem might be.
    
    If I run the other HUBwatch programs like the HUBloader, for example. 
    I get an error that says that it is specifying too much memory in the
    PIF.  The box is titled MS-DOS EDITOR... KB REQUIRED is too large. 
    This happened when I clicked on EDIT LIST.  The HWDOS.PIF file is the
    same as when it was installed.
    
    If I run the TFTP server, I get an error that the Windows Socket
    Library is not available.  I'm running WFW V3.11.
    
    Where do I go from here?
    
    	David

>>    file properly.  I had to edit it by hand.
The READ_ME.TXT specifically states for the "Other" Network Card Option you 
must manually edit the PROTOCOL.INI file.
    
>>    When I startup V4.1.1 and specify the address of the DEChub 900 I get
>>    an error after a few moments "system error."  Nothing more to indicate
>>    what the problem might be.
Taken from the READ_ME.TXT:
---------------------------
Message: Cannot Run Program	Reason:
				1- WINSOCK.DLL is not in PATH
				2- Network is not loaded

Message: System or General Error Reason:
				 1- DECPW.386 is not on the NETWORK= line
				    in the [386ENH] section of the
				    C:\WINDOWS\SYSTEM.INI.
				 2- Windows is started in standard mode.
				 3- Mismatch between HUBwatch environment
				    variable and location of the installation 
				    of the HUBwatch executable.
				 4- WINSOCK environment variable is not set.
    
Check specifically the WINSOCK.DLL in the path and all the Reasons for the
System or General Error.

Barb

Hi Barb!

	Thanks for the response.  Is the READ_ME.TXT in the HUBWATCH directory?
I'll have to look for it next time.

	I'll check out your comments and let you know if I have more problems.

	Thanks!
		David

Hi Barb!

	All is well now.  Here's what I needed to do:

	1)  Got new V2.40 DE435 driver kit from KALI::PCDRIVERS:[DE435.RELEASE]

	2)  Copied the NDIS2 DOS driver directory to the C: drive into a
	    DE435 directory for convenience

	3)  In the HUBwatch Installer, I chose set-up network configuration 
	    although you can also do this as part of the install.

	    3a)  Fill out addressing information as completely as possible.  The
		 XXX's that you'll see in address questions will cause problems
		 if left that way.  I replaced Gateway addresses with 0.0.0.0
		 instead.  Makes the TCP/IP components happier.  It would be
		 nice if the installer defaulted to 0.0.0.0 out of the box!

	    3b)  When you get to the driver selection, select OTHER

	    3c)  It will ask for the device/directory and driver name.  For my
		 environment I told it:

			Device/directory = C:\de435
			Driver           = dc21x4.dos

		 NOTE:  Check the resulting STRTNDIS.BAT.  Since I had changed
			the network config so many times I saw that the
			installer added multiple "ld" lines.  I deleted the
			duplicates and for good measure added the device and
			directory to the driver name as the installer didn't
			prepend it to the driver name.  I couldn't see how LD
			would know to find the driver in the DE435 directory.

	4)  When STRTNDIS.BAT is run it automatically adds the path to the
	    IPSTACK directory to the list.  WINSOCK.DLL lives there and is
	    important for HUBwatch.

	5)  Next I edited PROTOCOL.INI in C:\HUBWATCH\IPSTACK to add the
	    support for the DE435.  I'll post the file in the next 
	    note.

	6)  The last important thing to do is to edit C:\WINDOWS\SYSTEM.INI.
	    Find the [386ENH] section and the line NETWORK=.  Insure that
	    DECPW.386 is contained on that line somewhere.  It is a comma
	    separated list.  If it isn't there, add it!

Reboot your PC and you should be golden.  My PC is running fine now with the
HUBwatch IP stack, and Microsoft NETBIOS stuff in WFW V3.11.

Hope this is helpful and complete!

	Regards,
		David

[protocol manager]
    DRIVERNAME  = PROTMAN$
 
[DATALINK]
    DRIVERNAME  = DLL$MAC
    LG_BUFFERS  = 14
    SM_BUFFERS  = 6
    OUTSTANDING = 32
    BINDINGS    = DC21X4$
    DECPARM     = c:\hubwatch\
;;  NI_IRQ      = 5
;;
;;  Your DECnet address is AA000400A611
;;
 
[DC21X4$]

DRIVERNAME = DC21X4$

;; Range: 1-26.   
;; Usage: "Slot=nn"
;------------------
; SLOT = 16             

;; Options: TP, AUI, BNC, TP_FULL_DUPLEX, AUTOSENSE
;; Usage: "SIA_Mode=xxx" 
;-----------------------  
SIA_MODE = AUTOSENSE
  

The HUBwatch READ_ME.TXT is on diskette 1 and should reside in your \HUBWATCH
directory.
Barb