Dec 302017
OS/2 program that demonstrates the use of Named Pipes. | |||
---|---|---|---|
File Name | File Size | Zip Size | Zip Type |
PIPES.EXE | 30800 | 14171 | deflated |
PIPES.HLP | 24088 | 14036 | deflated |
READ.ME | 1523 | 814 | deflated |
Download File PIPES.ZIP Here
Contents of the READ.ME file
PIPES DOCUMENTATION
I wrote the pipes demo in order to learn a little more about OS2 PM and particularly
IPF. Additionally, I felt that named pipes will play a large role in the type
of applications that we are developing at the firm in which I work. The demonstration
allows a programmer who is unfamiliar with the operational sequences related to
named pipes processing to try them out.
The help facility is pretty extensive. F1 gives contextual help for almost all
operations.
The program runs only under OS2 1.2 as far as I know. I have only tested remote
pipes using the Novell SDK since EE 1.2 is not shipping yet. There is a bug
that shows itself in a remote requester that attempts to wait for a read to
complete. The read DOES NOT BLOCK and returns with message size 0. Also, the
output from DosPeekNmPipe issued by a remote client shows that the current
message in the buffer is the pipe buffer size. This bug will not show when
using local pipes. I am working through the problem with Novell and will
supply a corrected version if the bug is in my code.
You may place the EXE and HLP files in any directory and execute PIPES with
that directory as the current working directory. Alternately, you may place
the HLP file in a directory pointed to by the SET HELP= config.sys statement.
Y O U N E E D A M O U S E
I hope you have fun with the demo and start coding cooperative processing
shareware for LAN's.
Dave Lester
ldl011090
I wrote the pipes demo in order to learn a little more about OS2 PM and particularly
IPF. Additionally, I felt that named pipes will play a large role in the type
of applications that we are developing at the firm in which I work. The demonstration
allows a programmer who is unfamiliar with the operational sequences related to
named pipes processing to try them out.
The help facility is pretty extensive. F1 gives contextual help for almost all
operations.
The program runs only under OS2 1.2 as far as I know. I have only tested remote
pipes using the Novell SDK since EE 1.2 is not shipping yet. There is a bug
that shows itself in a remote requester that attempts to wait for a read to
complete. The read DOES NOT BLOCK and returns with message size 0. Also, the
output from DosPeekNmPipe issued by a remote client shows that the current
message in the buffer is the pipe buffer size. This bug will not show when
using local pipes. I am working through the problem with Novell and will
supply a corrected version if the bug is in my code.
You may place the EXE and HLP files in any directory and execute PIPES with
that directory as the current working directory. Alternately, you may place
the HLP file in a directory pointed to by the SET HELP= config.sys statement.
Y O U N E E D A M O U S E
I hope you have fun with the demo and start coding cooperative processing
shareware for LAN's.
Dave Lester
ldl011090
December 30, 2017
Add comments