Conference jamin::pathworks32

> 1) the license only requestor bits are 10MB big.
> 
> Is it really 10MB big when the other stuff fitted on to a couple of 
> floppys.

	Whoever created the download archive included everything that
	was on the CD-ROM.  This includes about 6MB of diskette images
	that are completely unnecessary.

> 2) when down loading them I now cant get the program to run

	Perhaps you made a mistake while downloading.  I used
	Netscape Navigator V3.01 and the executable unpacked
	fine when I used the required "/d" switch.
    
	What, exactly, is not working?

John -- you mean that the entire PW32 kit is online for free via the 
Internet?  You *have* mentioned this to John G, havn't you?  Or do 
you mean something entirely different?

He means All of the LICENSING kits, you know:

1 - OS/2
2 - Dos/Windows/wfwg
3 - Windows 95
4 - NT v4.0
5 - NT v3.51

Etc, and both LANMAN/NetWare where appropriate

Jeff

that's cool, thanks.

    Ok so as it is expected to be that bi I have copied the file to my NT
    client ran it with a -d and all worked OK. I have now copied it back to
    the directory on the DECUNIX v5.0g eco 2 server and it seems Ok.
    When trying to run the file from the dos box in the same dir I got
    
    "The system cannot execute the specified program"
    
    From explorer the message was 
    
    "Program not found box appearing and asking for the location of the
    program files."
    
    But I think its a PW UNIX type prob cos its works when expanding on the
    local disk and then copying it back to the server works OK.
    
    Trev UK CSC.

One of our customers tried unzipping the kit to a PATHWORKS share on an
OpenVMS server. Then he tried connecting a Windows 95 client to it to install
the bits.
He entered the path to the share in the "Copy manufacturer's files from:"
box, and got this error message:

	Select Device
	The specified location does not contain information about your hardware.


We found that if the contents of the \WIN95 directory are copied to the root of
the share, the installation is successful.

Linda,

Jennifer and Cindy both have elevations against the PW Server for 
this sort of problem -- don't believe this is a FPA 1.4 kit problem.

> One of our customers tried unzipping the kit to a PATHWORKS share on an
> OpenVMS server. Then he tried connecting a Windows 95 client to it to install
> the bits.
> He entered the path to the share in the "Copy manufacturer's files from:"
> box, and got this error message:
> 
> 	Select Device
> 	The specified location does not contain information about your hardware.

	If you look in the README.TXT file in the WIN95 directory (also copied
	in the main README.TXT file) you will see the instruction to:


		"Enter the path to the directory containing the PWLIC.INF
		file.

			- If installing from a CD this will be "d:\Win95"
			  where "d" is the drive letter of the CD drive.

			- If installing from diskettes, insert the diskette
			  labeled "PATHWORKS Licensing for Windos 95" into
			  the diskette drive and enter the drive name (usualy
			  "A:").

	I suspect that the user did not read this instruction and pointed the
	install NOT at the Win95 directory but at the root of the licensing kit.

	I copied the licensing kit to a directory two levels down in a file
	share and successfully installed it by UNC (\\server\service\directory\pwlic\win95)
	and by mapping to a drive letter (d:\directory\pwlic\win95).

 
Yes, he/we are following the directions.

Even if the 'browse' button is used to find the pwlic.inf file, the error still
occurs.

Are you testing files from the kit that actually got submitted to TIMA, or
files that existed before it was submitted?  

    I have seen this problem also. I pulled down the kit from the web.
    Unpacked the kit to my harddrive, no problem installing. Then I did the
    following:
    
    1) Create network share called \\jimws\junknew. Under VMS this
    corresponds to DKB200:[test].
    
    2) Copy the entire kit into a folder called PW14. VMS we now have
    DKB200:[test.pw14...]
    
    3) I then connect to the share and set the correct directory via Browse
    button so that the Copy manufacturer's files from: read G:\PW14\WIN95.
    
    4) Click ok, I get "The specified location does not contain information
    about your hardware.
    
    5) Now Under VMS I create a new share called \\jimws\pw14w95. This
    share points to DKB200:[test.pw14.win95]
    
    6) I then use browse button to connect to \\jimws\pw14w95 as G:
    
    7) #3now has copy manufacturer's files from: G:
    
    8) This installs fine. As long as the network share points directly to
    the win95 directory, it works. 
    
    9) I do not see this problem when I install WNT licensing bits.
    
    Your network share must point directly to the WIN95 directory to
    install. 
    
    jim fillers
    pathworks support
    csc atlanta

A CLD against the V5.x server has been filed on this issue (at least one),
it appears to an issue between the SMB dialect being used between
the W95 system and the PATHWORKS v5.x server. The work around it to
place drivers in the root of the share as suggested.

Jeff

> Are you testing files from the kit that actually got submitted to TIMA, or
> files that existed before it was submitted?  

	I downloaded the same kit you did by following the pointer you
	provided.  This is almost definitely a problem in the PATHWORKS 
	for OpenVMS server.

re:12, 11, 7

Ok. Thanks everybody.

Sorry for being so stubborn.