Jeffrey Altman wrote:
> Christopher D. Clausen wrote:
> 
>> [EMAIL PROTECTED] C:\>filever "c:\Program 
>> Files\OpenAFS\Client\Program\afs_shl*"
>> --a-- W32i   DLL   -       1.4.200.0 shp    267,248 08-21-2006 
>> afs_shl_ext.dll
>> --a--    -   -   -               -   -  3,181,568 08-21-2006 
>> afs_shl_ext.pdb
>>
>> Should I have another dll there as well?
> 
> The MSI is placing the other DLL in OpenAFS\Common.  I will fix that
> but it is not the cause of the problem.
> 
> I'm debugging explorer.exe at the moment on my 64-bit system and
> I'm seeing some very weird behavior that appears to indicate that
> the code the compiler is generating may in some cases be bad.
> 
> This is going to take a bit of additional debugging to figure out
> why the TaLocale_EnumModule() function is being called with the
> wrong parameters.
> 
> Jeffrey Altman

This was one of those bugs that once you see what is going on you
wonder how in the world it ever worked.  The file name "afs_shl_ext.dll"
does not fit in 8.3 notation so when the module name was queried it
would get the short name abbreviation whatever that happened to be.
The end result is that the wrong module name was being loaded and that
module didn't exist.  Specifying the name explicitly solves the problem.
This will be fixed in a future release.

Jeffrey Altman

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to