Erik Fløisbonn wrote: > > Heh, I see that I was lucky with the backslashes. > > "link /dump /exports msi.dll" gives the following output:
Did I say /exports? I see that I did. That was dumb. I meant to say /imports instead. However, "depends" does the same thing. > When I open the .dll in 'depends' (dependency walker), i get an error > message saying "Error: At least one module has an unresolved import > due to a missing export function in an implicitly dependent module." I > see the function called test, but I also get two red 'functions', with > function = "N/A" and entry point = "not bound". This is most probably > the two functions MsiEnumProducts and MsiEnumComponents that is called > in msi.c. I just noticed the name of your DLL. That's almost certainly the problem. You have called your DLL "msi.dll", but that's also the name of the system DLL that contains MsiEnumProducts and MsiEnumComponents! Change the name of your DLL to something like "msiwrapper.dll", and I'll bet the problem goes away. Do you have the system's msi.dll in \windows\system32? -- Tim Roberts, [EMAIL PROTECTED] Providenza & Boekelheide, Inc. _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
