Re: New NoSlot Clock fix!

[brian.hammack@rook.wa.com (Brian Hammack)]

 Obsbedia chanted almost zenlike:

 OC(|  And, unfortunately, this is one of those times.  One of the
    | chips died after two or three weeks, and when a NoSlot Clock dies
    | it is no longer recognized by
    | it's software, so it's NOT possible to just reset it after each
    | boot up.

Actually, here's the deal there, if I'm reading you right:

SMT's clock software wasn't written to handle the chip if the date is
not numerical, meaning that if the computer did something like power
down during a read it can reset it.  However, there's a freeware
program called SmartWatch which doesn't have the limitation; use that
to reset the clock and you'll be fine.

For awhile I thought my NSC was a goner because of a similar error,
but a month later the computer could deal with it somewhat because the
month had changed from garbage to JAN.  The year was still listed as
":I" under ProTerm, but SmartWatch fixed that.

 * 2qwk! 2.04 * If you're not part of solution, you're part of concentrate.