Conference netcad::hub_mgnt

1458.0. "Problem with X3.1 and/or HPOV" by PADNOM::PEYRACHE (Jean-Yves Peyrache Country Support Group France) Wed Sep 21 1994 06:42

 Hello,


  i have some trouble to install/and works with X3.1 of HUBWatch for dos
  and /or HPOV:

   my configuration is a DECPC425 and Etherworks 3 with 10M of memory 
   and before installing X3.1 and HPOV  X7.2 
   i  works with Hubwatch T2.0.1 and/or HPOV 7.1 and
   on-Demand (Chipcom Hub Products) and or course with no problem.

    First Problem:

   Starting Hubwatch X3.1 after installation in Stand-alone mode (without HPOV)
   an error message occured during the netbind (this problem has already        
   described in notefiles 1437).
    error message is 
   "MAC0020E hardware does not match MEMORYMODE parameter in protocol.ini file"
   "LD0014 driver failed to initialize" replacing with old networks files
(ewrk3.protocol.ini,netbind) from V2.0 kits
   cured the error message but Hubwatch could'nt display any HUB with
   a new message "windows error Hubwatch error in Hubwatch.exe at 0009:78CF"
   

   Second Problem:

   during the startup of HPOV just after the first banner "HPOPENVIEW FOR       
   Windows" 
   2 errors messages appears (already described in notes 1435)
   "Stop ping init failure  ovnetmon err 20"
   "NETOV Apllication did'net initialise OV212"

   i have the same error message with the TCP-IP stack from NETmanage and
   the Stack form Pathworks (Hubwatch for Dos V2.0 kit). 
   despite of that ,HPOV      seems to be worked :aka
   i can query some SNMP informations from a lot of Hubs using SNMP Manager      
   option under HPOV.


   thanks for any comments,pointers,replies

   Jean-Yves

>>    First Problem: MEMORYMODE
   Refer to 1437.1 and 1437.2.

>>    Second Problem: OPENVIEW 

   Refer to 1435.1 and 1435.2.  

Barb

 barb,

  >>>>    First Problem: MEMORYMODE
  >>>>    Refer to 1437.1 and 1437.2.

 
   it's ok for the MEMORYMODE error message, but i have always the "general
   Protection Failure at  0009:78CF"

   any others clue..

  Jean-Yves

   What version of HUBwatch are you using X3.1._ ????
   It may depend.

   Is WSAVERS=1.1 set in your AUTOEXEC.BAT. This is the WINSOCK.DLL version.
   Check to make sure that the WSAVERS environment variable is set. We 
   have corrected the GPF that is generated when WSAVERS is not set in 
   the latest version. 

Barb

 -5

  solved with set wsavers=1.1 in autoexec.bat
  hope that be fixed in SSB version

  jean-yves