Oops, Killed a WU!

GHoosdumGHoosdum Icrontian
edited November 2003 in Folding@Home
I reset my CMOS earlier today because my board wouldn't POST when I tried to OC it above 200 FSB - and I forgot to set the date forward from Jan 1 2002 (BIOS default).

I got home from work today 55% of the way through a WU. I noticed the incorrect date.

Not thinking right, I set the date forward to the correct date in Windows.

I lost the WU because it thought I passed the deadline.

Oops. :banghead:

Comments

  • Geeky1Geeky1 University of the Pacific (Stockton, CA, USA)
    edited November 2003
    MURDERER!! ;)
  • a2jfreaka2jfreak Houston, TX Member
    edited November 2003
    I updated my BIOS today and changed the CCMOS1 jumper. Fortunately my WU had been started before I made the change so that when I moved my clock forward I didn't lose the WU.
  • muddocktormuddocktor
    edited November 2003
    That's why I tell the client to ignore time errors when I run the -config flag to change or set up a rig. I've lost a couple like that too.:banghead:
  • SimGuySimGuy Ottawa, Canada
    edited November 2003
    I had a BSOD last night that completely killed 2 gromac units that were about each 75% completed.

    Still can't figure out what caused the BSOD.

    When I attempted to restart both clients, they just hung at the 75% completed mark. After running for 2 hours, neither WU advanced any more. I had to delete each client and set everything up again.

    Now I'm stuck on these damned Tinker units that take forever. :(
  • edcentricedcentric near Milwaukee, Wisconsin Icrontian
    edited November 2003
    I have a gromac 1023 FSunf 337 99 that keeps hanging my system. I have run other fine, but every time I reatart this one I get a little done and lock city.
    Oh well, that's life.
Sign In or Register to comment.