Please reboot your computer and try again. Some windows installs require a reboot to complete the install.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is neither a blocker, nor does it crash (according to your initial report, at least.) It's most likely an install problem. Have you tried rebooting yet?
Severity: blocker → normal
Oh, my bad, it wasn't Russ who changed those fields.
Summary: Crash on startup - unable to initialise debugger (BadMojo 4) → unable to initialise debugger (BadMojo 4)
Russ, do you have jsd3250.dll in your components directory? This works for most everyone else after a reboot, I'm stumped.
Status: NEW → ASSIGNED
I'm having exactly the same problem, which persists after a reboot. I'm also using Windows 2000 server, so this may be related.
Forgot to mention that I DO have jsd3250.dll in the components directory (C:\Program Files\Netscape\Netscape 6\components). I also have Netscape 4 installed on the same machine.
I've now successfully installed the debugger on my Win2K server by following these steps: - uninstalled Netscape 4 - uninstalled Netscape 6 - deleted C:\Program Files\Netscape (the unistall for Netscape 6 didn't remove this) - rebooted - reinstalled Netscape 6, taking all defaults. My initial installation was a custom, installing only the Navigator component, and additional components Sun Java 2, Quality Feedback Agent, and Classic Skin - reinstalled the debugger - rebooted (without even attempting to bring up the debugger) After I did all this, the debugger worked. So the problem is connected either with Netscape 4 on the same machine, a custom install, or attempting to use the debugger before rebooting. Hope this helps.
Of these, the idea that using the debugger without a reboot (on some windows systems) is the most likely. If you're not tied to NS6 for a specific reason, the latest mozilla build will have a more recent debugger, and can be installed by default.
Note that I did try rebooting before I tried the procedure above. The only difference here (aside from the deinstalls and reinstalls) is that I didn't even attempt to use the debugger until after the reboot. Are you saying that bringing up the debugger without first rebooting causes some kind of permanent damage so that even a subsequent reboot doesn't help? This should certainly be noted in the installation procedure.
Unfortunately, I'm going to have to reopen this issue. I tried to install the debugger on a second box running NT4. I followed these steps: - deinstalled all versions of Netscape - deleted all references to Netscape or Mozilla from the registry - rebooted - installed Netscape 6.2.1 from the Netscape web site - rebooted - installed the debugger - rebooted - attempted to use the debugger. No dice - I get the "bad mojo" message. This issue is easy to reproduce and a complete showstopper. Can I raise the priority? If necessary, I can make the box available to you - please email me (firstname.lastname@example.org) if you'd like to do this.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.