Mozilla 0.9.2 is not quite the same as Netscape 6.1, Mozilla 0.9.2.1 is the
matching source. I don't think a test binary was released for that.
There very likely was an API change in some class you import which causes
the .dll registration to fail, in which case you can't create a component
that is compatible with both at the same time. One of the main goals of the
"Mozilla 1.0" effort is to freeze a sufficient number of interfaces and
document which ones can be used safely in the future. Until then component
developers will either have to live with generating multiple
release-specific versions of their components or will have to seriously
restrict the number of Mozilla classes they import.
You can test this:
1) set the environment variables
NSPR_LOG_FILE=<valid path>\xpcom.log
NSPR_LOG_MODULES=nsComponentManager:5
2) delete component.reg (to force another autoreg)
3) start Netscape 6.1, quit
4) search the log file for output about your component,
and/or search for the text FAILED.
-Dan Veditz
shadows wrote:
> Hi,
>
> I have made an application for mozilla 0.92 and created an xpi package which
> copies the xpcom components (mytest.dll, mytest.xpt) to the components
> directory. In Mozilla I have no problems- when I restart Mozilla I have
> entries in component.reg. But in Netscape 6.1 somehow they don't register-
> the dll and xpt files are also in the components directory, but I can find
> to entry in the Netscape component.reg! And in JavaScript of course the
> XPConnect object doesn't have any properties...
> Can anyone help me? Do I need to do something special in Netscape to
> register my components?
>
> Thanks for any tips
> Fabian
>
>
>
