Mail Archives: opendos/2000/11/28/07:51:48.1
X-Comment-To: Matthias Paul
Hi!
27-ξΟΡ-2000 17:41 PAUL-MA AT reze-1 DOT rz DOT rwth-aachen DOT de (Matthias Paul) wrote to
opendos AT delorie DOT com:
Subject: RE: BASIC & EMS (was: Optimizing CONFIG.SYS...)
MP> But CLOAKING was developed by Helix (for their Netroom memory
MP> manager). Helix is now part of Network Associates (or was it
MP> Computer Associates???), and Netroom no longer exists as far as
Don't know who currently owns Helix and who owns NAI (Network
Associates), but NAI previously called McAffee Associates.
MP> using DPMS. It might also be a good idea to add DPMS support
MP> to CTMOUSE to have
MP> 1. a freely available example source how to "DPMS" an existing driver
MP> (so others can use that to adapt the techniques to their own
MP> drivers)
Probably this is good idea but I have absolutely no information about
DPMS API and examples how to use it.
MP> 2. to still have a tiny mouse driver when Logitech decides to
MP> abandon support of their DOS driver (they might have done
MP> already by now, at least this was appeared to me due to
MP> their neclectance to fix a few minor issues, I reported a while back...)
"Neclectance"? You mean "silence" or "rejection"? Unfortunately both
states are permanent for most vendors and can't indicate nothing.
27-ξΟΡ-2000 17:07 PAUL-MA AT reze-1 DOT rz DOT rwth-aachen DOT de (Matthias Paul) wrote to
opendos AT delorie DOT com:
MP> On Sat, 25 Nov 2000 03:35:58 Arkady V.Belousov wrote:
>> I don't use neither TASK MANAGER nor TERMINATE. I use Windows 3.x and
>> TERM90 from Norton Commander and have no troubles.
MP> I haven t had a look at CTMOUSE sources yet, but I will for sure when
MP> I find the time (currently I m using the LOGITECH 8.something LMOUSE
MP> driver because it supports CLOAKING to reduce the real mode memory
MP> footprint of the driver downto 1 Kb).
MP> I have a suggestion for CTMOUSE to further reduce the real-mode
MP> memory footprint. If data is not embedded into the code it should
MP> be possible to adapt it to support DR-DOS (and PC DOS) DPMS (DOS
MP> Protected Mode Services) leaving only a stub in the 1st meg.
MP> The DPMS SDK should still be available from Lineo for money,
_I_ can't pay for this.
MP> and shipping the DPMS.EXE driver with CTMOUSE would need licensing
MP> and also not harmonize well with the GPL, of course.
MP> However, supporting DPMS in applications is, of course, not subject
MP> to licensing. The DPMS API as it was publically and freely available
MP> from Caldera s web-site back in 1997 (excluding example sources
MP> etc.) should still be downloadable from ftp://ftp.lineo.com/.
If you give me concrete URL of all required files then I can download
they. Searching is not may hobby, sorry. B-\
MP> Ralf Brown s INTER61 also briefly lists the DPMS API.
RBIL is good as reference guide, but far not enough as educational
tool. :(
MP> Regarding any possible problems under TASKMGR (again, I haven t
MP> tried myself yet), hence I m guessing here, but it might be required
MP> to declare some of CTMOUSE s data areas holding status info (such as
MP> state engine data) as instance data. The API is identical to the
MP> Windows startup/exit broadcast API at INT 2Fh (see INTER61 as well).
MP> There are also some TASKMGR.INI directives to declare whole drivers
MP> as instance data "from outside".
As I say, RBIL not good to educate and I have no deal with Windows
programming. Moreover, because I not use TASKMGR I can't debug how it work
and this must do someone else.
- Raw text -