On Mon, 2005-02-21 at 15:16, Paul Vriens wrote:
Hi (again),
I've applied OLE#75 and OLE#76 and now I've something that doesn't look right:
trace (without OLE75/OLE76 and with native stdole32.tlb):
000b:trace:ole:LoadTypeLib (L"C:\windows\system\stdole32.tlb",0xa9d0dc) 000b:trace:ole:LoadTypeLibEx (L"C:\windows\system\stdole32.tlb",0,0xa9d0dc) 000b:trace:ole:LoadTypeLibEx File L"C:\windows\system\stdole32.tlb" index 1 000b:trace:ole:ITypeLib2_Constructor_SLTG 0x7e8702b0, TLB length = 4240
trace (with OLE75/OLE76 and builtin stdole32.tlb):
000b:trace:ole:LoadTypeLib (L"stdole32.tlb",0x3dd0dc) 000b:trace:ole:LoadTypeLibEx (L"stdole32.tlb",0,0x3dd0dc) 000b:trace:ole:LoadTypeLibEx File L"stdole32.tlb" index 1 000b:trace:ole:TLB_ReadTypeLib not found, trying to load L"stdole32.tlb" as library 000b:trace:loaddll:load_dll Loaded module L"c:\windows\system\stdole32.tlb" : builtin 000b:trace:ole:ITypeLib2_Constructor_MSFT 0xe31180, TLB length = 4384
trace (with OLE75/OLE76 and native stdole32.tlb copied to \windows\system):
000b:trace:ole:LoadTypeLib (L"stdole32.tlb",0x80d0dc) 000b:trace:ole:LoadTypeLibEx (L"stdole32.tlb",0,0x80d0dc) 000b:trace:ole:LoadTypeLibEx File L"C:\windows\system\stdole32.tlb" index 1 000b:trace:ole:ITypeLib2_Constructor_SLTG 0x7e9602b0, TLB length = 4240
Why do we use _SLTG in the first and last trace and _MSFT in the second?
Cheers,
Paul.
I have 3 native stdole files:
[paul@penguin tools]$ ll std* -rw-rw-r-- 1 paul paul 16896 Feb 21 14:39 stdole2.tlb -rw-rw-r-- 1 paul paul 7168 Feb 17 19:57 stdole32.tlb -rw-rw-r-- 1 paul paul 5472 Feb 21 16:48 stdole.tlb
`strings` show:
[paul@penguin tools]$ strings stdole2.tlb | grep -e MSFT -e SLTG MSFT [paul@penguin tools]$ strings stdole32.tlb | grep -e MSFT -e SLTG SLTG [paul@penguin tools]$ strings stdole.tlb | grep -e MSFT -e SLTG SLTG
This explains the traces (a bit). But not why our stdole32.tlb has a MSFT signature.
Cheers,
Paul.