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

# RE: AccuVote-OS 1.96.2 corrupt count

- To: <bugtrack@dieboldes.com>
- Subject: RE: AccuVote-OS 1.96.2 corrupt count
- From: "Ken Clark" <ken@dieboldes.com>
- Date: Tue, 13 Nov 2001 18:01:13 -0800
- Importance: Normal
- In-Reply-To: <00a901c13284$e4ee5120$0a04a8c0@dieboldes.com>

This is fixed and will be in 1.96.3.
Ken

> -----Original Message-----
> From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Nel Finberg
> Sent: Friday, August 31, 2001 6:25 PM
> To: bugtrack@dieboldes.com
> Subject: Re: AccuVote-OS 1.96.2 corrupt count
> The corrupt count is caused by a blank selection in a recall race, irrespective of the selection made in the dependent recalled race. Any ballot or control card fed after a ballot with a blank recall race is fed gives rise to the corrupt count message.
> Nel

> > ----- Original Message -----
> > From: Ken Clark
> > To: bugtrack@dieboldes.com
> > Sent: Thursday, August 23, 2001 5:00 PM
> > Subject: RE: AccuVote-OS 1.96.2 corrupt count
> > Okay, this is pretty potentially serious. Nel (and anyone else), can you please try a couple of other databases to narrow it down a little. Does this happen with any run-of-the-mill database, or is there something special about this one that causes corruption? Since it got through Wyle (correct?) I wonder whether there isn't something quirky about the database. Or is it possible we went through the process without actually testing reject? Doubtfull.
> > I will track this down, but it is going to take a bit to get a AVOS development environment up. I suggest people avoid 1.96.2 in the mean time. Are any accounts actually running 1.96.2?
> > Ken

> > > -----Original Message-----
> > > From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Nel Finberg
> > > Sent: Thursday, August 23, 2001 4:57 PM
> > > To: Bug Track
> > > Subject: AccuVote-OS 1.96.2 corrupt count
> > > Memory cards programmed to 1.96.2 firmware from the attached database consistently generate corrupt count messages when fed ballots marked in violation of ballot return conditions defined in the database. These include blank voted race, blank voted card and overvote. These corruption messages do not occur when ballots are fed that have been properly marked.
> > > This behavior does not occur with 1.94x and 1.95e firmware.
> > > Nel

- Prev by Date: RE: Central Count problem
- Next by Date: RE: Gems- Ballot Audit - View - Ballot not marked
- Index(es):
  - Chronological
  - Thread