[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::pwv50ift

Title:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:CPEEDY::KENNEDY
Created:Fri Dec 18 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4319
Total number of notes:18478

4288.0. "Windows 95 "for" loop cannot see long filenames in a PW share" by GIDDAY::MITROVSKI () Wed May 14 1997 05:04

Hi,

A customer of mine reported a strange behaveour on a Windows 95 client using a 

1. Created a file with a long name - LONGFILENAME.TXT in a PW share.

2. On a Windows 95 client,mapped a drive to the PW share (drive h:)

3. At the Windows 95 command prompt typed

        H:> for %f in (*.*) do echo %f

   The command is a for loop that goes through the list of files in the        

The problem is that it doesn't see the long filename. The same procedure perfor
Customer wants to use the "for" command in a batch file to manipulate the files
Can anyone explain this and maybe provide a solution.

Regards,
Marjan
CSC Sydney
T.RTitleUserPersonal
Name		DateLines
4288.1Does it work locally?VMSNET::P_NUNEZWed May 14 1997 10:167
    Marjan,
    
    Does it work for a long file name on a local hard drive?
    
    Could just be a DOS/COMMAND.COM limitation...
    
    Paul
4288.2GIDDAY::MITROVSKIWed May 14 1997 21:5022
Paul,

If the file with a long name is stored on the local hard disk or in a NT share 
it works fine.It must be a combination of how PW stores a file with a long name
and how Windows 95 "for" command reads it.Here is a list of all combinations I
have tried and their results:

		Operating	Location of the		"FOR" loop can
		  system	 long filename		 read the file

		Windows 95	local hard disk		      YES

		Windows 95	PW VMS share    	       NO

		Windows 95	Windows NT share	      YES

		Windows NT	Any of the above	      YES



Regards,
Marjan
4288.3IPMT TimeVMSNET::P_NUNEZThu May 15 1997 09:4912
    
    I'm convinced ;o).  If you can, you might put the server in debug mode:
    
    edit pwrk$lanman:lanman.ini
    [vmsserver]
    debug=yes
    debugsize=99999
    
    and see if you can see why or, better yet, get an IRIS trace - but in
    either case, it looks like IPMT is appropriate...
    
    Paul
4288.4CPEEDY::wells.lkg.dec.com::wellsPhil WellsFri May 16 1997 12:4810
The same command played from NT4.0 to PW5.0 does displays the lfns.

If w95's command.com's file searches ultimately results in smbsearch 
messages, smbsearch only support 8.3 names.  The client minimally 
needs to use t2find to find lfns.

If your trace show smbsearch SMBs then that is the problem and it is
a problem in the client.

Phil