[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

164.0. "license debug version" by KAOFS::M_VALLEE (csc hull canada) Fri Mar 14 1997 10:18

    Does PNLT32.EXE and PNLR32.EXE replace the instlicl.dll and declicl.vxd
    if so is there debug version of the above new components for
    troubleshooting. Is there a white paper describing their behavior since
    it seems to a changed from the v6 kit components?
T.RTitleUserPersonal
Name		DateLines
164.1JAMIN::WASSERJohn A. WasserFri Mar 14 1997 15:0050
> Does PNLT32.EXE and PNLR32.EXE replace the instlicl.dll and declicl.vxd

	Yes.  

	PNLT32.EXE (PATHWORKS NetBIOS License Transponder) does the
	same job as DECLICL.VXD.  For Windows NT it uses the help of
	PNLSRV32.EXE (a Windows NT "service") to get it started at
	Windows NT startup time.

	PNLR32.EXE (PATHWORKS NetBIOS License Requester) does the
	same job as INSTLICL.DLL+INSTLICL.EXE.

> if so is there debug version of the above new components for
> troubleshooting.

	Yes.  In the DEBUG tree for the platform of your choice.
	For example the W95 debug versions are in:

		\W95\DEBUG\Service\License\Lanman

	The created logs are PNLT.LOG, PNLR.LOG, PNLS.LOG and
	PNLC.LOG (for PNLCGF.EXE, the configuration program).

> Is there a white paper describing their behavior since it seems to 
> a changed from the v6 kit components?

	What aspect of the behavior do you want explained?  Here is
	a quick overview:

	Old bits:

		DECLICL.VXD is a Win16 virtual device driver that is
		loaded at Window startup time by being listed in the
		"[386enh] network=" line of System.ini.

		INSTLICL.DLL is a Win16 loadable device driver that 
		is run at Window startup time by being listed in 
		the "[boot] drivers=" line of System.ini.  It can
		also be run from the program INSTLICL.EXE.

	New bits:

		PNLT32.EXE is a Win32 application that doesn't
		put up any windows.  For Windows NT it is started
		by PNLSRV32.EXE which is registerd as a system service.
		For Windows 95 it is started from the registry entry
		"HKLM\Software\Microsoft\Windows\CurrentVersion\RunServices".

		PNLR32.EXE is a Win32 application.  It is normally 
		started by PNLT32.EXE but can be run manually.
164.2/?VMSNET::P_NUNEZSun Mar 16 1997 08:036
    John, 
    
    Are there any switches that one can utilize for troubleshooting when
    running PNLR32.EXE manually (ie, /SERVERS, /SHOW, etc)?
    
    Paul
164.3JAMIN::WASSERJohn A. WasserMon Mar 17 1997 10:057
> Are there any switches that one can utilize for troubleshooting when
> running PNLR32.EXE manually (ie, /SERVERS, /SHOW, etc)?
    
	No.  The new versions are based on the Windows 95 versions
	where these debug features were not implemented.  You can get 
	the information by running the debug version and reading the 
	debug log output.