Guest Blogged by John Gideon of VotersUnite.org and VoteTrustUSA.Org
Allegheny Co., Pennsylvania is admitting to 16 more voters voting on optical scan machines and 24 on iVotronics than ballots counted. Lonoke Co., Arkansas hoped to finally begin counting votes yesterday as ES&S may have fixed their software finally. White Co., Arkansas has announced they will go back to punch-cards for their early voting in the run-off elections….
AR: Train Wreck – 2 counties’ machine woes delaying final vote tally LINK
AR: Jackson County � Train Wreck – Election issues abound for weary candidates LINK
AR: Lonoke County � Train Wreck – County could start count today LINK
AR: White County � Train Wreck – Machines absent for early voting LINK
PA: Allegheny County � Train Wreck – Preston holds on to narrow lead in state race LINK
AR: Glitches didn’t hit everyone in primary LINK
CA: California trying to avoid Ohio pattern LINK
CA: San Joaquin County – Ready or not. Touchscreen voting machines await election test LINK
CA: Yuba County – Hmong tutored on Yuba voting LINK
IN: Union County – Election tallying up high costs. Union County still waiting to recoup funds for new election equipment LINK
KY: Robertson County – Robertson recount yields no change in results LINK
VT: West Rutland – West Rutland OKs voting machines LINK
**”Daily Voting News” is meant as a comprehensive listing of reports each day concerning issues related to election and voting news around the country regardless of quality or political slant. Therefore, items listed in “Daily Voting News” may not reflect the opinions of VotersUnite.Org or BradBlog.Com**
The Arkansas story: "Glitches didn’t hit everyone in primary", is the one that troubles me.
Assuming the same electronic voting machines, why would the same machine perform differently in the same circumstances?
They wouldn’t.
It could be the use of Kelly temps to haul the voting machines to and from the precincts? Or even permanent election officials keeping them in their homes and offices?
The big story is the variation in performance under equal circumstances. That does not pass the smell test.
Black Box Voting (link here) has released an update which deals, among other things, with the issue of different results in the same circumstances:
"Two machines with completely identical software release numbers had different behavior with the same macro. Machine A just had a software crash and become unstable, while machine B produced an error message on the system log and contained the error while still resulting in loss of software functionalities. There were also other examples of different, but reproducible, software behaviors between machines with both modified and unmodified macros" (link here, bold added).
Every time I have seen this happen (assuming the version id numbers are correct, and that the software is in fact identical, as is the hardware) it shows that the stack or heap or some other critical area of memory is being corrupted somehow.