There are a set of changes to the T102 ROM that make it, in small ways, different from M100.
One of those changes must be getting used incorrectly. Analyst appears to use the main ROM at 0x4994 (USING function) just before it crashes out. I can't really see the problem though. On Sat, Mar 18, 2023 at 8:22 AM Justin Poirier <gen.ele...@gmail.com> wrote: > Interesting. I only have CloudT and T102 findings to report. It sounds > like VirtualT emulates a M100, and I do have an M100, but the option ROM > socket was *MANGLED* by its previous owner. Since I have a real ROM burned, > I might try to fix the socket (or hardwire it in if it comes to it) and see > how it performs on M100 hardware. Are the M100 and T102 fully > ROM-compatible? As in they have the exact same libraries at the exact same > memory locations, or are they different in some ways. I believe I remember > some rumblings about how the ROM socket may have had a slightly different > pin-out allowing for auto-start ROMs or something, but I'm not sure how far > the other differences go. Maybe this really is an M100-only ROM? That would > be a bummer. > > —Justin > > On Mar 18, 2023, at 12:45 AM, John R. Hogerhuis <jho...@pobox.com> wrote: > > > > On Fri, Mar 17, 2023 at 9:25 PM Stephen Adolph <twospru...@gmail.com> > wrote: > >> additionally, earlier tonight I DID get the same error message, using the >> real ROM on real T102 hardware. >> >> AHAH! >> Business Analyst ROM works on M100 only! >> >> Isn't that odd, wonder why. But, this appears to be confirmed in >> VirtualT as well as on real hardware. >> >> Steve >> >> >> > First theory would be some m100 ROM dependency on the opt-rom installation > code which differs by model. > > -- John. > > >
