Conference jamin::pathworks32

> Any idea how long it might take for a new FPA kit (just the license
> bits and the appropriate oemsetup.inf file) to be produced?

	I would expect a new FPA kit within a few weeks after FCS of 
	DIGITAL PATHWORKS 32 V7.0.  There are currently some showstopper
	problems associated with Licensing that should be resolved before
	we ship the bits to anyone.

	For now the best solution is to continue to ship the V4.1b
	bits with the modified install.

>	I would expect a new FPA kit within a few weeks after FCS of 
>	DIGITAL PATHWORKS 32 V7.0. 

Can I hold you to that, John?  :-)

re: ...

John should have learned by now that the correct answer to this kind of 
question is the tried and true, "Soon!".

The other John

Any news on this kit?

Will it be submitted to TIMA so that it can be distributed in the same manner
as the old FPA kit?

-Linda

Yes it will be.

Jeff

today, if someone has a new wnt 4.0 client, and gets a new designated
access license, what would they put on the client in order to request the
license?

would they have to install the whole pathworks32 product, and remove everything
but the license agent?

or will the windows nt 3.51-to-wnt4.0 license agent 'unsupported' kit work 
with the new licenses?

> or will the windows nt 3.51-to-wnt4.0 license agent 'unsupported' kit work 
> with the new licenses?

	The new "Designated Access" license (DEC-PWLMXXXFP05.00) 
	looks exactly like the old "FPA" license (DEC-PWLMXXXFP05.00)
	so the older software does not even notice a difference.

> would they have to install the whole pathworks32 product, and remove everything
> but the license agent?

	They could do a "Custom Install" and only select Licensing.

    ...if they spent $99 for PW32.  If they don't want to do that, they
    need a new FPA kit, hence this note :-)
    

DOWNING_L asked:
>>> would they have to install the whole pathworks32 product, and remove
>>> everything but the license agent?

WASSER replied:
>> They could do a "Custom Install" and only select Licensing.

S_VORE commented:
> ...if they spent $99 for PW32.  If they don't want to do that, they
> need a new FPA kit, hence this note :-)

	They don't need a new FPA kit to use FPA (now Designated Access)
	licenses...  The two kits already available will work just fine
	for that.  

	If they have PATHWORKS for DOS and Windows CCS licenses and want 
	to switch to Windows NT (without PATHWORKS client software) they
	can either patch the PWLICLM.EXE in the FPA kit or wait for
	the new kit.

	To find the current FPA kit(s):

		http://www.service.digital.com:8031/
			?categories=All_Databases&query_string=FPA

    NO, because the current kits are UNSUPPORTED -- we've been through this
    over & over & over & over.  We have been PROMISED a new FPA kit which
    will be SUPPORTED and include the new license bits, hence this note.
    

and ... an FPA kit is comming.

Jeff

> NO, because the current kits are UNSUPPORTED -- we've been through this
> over & over & over & over.  We have been PROMISED a new FPA kit which
> will be SUPPORTED and include the new license bits, hence this note.
    
	Sorry about that.  The original intent got lost in the mists
	of time.  For a SUPPORTED Windows NT 4.0 solution there are 
	currently a limited set of choices:

		1) Switch to FPS (now "PC Concurrent") licenses

		2) Sell them the PATHWORKS 32 CD-ROM and have them
		   install only the licensing bits.  (Is the CD-ROM
		   alone available cheaper than the "Media and Doc Kit"?)
		
		3) Wait for the new FPA kit to get through the DIGITAL
		   release process.

	I am working on the installation aspects of the new kit and
	things are going well.  It appears to install and work on
	NT 3.51 just as well as NT 4.0 and Windows 95.

    >	I am working on the installation aspects of the new kit and
    >	things are going well.  It appears to install and work on
    >	NT 3.51 just as well as NT 4.0 and Windows 95.
    
    Thank you -- that's what we were looking for.
    
    We now return you to your originaly scheduled notesfile.
    

Re .11

Methinks Mickey had too much Dew today.  ;-)

#Gary

    Well Gary, when the engineer that (we believe) is putting together a
    new kit all of a sudden says things like "They [customers] don't need 
    a new FPA kit" and "they [customers] can ... patch [their software]"
    then there's a problem somewhere.

over a month later... any progress?

also, will the kit include a license requestor for NT 3.x that will 
allow complete specification of the license to be requested?  The one 
that existed before would only allow
	o FPA
	o CCS
and when selecting CCS, it asked for DEC-PWLMWNTCC04.01.  We'd prefer 
that the PW32-style license requestor (where the user can specify 
_exactly_ the license they need) work on both NT4 and nT3.x if 
possible.

> over a month later... any progress?

	Good progress.  The PATHWORKS Licensing kit is almost
	ready to go.  Shouldn't be much more than another month...
	It would have been sooner but I was asked to provide a
	work-around to the 100% CPU Utilization problem for
	inclusion in the TIMA and Licensing kits.

> also, will the kit include a license requestor for NT 3.x that will 
> allow complete specification of the license to be requested?

	The PATHWORKS 32 licensing pieces worked just fine on
	Windows NT 3.51.  My thanks to Dave Goble for doing the
	testing.  

	We won't be providing support for NT 3.1 or NT 3.5 but 
	will have full support for NT 3.51 using the new 
	PATHWORKS 32 implementation.  This will include the 
	NetWare licensing pieces.

> The one that existed before would only allow
>       o FPA
>       o CCS
> and when selecting CCS, it asked for DEC-PWLMWNTCC04.01.

	All of the people who designed that implementation are
	long gone.

> We'd prefer that the PW32-style license requestor (where the user 
> can specify _exactly_ the license they need) work on both NT4 and 
> NT3.x if possible.

	You've got it.

Bravo, John.  Now, let's get it out the door :-)

Hello John(s)?  You WERE joking about "another month", right?  We had 
gotten word that it was supposed to ship last friday but still have 
seen nothing - not even a "please test this kit before we ship" kit 
(hint hint). 

A pointer for internal folks has been placed on the internal PATHWORKS home page
at

		http://prodmgt.lkg.dec.com/

The .ZIP file, again for internal access only, is now located at 

		\\JAMIN\PW32

		   -or-

		JAMIN::PW32:

The SSB kit was submitted last week and we are still working the to make these
bits available via TIMA and CompuServe.

Sooooo, there is now internal access to the bits but no direct external access
to them, yet.

John

Thanks.

"shipped" -- see 314.*


             <<< JAMIN::USER2:[NOTES$LIBRARY]PATHWORKS32.NOTE;1 >>>
                           -< Digital PATHWORKS 32 >-
================================================================================
Note: 314.6        Needs Reflection over Telnet & PW licensing on     6 of 7
DELNI::GORCZYCA "PATHWORKS Prod/Bus Mgmt"           14 lines  28-MAY-1997 13:07
                          -< Available over ftp... >-
--------------------------------------------------------------------------------
re: availability

The TIMA kit was loaded on Friday.

The kit is available (publically) over the net at:

        ftp://ftp.service.digital.com/public/windows/pc/v6.22/pathworks/6.0

You should read         pwlic14_eo1.CVRLET_TXT

You should use          pwlic14_eo1.exe


John