Very Strange FileFindNextFile behavior found

[ISI360]

Hi!

I have found a very very strange behavior with FileFindNextFile and AutoIt v. 3.3.14.5:

At first my example script (adapted from help file):

;test.au3

#include <MsgBoxConstants.au3>

Example()

Func Example()
    ; Assign a Local variable the search handle of all files in the current directory.
    Local $hSearch = FileFindFirstFile("C:\Some Tests\Profildaten Backup\Desktop\Yi\uskin\Skins\Default\*.*")

    ; Check if the search was successful, if not display a message and return False.
    If $hSearch = -1 Then
        MsgBox($MB_SYSTEMMODAL, "", "Error: No files/directories matched the search pattern.")
        Return False
    EndIf

    ; Assign a Local variable the empty string which will contain the files names found.
    Local $sFileName = "", $iResult = 0

    While 1
        $sFileName = FileFindNextFile($hSearch)
        ; If there is no more file matching the search.
        If @error Then ExitLoop

        ; Display the file name.
        ConsoleWrite($sFileName&@crlf)

    WEnd

    ; Close the search handle.
    FileClose($hSearch)
EndFunc   ;==>Example

 

You can see, the script should output all Files in a path. Should be simple, right?
The ConsoleWrite Output looks like this:

-.bmp
bc_new.bmp
bf_new2.bmp

So all fine!

Sooo....now i put the exact same folder on a network drive. Let it be drive S: for example (effect is the same as with \\SERVERNAME\SHARE....)
Then the output looks like this:
 

-.bmp
.
..
bc_new.bmp
bf_new2.bmp

Where doese "." and ".." come from?! I really have no idea what is happening here ^^
Could this be an AutoIt bug? (Or just my stupid Win10 -.-)

Thanks for your help in advance!!

PS: I attached you a .zip with the testfiles. So you have the same enviroment for testings.
 

 

Files.zip

Edited April 18, 2018 by ISI360

[ISI360]

I just want you to know that i think it´s really my windows 10 pc what´s going crazy here... (Or has somebody testes this and has the same problems like me?)
I tested it today on my work pc (also win 10) and it is working fine here! (And other win7 machines too)

So i think it is time to finally reinstall windows new on my home computer

Edited April 19, 2018 by ISI360

[Simpel]

Hi.

Working with php on a server you'll find . and .. too. I guess it's not unusual at all.

Conrad

[UEZ]

@ISI360: on C drive I get the same results. When I put the files from the Zip file to my network drive with the drive letter L I get the same result but the order is different but "." or ".." chars.

Output for L drive:

bf_new2.bmp
-.bmp
bc_new.bmp

 

Tested on Win10 x64 and AutoIt v3.3.14.5 / 3.3.15.1.

[Melba23]

ISI360,

I once ran into a user with what seems a very similar problem - see this post and subsequent - which appeared to be caused by the fact that the server was using a different OS and transferring the FileFindFolder return to Windows meant that we got the additional . and .. items. Could this be the case here?

M23

[Bowmore]

A single dot is the current directory
a double dot is the parent directory

If you do a Dir from the command prompt you will see that these are always the first 2 listed. 
They are mostly used for specifying paths relative to the current directory.

[ISI360]

Thanks for the infos guys!

Yeah the strange thing is i never had this before on any system. Its the first time for me i got "." or ".." returned by FileFindNextFile.

And @Melba23 the target system (server) in this case is a Windows Server 2016...so they SHOULD be making the same...in theory ^^

But meanwhile i have accepted this as a "strange thing". And it can easily filtered by parsing the results.
Maybe its gone when i reinstall my pc.

Edited April 20, 2018 by ISI360