Re: No Slot Clock - Damaged?

["Gus Vilomar" <gvilomar@bellsouth.net>]

Hi Beverly,

Thanks for the info.  You're correct, no software that I know of can burn up
a chip.  However, "clock" softwares try to change the time (or data) on the
chip and I thought that ProSel 8 Y2k could have done that.  I wasn't blaming
the ProSel 8 Y2k software, instead, I was trying to state all the things I
did before the chip went bad.  As you should, one of the first steps in
solving a "bug" is noting all the changes done from the previous working
version.  That's what I was doing.

Since your software doesn't even make calls to the chip unless you use
Set.Date, I can safely elimate Prosel 8 from the possible causes.  The only
two options left are (1) bad chip or (2) dead battery on chip.  Sorry if
this caused any connfusion.

Gus


TEXAS II - AppleWorks <a2mg@aol.comNomail> wrote in message
19991010161018.13114.00000632@ng-cm1.aol.com">news:19991010161018.13114.00000632@ng-cm1.aol.com...
> The only ProSel 8 Y2K patch that is currently available to the public is
the
> patch to Mr. Fixit. Mr. Fixit has nothing to do with the bootup of
ProSel-8. It
> doesn't even run until you select Mr. Fixit from the menu. It couldn't
possibly
> affect the clock on startup.
>
> The ProSel-8 v4.1 that is about to become available does affect the menu
> program, as well as several other programs included with ProSel. But
nobody has
> it yet. Nobody.
>
> In any case, ProSel does nothing to set the clock unless you use the
Set.Date
> program. It only reads the clock. No software that I know of is going to
burn
> up a chip.
>
>
> Beverly Cadieux
> Y2K info at http://members.aol.com/A2MG
>