1. exiting a program without terminating
Hi all,
Can anyone tell me how I could execute a program and exit it without
terminating the application?
Yeah, I know about TSR's, but I'm hoping there is an easier way.. or does
that mean threading?
Or... is it possible somebody could explain to me how to implement a TSR.
I have Ralph Browns interupt list, but it is pretty difficult to follow. I
understand the majority of it, but I have troubles with the data structures
that need to be passed.
Using the segment and far addreses confuses me completely.
Also, all the TSR interupts that I found in the interupt list seemed to be
all dos interupts, is this right?
Is there a different method of setting up a TSR for Linux?
I could probably get away with just setting up an interupt handler, but that
is just as confusing as TSRs. I've looked at the demos for interupts that
came with EU, but they weren't too helpful.
I'm not too keen on experimenting with the interupts. Especially for things
like that.
I already messed up my monitor on my old computer playing with the video
interupts. :(
TIA
Chris
2. Re: exiting a program without terminating
On Thursday 16 August 2001 04:40, Chris Bensler wrote:
>
> Hi all,
>
> Can anyone tell me how I could execute a program and exit it without
> terminating the application?
> Yeah, I know about TSR's, but I'm hoping there is an easier way.. or does
> that mean threading?
>
> Or... is it possible somebody could explain to me how to implement a TSR.
> I have Ralph Browns interupt list, but it is pretty difficult to follow. I
> understand the majority of it, but I have troubles with the data structures
> that need to be passed.
> Using the segment and far addreses confuses me completely.
> Also, all the TSR interupts that I found in the interupt list seemed to be
> all dos interupts, is this right?
> Is there a different method of setting up a TSR for Linux?
Linux is a true multi-tasking os. Chances are there are 50 to 100 tasks
running on yours right now. There's no need TSR's. Just run your
program with a '&' following the name, and it will run in the background,
leaving you with an immediate prompt so you can do something else.
example: exu factorial &
returns:
[1] 7643 -- < 1 is the job (for this user) , 7643 is the process number.
Type fg 1 to bring that job back to the screen.
A TSR would be little use on Linux (or Windows) since you don't have
access to the hardware. So that rules out things like watching
for a certain keypress in your TSR, and doing something with it.
> I could probably get away with just setting up an interupt handler, but
> that is just as confusing as TSRs. I've looked at the demos for interupts
> that came with EU, but they weren't too helpful.
What is it you are trying to do?
Regards,
Irv
3. Re: exiting a program without terminating
> Linux is a true multi-tasking os. Chances are there are 50 to 100 tasks
> running on yours right now. There's no need TSR's. Just run your
> program with a '&' following the name, and it will run in the background,
> leaving you with an immediate prompt so you can do something else.
> example: exu factorial &
> returns:
> [1] 7643 -- < 1 is the job (for this user) , 7643 is the process
number.
>
> Type fg 1 to bring that job back to the screen.
>
> A TSR would be little use on Linux (or Windows) since you don't have
> access to the hardware. So that rules out things like watching
> for a certain keypress in your TSR, and doing something with it.
>
> > I could probably get away with just setting up an interupt handler, but
> > that is just as confusing as TSRs. I've looked at the demos for
interupts
> > that came with EU, but they weren't too helpful.
>
> What is it you are trying to do?
I'm am trying to devise a mechanism for writing and using dymically included
executable (bound) eupohoria files.
There is a library in the archives already for creating such a thing, but
I'll be damned if I could figure it out.
My plan is to have two include files. One is the 'server' which is included
in the application and controls any open dynamic lirbraries, and the other
is the 'client' which is included in the dynamic library file itself.
I have most all of the details worked out except how to load the client into
the background, to poll for a calls from the server.
This means the method of loading the client into the background, should be
the same for either platform. Or at least possible on either.
Chris
