Joshua O'Keefe wrote:
> After cutting out (and not replacing) the battery, the machine
> starts, prints the menu, and then freezes. In this state the
> clock is not advancing.
My second M100 has this exact problem.
I found out that the pin 10 of M18 (D1990AC) wasn't outputting a 256
Hz clock like
Peter Vollan wrote:
> My Model 100 keeps getting into that state where the menu items call up the
> wrong program. Why does this happen?
I did have the same problem for a while.
I kept refreshing the memory from a REX backup, but after a few days
the problem was back.
I thought it was my fault at
test
On Wed, 12 Jan 2022 at 11:48, John R. Hogerhuis wrote:
> You didn't say if you tried forcing a cold start.
>
> That's a normal thing to do any time you get weird behavior that might be
> due to corrupt system variables or data structures.
>
> That said, maybe without a battery a system does
You didn't say if you tried forcing a cold start.
That's a normal thing to do any time you get weird behavior that might be
due to corrupt system variables or data structures.
That said, maybe without a battery a system does cold start every time
power is first connected.
-- John.
