Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: A little help please...
Message-ID: <91472@sun.uucp>
Date: 28 Feb 89 01:29:29 GMT
References: <12492@gryphon.COM>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 27

In article <12492@gryphon.COM> ddave@pnet02.cts.com (David Donley) writes:
->OK, I am having several small problems.  First of all, I have two programs.  A
->program A and a program B.  It appears that if program A has the serial.device
->allocated in an exclusive manner, and program B tries to open it once,
->everything is fine, and program B is locked out and errored.  If program B
->tries to open it twice, it opens!  I can't figure this out, and for all I
->know, it may just be something stupid I'm doing.

When you fail do you go ahead and close it? If so you may be closing the
serial.device out from under your other program.

->I want an interrupt to render graphics into a RastPort inside a window.  I
->need to know when the layer is locked, so I won't draw into it and cause a
->lockup/crash/guru whatever.

Have your interrupt routine signal a "drawing" task and then return. You
should never draw from within the interrupt routine. 

->I want to know how to allocate my own stack for a C program.  

Excellent article by Bryce Nesbitt in the various Amiga mails and in 
various archives. 


--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.