| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Maxpipe |
BJ> I haven't used it, but both Binkley 2.60 (and 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). So, what were they used *for*? The only Bink/Max "interoperability" I've spotted in the source code has to do with the OS/2 semaphores. Wes --- Maximus/2 3.01* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000) SEEN-BY: 633/267 270 @PATH: 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.