[Date Prev][Date Next] [Chronological] [Thread] [Top]

# RE: Memory Card Corruption Problems

- To: <rcr@dieboldes.com>
- Subject: RE: Memory Card Corruption Problems
- From: "Ian S. Piper" <ian@dieboldes.com>
- Date: Fri, 30 Mar 2001 18:59:08 -0600
- Importance: Normal
- In-Reply-To: <3AC509AB.298D614B@dieboldes.com>

> > > Does it perform less multi-threading, and therefore have less data
> > > traffic?

> No. There have been no changes to the underlying operations. Thus I have trouble accepting that 1.95e doesn't suffer the same memory card corruption problems as 1.94w.

Ah, grasshopper.

> And for a little more perspective, we first added complete checksum and consistency checks to the memory cards with release 1.41 in November of 1989. This helped us trace down some programming errors that were causing corruptions and also helped us detect corruptions sooner that were caused by motor control and other timing functions. But we have never had a release that didn't occasionally get unexplained memory card corruptions. Not that we haven't chased a lot of theories that proved groundless. The problem is that we have not been able to set up tests that would reliably reproduce the corruptions. It could be that we could avoid the problem with some timing adjustments but what timing adjustments. I'm hoping that the EE study could help us there.

Hopefully all of the questions that we haven't been able to answer ourselves will have solutions by the end of the study. Let the chips fall where they may.

I think we would all be happy with a solution (whatever it may be) to just this one problem so we can breath a little easier as "Election Day" creeps closer on our calendars.

Ian

- References:
  - Re: Memory Card Corruption Problems
    - From: Guy Lancaster <glanca@dieboldes.com>

- Prev by Date: RE: Memory Card Corruption Problems
- Next by Date: Re: Memory Card Corruption Problems
- Index(es):
  - Chronological
  - Thread