nsComponentManager doesn't seem to like me, because for the last couple of months, I haven't been able to run a nightly build because of a failure in the component manager to load unicharutil.dll (it dies with error 0). Now, as of 5-13-99, the DocLoaderFactory in viewer is unable to create a ContentViewer, leaving me with an empty viewer window that can view nothing. apprunner dies immediately because of the failure to load npprofile32.dll (which I'm not seeing in any of the directories), again with error 0. Hard to test the thing for other bugs when I can't run it. :) I'm not sure how to file this (it appears to be a component manager thing, but I'm not sure where that falls into [is it XPCOM?]).

Jan, this basically says we dont work on win98 at all. Is that true. Hyatt and jevering build on win98. Do you think this is true.

A note here from the original reporter.... I deleted c:\windows\mozregistry.dat and it did help (the thing started finally). But I discovered that every time Mozilla crashed and was fatal (it dies in rptcl4.dll or something like that [I can't remember the exact name] and kills the keyboard and makes a safe shutdown impossible), this file was corrupted, and that causes the nsComponentManager problems. Obviously, it's not adequate to have the end user have to reset mozregistry.dat every time, so perhaps the solution could lie in a correction somewhere? I think I should probably file a new bug on the death-on-closing-of-browser thing. Is that correct?

we need some talkback data or stack traces if we are going to get this fixed in M6 or at all...

beppe, I don't think this is an issue with latest builds? Can your team verify?

moving to m7. let me know if you find something interesting and quick we can fix for m6.

This does not happen with final M6 199052620 build. But we'll check again when we start pounding on M7.

beppe, if this no longer occurs with latest M7 on Win98, please mark Verified. Thanks!