Sender: vheyndri AT rug DOT ac DOT be
Message-Id: <353C6A0E.D68@rug.ac.be>
Date: Tue, 21 Apr 1998 11:42:38 +0200
From: Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
Mime-Version: 1.0
To: Andris Pavenis <pavenis AT lanet DOT lv>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: Temporary files for gcc-2.81
References: <199804201720 DOT TAA55456 AT ieva06 DOT lanet DOT lv>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Andris Pavenis wrote:
> The best solution would be to implement some PID that would good enough.
[snip]
> So I can mention some possiblities with my comments:
>    -  _my_cs   - Is not usable under Win95. If I start 2 DOS sessions and
...
>    -  base address of _my_cs selector accessible through
...
>    -  reading time (biostime()). Perhaps this is only slightly better than nothing
...

There was recently a discussion about what would be a good PID here at
d-w (mainly under the subject of the temp functions).

I have a perfectly working and tested PID code available, but I need to
know whether it is acceptable to put that code in the stub (it really,
really, really needs to run in real-mode). Question is: is every
coff-image started with a stub, i.e. can a coff image been run without
one? I've been writing my own stub.asm (nearly 1/3 finished) but started
wondering then.
 
-- 
 \ Vik /-_-_-_-_-_-_/   
  \___/ Heyndrickx /          
   \ /-_-_-_-_-_-_/