SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Thu, 3 Jan 2002 18:10:56 PST7
From:	"J. R. Fox" <jr_fox@pacbell.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: NS 4.61 Mail Corruption

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Despite its flaws, mostly as a matter of convenience, I keep on
using the NS Communicator email client. It allows me to do
browsing, mail, and (rarely) news all from the same place, with a
central interface. Ever since I upgraded to the 8/19/2000 or
7/29/2K build (both dates are mentioned at the end of
NETSCAPE.EXE), back when it came out, the worst problems that I
used to experience went away. But I gotta tell ya, this is by
far still the buggiest item in OS/2-dom, the one thing I can
regularly count on to crash. Let me count the ways.

1) The latest, rather annoying thing is corruption of a mail
folder index file (*.snm), causing a block of mail -- usually
received after a certain date -- to "disappear." It is actually
still there, but no longer shows up in the mail directory, and
cannot be accessed without torturously circuitous methods,
_outside_ of NS. NS does not seem to provide any tool for
repairing or regenerating this index file. I know it was
corrupted, because the index file could not be copied to another
location; attempts to do so yielded a "File Not Found." By
experimentation, I did manage to recover such a block of mail
that had gone 'Poof' after some unknown glitch crashed NS, and to
bring it back into NS. If anyone is interested, I can give you
the details. However, I just had my 2nd. corruption of a mail
folder index in the last several days -- different folder -- but
this time instead of losing mail the result is that the affected
folder (which is not all that large) "fails" attempts at
compaction.

2) Saving a larger HTML file -- say, over 100K -- _in .TXT
format_ will often cause NS to crash. Happened this morning
here, and something involving Mozilla.DLL shows up in the system
Popup Log. Numerous other crashes of NETSCAPE.EXE reflected in
the log -- by far the most frequent entry.

3) I continue to have that problem I reported over a year ago
here, involving the Composition window for Replies, which no one
else seemed able to duplicate. On random occasions, it comes up
partly greyed out, with no quoted text, etc. If I'm willing to
wait for two, three, four minutes or more, **without doing
anything else** in NS, the missing stuff eventually arrives, and
I can proceed normally. BUT, cancelling the composition window
or clicking on any other NS menu item will crash the app. big
time. At least it doesn't usually take anything else along with
it for the ride.

Are we still talking about huge memory leaks here ? Clearly
something is seriously not right with this program !

4) This last item is probably a settings thing, and my fault. No
matter what I do -- and I try a lot of different things -- I
can't seem to get a consistent line wrap. Almost always plenty
of short, partial lines, messing up the flow, by the time you see
it here. What's the fix ?

Running Warp4 @ FP-9. TIA for any insights.

Jordan

P.S. : I'll give Warpzilla a go at some point, but not right
now. Is there a worthwhile later build of 4.61 ?

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 03 | January | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.