Hello SHAWN!

07 Feb 09 09:12, SHAWN HIGHFIELD wrote to Mike Tripp:

 ->> Do you know if it affects Maximus/2 2.x?

 SH>   No I don't Sorry.

OK...I'll have to remember to try and break it and report back if/when I
get to that stage.

 ->> obviously rather be using the OS2 versions of
 ->> Binkley/Max...assuming the DOS doors can still be integrated where
 ->> necessary.

 SH>   Shouldn't be a problem that's what I did for years.

It's just a matter of finding out where in the docs Ray hid that example
with the proper SIO specific commandline format for adding that extra pesky
dash for passing the hot comm handles back and forth.

 ->> I will be sticking with 2.x and not using 3.x, though, for reasons
 ->> of utility compatibility and personal preference.  If the bug
 ->> applies, then I may need

 SH>   I liked 3 more. :)  The one utility I liked for 2.x was febbs and I
 SH> would just create the 2.x files for it. :)

Febbs is sweet for interactive use and X_List is sweet for
batch/maintenance use with most of Febbs' tricks and few more of its own. 
As I recall, even generating 2.x files falls over if you try to use 3.x
heirarchical area names...which, of course, was one of the first things I
wanted to play with.

After a couple of days of canonizing both file and message areas and
creating a corresponding grouping setup in SEAL, I ended up having to back
it all out. I was kinda relieved that something broke, because I
don't think all the extra typing for area selection/tagging really
justified the convenience, anyway. Past the utility compatibility unknowns
to be discovered by trial and error, the biggies for me were hot-flash
menus and a common IPC scheme for DOS and OS2.

Supposedly, hot-flash got removed from all ports because the Win32 console
support in Watcom couldn't handle it.  In the early setup stages, it was
quite a boon to have one static line of display, no matter which menu and
how many options, and to see a full string instead of the one letter Xpert
mode.

In 2.x, the interprocess communication was file-based and DOS and OS2 nodes
could see/chat each other over the LAN...and I had/have nodes of both types
on a Netware LAN.  In 3.x, OS2 got the MCP (named pipe) server and DOS
retained the file-based method from 2.x and "never the twain shall
meet". Can't think of a good reason that the file-based method
couldn't have coexisted with the new MCP support in the OS2 flavor, and
Scott wasn't a short-cut type of programmer.

.\\ike

--- GoldED/2 2.50+