On 03 Jul 2024, Digital Man said the following...
Nope, those pipe functions are *not* present in the supported functions
of MS-DOS v4.
And indeed, from your linked reference:
"This function was introduced by LAN Manager but is also supported by the Novell DOS Named Pipe Extender, Banyan VINES, OS/2 Virtual DOS Machines, and others" not [MS/PC]-DOS.
Yes, so are you mad I didn't preface that with "You could install LAN Manager Client for DOS, Novell network support and use DOSNP.EXE or run inside a VDM using named pipes" ?
First paragraph of
https://helparchive.huntertur.net/document/61238 :
"The Communications Server MS-DOS and OS/2 clients use named
pipe connections to communicate with OS/2-based Communications Server computers."
A problem someone was having with named pipes in MS-DOS with DOS LAN Manager
https://library.thedatadungeon.com/msdn-1992-09/kbase/html/kbas5c4h.htm
And a problem using named pipes with Windows 3.11 (interesting symptom for a DOS machine to have)
https://jeffpar.github.io/kbarchive/kb/119/Q119106/
And the manual for MS SQL states the DOS client support uses named pipes too, using a TSR like the Novell one does. I can't find the link anymore but I'm guessing that's why they added those functions to the NTVDM in the first
place (they mentioned it was for DOS Point-of-Sale software).
.. and in any case, you said "DOS programs" don't support named pipes. If you want to say that it isn't technically a DOS program if it uses interrupts
that aren't supported on a plain install of MS-DOS 4, well, sure:
<grabs his MS-DOS programmers guide>
Nope, those pipe functions are *not* present in the supported functions
of MS-DOS v4.
MS-DOS 4 also didn't come with DPMI support. It didn't exist yet.. are those DOS programs or nah? :)
--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)