LoadLibrary is failing

[Art Araya]

Three users of my shareware product, FolderMatch, are receiving the following error when attempting to load my Powerbasic dll into memory using the LoadLibrary API call:

"A device attached to the system is not functioning"

They are all running the program on laptops. This seems to be the only commonality. None of my other users ever experience this problem.

I searched the MSDN Knowledge Base but it was not useful.

Any ideas as to what is causing this error?

Thanks

[Scott Turchin]

Assuming it works on all other programs then I would ask:

Are these 3 laptops created from an image (ie ghost)?.

Are there shortcuts not setting a "working directory"?

If your DLL is not in the path, you can expect that problem, assuming again that it works on all other PC's..


Scott



------------------
Scott
mailto:[email protected][email protected]</A>
MCSE, MCP+Internet

[Lance Edmonds]

The first thing is to check the "dependencies" of your app... Just run your app through the DEPENDS.EXE utility - but you'll need to do it on the laptops that are giving you trouble.

DEPENDS will tell you if one of the DLL's your app relies on has a problem (missing DLL or a missing exported function, etc), or if any of the dependent DLL's has a dependency problem... ie, DEPENDS does recursive analysis.

I find DEPENDS.EXE to be very handy. You can get it from our site: http://www.powerbasic.com/files/pub/.../depends10.zip



------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

[Art Araya]

Thanks Lance. I've got a very helpful user working with me on this problem. I believe that he'll be willing to run this on his laptop.

[QUOTE]Originally posted by Lance Edmonds:
[B]The first thing is to check the "dependencies" of your app... Just run your app through the DEPENDS.EXE utility - but you'll need to do it on the laptops that are giving you trouble.




------------------

[Art Araya]

I discovered the problem. My DLL was referencing a Win API function called GetDiskFreeSpaceEx. This function does not exist in the retail version of Win95. When the DLL is loaded into memory on a Win95 (retail version) the error mentioned in my first email occurs.

I resolved the problem by removing the routine which references this API call from my PowerBasic DLL and putting it into my VB executable.



------------------