Inadvertant spike...

[dfamily]

Machine was running K-55459 N-4371432 - Account pcdeatherage

Machine died when test was at 32%. Replaced motherboard. Had to reinstall W2k which killed the registry. Determined to continue running current test, added registry entries for test no problem...

After about 3 blocks, I noticed that the pending test info had not been updated. Looked at stats and saw spke . This is when I realized that I had typo'ed the hex on the K... Stopped test. Corrected registry entry. Restarted test.

Daily results seem to be relatively normal but not sure...9 machines last 2 days were .24 and .23 plus the xp1900 for 7 hours today gave me .26 - but the graphs are definitely spiked. And this was I'm sure just 3 blocks worth...

(This also spiked the team's graph .)

Assume I should kill and release this test just in case? Did I mess up big time? Am I going to be branded the guy that spiked the graph the rest of my life? (talk about life's little co-incidences...just realized, "Spike" was my mother's nickname in high school)(no, she never did tell me why, I found it written on the back of her high school picture and photo album)(maybe she's trying to tell me go give up DC and go back to genealogy)...

Somebody please tell me I didn't break it...

patrick.

[Frodo42]

To me it just seems like you have done a big amount on one test for a short time and then abondend it . The spike will probably remain but I don't think anything is broken. But someone who knows more ought to check it.

[dmbrubac]

I haven't been shunned yet, so you probably won't either.

(That big dip is what happens when a box goes down, then the whole darn power grid does too!)