[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

230.0. "PW32 still loads 1.0a lic req" by VMSNET::DMCFARLAND (still TurboMom[tm]...) Tue Apr 15 1997 18:16

    Hi folx, 
    
    Has anyone heard of a Win95/PW 1.0a to PW32 upgrade in which the client
    simply can NOT get rid of the old 1.0a license requester?  This poor
    customer has gone through the PW32 remove procedure, he has removed
    PW 1.0a from Network Control Panel, deleted DEC* and PW* files from
    all pertinent directories, has scoured the registry for entries of PW*,
    DEC*, Digital and PATHWORKS.  Yet, when he reinstalls PW32, the old
    license requester wants to load.
    
    I have had a suggestion to remove/rename the INSTLICL.DLL file and
    any registry references to it.  Any/all other suggestions are also
    welcome.  His PW Event Log follows:
    
    Diane
    
            	LOG0002N:	Start logging at 09:21:16, on Tuesday April
    15, 1997
            	CORE0001S:	DECCORE V1.0.035 Loaded Successfully. 
    (SignOn) 
            	IOCB0009S:	DECIOCB V1.0.041 Successfully Hooked INT's
    6E & 78.  (SignOn) 
            	TUNE0001S:	DECSHOW Version 1.0.4   (SignOn) 
            	TUNE0002S:	Copyright (c) 1995,1997 Digital Equipment
    Corporation  (SignOn) 
            	TUNE0006S:	Installed successfully  (SignOn) 
            	LMAP0001S:	DECLMAP Version 1.0.8   (SignOn) 
            	LMAP0002S:	Copyright (c) 1995,1997 Digital Equipment
    Corporation  (SignOn) 
            	LMAP0006N:	DECLMAP installed successfully  
            	NDIS0001S:	DECNDIS Version  1.0.31   (SignOn) 
            	NDIS0002S:	Copyright (c) 1995,1997 Digital Equipment
    Corporation  (SignOn) 
            	NDIS0006S:	Datalink installed successfully.  (SignOn) 
            	NDIS0008S:	Datalink #0 bound to adapter 0000 (DEC
    DC21041 PCI Ethernet Adapter).  (SignOn) 
            	NDIS0008S:	Datalink #1 bound to adapter 0000 (DEC
    DC21041 PCI Ethernet Adapter).  (SignOn) 
            	DNP0001S: 	DECDNP Version 1.0.80   (SignOn) 
            	DNP0002S: 	Copyright (c) 1995,1997 Digital Equipment
    Corporation  (SignOn) 
            	DNP0003S: 	Reading database file C:\PW32\PWENT.DAT 
    (SignOn) 
            	DNP0004S: 	DECnet node name 0TC114 (1.114)  (SignOn) 
            	IOCB0003N:	DNP IOCB Interface Loaded.  
            	DNP0006S: 	DECnet Installed successfully  (SignOn) 
            	DNP0005S: 	DECnet NETBIOS installed on LANA 1 
    (SignOn) 
            	LAT0001S: 	DECLAT Version 1.0.31   (SignOn) 
            	LAT0002S: 	Copyright (c) 1995,1997 Digital Equipment
    Corporation  (SignOn) 
            	IOCB0003N:	LAT IOCB Interface Loaded.  
            	LMAP0012N:	LAT SCB (INT 6A) Interface Loaded.  
            	LAT0006S: 	DECLAT installed successfully.  (SignOn) 
            	CORE0003N:	PATHWORKS Directory:  PCSA=C:\PW32  
            	LRQL0200S:	PATHWORKS LICENSING   (SignOn) 
    ********>>  LRQL0200S:	(LANMAN) Client License Requester (DLL)
    Version 1.0.6  (SignOn) 
            	LRQL0201S:	Copyright (C) 1993, 1994, 1995 by Digital
    Equipment Corporation.  All Rights Reserved.  (SignOn) 
            	DNP0210N: 	DECnet adjacency up, node 1.918  
            	LRQL0091E:	DECLICL.VXD is not responding.  Protected
    Mode Licensing can not function without this program.  (Error)  
            	PNLT0001S:	DEC LAN Manager License Transponder
    (PNLT32.EXE)  Version V7.0.061    (SignOn) 
            	PNLT0002S:	Copyright (c) 1993-1997 Digital Equipment
    Corporation  (SignOn) 
            	PNLR0001S:	DEC LAN Manager License Requester
    (PNLR32.EXE)  Version V7.0.062    (SignOn) 
            	PNLR0002S:	Copyright (c) 1993-1997 Digital Equipment
    Corporation  (SignOn) 
            	PNLR0045E:	NetBIOS Name Claim failed on LANA 0. The
    name "OTC114         L" is already in the local name table.  (Error)  
            	PNLR0045E:	NetBIOS Name Claim failed on LANA 1. The
    name "OTC114         L" is already in the local name table.  (Error)  
            	PNLR0045E:	NetBIOS Name Claim failed on LANA 7. The
    name "OTC114         L" is already in the local name table.  (Error)  
            	PNLR0060E:	The license server "VAX2" is not available
    to validate your license.  (Error)  
            	PNLR0060E:	The license server "VAX2" is not available
    to validate your license.  (Error)  
            	PNLR0003N:	Loading license for "DEC-PWLMDOSCC06.00"
    from server "VAX2", group "default"  
            	PNLR0003N:	Loading license for "DEC-PWXXWINAT07.00"
    from server "VAX2", group "default"  
            	PNLR0056W:	License server "VAX2" is not reachable. 
    (Warning)
    10:34:09	PWIO0001S:	IOCB/DSCB Interface Library (PWIOCB32) 
    Version 1.0.011  Loaded Successfully.  (SignOn) 
    10:34:09	TNET0001S:	pwtelnt (pwtelnt)  Version V7.0.007 
    Loaded.  (SignOn) 
    10:34:10	CTRM0001S:	pwcterm (pwcterm)  Version V7.0.007 
    PWCTERM/WinSock load failed. Error = -2  (SignOn) 
    10:34:10	TAL0001S: 	Terminal Access Library [32-bit] (DECTAL) 
    Version 1.0.012  Loaded Successfully.  (SignOn) 
    10:34:10	LAT0010N: 	LAT connecting to VAX  
    10:34:10	LAT0011N: 	LAT successfully connected to VAX  
    11:09:26	TAL0002N: 	DECTAL.DLL Unloaded Successfully.  
    11:09:26	TNET0002N:	PWTELNT Unloading  
    11:09:26	CTRM0002N:	CTERM Unloading  
    11:09:27	PWIO0002N:	PWIOCB32.DLL Unloaded Successfully.  
    
T.RTitleUserPersonal
Name
DateLines
230.1JAMIN::WASSERJohn A. WasserThu Apr 17 1997 11:2919
> Has anyone heard of a Win95/PW 1.0a to PW32 upgrade in which the client
> simply can NOT get rid of the old 1.0a license requester?

	Yes!

	When you install PATHWORKS V6.0 for DOS and Windows on Windows
	for Workgroup V3.11 it uses the Protected Mode licenseing code
	including DECLICL.VXD (the License Transponder)

	If you upgrade WfW to Windows 95, Microsoft MERGES all of
	the installed VXDs into one big one called VMM32.VXD.  I
	think it does that to reduce startup time.

	Apparently it will then load every VXD in that file even if
	the VXD is no longer "installed".

	I'm not sure but I think the solution is to re-install
	Windows 95 over the existing Windows 95.  I expect that
	this will clean up the VMM32.VXD file.
230.2thanxVMSNET::DMCFARLANDstill TurboMom[tm]...Tue Apr 22 1997 11:184
    thanx!  this explains it as well as anything else could...
    
    diane