Unable to import dll extension that relies on a second dll

[John M. Camara]

camara at home.com (John M. Camara) wrote in message news:<9eb7f931.0108150448.2f6da101 at posting.google.com>...
> "Alex Martelli" <aleaxit at yahoo.com> wrote in message news:<9ldb8801jhq at enews3.newsguy.com>...
> > "John M. Camara" <camara at home.com> wrote in message
> > news:9eb7f931.0108141939.319a2e58 at posting.google.com...
> > > I have not been able to create a Python extension in Windows
> > > that requires a call to a function in another dll.  In the
> > > simplified example below a function called foo in extension.dll
> > > calls bar a function in supporting.dll.  I used SWIG to wrap the
> > > functions in extension.dll and compiled both dlls in Borland C++
> > > Builder 5.  When I try to import the extension I get an import
> > > error stating that the module could not be found.
> > 
> > Where do the extensions DLL's live?  Depending on your version
> > of Windows (95 and 98 go one way, NT another, 2000 yet
> > another, &c) that may be the root of things.  If they're all on
> > the PATH or system directories, then it should work on all
> > Windows versions, otherwise it gets hairy.
> > 
> > 
> > Alex
> 
> I'm using Win NT 4 and the extensions exist in /winnt/system32 directory.

I found the problem.  The supporting dll needed another dll that was
missing from my system.