Windows XP Pro SP3

Got a "hot fix" for a piece of commercial software which consisted of a
replacement for a DLL. For the sake of discussion, let's call it
"that.dll."

The properties of the original showed a version of 10.0.0.14 and a
"Digital Signature" date of March 14, 2011. The properties of the new
one showed a version of 10.0.0.15 and a Digital Signature date of July
5, 2011.

With nobody using the DLL, I changed the name of the original to
"that.dll.old", then copied the new one into the application's
directory.

Checking the properties, it now had a version of 10.0.0.14, but the
Digital Signature date was still July 5.

I repeated the process a couple of times to be sure I wasn't
accidentally copying things in the wrong direction, but the results were
always the same. The new DLL in its download directory still showed the
correct version of 10.0.0.15.

What could explain this apparent change of versions?

--
Bert Hyman St. Paul, MN (E-Mail Removed)

On 07 Jul 2011 16:15:49 GMT, Bert Hyman <(E-Mail Removed)> wrote:

>Windows XP Pro SP3
>
>Got a "hot fix" for a piece of commercial software which consisted of a
>replacement for a DLL. For the sake of discussion, let's call it
>"that.dll."
>
>The properties of the original showed a version of 10.0.0.14 and a
>"Digital Signature" date of March 14, 2011. The properties of the new
>one showed a version of 10.0.0.15 and a Digital Signature date of July
>5, 2011.
>
>With nobody using the DLL, I changed the name of the original to
>"that.dll.old", then copied the new one into the application's
>directory.
>
>Checking the properties, it now had a version of 10.0.0.14, but the
>Digital Signature date was still July 5.
>
>I repeated the process a couple of times to be sure I wasn't
>accidentally copying things in the wrong direction, but the results were
>always the same. The new DLL in its download directory still showed the
>correct version of 10.0.0.15.
>
>What could explain this apparent change of versions?

The original probably has a copy in the C:\WINDOWS\system32\dllcache folder.
When Windows detects that the file has changed, it replaces it from the dllcache folder.

Google Hiren's BootCD, burn it and boot to Mini Windows. Replace the one in the dllcache folder
with the new one.

Unk

In news:(E-Mail Removed) Unk <(E-Mail Removed)>
wrote:

> On 07 Jul 2011 16:15:49 GMT, Bert Hyman <(E-Mail Removed)> wrote:
>>
>>What could explain this apparent change of versions?
>
> The original probably has a copy in the C:\WINDOWS\system32\dllcache
> folder. When Windows detects that the file has changed, it replaces it
> from the dllcache folder.

Never occurred to me that a third-party DLL would end up in the dll
cache; I'd assumed it was Windows' personal property.

Thanks.

--
Bert Hyman St. Paul, MN (E-Mail Removed)

On 10 Jul 2011 14:32:41 GMT, Bert Hyman <(E-Mail Removed)> wrote:

>In news:(E-Mail Removed) Unk <(E-Mail Removed)>
>wrote:
>
>> On 07 Jul 2011 16:15:49 GMT, Bert Hyman <(E-Mail Removed)> wrote:
>>>
>>>What could explain this apparent change of versions?
>>
>> The original probably has a copy in the C:\WINDOWS\system32\dllcache
>> folder. When Windows detects that the file has changed, it replaces it
>> from the dllcache folder.
>
>Never occurred to me that a third-party DLL would end up in the dll
>cache; I'd assumed it was Windows' personal property.
>
>Thanks.

You're welcome.