🚀 go-pugleaf

In article <1353@datmuc.UUCP>, vincent@datmuc.UUCP (vincent) writes:
|> In article <smithbm.722096804@craft.camp.clarkson.edu> smithbm@craft.camp.clarkson.edu (Azrak) writes:
|> >c.brennan@student.utas.edu.au (chris brennan) writes:
|> >
|> >>In article <smithbm.721597007@craft.camp.clarkson.edu>, smithbm@craft.camp.clarkson.edu (Azrak) writes:
|> >>> 
|> >>> vincent@datmuc.UUCP (vincent) writes:
|> >>> 
|> 
|> Lots of stuff deleted.
|> 

Suggestions
1) My attempted mail to you bounced.
2) you don't need the CODESEG in the tsrstack declaration, it may be
   confusing the compiler.
3) you need to keep a flag or counter for int 8, it is quite possible
   for an int 8 to happen while your int 8 code is executing.
4) your calculation for malloc is off, you allocate tsrstack to be
   0..1023, then assign the stack to be at 1024.
5) you might want to simply declare an array or use some other method
   for keeping the stack, the malloc method doesn't strike me as being
   very stable accross compilers and compiler releases.
6) alt.msdos.programmer is not a valid group

Good Luck.

-- 
Ralph Trickey       | (513) 865-6800                  |    	
Mead Data Central   | x4870                           |  Disclaimer
P.O. Box 933        | ralpht@meaddata.com             |  My opinions are my own
Dayton, Ohio  45401 | ...!uunet!meaddata!ralpht       |