🚀 go-pugleaf

In article <Dq024M.3Hu@cix.compulink.co.uk>
           dcollier@cix.compulink.co.uk "David Collier" writes:

> 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.

Yes, also useful to integrate the OS2 resource compiler too.

> I need, from time to time, to produce little DOS device drivers. 
> 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".

I don't see why you couldn't give it a try. It'll be interesting :-)
Do you have the source code kit available ?    
initexe.a isn't all that long, so you have a sporting chance of 
creating an initsys.a based on it. I suspect the hardest part
will be tricking the TS linker and memory models into doing what
you want for a valid SYS file. 

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

Be interested if you make it work!

Good luck!
Martin
-- 
Martin Brown  <martin@nezumi.demon.co.uk>     __                CIS: 71651,470
Scientific Software Consultancy             /^,,)__/