Ok here's the backstory. You know I have an nsc800 based machine.
Well I am debugging a really strange problem, and I suspect there is a hidden undocumented opcode happening. I imagine that it is one of those strange fall through code snippets, with something nonsensical but benign. Such code approaches make disassembly pretty hard. I think the nsc800 is having a bad reaction to such a piece of code. So my theory is to run virtualt with all undoc opcodes set to hALT. Since there are no formal uses of undoc opcodes in m100 rom, if I am right the 8085 will halt where the nsc800 gets tripped up. On Saturday, December 14, 2024, John R. Hogerhuis <[email protected]> wrote: > What is FL? If that's from fltk it wouldn't be in the source tree since > it's a library. > > Also what does it mean to run with no undocumented opcodes? If the > processor sees one of the undocumented opcodes what will it do instead of > the regular behavior? > > -- John. > > On Sat, Dec 14, 2024, 5:29 PM Stephen Adolph <[email protected]> wrote: > >> As said, I am trying to build virtualT on windows 10 using >> Microsoft Visual Studio Community 2022 (64-bit) - Current >> Version 17.4.5 >> >> I keep getting this error: >> >> Error C1083 Cannot open include file: 'FL/Fl.H': No such file or >> directory VirtualT E:\dev\virtualt-src-v1.6\src\watchtable.cpp 30 >> >> This file indeed seems to be missing and is not in VT1.6 source either. >> >> Any suggestions? >> thanks >> Steve >> >> >> PS - why ? because I want to run the 8085 in VT with "no undoc opcodes" >> by modifying >> >> do_instruct.h >> >> >
