Talk:DOS Protected Mode Services

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

DPMI / DPMS[edit]

What is the difference between them? Is one the precondigion of the other? I am confused. --RokerHRO (talk) 15:36, 11 September 2011 (UTC)[reply]

DPMS and DPMI serve different purposes. If you want to write extended DOS applications, use DPMI (or a DOS extender built on top of it). If, however, you want to write a DOS device driver or TSR, consider utilizing DPMS to significantly reduce its conventional memory footprint (when loaded on 286+ machines) so that there will be more free memory left either for (non-extended) DOS applications or other drivers to run, or simply to have more free system resources under a multitasker such as Windows. DPMS and DPMI can coexist, but do not depend on each other. --Matthiaspaul (talk) 19:12, 11 September 2011 (UTC)[reply]
Fine, thank you for your answer. But I think it should be answered in the article, shouldnt' it? ;-) --RokerHRO (talk) 16:04, 13 September 2011 (UTC)[reply]

Helix Cloaking API Manual[edit]

Back in 1995, someone added a citation referring to a "CLOAKING_API_SERVICES_MANUAL.pdf" file uploaded to Commons. Unfortunately, the file got swiftly deleted at Commons as they do not host PDFs and because someone found this to be a circular reference (which it wasn't, as the file originated from Helix). I seem to remember that I saw the file being archived at archive.org, but the snapshots I could find now only show the former landing page at Commons but without the PDF. I could find an archive of a thumbnail of the PDF ([1]), but it only shows the first page of the document and is way too small to be readable. I think for historical completeness the article would benefit from including a link to the Cloaking API manual either in a citation or in the external links section. So, if someone still has this file it would be great if they could upload it somewhere else and then add a link to the article. --Matthiaspaul (talk) 00:25, 6 January 2022 (UTC)[reply]