I just looked on my dosbox, my 475 size com uses 0kb, its using 0x12 paragraphs, so just over 256 bytes..

ok I realised what your seeing, the line 136 should be

mov dx,setup_isr ;; already aligned correctly for tsr
shr dx,1
shr dx,1
shr dx,1
shr dx,1

I checked my original, yeah copy pasta error from hacking my uansi driver up for you. if you have umb its fine 😀

Okay, I will patch the code once I have access to my own pc and check again. 😀

@bloodycactus:
I added the missing lines, it works as expected now.

BloodyCactus wrote on 2021-07-27, 22:23:

I just looked on my dosbox, my 475 size com uses 0kb, its using 0x12 paragraphs, so just over 256 bytes.. […]
Show full quote

I just looked on my dosbox, my 475 size com uses 0kb, its using 0x12 paragraphs, so just over 256 bytes..

Screenshot_2021-07-27_18-22-00.png

ok I realised what your seeing, the line 136 should be

mov dx,setup_isr ;; already aligned correctly for tsr
shr dx,1
shr dx,1
shr dx,1
shr dx,1

I checked my original, yeah copy pasta error from hacking my uansi driver up for you. if you have umb its fine 😀

hi, sorry for bringing up a nearly old post.
is there a license or a name I could cite for this TSR shell?

I'm in the middle of writing up some ms-dos code for a Timestamp Counter based delay function/frame/tick-timer
and would eventually like to make a TSR/DOS API with for patching older speed sensitive games.

a NASM skel like this is pretty much perfect, cheers

nah I'm not worry, call it PD 😀 use it as you will, its all cool.

just make sure you get the little patch I put above for fixing the memory
Re: Writing a TSR for memory dumping.

@slartibardfast0: license? Nah, just leave a little positive feedback or a link to my project.

Thanks @BloodyCactus got that patch running. ahh cheers, this is great, will save a lot of time.

@Peter Swinkels I'll be sure to reference your TSR on github when I've something up there too

@slartibardfast0: that would be appreciated!