Hello,
2011/7/7 Rugxulo rugx...@gmail.com:
All keyboards aren't all the same, though, which is why it's best not
to hardcode key settings or use anything too obscure. My old 486 had a
Macro key (available to use in SETEDIT via included TSR), my P166 had
a Turbo key (typematic rate?), my
Appart from turning DISPLAY into a DOS device driver and override
kernel's CON, but not only IOCTL, but also write.
FWIW, you don't actually need to turn DISPLAY into a device driver in order to
replace/enhance CON. You can do that with a TSR also. See my USBPRINT if you
want an example of
Ok, sorry, that's what I meant. That you find the chain at the List of
Lists, right?
Aitor
2011/7/10 Bret Johnson bretj...@juno.com:
I'm curious, you check the LoL to get the pointers and override it?
No, you just insert a new one with the same name in the Device Driver chain.
DOS always
IMHO, TSR's have a lot of advantages over device drivers, and can still be
installed in CONFIG.SYS if you actually want/need to do that (with the
INSTALL= option).
You can even write a single executable which can be loaded both as device
driver (DEVICE= or DEVLOAD) and as normal program
Ok, sorry, that's what I meant. That you find the chain at the List
of Lists, right?
Yes. The first Device Driver header (NUL) is in the LoL. From there, you can
follow the chain (a linked list of pointers) as far as you want, and can
insert/remove new headers wherever you want.
Most programs could already be loaded earlier in CONFIG.SYS if they
were adjusted in that way, though some of the DOS structures aren't
available yet in that case.
That's one of the big advantages of TSR's, in my opinion. While CONFIG.SYS is
being processed, DOS is not yet all there. As a
Hi,
Last year I wrote about a problem with 16-bit 2039 kernels in portable
computers: ChkDsk would report errors, and wouldn't even run.
I later found that the 2039 32-bit kernel did not produce these errors, so
I started using it in my two portables (IBM ThinkPad and Compaq Armada),
and the
