Chromedome45
Veteran Member
Rev a. Ok I checked the maintenance bulletins and all the rev a mods are done.
Last edited:
Forgot about that. OK, That's not the problem. I would get a copy of the diag disk as NF6X suggested as a start.Remember this used to run Xenix 3.x! So it has the right PAL's in it. Had it installed on the hard drive and booting Xenix.
I'm also curious about the specific hardware behavior that triggers the "bughlt no68k" error message. But unless one of the original Xenix developers drops in here, the only way we're likely to figure this out would be by reverse-engineering the code, and that task is probably a bit too advanced for me at this time.
The one person to ask would be Frank Durda IV, as he maintained the z80ctl codebase. And due to Bob Snapp making Tandy Support's job more difficult, Frank put in intentionally obfuscated code to try to thwart patching of z80ctl (even if Snappware's software was at fault, customers demanded that Tandy fix the problem; there's a post on comp.sys.tandy out there detailing that frustration). Frank is very busy these days, and likely wouldn't have the time to try to dig that source up (he has sources of z80ctl on 8 inch disks). Oh, and one thing to know about Frank: the more people ask him about something, the less likely that he will actually do that something (he said as much in multiple comp.sys.tandy posts over the years; while Frank is a nice guy and his information is golden, he has a very low tolerance for people making too many requests of his free time.
Reverse engineering of z80ctl will be absolutely required for any patching of the hard disk driver in Xenix to use the Lo-Tech IDE solution.