MartyMacGyver
New Member
I've recently upgraded one machine from XP Pro to Vista Business 32-bit, and the other is a brand new laptop with Vista Home Premium x64. Both exhibit the following problem... or is it just me?
The setup:
On media you can write protect (i.e., a flash drive) make a copy of mfc71.dll (usually found in Windows\system32... other MFC DLLs seem to have the same effect but try this one if you have it).
Now, remove the media, write-protect it and re-insert it. Attempt to copy that DLL from the media to your desktop (NOT in \Windows or other highly protected areas). Attempt to read the properties page of the DLL as it sits on the media: doesn't work.
Can someone explain why one cannot copy or even read the properties of such DLLs? I can see if it's replacing something bad or such, but simple copying is disallowed if the DLL is on write-protected media. What's up with that? And how might one get that to work normally? I've never seen anything quite like it.
Why does this matter? Because it causes MAJOR problems when comparing backup media that uses an emulation layer to emulate a drive (e.g., TrueCrypt). In the example above it just doesn't work... in something like TrueCrypt (within a write-protected volume) it locks Explorer up quite thoroughly, requiring a reboot. I presume that's a failure of TrueCrypt but still, what the heck is Vista doing here?
The setup:
On media you can write protect (i.e., a flash drive) make a copy of mfc71.dll (usually found in Windows\system32... other MFC DLLs seem to have the same effect but try this one if you have it).
Now, remove the media, write-protect it and re-insert it. Attempt to copy that DLL from the media to your desktop (NOT in \Windows or other highly protected areas). Attempt to read the properties page of the DLL as it sits on the media: doesn't work.
Can someone explain why one cannot copy or even read the properties of such DLLs? I can see if it's replacing something bad or such, but simple copying is disallowed if the DLL is on write-protected media. What's up with that? And how might one get that to work normally? I've never seen anything quite like it.
Why does this matter? Because it causes MAJOR problems when comparing backup media that uses an emulation layer to emulate a drive (e.g., TrueCrypt). In the example above it just doesn't work... in something like TrueCrypt (within a write-protected volume) it locks Explorer up quite thoroughly, requiring a reboot. I presume that's a failure of TrueCrypt but still, what the heck is Vista doing here?
