Conference jamin::pathworks32

    some reading through the release notes finds this section, perhaps it
    will answer your questions ...
    
    
    
    |
    |     A user who initiates an asynchronous connection may receive
    |     an error response from the remote node, because the 
    |     licensing request has not been automatically established
    |     after a dial-up connection has been made.
    |
    |     In this case the user can run PNLR32.EXE manually to
    |     acquire a license and connect successfully.  
    |
    |     After a week the user will receive a PNLR0060 warning that 
    |     the license has not been validated for a while.  To dismiss
    |     this warning condition, the user can restart the timer for
    |     the error by running PNLR32.EXE again after the remote
    |     connection has been made.  
    |
    |     On the Windows 95 operating system, PNLR32.EXE is found in 
    |     \Windows\System.
    |
    |     On the Windows NT operating system, PNLR32.EXE is found in  
    |     \Windows\System32.
    
    
                               

Hi, 

yes, you where right, I should have found it...

but with this explanation in the release notes there comes
up another question:

The pnlr32.exe requests only a licenses (I hope I'm not wrong)
if the client license is installed.
So the PC always tries at startup to request a license, - can't get one
and then I can use the pnlr32.exe.

With the old PW WIn95 I could remove the instlic.dll (from system.ini) to 
prevent the PC to request a license at startup. (the customer has 
not to wait for the license requester timeout)

Is this possible with the new PW32 ?

thanks,
Robert 
[Posted by WWW Notes gateway]

> The pnlr32.exe requests only a licenses (I hope I'm not wrong) if the 
> client license is installed.  So the PC always tries at startup to request 
> a license, - can't get one and then I can use the pnlr32.exe.

	Running the licensing components at startup time is usualy only
	a problem until you have acquired your licenses.  After you have
	acquired licneses, PNLR32 will run at startup time, fail to connect 
	to the License Server, load the existing licenses into the
	License Transponder and exit, usualy within 10 seconds.

	You can run the licensing components without installing them
	by running PNLT32.EXE (the License Transponder) first and then
	running PNLR32.EXE (the License Requester).  They are both
	just Win32 applications.

    John,
    
    Does PNLR32 also obtain a NetWare license, or is there a different
    executable for that?  Also, for both types of NetWare request (I see
    that there are three choices when installing licensing; one LAN Manager
    and two NetWare)?
    
    -Steven
    

> Does PNLR32 also obtain a NetWare license, or is there a different
> executable for that?

	PNLR32.EXE will not obtain NetWare licenses.  It looks at the
	two letters after "DEC-PW" and will ignore the setting if it
	does not match "LM" or "XX".  In the same way,  PILR32M.EXE 
	and PILR32N.EXE will not obtain LAN Manager licenses.  It looks 
	at the two letters after "DEC-PW" and will ignore the setting 
	if it does not match "NW" or "XX".  

	For licenses that are not NOS-specific (like PWXXWINAT07.00)
	you can use either LAN Manager or NetWare or both.  If
	you use both you will be assigning two licenses of the 
	same kind to that machine.

> Also, for both types of NetWare request (I see that there are three 
> choices when installing licensing; one LAN Manager and two NetWare)?
    
	For Windows 95 use PILR32M.EXE for Microsoft's NetWare Client 
	or PILR32N.EXE for Novell's NetWare Client.  The PATHWORKS 32
	setup program will pick the right one for your current
	installation.

	V7.0 does not support licensing for Novell's NetWare Client on
	Windows NT.  V7.0a will use PILR32M.EXE for Novell's client 
	(Novell uses Microsoft's IPX stack).

    PNLR32.exe = LAN Manager license requestor
    PILR32N.exe = NetWare license requestor
    
    are these names supposed to be acronyms for something?  :-)

PNLR32.EXE  = LAN Manager license requestor
PILR32M.EXE = NetWare license requestor for Microsoft IPX
PILR32N.EXE = NetWare license requestor for Novell IPX
    
> are these names supposed to be acronyms for something?  :-)

	PNLR32:	PATHWORKS NetBIOS License Requester for Win32
	PILR32: PATHWORKS IPX License Requester for Win32

    Doh!  Thanks - I was thinking in terms of LAN Manager/NetWare rather
    than NetBIOS/IPX  -- hence the "I" was really confusing me :-)