For first step I'd try to get it manually via ProcessExplorer or similar tools checking when loaded by vfp process. Then look in which log/with which query the info can be found.
>yes, I've looked in the virtual folder. nothing.
>
>I've looked in the WinSxS folder too, and while yes, there are several wininet.dll files. they all have the same version as the one in system32 folder.
>The closest clue I've found is that there are 2 WininetPlugin.dll files in the WinSxS folder. these have a version of 6.3.9600.16384. the last part of this version matches the version returned by: AGETFILEVERSION() (which is 11.00.9600.16384). but the 1st major version numbers are way off.
>
>so befuddled we remain. either FoxPro is getting incorrect version info through all the semantics of windows redirection. or it's not reporting the correct version of the file it's finding. because I can't find whichever dll AGETFILEVERSION() is finding. I have hidden folders and files turned off in windows.
>
>any other ideas how to get the correct installed version of wininet.dll in FoxPro? Apparently FoxPro is using the latest wininet.dll because the ftp bug is gone. (although there still seems another intermittent bug with ftpPutFile(), where now and then parts of files are getting dropped when uploaded.
>
>
>>Since Vista some folders are virtualized/protected/hidden by default.
>>
>>Do you see any differences if you run your app as an administrator, and also run Windows Explorer as an administrator?
>>
>>Also, for Windows 7 and 8 the Side-by-Side folder may come into play:
http://www.thewindowsclub.com/winsxs-folder-windows-7-8>>
>>>Thanks for verifying that you get the same difference as I do.
>>>I just now copied c:\windows\syswow64\wininet.dll to c:\temp\ folder.
>>>then did:
>>>
? AGETFILEVERSION(la1, "c:\temp\wininet.dll"), la1(11)
>>>and yay!! it returns the same version as win explorer.
>>>
>>>... so now the question is, what and where is Fox finding wininet.dll. I've searched the entire pc, and can't find any with the 16384 version. what a mystery huh??
>>>
>>>I don't suppose it's possible to force a different wininet.dll with my vfp app? that's probably not a good idea if I could. I need to make sure they aren't using the buggy one from MS.
>>>
>>>btw, what does TTF mean?
>>>
>>>
>>>>TTF:
>>>>
>>>>?FULLPATH('wininet.dll',1)
>>>>*c:\windows\system32\wininet.dll"
>>>>>>>>
>>>>I prefer [ALT][ENTER] :) but it returns
>>>>
>>>>11.0.9600.16521
>>>>
>>>>possibly the old fox is not able to read information available to Win8.1 ....
>>>>
>>>>Or there is some hidden place. Do you have something more intelligent to search the comp? Hidden and system stuff, I have no idea where to include in search. But default was off before Win 8.1 ....
>>>>
>>>>Lutz
>>>>
>>>>>so what does win explorer return? (right click > properties > details tab)
>>>>>>
>>>>>>?FULLPATH('wininet.dll')
>>>>>>*E:\SE\FOXPRO\WININET.DLL
>>>>>>AGETFILEVERSION(la1, "wininet.dll")
>>>>>>?la1(11)
>>>>>>*11.00.9600.16384
>>>>>>AGETFILEVERSION(la1, "E:\SE\FOXPRO\WININET.DLL")
>>>>>>?la1(11)
>>>>>>*11.00.9600.16384
>>>>>>AGETFILEVERSION(la1, "c:\windows\system32\wininet.dll")
>>>>>>?la1(11)
>>>>>>*11.00.9600.16384
>>>>>>>>>>>>
>>>>>>Edit:
>>>>>>OS is Win 8.1
>>>>>>
>>>>>>Lutz
>>>>>>>returns: c:\windows\system32\wininet.dll
>>>>>>>so why the different version reported by vfp I wonder...? curious if anyone else with win8.1 having same result.
>>>>>>>
