Conference netcad::hub_mgnt

1429.0. "Hubwatch on DOS some feedback" by KETJE::VANDENBERG_R () Thu Sep 15 1994 06:25

	I would like to report some problem encountered using Hubwatch on DOS

	The Pc used is a so called DCWB PC (Digital Consultant Work Bench)
	model DECpc 425SL/e
	8 Mbytes mem
	Clock 25 MHz

	1. With hubwatch 2.x 
	   Work fine if not connected to an eavy configured Hub900 
	   (more than 2 repeaters 900TM for example)
	   Or using polling.
	   The symptom is an excessive disk activity with envetually 
	   a refresh of the screen but mostly a 'hourglass' is diplayed.
	   My impression is that the problem is due the dblspace mechanism.
	   Any idea about that ?

	2. With hubwatch 3.1
	   I couldn't manage to let it run.
	   The following message occurs trying to access a hub:

	   WinExec PWWSOCK.EXE failed, low conventional memory ?

	   Doing a mem/d/p I have:
	   Type of memory	Total	=	Used	=	Free
	   ------------------ ---------     -----------   ------------
	   Conventional		655,360		159,744		495,616
	   Upper	         76,592          76,592		      0
	   Reserved	        393,216		393,216		      0
	   Extended (XMS)     7,263,440	      6,214,864	      1,048,576
	   ------------------ ---------      -----------  -------------
	   Total memory       8,388,608	      6,844,416	      1,544,192

	   I have tryed  to have the smallest config as possible; the only 	
	   program that I can't get out of the conventional memory
	   is TCPIP wich is taking 41K
	   Of course I am not a DOS specialist so I don't know what I should do.
	
	   Is 495K of conventional memory not sufficient ?

		Thanks,
		Robert	   

Robert,

I encountered this error when attempting to run HUBwatch on a PC which also had
Pathworks running.  I don't know if you have Pathworks or not, but if you do, it
is documented in the READ_ME.TXT file that comes with HUBwatch that you must
copy two files to the Pathworks directory in order for HUBwatch to work.  When I
did this, HUBwatch came up just fine with Pathworks running.

From the READ_ME.TXT file, "A SPECIAL NOTE TO PATHWORKS USERS" section:

2. Reconnect to your PC client and manually copy the following files from the
PCAPPS directory to your PATHWORKS directory:

	* WINSOCK.DLL
	* PWWSOCK.EXE

Hope this helps.

...Roger...

	It works, many thanks, I didn't check that one  because of the message.

	Robert

    Another little bug I found with the X3.1.3 version is the following:
    When I click on a DETMM module and then on a specific port, I want to
    add a port description. Every first attempt on the module fails with
    "no response from agent".
    If I just do it again, it works. All subsequent port defintions on the
    same module are fine too. As soon as I select a new module, the first 
    port I select needs again 2 attempts to get its data.
    
    Cheers, Peter