Sh'mae Technology, On Thu, 12 Sep 2002, at 17:25:21 [GMT -0400] (or 22:25 in Wales) regarding 'Mangled attachments' you wrote:
BBTE> It seems that Adam Rykala said ... A>> Tried swapping out your ram? You may have a dodgy chip somewhere? BBTE> Ahhhh.... Adam ... BBTE> Everyone who has this problem has bad memory? And I have bad memory on BBTE> THREE computers? And the problem doesn't manifest itself with any BBTE> other e-mail program? (Not even with that inferior thing Microsoft BBTE> ships.) Tell you what, rather then just knocking me back like that. Take your main machine it happens with and try it. FYI I'm a Senior Support guy and the first thing I teach my staff under me is to attack a problem from all likely angles. ANd you say its impossible to have bad ram on three computers - no not impossible. Unlikely, but not impossible. Remove the impossible and whatever is left, even the unlikely - must be suspected. I've seen stranger things that happen. Lets look at what you've said. Attachments come in and on those machines they seem corrupted. JPG's show some file corruption within them right? Documents don't open. Therefore something isn't being read from message store correctly. Seeing as (IIRC) you're storing attachments with the message in the store its safe to assume that for some reason the decoding of the attachment from store is not going right. I said that I suspect a) Its being corrupted in memory as the attachment is being reconstructed. Because its obvious (as other people can read your attachments when forwarded) that the deconstruction process is going wrong. If they are stored in the message base coded then there is no real reconstruction going on in forwarding them - they are merely block copied and sent out. Also you mentioned ZA and mail checking - well I had to rebuild an exchange server with a 12gb database because a virus checker was silently corrupting attachments due to what is called (oh how I laugh) "Known Issues".... So any software that sits between you and the mail store is also suspect. Mainly because the process of "checking" goes on (1) when writing the message to store and (2) retrieving from store. So there are several angles to try. Me - I'd isolate the easy ones first. Change the RAM - try it. Still the same? then strike ram from it. Check to remove overheating from the equation. Many people just slam in any old RAM into their PC's without a second thought for the issues. Mismatching RAM is a big troublemaker.... If you have three machines then strip one down to windows and TB!. Remove all extraneous software from it. You may, for example, have an esoteric bit of software that conflicts. a. -- 12 September 2002, 22:32 |\ _,,,---,,_ http://new-wales.net | /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED] | |,4- ) )-,_..;\ ( `'-' Checked by Antivir Mail Gateway | '---''(_/--' `-'\_) pgp key : [EMAIL PROTECTED] | | You are here: X My opinion is neither copyrighted nor trademarked, and it's price competitive. If you like, I'll trade for one of yours. ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
