On 12/12/20 10:52 pm, Stephen Adolph wrote:
*7FECH* *(7EH)* *MOV A,M* *!! Can't take an interrupt here, if we change
the hook itself!!!*
*7FEDH* *(23H)* *INX H* *
*7FEEH* *(66H)* *MOV H,M* *
*7FEFH* *(6FH)* *MOV L,A*
At 7FEC, the software hook data is read not as a single
I've played with crdfil.rom a little with my m100+REX, it seemed to work fine.
I really liked it, just didn't have much need.
You need a regular Intel HEX file to binary converter... That would depend on
what OS you use...
Or you can grab it at
Hi folks,
I've been having a blast playing with my REX and NADSBox this past week, and
I've been going through the different ROM files that are available via the
Wiki. I noticed that club100.org has the "Card File" ROM available for
download, but this isn't one of the ROMs available with the
Hi, wondering if anybody else has had this odd thing happen. I noticed a while
ago that the battery statistic information in my NADSbox has become corrupt, or
at least I assume that's what has happened. The "Bat Date" field was showing
the current date (even though I had not changed the
Hi John,
I guess I should clarify.
When REX is operating, I must have the interrupts enabled, so the Timer
hook can be used to grab control automatically , and do the ROM selection
and a bunch of other things.
So, if an RST 7 call happens to be in process when the timer hook fires,
disabling
Hi Steve --
" The M100 during normal operation isn't in disabled state."
Right. Otherwise, interrupts would be broken.
"In fact I am relying on the TIMER hook to enable all those functions of
REX -* so the timer hook has to happen."*
Not sure I understand what you're saying.
The code you
Hey Steve,
It's nice to hear that VirtualT continues to be useful for you! It's
always great to hear as a developer that your stuff is being used. I
think VirtualT is probably the most used thing I have developed, even
including my professional career. :)
Ken
On 12/12/20 4:22 AM,
;) No, not quite.
The M100 during normal operation isn't in disabled state. In fact I am
relying on the TIMER hook to enable all those functions of REX - so the
timer hook has to happen.
What I have to do is, when a TIMER interrupt occurs, I need to peer back up
the stack and deduce where the
Nice *DI*gression, Steve. So is that the fix for you - DI on the REX
side whenever you're writing a hook?
Philip
On 13/12/2020 1:22 am, Stephen Adolph wrote:
I've been on a deep dive lately, integrating my early VT100 video
driver into REX# and REXCPM. It has been a marathon of reverse
I've been on a deep dive lately, integrating my early VT100 video driver
into REX# and REXCPM. It has been a marathon of reverse engineering,
troubleshooting and testing. All good, coming together well.
The purpose of this note is to highlight the value of Virtual T, for me.
REX generally gets
10 matches
Mail list logo
