Eudora 4.3 is out; update was removed earlier today due to problems but was returned; it is now gone again (until it returns aga

Eudora 4.3 is out (see this link for the annoucement). However, many readers are already reporting major problems with just getting it to install.

In particular, you may not be able to get the downloaded bin file to decode. And if you somehow do get it to decode, you will likely get the following error message when launching the Installer: "The application program 'eudora_43 Installer' could not be opened, because an error of type -199 occurred."

Brian Quint found that the cause of the decoding problem was that "the binary file had the wrong type and creator codes so it wouldn't decompress." However, when he "corrected the codes and decompressed the binary file, the installer crashed" (presumably with the type -199 error).

(Thanks also to R. Lynn Rardin, Dan Nelson, Rob Wiebe, David Frye, and others.)

Update: The file was temporarily pulled earlier today. A message appeared that said: "We're sorry, but the Mac installer is temporarily unavailable. Please try again later." Qualcomm confirmed that the reason for this pull were the problems reported above. (Thanks, David Kanter and Robert Wiebe.)

Update: The 4.3 Update has now returned. Readers are confirming that it fixes the initial glitches. Ray Zimmerman found that: "it installed the evil ObjectSupportLib in my Extensions folder on a Wall Street running Mac OS 8.6." However, others have not seen this Lib file show up.

Update: Paid mode not yet available A message on the Eudora web site now reads: "We're sorry, but the updater that will enable registered Eudora Pro 4.x users to upgrade to Eudora 4.3 in Paid mode (without ads) is not quite ready, though it should be soon." (Thanks, Joe Hanson and Tom Sykes.)

Update: Eudora is gone again! Several readers continue to report problems with using the update, including system crashes. Maybe that's why the update has been pulled altogether for the second time today (the "We're sorry..." message has returned!) Whew! It's been a real hassle for us to keep up with all of this. I can only imagine how Qualcomm must be feeling.