[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

2522.0. "gpf when installing V4 Hubwatch for Windows" by CSC32::R_BUCK (Have been assimilated) Fri Jul 14 1995 18:36

    Working with a customer trying to install Hubwatch V4 on a number of
    PC's.  All are running MS-DOS 6.1 and WFW 3.11.  Different disk
    configurations.  Some have SCSI drives.  At least one uses Norton
    Desktop.  Installation option being used is option 1, Install Hubwatch,
    Hubloaded, TFTP_server - no network.
    
    On every system this customer attempted an install, after the step
    where the program icons are setup in a program group, the installation
    will abort with a gpf.  Last message seen is something about looking
    for installed Pathworks components.  Customer also believe that it
    seems to fail when drive D: is being accessed.
    
    Actual text of message is probably not accurate.  States it's something
    like "gpf shadow caused gpf fault in module tmp1d26.exe@0001;2e6c" 
    Further stated that the file name changes.
    
    In this case I had him just restart windows and attempt to use
    Hubwatch.  It *seems* like it's ok, however, in this case he was not
    able to actually work with a hub because it was not yet installed.
    
    As best I can tell, the only thing in commom with all of the failed
    installs is the distribution being used.  I will probably send him a
    new copy of the Hubwatch distribution just to check this out.  Anyone
    else getting reports of install problems?  Anything else I should
    check??
    
    Thank You
    Randall Buck
T.RTitleUserPersonal
Name
DateLines
2522.1Distribution?NETCAD::FORINOMon Jul 17 1995 09:584
    What is the distribution being used?  Are you pulling the kits off the
    net or are these real kits coming out of manufacturing?
    
    							John
2522.2It's the real thingCSC32::R_BUCKHave been assimilatedMon Jul 17 1995 11:298
    This is a real kit.  In fact, the customer was a little suprised at
    the amount of stuff he received.  What he believed he ordered was a
    DECswitch 900EE with a DEChub one and the Hubwatch for Windows
    software.  He received over 20 disks, (Hubwatch, Firmware, Gigaswitch,
    tutorials, and other), plus lots of documentation on everything but the
    DECswitch.  
    
    Randall Buck
2522.3same problem, hubwatch 4.1.1NYOSS1::PASAGE::PLUNKETTMon Dec 04 1995 11:1914
    I'm having the exact same error in the base note: SHADOW caused a
    gpf in module ~TM1D121.exe at 0001:2e6c.  The failure occurs when
    Instalit is telling me that it is searching all drives for pathworks
    components.
    
    I am trying to install
    Hubwatch version 4.1.1 that I pulled off the net.  Any ideas?  The
    system is a compaq 486/33 with 16mbytes and netware with LAN
    workplace for DOS as the IP stack.  
    
    It happens when I choose the install hubwatch, hubloader, and
    netrider only.  
    
    -Craig
2522.4Installer can't deal with a large search set, I guessNYOSS1::PASAGE::PLUNKETTTue Dec 05 1995 09:426
    This problem was resolved by logging out of the netware server that
    the PC was using.  Evidently, if you have a large amount of drives
    mapped to network directories, some piece of the installation
    procedure chokes and dies.
    
    -Craig
2522.5Installation GPF, Shadow probs will not exist in V5.0NETCAD::WAGNERCOFFILTue Dec 05 1995 11:0511
>>	Evidently, if you have a large amount of drives
>>    mapped to network directories, some piece of the installation
>>    procedure chokes and dies.
When I read your first note, me reponse was to disable the network stack 
or disable any network drive connections. This is not an exceptable response.

But...    
This will be fixed in Version 5.0, we will be using a different Installer.

Barb