> Sometimes, I suffer from a severe lack of trust in other
> programmers. I look at the "Install Check" and see only specific
> registers are to be modified and no others are to be destroyed. But
> in my head, I think that someone out there may think it is a good
> idea to save some time by
Hi ecm,
> On Apr 24, 2023, at 12:57 PM, C. Masloch wrote:
> [..]
>
>> 2) We could walk the device driver chain. Thats fairly straight forward and
>> easy enough to implement. Lets do that… Hmmm, not all device drivers are
>> showing up in the chain and logger is not being seen. Let’s not
> For fun, I implemented initial versions of both the 0x2b interrupt
> hook and a partial 0x2d implementation to locate the Logger device
> driver.
>
> The 0x2d version is very bare bones and does not include several
> functions required to be fully compliant. It only responds to the
> install
(Replying to multiple mails again.)
On at 2023-04-21 19:03 -0400, jer...@shidel.net wrote:
Hi Tom,
On Apr 21, 2023, at 2:01 PM, tom ehlert wrote:
Hi ecm,
[1]:
https://gitlab.com/DOSx86/logger/-/blob/aae3dfddcdacfea18950a96ce9449767c20b2d66/source/logger/common.inc#L267
this got me
Hi All,
For “fun”, I implemented initial versions of both the 0x2b interrupt hook and a
partial 0x2d implementation to locate the Logger device driver.
The 0x2d version is very bare bones and does not include several functions
required to be “fully compliant”. It only responds to the install
Hi Tom,
> On Apr 21, 2023, at 2:01 PM, tom ehlert wrote:
>
> Hi ecm,
>
>
>> [1]:
>> https://gitlab.com/DOSx86/logger/-/blob/aae3dfddcdacfea18950a96ce9449767c20b2d66/source/logger/common.inc#L267
>
> this got me looking into this 'too slow' detection method.
> and it is indeed slow. as in
Hi,
> On Apr 21, 2023, at 12:43 PM, C. Masloch wrote:
>
> I'm responding to all of your mails (Jerome's) so far.
>
> On at 2023-04-21 06:55 -0400, jer...@shidel.net wrote:
>> Hi All,
>> At present, the interface program for Logger just performs a slightly
>> optimized brute force search for
Hi ecm,
> [1]:
> https://gitlab.com/DOSx86/logger/-/blob/aae3dfddcdacfea18950a96ce9449767c20b2d66/source/logger/common.inc#L267
this got me looking into this 'too slow' detection method.
and it is indeed slow. as in molasse. let me explain.
a) isn't
%%Comparing:
inc di
I'm responding to all of your mails (Jerome's) so far.
On at 2023-04-21 06:55 -0400, jer...@shidel.net wrote:
Hi All,
At present, the interface program for Logger just performs a slightly
optimized brute force search for the Logger device driver. Although
reliable, it is very slow compared
Hi Eric,
> On Apr 21, 2023, at 10:27 AM, Eric Auer wrote:
>
>
> 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
> On Apr 21, 2023, at 10:21 AM, tom ehlert wrote:
>
> Hi,
>
>
>> At present, the interface program for Logger just performs a slightly
>> optimized brute force search for the Logger device driver. Although
>> reliable, it is very slow compared to providing a simple interrupt call to
>>
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
Hi,
> At present, the interface program for Logger just performs a slightly
> optimized brute force search for the Logger device driver. Although reliable,
> it is very slow compared to providing a simple interrupt call to test for
> installation.
given that this detection will be done once
Hi Eric and Bret,
I looked at 2D, 2F and even absolute AMIS 7D.
> On Apr 21, 2023, at 7:44 AM, Eric Auer wrote:
>
>
> Hi Jerome,
>
> there is no need to allocate a whole int 0x2b for just one driver.
It need not be just for one driver.
Anyone could hook 0x2b and is a very loose and light
Why not use AMIS (INT 2Dh)? It's there for the very reason you're proposing.
However, it's much more involved than your simple test, but also provides many,
many additional features and allows simple communication, interaction, and even
cooperation between all TSRs and Device Drivers that
Hi Jerome,
there is no need to allocate a whole int 0x2b for just one driver.
There are mechanisms which already invite drivers to share them :-)
INT 2D - ALTERNATE MULTIPLEX INTERRUPT SPECIFICATION (AMIS) [v3.6]
AH = multiplex number
AL = function
00h installation
Hi All,
At present, the interface program for Logger just performs a slightly optimized
brute force search for the Logger device driver. Although reliable, it is very
slow compared to providing a simple interrupt call to test for installation.
Looking at the different interrupts, I think I
17 matches
Mail list logo
