Cannot See files saved with 32-bit programs on Windows 7 64-bit
Posted on 2011-10-26
I have seen this in a couple of different applications now, you save a file on your Windows 7 64-bit machine and then go into Explorer of the command prompt and the file does not appear. However, if you open the 32-bit application, you can see the file - it appears with a lock icon on it as well. This happens with Putty.exe and Crystal Reports (version for MAS 500).
Steps to reproduce using Putty.
1) download Putty.exe (I have release 0.6)
2) Unpack and put it in a folder c:\program files (x86)\Putty
3) Launch Putty.exe and connect to something - like a Cisco Switch
4) Once connected Click the top left corner of window and select "Change Settings"
5) Select Session and under that Logging
6) Sellect All session output and browse to the same folder as in #2 above. Call the file MYOUTPUT.Log.
7) Save some output (like show running-config)
Examine the file in Windows (If you can!!)
9) open Windows Explorer. You will NOT see the file in the specfied folder.
10) Open a Command Prompt (even using Run as Administrator) and CD to the folder.
11) Do a DIR *.LOG - you won't see the file
12) Do an ATTRIB *.Log - you won't see the file
Look in PUTTY again
13) Open Putty
14) Click on Session and Logging (no need to connect to anything at this point)
15) Click Browse - and Whoa! There is the MYOUTPUT.LOG plain as day. However, it differs from other files in the folder in that it has a lock icon in the bottom left.
16) Examine the properties on the file and you will see it is identical to all other files in the folder EXCEPT that it has the odd lock icon on the bottom left.
So, what happened? It appears that is some type of attribute set on the file that only the 32-bit programs understand. I have also done this with a 32-bit version of Crystal Reports. Oddly, the Putty.exe can see the files created by Crystal, but nothing else can.
I would surmise that these programs are using an API for Explorer that has been replaced by something newer. But, what attribute is being set and can I unset it to correct the visibility within the native Windows 7 64-bit OS?