Conference noted::pwv50ift

4292.0. "Directory name not 8.3 convention created from WIN95" by GIDDAY::CRISOLOGO () Thu May 15 1997 21:53

	Hi,

	I've read note 2803 which I believe is related to my customer 
	situation. He create subdirectories from Win95 as follows

	nmt board report
	templates

	From VMS via DIR command they appear as follows

	NMT__20BOARD__20REPORT.DIR;1
	TEMPLATES.DIR;1

	Now, customer wants to change permission of the files from ADMIN/PATH
	and he could not see the subdirectories as they don't adhere to the
	8.3 format. What he did was give permission for the full directory
	tree of the share which security wise is not safe.

	He is running 5.0D of server and Win95 and PW Win95. 

	What is our current standing on this? Can it be IPMTd or just explain
	to the customer that's how it is, he must adhere to 8.3 format. 

	Thanks,
	Arlene
	CSC-Sydney

    Arlene,
    
    I doubt you'll see the ADMIN/PATHWORKS UI limitation regarding 8.3
    filenames go away.  But only because there are alternatives - namely,
    the $ NET ACCESS command:
    
    	$ NET ACCESS dev:[dirpath.NMT__20BOARD__20REPORT]   ! to view perms
    
    	$ NET HELP ACCESS ! for options like /ADD, /GRANT, /CHANGE, etc...
    
    Optionally, you can temporarily rename the directory file to 8.3, use
    ADMIN UI to set permissions, and then rename the directory file back to
    its original name...
    
    Perhaps you can use Windows NT Server (tools) to set permissions????
    
    Paul

You have the possibility from VMS to make the good acl on the 
directory that is more than 8,3 caracteres by

$ set file/acl/like=less_than_8_3_caractere.dir disk:[directory...]*.dir

Michel