DOS Protected Mode Services

"DPMS 1.0" redirects here. For the display power management standard, see VESA DPMS 1.0.

DOS Protected Mode Services (DPMS) is a set of extended DOS memory management services to allow DPMS-enabled DOS drivers to load and execute in extended memory and protected mode.[1]

Not being a DOS extender by itself, DPMS is a minimal set of extended DOS memory management services to allow slightly modified DOS resident system extensions (RSX) such as device drivers or TSRs (as so called DPMS clients) to relocate themselves into extended memory and run in 16-bit or 32-bit protected mode while leaving only a tiny stub in conventional memory as an interface to communicate with the conventional DOS environment. The DPMS clients do so through DPMS services provided by a previously loaded DPMS server.[1] The necessary size of the remaining stub depends on the type of driver, but often can be reduced downto a few hundred bytes for just the header even for complex drivers.

By executing the driver in extended memory and freeing up conventional memory, DPMS not only allows very large drivers to load and take advantage of the available memory, but also to leave more memory available for normal DOS drivers to load or non-extended DOS applications to execute within the space constraints of the conventional memory area. This will also help increase the amount of free system resources under Windows. Providing unified interfaces for the software to allocate and use memory in protected mode[1] without having to tunnel all requests through real mode DOS, DPMS at the same time can help improve system performance as well.

DPMS

DPMS was originally developed by Novell's Digital Research GmbH, Germany, in 1992. It is compatible with any DOS and can coexist with memory managers and DOS extenders such as DPMI, VCPI, etc. The DPMS API is reentrant[1] and compatible with multitaskers such as the DR-DOS multitasker or DESQview.[2] By providing a built-in DPMS VxD-driver, it is also compatible with Windows 3.x and Windows 9x.[2]

The DPMS server must be loaded after the memory managers (and before the drivers using it), either as a "DPMSXXX0"[2] device driver per DEVICE statement in CONFIG.SYS (preferred method), or later as a TSR.[2] For debug purposes (for example in conjunction with Microsoft's WDEB386.EXE[1]), SDK-versions of EMM386.EXE 3.00 can alternatively provide DPMS services[1] via EMM386 [/]DPMS[=ON] through a built-in DPMS.SYS module,[3] then running at ring 1 instead of ring 0, as with the stand-alone version of DPMS.EXE. The DPMS [/]NOCR3 option allows debugging under Nu-Mega's SoftICE.[3]

Depending on circumstances the server will occupy between about 700 to 1400 bytes of conventional memory by itself and cannot be loaded into UMBs.[2][nb 1] The DPMS server will require at least a 286 machine to run, but since DPMS-enabled software can be designed in a way so that it continues to execute in conventional memory if DPMS services are not available, the software does not need to give up compatibility with systems not providing DPMS services, either because DPMS is not loaded or not available (for example on pre-286 processors).[1][2] On 386 CPUs (and higher), the DPMS server will not only provide a set of 16-bit, but also a set of 32-bit services.[1] Even on these machines, DPMS can be forced to load only its 16-bit services using the DPMS [/]2[86] option.

DPMS will allocate memory either through VCPI or XMS,[3] depending on what kind of memory is available. VCPI will typically call down to XMS as well. Newer versions of DPMS can be forced to use one of these interfaces using the DPMS [/]MEM=XMS|VCPI option.[3] In some versions, it is possible to specify the maximum amount of extended memory to be allocated with DPMS [/]MB=nnnn.[3]

DPMS registering services can be disabled or re-enabled at any time after load using the DPMS [/]OFF or DPMS [/]ON command, however, this will only affect new drivers loaded, not those already running and using DPMS.[1][2]

There are basically three revisions of the DPMS specification, DPMS beta,[4] DPMS 1.0 (original Novell DOS 7 shipment)[1] and DPMS 1.1 (since March 1994 update).[5] The 1.0 specification continued to support the beta specification as well, whereas the 1.1 (and higher) implementation does not.[5]

DPMS saw its debut in beta versions of DR DOS "Panther" in October 1992,[3] which, besides others, came with DPMS-enabled versions of the Super PC-Kwik disk cache,[3] the SuperStor disk compression,[3] and DEBUG as "stealth" protected mode system debugger.[3] The PCMCIA card services CS in PalmDOS were DPMS-enabled as well.[3] Later retail products such as Novell DOS 7 and Personal NetWare 1.0 in December 1993 also came with many DPMS-enabled drivers such as the file deletion tracking component DELWATCH 2.00, the adaptive disk cache NWCACHE 1.00,[2] NWCDEX 1.00,[2] a CD-ROM redirector extension, the peer-to-peer networking server SERVER 1.20, and STACKER 3.12, the disk compression component. DPMS was also provided by Caldera OpenDOS 7.01,[1] DR-DOS 7.02 and 7.03, which, at least in some releases, added DPMS-enabled issues of DRFAT32 (a FAT32 redirector extension),[3] LONGNAME (VFAT long filename support)[3] and VDISK (virtual RAM disk).[1][4] DR-DOS 7.03 contains the latest version of DPMS 1.44.

DPMS was also provided by IBM's PC DOS 7.0 and PC DOS 2000, which came with an older version of Novell's DPMS server and a DPMS-enabled version of Stacker 4.02 bundled.

Stac Electronics also produced a DPMS-enabled stand-alone version of Stacker 4.

Some third-party DOS driver suites such as the Eicon Diva CAPI ISDN drivers or PCMCIA driver stacks such as Award's CardWare 2.5 (or higher) are known to support DPMS as well.[3] After Phoenix's acquisition of Award, their PCMCIA drivers 6.0 (and higher) have been sold off to UniCore.[3]

CLOAKING

In 1993, Helix Software Company's memory manager NETROOM 3 introduced a feature very similar to Novell's DPMS: CLOAKING was used to relocate Helix's and third-party drivers into extended memory and run them at ring 0.[6] Providing its functions as an extension to the real-mode EMS and XMS interface, its protected mode services are available under INT 2Ch.[4][7] A CLOAKING developer's kit was available which included a Nu-Mega Technologies' SoftICE debugger.[8] Cloaked driver or TSR software hooking interrupts had to leave a small 11-byte stub in conventional memory which would invoke the CLOAKING server to pass execution to the protected mode portion of the driver software.[6]

CLOAKING includes support for seamless operation under Windows 3.x and Windows 95, providing compatible INT 2Ch services to protected mode drivers via a Windows VxD, as well as seamless debugging through Windows start-up using SoftICE. This ability to transition between protected mode host environments is also the subject of a patent.[9]

CLOAKING integrates into and works with existing virtual memory control programs, without switching descriptor tables or resetting the control registers. This allows for faster interrupt processing, according to Helix's documentation.[9]

In contrast to Novell's DPMS, Helix's CLOAKING driver can be loaded high,[2][nb 1] but it does not run on 286 machines,[2][nb 1] though it does support 16-bit services and program structure on a 386. Also, CLOAKING 2.01 has been found to be incompatible with the DR-DOS multitasker (EMM386 /MULTI[=ON] + TASKMGR).[2]

If no DPMS server is present when CLOAKING.EXE loads, CLOAKING will, by default, also provide a cloaked DPMS server at a mere 100 bytes increase of its DOS memory footprint.[2] However, it can also coexist with a DPMS server loaded before CLOAKING. The loading of its built-in DPMS server can be suppressed using the CLOAKING /NODPMS parameter.[2] DPMS-enabled drivers will work with both DPMS or CLOAKING, but not vice versa.[2]

In NETROOM v3.04, Supplemental Disk distribution dated "2-10-95," the password protected resource file NR.ZIP (679,271 KB) has an undocumented file; DPMSCLK.EXE (13,904 KB), "Cloaked DPMS Server v3.03". The file does not reveal support for any options or parameters when queried using the standard help option, DPMSCLK /? . This file is not unzipped by the NETROOM 3 SETUP.EXE program and does not install. There is no hint of the file's existence in the NETROOM 3 software manual[10] or any of the on-disk program documentation and human-readable files.[11] This final version of NETROOM as released basically ignored DPMS.

Helix licensed a version of Award Software's BIOS and developed cloaked system and video BIOSes which executed entirely in protected mode, reducing their real-mode memory footprint down to 8 KB (instead of 96 KB[4]) and used these as run-time BIOS in conjunction with their NETROOM memory manager.[2][7]

As part of their Multimedia Cloaking product, Helix provided cloaked versions of Logitech's MOUSE 6.33 driver, Microsoft's MSCDEX, and a home-grown disk cache to replace Microsoft's SmartDrive drivers.

There was also a product named Multimedia Stacker consisting of Stac's DPMS-enabled Stacker 4.01 with Helix's above suite of cloaked DOS utilities.

The Logitech DOS mouse driver since MouseWare 6.50 was enabled to take advantage of CLOAKING as well, thereby reducing the mouse driver's memory footprint visible to DOS applications from 27 KB to 1 KB.[2]

CLOAKING was also licensed to Symantec for their utility suite, to Corel for their CD Creator and Corel SCSI products, and to SMC Networks for their Ethernet drivers.

Novell's DPMS utility may not be used to temporarily disable DPMS with a DPMS [/]OFF command if those DPMS services are provided by CLOAKING instead of DPMS itself, because Helix's implementation will erroneously not only disallow new drivers to register with DPMS, but completely switch off DPMS services even for already loaded drivers, leading to a system crash.[2]

NIOS

In 1993, Novell had announced plans to convert their resident workstation management utilities as well as their DOS network driver stacks (shells, redirectors and requestors) to use DPMS,[4] however, so far only the Personal NetWare server component had actually taken advantage of it.

In 1996, Novell introduced a new 32-bit DOS/Windows NetWare client (Client32) based on ODI32/NIOS, replacing the former 16-bit client based on ODI/VLM.[2] The NIOS (NetWare Input/Output System) client used techniques very similar to DPMS or Cloaking to relocate and run the code of the loaded NLMs (NetWare Loadable Modules) in protected mode and extended memory in order to reduce the conventional memory footprint of the network stack downto about 2 to 5 KB.[2]

NIOS neither required nor used DPMS or Cloaking directly, and it did not provide a generic interface which could be used by non-NLM modules, however, it was certainly inspired by the DPMS technology and it can coexist with both of them.

While Novell's Personal NetWare continues to be published unmodified as part of the DR-DOS suite by its newer owners Caldera, Lineo and DeviceLogics up to the present, Personal NetWare had been abandoned since 1995 within Novell itself. This led to the situation that Novell never published a PNW.NLM driver to support the Personal NetWare protocol under the newer 32-bit ODI32/NIOS stack, so that users of Personal NetWare, who could take advantage of the PNW server module's DPMS capabilities already, were ironically bound to continue to use the memory-consuming ODI/VLM 16-bit client with its PNW.VLM protocol driver.

See also

Notes

  1. 1 2 3 Some early versions of DPMS could be loaded high, but this was deliberately defeated in later versions (by artificially letting the driver declare an impossible to satisfy amount of memory during initialization, so that the operating system could not load it high and had to leave it in conventional memory during initialization) for compatibility reasons. It could cause stability problems in some scenarios on 286 and 386 machines supporting chipset-level memory backfilling mechanisms.

    References

    1. 1 2 3 4 5 6 7 8 9 10 11 12 Caldera, Inc. (1997). OpenDOS Developer's Reference Series — DOS Protected Mode Services (DPMS) 1.0 API — Programmer's Guide. Printed in the UK, August 1997. Caldera Part No. 200-DODG-005 ().
    2. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Matthias Paul (1997-07-30). NWDOS-TIPs — Tips & Tricks rund um Novell DOS 7, mit Blick auf undokumentierte Details, Bugs und Workarounds. MPDOSTIP (e-book) (in German) (edition 3, release 157 ed.). Retrieved 2012-01-11. NWDOSTIP.TXT is a comprehensive work on Novell DOS 7 and OpenDOS 7.01, including the description of many undocumented features and internals. It is part of the author's yet larger MPDOSTIP.ZIP collection maintained up to 2001 and distributed on many sites at the time. The provided link points to a HTML-converted older version of the NWDOSTIP.TXT file.
    3. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Matthias Paul (2001-04-09). NWDOS-TIPs — Tips & Tricks rund um Novell DOS 7, mit Blick auf undokumentierte Details, Bugs und Workarounds. MPDOSTIP (e-book) (in German) (edition 3, release 183 ed.).
    4. 1 2 3 4 5 Schulman, Andrew; Brown, Ralf; Maxey, David; Michels, Raymond J.; Kyle, Jim (1994). Undocumented DOS - A programmer's guide to reserved MS-DOS functions and data structures - expanded to include MS-DOS 6, Novell DOS and Windows 3.1 (2 ed.). Addison Wesley. p. 11. ISBN 0-201-63287-X. ISBN 978-0-201-63287-3.
    5. 1 2 Ralf Brown (2002-12-29). "The x86 Interrupt List". Ralf Brown's Interrupt List (61 ed.). Retrieved 2012-01-14. See also: Ralf Brown's Interrupt List
    6. 1 2 Schmit, Michael L. (1995). Pentium Processor Optimization Tools (1 ed.). Cambridge, MA, USA: Academic Press, Inc. (AP Professional). pp. 252–253. ISBN 0-12-627230-1.
    7. 1 2 Singh, Amarendra (1993-07-13). "NETROOM 3.0 More Room at the Top". PC Magazine 12 (13). Retrieved 2014-12-12.
    8. ↑ Knoblauch, Rick (1994-05-17). "Hide Programs With Cloaking". PC Magazine 13 (9): 269. Retrieved 2014-12-04.
    9. 1 2 US patent 5459869
    10. ↑ NETROOM Version 3 Guide to Operations, Sixth Edition - October 1994, part # N03,1094
    11. ↑ NETROOM Version 3 Supplemental Disk, all (11) *.BAT/*.DOC/*.HLP/*.INF/*.TXT files, 2-10-95 distribution

    External links

    This article is issued from Wikipedia - version of the Thursday, January 07, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.