BJ> I haven't used it, but both Binkley 2.60 (and 
 BJ> Binkley XE, since it is 
 BJ> derived from 2.60) and Maximus (2.0 on?) allow for 
 BJ> the use of maxpipe under OS/2 (and later Win32 
 BJ> Max?).  If I understand things correctly, you could 
 BJ> think of Unixed named pipes as what was implemented 
 BJ> under OS/2....  So, this should be relatively 
 BJ> simple to implement for pipes that are used.  I'm 
 BJ> not sure if a keyword will need to be added under 
 BJ> Linux to turn off creation of the named pipes when 
 BJ> they are not used (or direct them to /dev/null when 
 BJ> not used).
 WG>  
 WG> So, what were they used *for*? The only Bink/Max 
 WG> "interoperability" I've spotted in the source code has 
 WG> to do with the OS/2 semaphores.


I think they are used to display the sysop console in another window, which
is something we would like under Linux.  I don't remember if those pipes
were one way (display only) or two way.  If two way, we could junk the
direct console writes and force a seperate program for the console.....  I
seem to recall the pipes were just one way.....  I believe one way this was
used was when using a PC with two heads (video displays), one could setup a
console display window on the second head so that you could see what was
going on with the bbs....

As I said, I haven't used the pipe options.

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01