[RC5] DOS Client

Adam C Luter gryn at gryn.dyn.marko.net
Thu Apr 15 15:36:02 EDT 1999

On Wed, 14 Apr 1999, Hugo Villeneuve wrote:

> It can't be done. In DOS there is only one process running at any time
> (the foreground process or command.com). TSR stay in memory but doesn't
> get any processor time. 
> They can attach themself to IRQs so that they can get executed when an
> external event trigger an IRQ, the CPU then drop every thing he's doing
> and execute the code.
> Or they modify or add entries to the dos interuption table to make their
> services available for other program. Other program have to call the
> interuption to get the service. A lot of services are made available in
> this way by the DOS.
> I could be wrong, I'm not an expert.
> Hugo Villeneuve
> (with d.net since February 1998)

you -could- do it.  but the thing is, it would most likely screw more
things up then you'd like.  you'd either have to make a compromise on
speed (of both the computer and your client), or do as you suggest, with
letting the program call rc5des.  -or- you could setup a mini
taskswitching environment, which would "work best" but cause the most
problems :) hehe.


To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest

More information about the rc5 mailing list