Hi Jerome,

if you are worried about collisions, use AMIS int 2d.
Overhead is low and it is less crowded than MUX int 2f.

RBIL was famous enough to make AMIS more widespread. FreeDOS is too
niche to re-invent that wheel and declare int 2b to be a new trend.

Why would your RESIDENT driver have to do install checks?
You can do those in the TRANSIENT part and just store the
results as static data in the resident driver part.

So the risk of wasting RAM by using AMIS are minimal :-)

I agree that MUX can get crowded. However, for disk I/O,
the actual I/O still is the main bottleneck (unless you
are a large cache with a very inefficient algorithm) and
you would not do install checks for each invocation anyway.

One example of slow call chains which you can feel may
be old ANSI variants and slow system and VGA BIOS. But
that was long ago and even those were not THAT slow.

AMIS can be expected to be much faster than MUX and it
will not be in the way for your CDEX performance either.

If you want to avoid the hassle of scanning for a free
magic number, I would just hardcode one. Collision risk
will still be lower than when grabbing the whole int 2b.

I agree with Tom: Use int 2d, it is the better choice and
2023 is not the year for MORE standards for simple things.

Regards, Eric

Freedos-devel mailing list

Reply via email to