🚀 go-pugleaf

Lately I have been messing around with some stuff using TCC -S to make .ASM
output, then using TASM, TLINK, EXE2BIN, then REN file.BIN file.EXE....in
that order.  However....

I wrote a real simple program in inline assembly that saves your cursor
size, turns off the cursor (via setting the size to zero), swaps pages
to a blank page (arbitrarily it is page 2), then waits for a key to be
pressed...when a key is pressed, the cursor is turned back on and the page
swapped back to 0.

After I compiled this program using TCC -f- -mt -lt to produce a COM file
it came out to ~3000 bytes.  Next I did TCC -f- -mt -S, TASM OFF.ASM, then
TLINK OFF.ASM.  This resulted in an .EXE file of about 549 bytes.  I
then ran it through EXE2BIN, renamed the BIN file, then had a 37 byte
.COM file that WORKED!  Not bad for not really knowing 80x86 asm!

Anyway, after I had this wonderful experience using C as a shell of sorts
around assembly (let the C compiler do setup and clean up), I tried
converting an old program of mine, NMORE.C, that replaces the DOS MORE.COM
file.  The only difference is that it can page up a file and you use it
directly (NMORE FILE.TXT) instead of only as a pipe.

However, when I did the EXACT same routine as I listed above, I had no
errors whatsoever.  But it won't work.  It locks the machine up.  Is there
ANY reason that doing what I did with OFF.COM would not work with
NMORE.COM?  Here are the specifics:

NMORE.C:

Some C and assembly routines, 1 source file
NMORE.C does not containt ANY external routines..examining the .ASM output
confirms this.
TCC -mt -lt -f- NMORE.C works perfectly
TCC -mt -f- -S NMORE.C works just fine to produce .ASM
TASM NMORE.ASM does NOT produce a working EXE file, and changing it to
a .COM file does not help....


To sum, why would using TASM to compile .ASM files generated by TCC -S
NOT work?

Thanks for any help,

Brian