http://bugs.winehq.org/show_bug.cgi?id=14798
--- Comment #31 from andrew@magneticbooks.com.au 2011-07-09 17:59:18 CDT --- Attached some memory dumps from SSL_write() calls when running in a Windows 7 VM. Used winapioverride32 (like ltrace) for dumps.
TODO: dump wine SSL_write() calls, compare.
Unfortunately I could not get winapioverride32 to work with etax in wine. I will probably use winedbg then decode the stack and do a memory dump by hand.
I suspect it may be a date related problem - now that there is a new version of etax it keeps on reporting that a new version even if that new version is install. One of the fields in the SOAP request is "InstalledDate" - presumably this is what is used to detect the latest version.
Also note that the previously mentioned Error 5011 is usually also date related.