GnuPG 1.2.5 + EudoraGPG 2.0/Enigmail 0.85.0 Broken?

[Adam Lau]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

My gpg.conf file is as follows:

armor
cipher-algo TWOFISH
comment DC39 FB90 71FF F1F4 F235 8482 E65C E36B BE90 8723
default-key BA907EB4
default-recipient foo at bar.com
digest-algo RIPEMD160
force-mdc
keyring gnupg-ring:A:\Rings\Default\pubring.gpg
lock-once
no-default-keyring
no-greeting
no-random-seed-file
no-sig-cache
no-tty
no-verbose
openpgp
quiet
rfc2440
secret-keyring gnupg-ring:A:\Rings\Default\secring.gpg
s2k-cipher-algo TWOFISH
throw-keyid

The conf file works *fine* w/ (GnuPG 1.2.4 + EudoraGPG 2.0 + Eudora
6.1.2) *and* (GnuPG 1.2.4 + Enigmail 0.85.0 + Thunderbird 0.7+). The use
of GnuPG 1.2.5, however kicks back unsupported options errors with both
of the previously mentioned plugin/client combos. Registry were updated
accordingly (gpgProgram="C:\1.2.4" and gpgProgram="C:\1.2.5"). Is 1.2.5
broken? Or have the options listed in my gpg.conf file been deprecated?
- --
Adam Lau @ Yahoo!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iEYEAREDAAYFAkEq0ycACgkQAZ94haZ93oCBYgCbBIDP3vNo9Wjls1hQCTBADUkF
PE0AoIvpA9t11eCslOYJ09re9mkwk264
=XyPY
-----END PGP SIGNATURE-----