[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

1464.0. "HUBwatch 3.1, windows, compaq: GPF!" by OREGUN::GREGORYDA (David Gregory, MCS, Portland, OR ) Wed Sep 21 1994 22:09

I just installed HUBwatch 3.1 onto a COMPAQ 486-66 with WIndows 3.1, Intel
Etherexpress-16, TCP/IP and NDIS already loaded.

Added the SET = command to autoexec and the required line to WIN.INI

I don't require the network \IPSTACK stuff, so did not config network stuff.

After clicking the HUBwatch Icon and answering the questions about the Agent,
Windows gets GPF, in module HUBWATCH.EXE.


Is there anything obviously wrong with this picture? I did capture the GPF with
DrWatson, for what that is worth. Usually, not much. Details available.

 - dave
T.RTitleUserPersonal
Name		DateLines
1464.1Moi aussiPADNOM::PEYRACHEJean-Yves Peyrache Country Support Group FranceThu Sep 22 1994 08:518
  hi dave,


 you ar'nt alone , i have same problem (seems notes 1458)
 awaiting a response from engeneering group

  Jean-Yves
1464.2hindsight:==20/20OREGUN::GREGORYDADavid Gregory, MCS, Portland, OR Thu Sep 22 1994 21:5222
An update: problem resolved.

How:  I backed off to HUBwatch 2.0 and that failed using the customers TCP-IP
stack, with a failed to open socket message.  I then ripped out and config'd
around that stack and implimented HUBwatch/IPstack, however the 2.0 version
failed to correctly build PROTOCOL.INI, on the Intel NIC (Etherexpress16).

I figured that the GPF using HUBwatch X3.1.3 was probably caused by the other
guys IP stack, so I rebuilt 3.1.3 using the network IPstack with HUBwatch. (of
course if anything can go wrong, it will... the bridge900mx went to sleep,
which is the hub manager; i attributed that to being a demo/old/loaner
product...)

ANyway, after that was rebooted, HUBwatch was up and the DEChub900 was
configurable.

Moral of the story: use your IPstack!

BTW: The Etherexpress16 was a selectable NIC with HUBwatch x3.1.3! good job!
 - dave
1464.3DEMO UNITS NOT SUPPORTED BY ENGDELNI::ROUNDSFri Sep 23 1994 07:347
    Dave,
    
       Is that 'old' bridge in a customer's production environment or is it
    in your own DEC test environment? If it is in a customer's network. It
    is not supported and it needs to be removed.
    
    Nat
1464.4GPF againPADNOM::PEYRACHEJean-Yves Peyrache Country Support Group FranceFri Sep 23 1994 09:3410
   Dave,

  it's  GPF in HUBwatch.exe at 0009:78CF your error message
  i have the same problem, and i can't resolve it 
  can you described in deep your solution

  thanks

  Jean-Yves
1464.5try using the HW IPstack; works 4 meOREGUN::GREGORYDADavid Gregory, MCS, Portland, OR Fri Sep 23 1994 12:3324
That GPF @ 0009:78CF seems to be the one.

Basically, I reverted back to using HUBwatch v2.0 and that failed with the
message: cannot open socket...  At that point I removed the customers IP
software (ftpSoftware) and configured for HUBwatch's own IPstack, with the
Intel Etherexpress16 NIC. This also failed however, when PROTOCOL.INI wasn't
built correctly by HUBwatch. It seems HW never modified the stub file...

At this point I decided to rebuild HUBwatch using X3.1.3 WITH the HUBwatch
IPstack. This configured much better, being able to choose from the menu, the
Intel Etherexpress16 NIC and PROTOCOL.INI was configured correctly now. I
rebooted and verfied that IP was loaded correctly, started Windows, clicked on
the HUBwatch icon, answered the questions about AgentName, IPaddress,
CommunityName, Retry & TimeOut and then HUBwatch came up, and was able to
configure the hub.

I suspect that the ftpSoftware stack amy not have been configured to use the
WINsock dll properly, etc.... I could not detect that when WIndows just throws
up a GPF, and didn't realize that there might be a problem with the customer
previously configured stack until HW v2.0 complained about being unable to find
a socket... at least it didn't GPF.

-dave
1464.6merciPADNOM::PEYRACHEJean-Yves Peyrache Country Support Group FranceFri Sep 23 1994 13:316
  thanks dave,

  i tried a new installation from scratch disk

  Jean-yves
1464.7Please verify real status of that bridge....NETCAD::BATTERSBYFri Sep 23 1994 13:325
    Dave, what about Nat's question?? Old loaners...etc. should
    *really* be removed from the customer's environment if such is
    the case and replaced with an equivalent that can be fully supported.
    
    Bob
1464.8send it to: me @pdoOREGUN::GREGORYDADavid Gregory, MCS, Portland, OR Sat Sep 24 1994 12:1114
Well, at this point in time there is no other product yet available. 

When one is produced it will be Fed-Ex'd and installed - next week.  This
was/is a rush job for a customer investigating the DEChub900 solution, after
failing to get either a SynOptics or a Chipcom solution functional.


<sarcasim = ON>
HUBwatch still GPF's intermitently when some operations appear to overly tax
the robust DOS/Windows platform. At least it is an open system. Non of that
stable VMS stuff to contend with...

 -dg