A problem concerning registering java COM on ms windows

hello, everybody.
i'm not sure that this's the right place to ask this question, but i'll try.
situation is like this: i've written a simple java class that's a wrapper around java.util.zip Inflate and Deflate methods. i wrote it in microsoft j++ with service pack 5. next, i set properties to the project to produce a COM DLL with type library. everything so far so good.
i registered it with regsvr32 and then used it from visual basic, and everything worked just fine on approximately 20 machines.
BUT, on 2 machines, regsvr32 failed with error "myZip.dll was loaded, but the DllRegisterServer entry point was not found ...".
typically, that error means that the dll does not contain a COM object, but this one DOES, and it exports DllRegisterServer and DllUnregisterServer methods (checked with depends.exe).
this error seems to happen on micorosft windows 2000 with service pack 4 applied.
please, any comment, ideas, or solutions?

i wrote it in microsoft j++ with service pack 5. next, i set properties to the project to produce a COM DLL with type library. everything so far so good.
Your Java code is compiled and packaged as a COM DLL, -- do I understand it correctly? Kinda defeats the purpose of Java, if you ask me. Also, the last time I've heard someone using Microsoft J++ as an IDE was a few years ago, -- as far as I know, J++ relies on Microsoft specific classes and libraries and the resulting code could not even be considered Java.

Your Java code is compiled and packaged as a COM DLL, -- do I understand it correctly? Kinda defeats the purpose of Java, if you ask me.
yup, compiled and packaged as COM DLL. i needed that, so i can make zip file from java applet on html page, and unzip from another COM object on server written in visual basic.
J++ relies on Microsoft specific classes and libraries and the resulting code could not even be considered Java.
well, that's exactly what i needed, because that COM written in Java is consumed by another COM written in visual basic.

I thought MS did a very clever job of extending Java to produce COM objects. Sun didn't agree so the product is kinda dead. Or have they brought it back for dot net?
Anyhow, I think you'll get better help with a COM problem on a discussion group more in tune with MS products. It's been years since I tried to understand that stuff and it's all leaked out since then.

I thought MS did a very clever job of extending Java to produce COM objects. Sun didn't agree so the product is kinda dead. Or have they brought it back for dot net?
no, you're right - there're no COM objects on dotnet platform.
Anyhow, I think you'll get better help with a COM problem on a discussion group more in tune with MS products. It's been years since I tried to understand that stuff and it's all leaked out since then.
well, i kinda found the solution - i'm registering the COM manually. :

but, anyway, thank you for your time, guys.