Closed Bug 36933 Opened 24 years ago Closed 24 years ago

N6B1 not starting/100% CPU/Not showing up in task manager

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: mowersricharda, Assigned: asa)

Details

I cannot get N6B1 to start on my NT 4.0 machine.  It runs the CPU at 100%, but 
N6 does not show up in task manager.
mowersricharda@jdcorp.deere.com, bugs found in Netscape's products should be 
reported to Netscape.  The Bugzilla database is reserved for bugs found in the 
Mozilla builds.  If you can reproduce this with a current Mozilla nightly or 
Milestone15 build please reopen this bug with comments about the build you 
tested with and any error messages you see.  You might also make sure that you 
have deleted any old 5.0 profiles as well as the mozregistry.dat file located 
in the windows directory (these may help get your Netscape build up as well).  
Thanks.  And if you're still having trouble and have access to IRC please stop 
by irc.mozilla.org #mozillazine weekday evenings and I'll try to help out.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
mowersricharda@jdcorp.deere.com, here is the location to file Netscape bugs.  
Like I said above, if you can reproduce this problem in a nightly mozilla build 
and can give any information which might help me get this bug assigned to the 
correct component and developer then please reopen the bug.  Current nightly 
and M15 builds start up and run just fine for me under NT and I'd be glad to 
help troubleshoot your issue in email or irc.  Did you try deleting your 
mozregistry.dat file and old profiles? 

http://home.netscape.com/browsers/6/feedback/index.html
Sorry for the spam.  New QA Contact for Browser General.  Thanks for your help
Joseph (good luck with the new job) and welcome aboard Doron Rosenberg
QA Contact: jelwell → doronr
verified invalid!
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.