From: NotesTracker on
On Nov 22, 5:10 am, "John H Meyers" <jhmey...(a)nomail.invalid> wrote:
> On Fri, 20 Nov 2009 20:06:48 -0600, Old Eudora User wrote:
>
----> To find out, try moving the "user" dictionaries somewhere else,
----> and also look at each dictionary's "word count" line
----> (the first non-comment line in the file) for anomalies.

# THANKS for your interest, John! ... THANKS.
# I renamed the three .tlx files starting with "u" (presumably you
meant
# these user lexicon files) and experienced the same reverse
highlighting
# of the first misspelled world with freezing up.
# Also checked back to the various old installations (I've kept them
all)
# and these .tlx files seem to be nothing out of the ordinary
# although I've no idea what the parameters on that first line
represent
# nor how to validate them against actual lexicon file contents.
# Any tips? (The problem might lie elsewhere, anyhow.)

> > I'm thinking of doing a re-installation of Eudora
> > (which I know from bitter experience can have its own issues)
----> What sort of bitter experience?
# Well, "bitter" might be going a bit too far I suppose...
# I've a modestly good understanding of what some of the files do.
# I've probably re-installed Eudora 15 or 20 times over the years,
from Windows 3.1 to Windows 7.
# since latching onto it (a year or two before Windows 95 and Outlook
turned up).
# I've steadfastly refused to move to Outlook, prefer Eudora's
separate folders
# to Outlooks monolithic .PST approach (folders are easily backed up,
manipulated and recovered).
# After some reinstalls, but curiously not every time, found (I think)
the uignore.tlx
# had become read-only -- goodness knows why, again "out of the blue"
-- and
# only found out this was the cause via Qualcomm technical support
(I'm a paid-up user).
# I think this read-only problem occurred once early on (mid 1990s)
# and it turned out to be with the LMOS.DAT file (Leave Mail On
Server)
# once again only found out after help from Qualcomm tech support.
# These cases were resolved, of course, by switching off the read-only
attribute
# for the files concerned, this being not at all obvious to the
uninitiated!
#Then after a couple of other re-installs, I found Eudora would launch
but quickly freeze up
# very early on and become unusable. Fixed this each time after
fiddling with various files,
# can't remember exactly what I had to do (flew by the seat of my
pants).
#
# I still find Eudora version 7.1.0.9 (the final one released by
Qualcomm, alas)
# to be quite effective, what with X1 search built in and other
features I like
# (even little features like "Send to Browser" that I'd sorely miss if
not in
# whatever I might eventually have to migrate to if forced screaming
to drop Eudora).

>
----> FWIW, Eudora's spell check engine is Wintertree Software's
----> spell32.dll library (version 4.21)
# Yeah, John, just noticed that in some of the files I checked.
# What else might cause this "out of the blue" recent lapse into
freezing up, I wonder.
# Could it even be some obscure Windows Update effect that happened
last week?
# I'm running 64-bit Windows 7 Ultimate (which I find rather nice).
> --

From: NotesTracker on
BTW, in case you wondered, we are one and the same:
"Old Eudora User" and "NotesTracker" that is.
(FWIW, the latter is an SDK I developed for Lotus Notes).
From: John H Meyers on
On Mon, 23 Nov 2009 19:30:02 -0600, NotesTracker wrote:

> What else might cause this "out of the blue" recent lapse into
> freezing up, I wonder.

> Could it even be some obscure Windows Update effect that happened
> last week?

I do not know. Does anyone else have this problem,
or can you find a fellow sufferer via internet searching?

Various "usual suspects" include anti-virus programs (or suites)
and other software -- even errant device drivers.

Investigating these suspects is, unfortunately, a matter
of one at a time disabling, then see what happens.

> I'm running 64-bit Windows 7 Ultimate (which I find rather nice).

Glad you have enough bits on hand to run it :)

The "advisor" tells me to forget it,
which I'm perfectly happy to agree with.

Is the first you've mentioned Windows 7?

Does your "Data" path in "Help" | "About Eudora"
have anything to do with where program files are normally stored?

Reminder to the world: This ain't no good in Windows,
has been bad ever since Windows 2000,
and is now punishable by real malfunctions.

--
From: D G Couper on
On Tue, 24 Nov 2009 02:34:30 -0600, "John H Meyers"
<jhmeyers(a)nomail.invalid> wrote:


>Does your "Data" path in "Help" | "About Eudora"
>have anything to do with where program files are normally stored?
>
>Reminder to the world: This ain't no good in Windows,
>has been bad ever since Windows 2000,
>and is now punishable by real malfunctions.

Should probably have another thread but...

I have both program and data in C:\ program files\qualcom\eudora which
seems to be a problem for most people. But it's been this way since
2kPro up to (now) 76 Ultimate 32bit).

Luck or superior computering?

*****************

Now most dentist's chair go up and down, don't they? The one I was in went backwards and forwards. I thought "This is unusual". And the dentist said to me, "Mr Cooper, get out of the filing cabinet".
From: John H Meyers on
On Tue, 24 Nov 2009 04:18:46 -0600, D G Couper wrote:

JHM:
>> Does your "Data" path in "Help" | "About Eudora"
>> have anything to do with where program files are normally stored?
>>
>> Reminder to the world: This ain't no good in Windows,
>> has been bad ever since Windows 2000,
>> and is now punishable by real malfunctions.

D G C
> Should probably have another thread but...
>
> I have both program and data in C:\ program files\qualcom\eudora which
> seems to be a problem for most people. But it's been this way since
> 2kPro up to (now) 76 Ultimate 32bit).
>
> Luck or superior computering?

Pure Irish charm (or luck :)

Completely and permanently disabling UAC increases that luck
(although decreasing security for program files).

Automatic "Folder virtualization" in Vista and Windows 7
is _supposed_ to make it possible to not notice anyway,
and to keep functioning despite all "data writing"
being diverted elsewhere, but this "breaks"
for many users, revealing that it is
"skating on pretty thin ice" to rely on it,
as well as complicating any backup (or data transfer) strategy.

Toying with "Run as" and "Compatibility" settings
may vary the results, but installing in accord with
basic guidelines (programs where they belong, data elsewhere)
raises perfect operation to a certainty.

For the complete scoop about Vista
and user data in "Program Files" folders, see:

"A Closer Look at Windows Vista, Part I: Security Changes"
("File System and Registry Virtualization")
http://zone.ni.com/devzone/cda/tut/p/id/5538#toc3

Or just admire the nice drawings accompanying the geek stuff :)

--