Shalaev 2.06 + time

Has anyone from the olla encountered such a phenomenon as time running ahead
during the work of a subject? Or do I have a unique copy? Of course, it doesn’t
register in CMOS, just reboot (or, for example, start UKV) and everything
will be ok, but it’s still unpleasant...

See you later, All! Vova. WBR.
[Team·ZX·ASM]∙[Team·Me┼a║ica]

Hello, Vova!

It’s quiet outside the window, and I’m sitting and writing a response to a letter written from Vova Hex to All
Mon Mar 10, 1997 at 15:19...

VH> Has anyone from the olla encountered such a phenomenon as time running forward
VH> while the subject is running? Or do I have a unique copy? Of course, it doesn’t register in CMOS
VH>, just reboot (or, for example, start UKV)
VH> and everything will be ok, but it’s still unpleasant...

And exactly in Shalaev? Because this is exactly the behavior of the watch that I
observed after using the Lunter one, which was adapted to tr-dos.
I did not find the answer. ;(

With all kinds of regards and wishes.
Igor.

... Sometimes nothing is so far from honor as the honor of the uniform.

IG> And exactly in Shalaev? Because this is exactly the behavior of the clock that I
IG> observed after using Lunter's, which was adapted to tr-dos.
IG> I did not find the answer. ;(

Likely in Shalaev. I only use it and UKV. By the way, UKV
`restores time`.

See you later, Igor! Vova, WBR.

Theoretically, the emulator should reprogram the timer for itself, which
is actually used by DOS to count time (Lutner's emulator does just that, Shalaev's - I don't know). The result may be some inaccuracy of the clock - due to the partial loss of interrupt returns to the DOS handler
(or vice versa :).
But, IMHO, this should not get into CMOS, and after a reboot the time can
be restored...

Andrew