🚀 go-pugleaf

"Denville Longhurst" <denville@metco.co.uk> wrote in message 
news:4818202a$1@newsgroups.borland.com...

> The function is absolutely fundamental, the support documentation
> states that it must be the first function called to get a handle to
> one or more embedded devices attached to the network.

Then it should be exported properly.  If it is not, then the DLL author 
likely goofed up when compiling it.

> I examined the .dll using a program called WinHex which
> provides a hex and an ascii dump of any file.

That is not the best way to examine executables.  I suggest you use an 
actual PE viewing tool instead.  That will show you the actual exports table 
(and imports, resources, etc).

> All of the functions within the dll are listed twice

Which means nothing without knowing what kind of tables they are actually 
listed in.

> once in what is obviously the export list, and again later I
> presume at the implementation

Implementation names are not stored anywhere in the DLL.  They are resolved 
to memory addresses by the compiler.  The exports table is a look-up table 
that maps the exported name to the cooreponding address within the DLL.

> I think the dll supplied with this sdk must be broken, I just wanted to 
> check that MS hadn't added some new mechanism
> that I wasn't aware of.

Which DLL specifically are you actually trying to use?  Which function?  Is 
this a Microsoft DLL, or a third-party DLL?


Gambit