🚀 go-pugleaf

	I have an interrupt service routine which is linked with
	my Microsoft 'C' application program. When the program is started
	it installs the pointer to the service routine in the vector table.
	As soon as the first interrupt is generated I get a stack overflow 
	message on the screen and the system hangs. If I disable the external
	interrupt source everything works fine. Sounds like a problem in the 
	interrupt service routine.

	History:
	This service routine is written in assembler and works fine when
	linked with compiled MS basic. To link with 'C' I changed it
	to assume the _TEXT segment for code and DGROUP for data, bss, and 
	stack, as per the Microsoft 'C' manual. I allocated more stack during
	the linking phase but that didn't seem to help.

	One thing that I'm doing that may be a problem is the way I
	install the interrupt vector. Rather than using the get/set interrupt
	vector functions in DOS I just poke the segment and offset into the
	vector page at address 0x2c (IRQ3). I don't understand why this should 
	cause a problem.  I did it this way with the compiled basic version.


	Is there anything special I need to do when installing a
	interrupt service routine which is  used by a Microsoft 'C'
	program. Any comments or code examples would be welcome.


					Thank You,
				
					John Antrosiglio
					ATT-Bell Labs
					ihnp4!hou2f!jca