Registering IO.dll .... Wierd things, maybe you can explain!

[INF3RN0666]

Thanks in advance for helping me out.

I got IO.DLL from geekshidout.com and I was trying to reference it in VB6 but it says "Cannot add reference to the specified file.". So I thought that registering the DLL might fix the problem. Thus, I type in the following into the command prompt: "regsvr32 io.dll" but it says "io.dll was loaded, but the DLLRegisterServer entrypoint was not found. This file cannot be registered".

This is funny actually because i got the file working last time on my old PC on Windows XP Pro, but it doesn't want to work on my new pc with Windows XP Home. Maybe it's something I'm forgetting to do. I'd appreciate any help. This is probably more simple than it looks!

[Madboy]

How odd? I doubt it will be due to different OS versions but i cant think what else. I would of said the DLL may be corrupt, but obviously it aint if it loaded on your XP Home. How strange

[crptcblade]

It sounds to me like the DLL is not registerable. Are you sure its not a standard DLL, like the kind you have to make API style calls to?

[gaffa]

The DLL probably needs to be in either the System path or the App path.

That message usually means it's not a COM component, so you need to declare the function API style rather than actually reference it.

- gaffa

[INF3RN0666]

gaffa's right. I forgot that I dont need to reference the file, nor register it. You declare them API style. The thing is, let's say that i make a program, does the DLL have to be in the system path or the current directory? Because sometimes, even if the file is in the current directory, it says that the DLL couldn't be found :S!