Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!usc!polyslo!csun!srhqla!kosman!kevin
From: kevin@kosman.UUCP (Kevin O'Gorman)
Newsgroups: comp.sys.ibm.pc
Subject: PROCOMM and my machine(?)
Message-ID: <807@kosman.UUCP>
Date: 7 Jul 89 05:59:24 GMT
Reply-To: kevin@kosman.UUCP (Kevin O'Gorman)
Distribution: na
Organization: K.O.'s Manor - Vital Computer Systems, Oxnard, CA 93035
Lines: 24

A couple of days ago, I posted a query about Procomm and DOS 4.0, thinking
that my troubles had to do with the OS.  A few people have assured me that
they are running on 4.0 with no trouble, so that's not it.

So I dug just a bit more (I have nothing better to do this late at night),
and found that I could get PROCOMM to act normally if I removed the
PROCOMM environment variable.  Of course then it expects the dialing
directory (and maybe other stuff) to be in the current directory.  I can
arrange for this, but it is not a good permanent solution.

The PROCOMM variable is correct as set up, so I can't quite imagine what
the trouble is.  I tried it with a trailing \ and without.

What I get is a message about a failed FMALLOC (Malloc from the far heap?)
for the Dial directory, overlaid on the startup screen, and ALT-D just
gives me an error message.

Does this jog anyone's thinking cap?  Can I get a guess as to what the
environment variable has to do with heap failure?

I would be happy to spring for PROCOMM plus if I knew that would fix the
problem, but other folks run with this thing.  This leads me to suspect
I would have the same trouble with PROCOMM+, and that's too expensive
a lesson for me.