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

Re: AccuVote-OS 1.96.2 corrupt count

I have used AVOS-1-96-2 for one small election with rejection set for blank ballot and over-voted race without problems.  I also used this for trade shows demonstrating these two rejections without incidence.
----- Original Message -----
From: Larry Dix
Sent: Monday, August 27, 2001 9:15 AM
Subject: RE: AccuVote-OS 1.96.2 corrupt count

This has not been through Wyle.  They are only at the source code review stage.  They have not started the functionality test as of yet. 


Larry J. Dix

Vice President of Operations

Global Election Systems


-----Original Message-----
From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Ken Clark
Sent: Thursday, August 23, 2001 7:00 PM
To: bugtrack@dieboldes.com
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? 





-----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.