Hi Sylvain,
SL>  Maybe in a near future. What about SGI computers?
At the rate things are happening.... anything is possible....
SL>  > available for calling functions yourself. The best method is
SL>  > to set aside memory in your TSR for your own stack operations.
SL>  > (just to play it safe)
SL>   Saving SS and using own?
Save the ss and sp to some place, then load values that represent
an area that you have defined in your TSR for that....
SL>  > To be honest.... Don't make assumptions about DOS.... it
SL>
SL>  Yes, but those guys who created these good tuturials looks very neat.
SL>  I guess don't trust in anyone apply here :)
Not exactly. Writing TSR's and writing about them are two different
things.
SL>  > "single task" operating system. By writing a TSR, you are
SL>  > circumventing around DOS
SL>  All device drivers are TSR. And there are many for each OS.
That's not exactly true.... A device driver is structured by design
for the operating system. It has criteria in it's makeup for that.
When a device driver is called, it isn't stopping another program
somewhere during it's operation and in an unknown state. A device
driver is called by programs. The program that's calling it is in
a known state of operation.
SL>  Do you have a tutorial by dave williams? Mime is like a bit too old.
Actually, I tossed my tutorials long ago. I get new references.
Chip data books, interupt listings, little bits of code here and there.
I spend quite a bit of time just coding first one thing or another.
glen
--- ProBoard v2.15 [Reg]
---------------