Didn't see anything about this at Moz. Solved, but maybe of passing interest; doubt any Moz user here has seen this one -?-

Had viewed something innocuous - in fact I think it was one of the links off of Another Scott's APOD link in today's Water Cooler. I noted I'd left a WW filter off, as needed to login to zIWE - and turned it on while the link was loading. (Which may have zippo to do with the phenom, natch)

Went then to Edit, to see if any cookies had sneaked by and.. as I hit Preferences Moz froze. Kill task. Reload Moz - same. Hmmm

(Note - per grc.com and a few others, my firewall, ZA, be functioning like Stealth, on at least the first few 1000 ports and all the usual suspects. jscript On, but not Java, of course)

OK.. look for any new parasites in / and a few other places. Check Reg via Norton + a few other inspections. Nada. Reboot. Moz loads, goes to site, etc. Try prefs again: DITTO. Dead in a mSec. Reload it, find I can sneak into the area via Tools/Cookie Mgr. OK on cookie mgr.

Go to Mail and to Account Setup; OK on Server; hit Copies & Folders - DITTO. (See.. I wanted Prefs/Advanced to clear the &^#^* cache; not a bad idea after any unknown crash. Couldn't Get There :(

OK I tried the obvious; no Easter Egg. But it's *Moz* -!- so d/l 1.30; Install. The usual lovely NO-reconfig.. I'm using it. Still have 1.2.1 in its own folder, if it looks like fun to dissect it sometime.

Seems a bit snappier, but that could be ~ the car wash that makes the car seem faster. (And a blank History file)


Ashton
Next to try: Prefs|Advanced|HTTP Networking ... pipelining! & see if That works on this 98-lite setup and whatever's in that M$ TCP stack.

WOW - I think this yere pipelining WORKS; at least a few links tried on aforementioned APOD page.. show up like almost-DSL on my top-notch (51-52K normal) dialup..

Little early to know if someplace else will choke on this, but so far -- Pipes Smoke!

I also neglected to add: I had reinstalled from orig. d/l file - had even reloaded prefs.js from my backup CD - thinking it might have been corrupted by some unscheduled save while Moz was running in Quayle-mode.. no dice.

98-SE dejunked by 98-lite; all the usual "save this glass-fragile POS" stuff usually done, incl. defrag via Norton, no gratuitous installs / deinstalls. No latest spyware from Real or the Beast allowed in. No Orifice Satanic-DLLs, LookOut, Power Punt yada yada.

I still don't get it how: a complete reload would also fail, on 1.2.1. The only junk found by Norton in Registry - had to do with a few orphan files for some M$ cockamamie TV-thing never intentionally installed. So if W2K is also vulnerable.. WTF *could* persist from Moz. thru a complete replacement (except for data). And if the data had a bizarre glitch: hows come it didn't bomb 1.3.0 ??

A rhetorical question, of course: It's Doze. Useful to hear that I'm not the only one to be bit by 1.2.1 though. I mean.. I'm a Licensed Driver.

So far - 1.3.0. seems peachy keen - and the threaded option appears to account for rilly Fast loading, like the book says. (Wonder what goes wrong with that.. when it does go wrong)



Ashton