It seems that Adam Rykala said ...
A> a) Its being corrupted in memory as the attachment is being reconstructed. Agreed, but would it not have the same effect when the message is being reconstructed in Eudora, Outlook, Outlook Express, Pegasus, Netscape Maill, or SOME other program? I have never seen one of these programs corrupt an attachment. If memory was the problem, wouldn't I see some evidence of it in other programs? Wouldn't I see BSODs on a regular basis? I agree absolutely that it's probably happening when the attachment is being reconstructed, but if it's bad memory, would the same image fail in the same way every single time? Wouldn't that be memory dependent? Wouldn't you expect the attachment to open sometimes and to fail sometimes? That's the nature of a memory problem -- transient. But once an image fails, it always fails. If an image is good, it's always good. I'm really not trying to "knock you back" or to be a smart ass, but I'm not about to take apart three computers (or even one) on what looks to me like a wild goose chase. A> Also you mentioned ZA and mail checking - well I had to rebuild an exchange A> server with a 12gb database because a virus checker was silently corrupting A> attachments due to what is called (oh how I laugh) "Known Issues".... Both ZA and NAV were out of the picture when I received a fax attachment earlier today -- it was corrupt. Fortunately my jFax account is set to leave mail on the server, so I retrieved the attachment with Eudora -- no problem. A> So there are several angles to try. A> Me - I'd isolate the easy ones first. Change the RAM - try it. Still the same? A> then strike ram from it. Check to remove overheating from the equation. Many A> people just slam in any old RAM into their PC's without a second thought for the A> issues. Mismatching RAM is a big troublemaker.... I can't say that the RAM is perfect, but I pay extra for quality, matched RAM when I build a machine. I see no other indication that there is a RAM problem with any of the 3 computers. One of these is a computer that has been replaced during the time I have used TB. The problem occurred with the previous machine, too. So that would be FOUR machines (two that I built with known good components and two from decent manufacturers -- Sony for the notebook and Compaq for the desktop) with bad RAM. That's just too coincidental to fit. Possible, yes, but very unlikely. A> If you have three machines then strip one down to windows and TB!. Remove all A> extraneous software from it. You may, for example, have an esoteric bit of A> software that conflicts. NAV and ZA were on all 3 machines (different versions). Except for that, running apps and processes differ quite a bit. Removing ZA and NAV had no effect, as others have already said. Trust me -- I *really* would love to find out that it's not TB because I really like this program. I've used it for 18+ months and, even with the problem I see, am not seriously considering any other program. There simply is no better or more configurable e-mail program than TB. Thanks to EVERYONE for the ideas, thoughts, and suggestions! Using The Bat! v1.61 on Windows XP 5.1 Build 2600 -- Bill Blinn, Technology Editor ([EMAIL PROTECTED]) - 9/12/2002 at 6:07 PM Technology Corner on Newsradio 610 WTVN, Columbus, Ohio Direct: 614-785-9359 Fax: 630-604-9842 http://wtvn.blinn.com http://www.wtvn.com Random thought: "Managing senior programmers is like herding cats." -- Dave Platt ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
