IE code download failure for dll and ActiveX control using INF and CAB

[grop01]

Is there a way to find out more about the cause
of the failure?
It used to work but not anymore.
It did that to me on two different computers.
The file other.dll doesn't get copied to C:\WINNT\system,
so myX.dll cannot be registered (since it depends on it).
See CAB, INF file and error log below...
Thanks!

-----------------
CAB FILE CREATION
-----------------
CabArc.exe n myX.cab other.dll myX.dll myX.inf

--------
INF file
--------
[Version]
; This section is required for compatibility on both Windows 95 and Windows NT.
Signature="$CHICAGO$"
AdvancedInf=2.0

[Add.Code]
other.dll=other.dll
myX.dll=myX.dll

[other.dll]
file-win32-x86=thiscab
FileVersion=1,0,0,1
DestDir=10
RegisterServer=no

[myX.dll]
file-win32-x86=thiscab
clsid={98B6686C-EF56-4FFF-ACBD-2BC5A853377D}
FileVersion=1,0,0,1
RegisterServer=yes

------------
IE Error log
------------
*** Code Download Log entry (02 Mar 2005 @ 14:34:52) ***
Code Download Error: (hr = 8007007e) The specified module could not be found.

Operation failed. Detailed Information:
CodeBase: file:///C:/Dev/myX/myX.cab
CLSID: {98B6686C-EF56-4FFF-ACBD-2BC5A853377D}
Extension:
Type:

LOG: Item other.dll being processed.
--- Detailed Error Log Follows ---
LOG: Download OnStopBinding called (hrStatus = 0 / hrResponseHdr = 0).
LOG: Item other.dll being processed.
LOG: Item myX.dll being processed.
LOG: URL Download Complete: hrStatus:0, hrOSB:1, hrResponseHdr:0, URLfile://C:\Dev\myX\myX.cab)
LOG: File C:\WINNT\Downloaded Program Files\myX.dll being registered.
ERR: Setup Failed Error Code: (hr) = 8007007e, installing: myX.dll to (null) destination code(0)
LOG: Reporting Code Download Completion: (hr:8007007e (FAILED), CLASSID: 98b6686c..., szCODEfile:///C:/Dev/myX/myX.cab), MainTypenull), MainExtnull))

 

[r1sto]

Hi grop01,

Dont know if you read this anymore but Ive had the
same problem for a while now and I havent found any
post out there solving this problem. Just solved it
so I thought would share...

Anyway, in my case this error message showed up when
I had forgot to include a dll that the main dll
(the dll or ocx causing the error) linked to.

Word up