🚀 go-pugleaf

I recently went with great trepidation into the .txt file which assigns 
compilers to various file extensions and persuaded TSV3 to use MASM for 
compiling .asm files. It works a treat. I even patched masm so the error 
messages come up in window 0. Wonderful.

I need, from time to time, to produce little DOS device drivers. At 
present I have to go and do this in Borland C, and it's a pain in the 
butt. 

The only real reason for using C is that the front end of a device driver 
must have a small table of values on it, describing itself. With tlink I 
can control the link order. M2V3 programs  always start with whatever 
gets linked in first.
 
Peering into the same .txt file, I see stuff which can be paraphrased as 
"for a DOS exe file, link in initexe first"

Has anyone ever fiddled with this stuff, for instance to add a new file 
type "sys", which says " for SYS files, link in driver.obj, and link 
initexe.obj too".
Then in driver.obj I could use "extrn fred", where fred some label in 
initexe, to ensure initexe gets called. 

That would allow me to write my device drivers in M2, and my head could 
cool down a bit.....

David.