Eudora TM Search Contact Us
Support - Technical Support Resources and Knowledgebase User Forums - See users' online questions and answers about Eudora products, or post your own questions to the Eudora Community. Developers - Resources for Developers writing code to interact with Eudora Press - Press Releases and News Articles Testimonials - Read what others are saying about Eudora
Qualcomm

 

Translator Initialization failed error message

Document ID: 911HQ

The error message "Translator Initialization Failed, consult translator documentation {-2804.0}", or "Translator Initialization Failed" indicates that a plug-in file has failed to load properly when you started your system.

Plug-in files, which are similar to Extensions, load when you start your system except that plug-in files can be loaded and unloaded at any time, not just at system start-up time.

Although plug-in files are not Extensions, the Finder reports them as such. Plug-in files are actually COMPONENTS requiring the Component Manager to be present; it is part of System 7.5.3 and above.

Eudora plug-in files are "registered" with the system when loading Eudora, and plug-in files can be "unregistered" when exiting Eudora. However, it is often impossible for Eudora to return the NAME of the plug-in file causing a problem, so Eudora cannot "unregister" the plug-in file.

To determine which plug-in file (component) is causing the problem, do the following:

  1. Use the Macintosh's built-in "Find..." to search for files whose "File Type" is "thng" (all lower case).

  2. Look through the list and find the "thng" files which may be located in any of the following folders:


    • Eudora Application Folder (the folder where the Eudora application resides)

    • Eudora Stuff (inside the Eudora Application Folder)

    • Eudora Folder (usually found in the "System Folder" or the "Documents" folder)

    • Preferences Folder (in the System Folder)

    • Any sub-folder of any folder mentioned above.


    Note: If you do not have the Find File installed, look in these folders for files which are listed as "System Extensions"

  3. Move the "thng" files to the desktop and restart your computer.

    Note: Restarting is IMPORTANT because a component will remain registered until either the machine is rebooted, or the component is unregistered, which Eudora cannot do when the "Initialization" fails.

  4. Launch Eudora.

  5. Move one plug-in file back to the appropriate folder.

    Tip: An easy way to move a plug-in file back from where it originally came is to highlight the plug-in file on the desktop and then select "Put Away" from the "File" menu.

  6. Quit and restart Eudora so that Eudora tries to initialize the plug-in file you have just installed. Repeat step 5 and 6 until the error message appears. Then you will know which plug-in file caused the problem.

  7. The easiest method to fix the problem is to delete and then reinstall the plug-in file causing the problem.

    Note: The problem can be caused by another file rather than the plug-in file itself.

However, THE MOST COMMON CAUSE OF THIS ERROR (so far) is the PGP plug-in file. PGP relies on the presence of some files in the extensions folder, namely:

  • PGPemailer

  • PGPLib

  • PGPmenu

These files can be "disabled" through the use of utilities such as Extensions Manager, Now Startup Manager and Conflict Catcher. Disabling these files, while leaving the PGP plugin in the Eudora Sfuff folder, will cause Eudora to display the "Translator Initialization Failed" error.

----

KEYWORDS: EPMAC,TRANSLATOR, FAILED


[Search Again]

Did this document help you to resolve your issue?
YES
NO


 

| Home | Support | Developers | Forums | Contact Us |

| QUALCOMM | Investor Relations | Section 508 | Privacy Statement | Terms of Use |


© 1999-2008 QUALCOMM Incorporated. All rights reserved. QUALCOMM and Eudora are registered trademarks of QUALCOMM Incorporated. All other trademarks are the property of their respective owners.