Hello Joel!

Monday February 05 1996 21:20, Joel Downer wrote to All:

JD> Anyway, this afternoon I got a report that my game was failing to create
JD> a remote pipe (returning error 3, or invalid pathname).  My code allows
JD> the sysop to specify the pipe name so that he/she can include a server
JD> name, and the sysop here appears to be using the correct one given the
JD> server name of sys2:

PE>> \\sys2\pipe\oxpipe

Ok, first of all. You never actually "create" a remote pipe. You
create a local pipe (ie. the name is like '\PIPE\MyPipe') which can be
opened from a remote workstation (name is like '\\MyServer\PIPE\MyPipe').

JD> sprintf(pipename, "%s.%d", od_control.od_pipe_name,
od_control.od_node);

I'm unfamiliar with your program (I probably should get around to
installing a few doors ;-) I'm not sure what exactly you are doing.
However, what you want to end up with is:

On machine 'sys2': DosCreateNPipe("\\pipe\\oxpipe.0",...);
On the client    : DosOpen("\\sys2\\pipe\\oxpipe.0",...);

JD> Now... I'm a relative novice at OS/2 LAN setup (I just set up a simple
JD> Warp Connect Peer LAN for file and printer sharing a couple months
JD> ago, and I don't run my BBS across the LAN) but when I try to create a
JD> pipe on my server (pipename:  \\BBSSERV\PIPE\OXPIPE), I'm getting the
JD> same error.

Same problem. Only specify the machine name in DosOpen.

Doug

--- GoldED/2 2.50+