NODE 1e2416a3Re: CryptoStacker Update
Jonathan K Saville <ee92jks@brunel.ac.uk>Thu, 10 Jun 93 11:07:37 PDT
Re: possible problems with INT13
I may be mistaken, but I have this feeling that DPMI servers (including
MS Windows) react unkindly to people using INT13. This is certainly what
the Borland Open Architecture handbook says. If your program is resident
when such a server is running, it could throw up a General Protection
fault. I will check into this myself...
--
# Jon Saville | Who alive can say, 'Thou art no John Keats
# ee92jks@brunel.ac.uk | Poet, may'st not tell thy dreams?' 1819
PGP 2.2 public key available upon request
NODE 30e8231eRe: CryptoStacker Update
RYAN Alan Porter <ryan@rtfm.mlb.fl.us>Thu, 10 Jun 93 13:56:27 PDT
On Thu, 10 Jun 1993, Jonathan K Saville wrote:
>
> Re: possible problems with INT13
>
> I may be mistaken, but I have this feeling that DPMI servers (including
> MS Windows) react unkindly to people using INT13. This is certainly what
> the Borland Open Architecture handbook says. If your program is resident
> when such a server is running, it could throw up a General Protection
> fault. I will check into this myself...
The programs running on the system will not be using INT13. They will use
the higher level interrupts that they normally use. The block driver
exists below all of that and merely controls what happens once the higher
level interrupts already call INT13.
I don't think that it will be any problem, certainly less of a problem
than if I tried to screw with higher level interrupts.
-=Ryan=-
the Bit Wallah