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

Conference jamin::pathworks32

Title:	Digital PATHWORKS 32

Moderator:	SPELNK::curless

Created:	Fri Nov 01 1996
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	337
Total number of notes:	1612

171.0. "Install Bug on Win95" by ALFSS2::TAYLOR_D (Hang On, Sloopy) Tue Mar 18 1997 11:55

    A bug maybe?
    
    Windows95 client, no PWRKS on it.  Under Control Panel >> Networking,
    here's the installed components.
    
    Client for Microsoft Networks
    DEC EtherWORKS 3/TURBO
    Dial-Up Adapter
    TCP/IP -> DEC EtherWORKS 3/TURBO
    TCP/IP -> Dial-Up Adapter
    
    Run the autoplay on the PW32 CD, pick Custom Install, select DECnet,
    VT320, LAT, DEC LAN Manager Licensing Agent.  Setup goes through
    copying all the files to \PW32 directory, and *appears* to create the
    icon group, etc.  When it finishes, it asks to be rebooted.
    
    Upon restart, the licensing bit runs.  Logon to NT domain PDC is
    successful.  However, a few things are missing.
    
    1.  Start >> Programs >> Startup -> The Event Logger isn't there.
    2.  Start >> Programs -> there is no PATHWORKS 32 icon group.
    3.  Start >> Settings >> Control Panel >> Network reveals:
    
    Client for Microsoft Networks
    DEC EtherWORKS 3/TURBO
    Dial-Up Adapter
    PATHWORKS LAT -> PATHWORKS NDIS Support
    PATHWORKS NDIS Support -> DEC EtherWORKS 3/TURBO
    TCP/IP -> DEC EtherWORKS 3/TURBO
    TCP/IP -> Dial-Up Adapter
    DEC LAN Manager Licensing Agent
    
    No DECnet!!  Go to DOS box, run NCP LOOP EXEC and it says "DECnet Not
    Installed."
    
    If the Dial-Up adapter is not installed prior to installing PW32, this
    problem does not occur.
    
    IPMT time?
    
    -Dave

T.R	Title	User	Personal Name	Date	Lines
171.1		JAMIN::WASSER	John A. Wasser	`Tue Mar 18 1997 15:12`	15
	> 1. Start >> Programs >> Startup -> The Event Logger isn't there. I don't think it is installed to run at startup time automatically. > 2. Start >> Programs -> there is no PATHWORKS 32 icon group. That is probably worth an IPMT. > 3. Start >> Settings >> Control Panel >> Network reveals: No DECnet!! I would want to check the PATHWORKS Event Log before escalating this one.
171.2		JAMIN::MAJEWSKI		`Tue Mar 18 1997 15:31`	3
	there are notes in the release notes about how PW32 behaves when there are 'multiple adapters' in the system. this may already be covered....
171.3	here comes another one...	VMSNET::DMCFARLAND	still TurboMom[tm]...	`Wed Mar 19 1997 17:01`	16
	Hi Gang, FWIW, the same thing bit me and a customer in the b*tt today. We removed everything PATHWORKS and reinstalled. Still DECnet did not show up on the Configuration screen of Control Panel, Network. We added DECnet manually from there and it worked. He also had a dial-up adapter loaded. Note -.1 is correct about the Release Notes discussing multiple adapters and how to fix it if DECnet gets bound to the wrong adapter. In my customer's case, we did not see where anything DEC was bound to the dial-up adapter. Also, my customer did get the PW32 folder and the Event Log Viewer added during the install. Diane