Closed
Bug 177255
Opened 22 years ago
Closed 22 years ago
browser stuck in stopped state
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jgalanes, Assigned: asa)
Details
Running win98SE with ZoneAlarm Pro on AT&T broadband. If I do a Google search, then open one of those links in a new window, then hit the STOP button (because the page is taking too long to load, etc.) then the browser seems to be hosed. If I close the new window and go back to the original and try and click on any other link, it may open a new window, but doesn't seem to access any page. Only remedy is to close mozilla and start over, which means I've lost the search results and my place within them. Tried both versions 1.0.1 and 1.1 - same. I've been using 1.0.1 at work on Win NT (4.0) and it seems to work fine. COuld this be a win98 (SE) issue?
Comment 1•22 years ago
|
||
Does this problem appear with a new build of Mozilla?
| Reporter | ||
Comment 2•22 years ago
|
||
Yes the problem still ocurred with version 1.2.1, but it got me to thinking about what was different between my 2 os systems (win98 se and win 2000). The win 2000 install was fairly recent, and mozilla works fine there. Ultimately, I found some cruft in the win.ini file for win98se that was left over from my old dial-up ISP (USA datanet - NetSurfer stuff) - I now have AT&T broadband. For anyone else who might run into this problem, do this: click Start then RUN and type in msconfig. Then click on win.ini, then look for Netsurfer stuff and uncheck it (requires rebooting to take effect). Seems to work great now for me!
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 3•22 years ago
|
||
Reopening to resolve properly - Mozilla was neither broken nor fixed.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Comment 4•22 years ago
|
||
->WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•