Hi,
just a tip from my experience with troubleshooting DLL problems under Windows:
there is a utility called "Dependency Walker" that helps both to show the module dependencies (and missing modules) and allows (in more recent versions) even to profile the startup phase of a module.
it is part of the Windows2000 Support Tools
and Windows XP Support Tools
(I think they are on the corresponding product CDs, but must be installed explicitly)
Peter
> -----Original Message-----
> From: Clift Norris [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 14, 2002 3:22 PM
> To: [EMAIL PROTECTED]
> Subject: RE: pythoncom not loaded
>
>
> GREAT! I'm glad to hear you got this mystery solved.
>
> Microsoft calls executables "modules". This could mean
> any DLL or EXE, not just a COM server. In fact, there
> is a Win32 API function named "GetModuleFileName" that can return
> the path to the "module" from which it is called.
> This of course doesn't help you now, but at least it might
> help clarify the "module not found" message.
>
> -Clift
>
>
