Keystroke delay in Eudora 5.2

[rongold]

I have experienced a new problem with Eudora 5.2.1 Classic. New relative to version 5.1, as the problem first appeared with the first 5.2 Beta and has persisted through all of the beta versions into 5.2 and 5.2.1.

The problem: a long delay between keystroke and letter appearing on the screen in Eudora. The delay does not occur in any other program, only Eudora 5.2 Classic. The delay also manifests itself when using keyboard commands to select any command.

The bug occurs whether I do a clean or first install of Eudora and re-enter my setting or install the new version over my existing version 5.1.1.

Eudora Tech Support, after an inordinant delay in replying to my email, had no useful suggestions.

The only solution I have found is to continue using 5.1.1 and live with the intermittent crashes on quiting Eudora which were supposed to be fixed in version 5.2.

Any suggestions of a remedy?

[sandbox]

Hey Ron, sounds like something is running in the background? Or maybe Eudora is writing to your Hard drive? Check your memory allocation as well! I don’t use it and can’t find any reference to your problem anywhere else. Do you have a lot of stuff in your start up folder? Virtual Memory On?
Sorry I’m not much help, maybe someone else will come along and figure it out?

seeya

[rongold]

quote:Originally posted by sandbox:
Hey Ron, sounds like something is running in the background? Or maybe Eudora is writing to your Hard drive? Check your memory allocation as well! I don’t use it and can’t find any reference to your problem anywhere else. Do you have a lot of stuff in your start up folder? Virtual Memory On?
Sorry I’m not much help, maybe someone else will come along and figure it out?

seeya    

The problem is not unique to my computer (PowerMac 7200/90, 48 MB RAM, RamDoubler installed, Mac OS 8.6), but has been reported a number of OS 8.6 users on Eudora Usenet News group: news:comp.mail.eudora.mac (see "Slow Typing… " with 9 messages).

I tried the fix suggested in the Eudora FAQ:
------------
Spell Catcher causes slow typing (Mac)
Document ID: 1590HQ
ISSUE: Typing in Eudora is slow.
SOLUTION: If you are running Spell Catcher or any other utility that would be intercepting keystrokes on your machine and you are experiencing typing problems in Eudora, copy and paste the URL below into a new message in Eudora and double click on the resulting URL.
<x-eudora-setting:197>
A new window will appear with the default setting set to "Y". This enables Eudora to process keystrokes as fast as it can and may be incompatible with some key-processing extensions.

The new default value should be set to "N" (no quotes).
-----------

I don't know whether setting:197 does anything in version 5.2 or 5.2.1 as the default value is blank and there is no informationabout the setting in the dialog box. Changing the value of setting to "N" has no effect on the slow typing.

Slow typing persisted if I quit all programs running in background (Blackwatch, SpeedDoubler, KeyQuencer) or got even slower! I also rebooted via CoOnflict Catcher with only the OS 8.6 set enabled and slow typing was only slightly better, but still much slower than with version 5.1.1.

No response after two days from Tech Support at Qualcomm, but the few times a real person (not their automated response saying Thank you and referring you to FAQ) has responded it has taken more than a week.

So I will continue to use 5.1.1 and put up with the intermittent crashes that occur when quitting Eudora - a bug which was supposed to be fixed in 5.2.1.

[sandbox]

Hey Ron, when I use my PB 5300 with 64mb of ram and need more memory I turn on Virtual Memory and things get written to the hard drive. This process slows down my activity and I can experience lags in typing speed. Other than that I can’t think of a thing I’ve experienced that would cause a slow down unless there’s some activity in the background which you covered.

The upgrade may have caused a new problem when solving the old, sometimes you can’t win!  

The guys at Qualcom probably said, hey we received 10,000 calls a month for the last problem, let’s see how many this one generates? Then we can pick the winner!