Path: utzoo!attcan!uunet!samsung!usc!zaphod.mps.ohio-state.edu!wuarchive!udel!princeton!siemens!demon!jrv
From: jrv@demon.siemens.com (James R Vallino)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: TSR's with no assembly language
Message-ID: <28050@siemens.siemens.com>
Date: 9 Apr 90 14:39:20 GMT
References: <27810@siemens.siemens.com> <127@demott.COM>
Sender: news@siemens.siemens.com
Reply-To: jrv@demon.siemens.com
Organization: Siemens Corporate Research, Inc.
Lines: 23

In article <127@demott.COM> kdq@demott.COM (Kevin D. Quitt) writes:
>In article <27810@siemens.siemens.com> jrv@demon.siemens.com (James R Vallino) writes:
>
>>There is at least one potentially fatal flaw in writting interrupt routines
>>"without a drop of assembly" using MSC or QuickC.  The last time I checked I
>>could not find anyway to switch to a local stack while executing the
>>interrupt.
>
>    MSC 5.0 and beyond have Memory model customization swicthes that
>lets you select a separate stack segment.  RTFM User's Guide, 6.5.3

If there is anyone who can show me the method to use a local stack when my
MSC "all C" interrupt is called I would be most appreciative.  As far as I
can determine the compiler flags which are desribed in User's Guide, 6.5.3,
do didly to allow you to control your stack within the interrupt routine.  (I
already had read the manuals and the README file where the interrupt
attribute is described.  Flame withheld.)  I still stand by my statement that
interrupts in MSC "without a drop of assembly" are potentially dangerous.

Jim Vallino	Siemens Corporate Research, Inc., Princeton, NJ
jrv@demon.siemens.com
princeton!siemens!demon!jrv
(609) 734-3331