🚀 go-pugleaf

Steve Brown (brown@dlogics.com) wrote:
: 
: I just got a bulletin from Microsoft claiming (justifiably) that their 
: SQLServer won't talk to WINOS2/DOS sessions on the same machine (local 
: named pipes). 
: They claim:
: 	Due to a bug in the OS/2 2.0 named pipes implementation, no
: 	support is available for client applications running in the virtual
: 	MS-DOS and Windows sessions running on OS/2 2.0.  This bug also
: 	prevents SQL Administrator from running on OS/2 2.0.
: 
: I am aware that network named pipes are not supported from the WINOS2/DOS,
: but find nothing about local named pipes being busted.  Does anybody have any
: background on this, like, Is it true?  If so, will it be fixed?  

I know that local named pipes (\pipe\pipename) work fine under OS/2
2.0, and if Microsoft wants I can send them some source code and the
GNU C++ compiler.

However, my guess is that Microsoft is implementing client
applications running locally just like client applications running
remotely, through a network server named pipe (\\SERVER\PIPE\pipename).  
That would make the programming a lot simpler, because you wouldn't
have to distinguish between "local" and "remote" clients.  However,
since the local DOS boxes don't know about the server pipes (yet), the
applications cannot be run locally.  This is supposed to be fixed in a
future version of OS/2.

- Kevin Lowey (Lowey@Sask.USask.CA)
>>>>> Anonymous FTP to FTP.USASK.CA for DOS, OS/2, and Windows programs <<<<<