Hello Sean!

18 Feb 09 23:06, Sean Dennis wrote to Mike Tripp:

 SD> It won't work with either 3.x or 2.x on my system.  It just keeps
 SD> whining about no valid areas found and at this point, Blue Wave is no
 SD> longer on my hard drive and it's going to be a snowball's chance in
 SD> hell that I'll put it on my system. I dislike putting kludgy things up
 SD> in the first place, but the way this program keeps whining about
 SD> things being wrong when they're not, well, in the bit bucket it went.

Has got to be something painfully simple.  It's been running flawlessly
here since '91.

Since I have a newfound need to support it over telnet on OS/2 instead of
dialup on DOS, I decided to test a clean install of 3.20 OS/2 (for DOS Max
2.x on DOS or OS/2 VDM, I'm still using BW 3.01).  The only input I gave it
was path\filename to Max 3.x PRM and a string to name packets.  The door
bombed on the first attempt with "can't find MSGAPI32", even
though MSGAPI32.DLL is found in the Max3 dir. Copied to the BW dir, fired
it up again (local /k), tagged the first area and built a packet.

Decided to rinse/lather/repeat in a new dir for the DOS flavor, to see if
it did anything different.  Worked fine first try...no MSGAPI32 error this
time.

I think there must be some Max 2.x/3.x confusion in your setup, since 3.20
is no go for 2.x.  I would check your MAXIMUS= environment variable and
make sure that you're SILTing everything (to get fresh AREA.DAT) =without=
any compatibility switches.

.\\ike

--- GoldED/2 2.50+