Re: not really an Ada question

[Charles Hixson <charleshixsn@earthlink.net>]

What are you doing in the spawned (ok, not task) process?  If I remember
correctly, whenever Win95 calls on a 16-bit system routine, it goes into
single executable thread mode... I'm a bit vague on the details here
(answering my question won't mean much to me!), but I am sure that there is
only one 16-bit thread, that is shared by all of the 16-bit processes that are
running.  So you could easily be colliding with yourself if you make any
system calls.

Ehud Lamm wrote:

> On Wed, 16 Feb 2000, Ehud Lamm wrote:
>
> |On Wed, 16 Feb 2000, Robert Dewar wrote:
> |
> ||Why doesn't GNAT.OS_Lib.Spawn do the job (don't overlook the
> ||stuff in GNAT.*, there is useful stuff there :-)
> ||
> |
> |funny. I am a great fan of the GNAT.* packages. Strange I didn't think of
> |checking there this time! I will, now!
>
> Well I tried using non_Blocking_Spawn - as this seems the thing I want,
> right? I want the next spawn to work in such a way that the two programs
> will work side by side.
>
> Well this is not what happens.
>
> To be concrete: the program I execute is a simple prgram create using
> GNAT, toom that loops printing a word to the screen and delaying.
>
> I am pretty sure the issue here is how Windows works, not Ada - but any
> clue will be recieved gratefully.
>
> Ehud Lamm mslamm@mscc.huji.ac.il
> http://purl.oclc.org/NET/ehudlamm <== My home on the web
> Check it out and subscribe to the E-List- for interesting essays and more!