[Coco] Back to os9level 2

Tue Apr 28 17:06:59 EDT 2020

Thanks. Can you please provide me with a example to set and get the current
date and time? Will it show the correct date for example 2020/04/28
17:06:00?

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Tue, Apr 28, 2020 at 4:34 PM Rick Ulland <rickulland1 at gmail.com> wrote:

> Important to note the time display is not the clock. The actual clock
> uses a one byte value for year,and the OS9 system read and set calls
> F$STime and F$Time deal with the correct number. Hardware clocks all?
> worked by setting the software clock using the (good) OS9 system calls,
> if the drive did the year as math, things might just work. I remember my
> Dallas RTC kept going and I was not running Nitros9.
>
> Two big bugs in 2.0.1:
>
> The 'date' command should display (1900 + clock year), but it doesn't do
> the math, it prints a fixed string "19" then the clock year. Data is
> fine, but looks weird.
>
> The 'setime' utility ignores the problem by only accepting 2 digits for
> a 1 byte value. If you don't have a hardware clock, no way to set the year.
>
>
> If these two utility programs were tweaked, you would be good until
> 2154. This must have been done by somebody. I'll poke around here.
>
>
> -ricku
> CoNect
>
>
>
> On 4/28/20 8:22 AM, phil pt wrote:
> > 'The correct format is yyy-mm-dd hh:mm:ss
> >
> > <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
> >
> > Virus-free.
> > www.avast.com
> > <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> >
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > On Tue, Apr 28, 2020 at 8:58 AM Alex Evans <varmfskii at gmail.com> wrote:
> >
> >> I'm not sure what you want to patch the clock to do. The way I see it
> >> is that you can wither leave the clock alone and patch the utilities
> >> that misinterpret the system time, or patch the utilities that
> >> misinterpret the system time. Now, the matter is different when you
> >> start talking about dealing with modules that support hardware RTCs.
> >> Look at it this way, the current clock module (60Hz, but I assume 50Hz
> >> is the same) will roll over from 99-12-31 to 100-01-01 and would store
> >> the current year as 120 (the epoch is 1900). What do you think the
> >> system should store the current year as, and how do you intend to
> >> manage this by only patching the clock module?
> >>
> >> On Mon, Apr 27, 2020 at 8:57 PM phil pt <ptaylor2446 at gmail.com> wrote:
> >>> I think the best way to resolve this issue is to patch the clock on the
> >> old
> >>> Os9 Level 2 and use that. This way I do not have to make several
> hundred
> >>> lines of changes in the code.
> >>>
> >>> <
> >>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
> >>> Virus-free.
> >>> www.avast.com
> >>> <
> >>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> >>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >>>
> >>> On Sun, Apr 26, 2020 at 10:34 PM Bill Nobel <b_nobel at hotmail.com>
> wrote:
> >>>
> >>>> Well to tell the truth the only place that exists nowadays is in the
> >>>> original code.  Over time Clock got split between to modules. First
> >> being
> >>>> the base, then the second became hardware specific for each type.
> I’ve
> >>>> been getting it put back to one for the level3 mods from Allan DeKok.
> >>>>
> >>>> Sent from my iPad
> >>>>
> >>>>> On Apr 26, 2020, at 12:29 PM, phil pt <ptaylor2446 at gmail.com> wrote:
> >>>>>
> >>>>> Is there any patch to the clock on the old os9 level 2 so the date
> >> would
> >>>>> work as yyyy/mm/dd Hr:mm:ss?
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> <
> >>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
> >>>>> Virus-free.
> >>>>> www.avast.com
> >>>>> <
> >>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> >>>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >>>>>
> >>>>> --
> >>>>> Coco mailing list
> >>>>> Coco at maltedmedia.com
> >>>>> https://pairlist5.pair.net/mailman/listinfo/coco
> >>>> --
> >>>> Coco mailing list
> >>>> Coco at maltedmedia.com
> >>>> https://pairlist5.pair.net/mailman/listinfo/coco
> >>>>
> >>> --
> >>> Coco mailing list
> >>> Coco at maltedmedia.com
> >>> https://pairlist5.pair.net/mailman/listinfo/coco
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> https://pairlist5.pair.net/mailman/listinfo/coco
> >>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>