I'd be curious to see how you are estimating the clock speed. Just a simple machine language loop?
It would be interesting to see how emulators compare and to test them against both the M100's internal sense of time and objective "wall time". For example, I expect MAME will have the best match to the internal clock and worst match to actual time. Virtual T seems to have a reasonable clock for the M100, but it is slightly off for the T200. I'm not sure how Virtual T's clock works. It seems to magically sync with the host computer's time, but does that only happen at start-up or is it replacing the M100's time-of-day clock completely? --b9 On November 12, 2026 12:31:53 PM PST, "John R. Hogerhuis" <[email protected]> wrote: >On Thu, Nov 12, 2026 at 11:45 AM Daniel L <[email protected]> wrote: > >> >>> How did it turn out? >> >> daniel >> sysop | air & wave bbs >> finger | [email protected] >> > >Thanks for asking Daniel. Still working on it... went on a sidequest of >fixing several little emulator bugs and creating more software tools. I had >no idea the "undocumented instructions" were finally completely reverse >engineered with a microscope (Shirriff)! Simplifications, little details >with undocumented flag behavior that the giants didn't figure out in 1979, >and whatnot. > >Anyway, almost back to the clock stuff. > >-- John.
