Hello Thomas, Saturday, August 31, 2002, 1:59:06 AM, you wrote:
TF> Hello Eddy, TF> On Fri, 30 Aug 2002 15:20:06 -0400 GMT (31/08/02, 02:20 +0700 GMT), TF> Eddy wrote: E>> - If I copy the offending message to a new folder called "Test", zip E>> up the "Test" folder created by TB! (containg a .TBB and .TBI file), E>> mail it to a friend of mine who uses TB!, and he imports it, he also E>> gets the "JPG Err#68" message. And he has never experienced any E>> problems with attachment corruption. TF> I have seen this error at a few occasions, and it was fair to assume TF> that the jpg files were indeed corrupted. I recently changed over to TB! from PMMail2000, which I'd been using for years. A fair percentage of the attachments I recieve are now (since switching to TB!) corrupted. I get the Err#68 for corrupt JPG's when I try to view with TB!'s internal viewer (Blank page when I go to the tab). When I save to disk and then view with another viewer, I can view part of the file. It's not just JPG's that get corrupt though. Since switching to TB!, I have seen a huge increase in corrupt attachements of many different types, including a lot of corrupt ".doc" files. E>> - Forwarding the message to an account that receives mail with another E>> MUA, such as Outlook, the message will be fine and is NOT corrupted. TF> message), I don't think it is a RAM problem either. It could be file TF> I/O handling, either by TB or by the OS. Alas, it would help me if TF> anybody has any idea what this JPG Err#68 means. I "think" that the Err#68 is from TB!'s image viewer. -- Regards, Mark mailto:[EMAIL PROTECTED] The Bat! Version 1.61 OS info: Windows 98 4.10 Build 2222 A ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
