On Apr 13, 1997, Michael McBroom wrote:
 JS> head over this.  Given that only two users seem to be
 JS> having the problem, it almost has to be something wrong
 JS> on their end.
 MM> Yeah, this is what I figured, too.  This reminded me of
 MM> something I ran into while checking this out, though.  Have
 MM> you had any experience with using Win95's hyper terminal to
 MM> connect with Max/2?  When I try logging in using this setup
 MM> from my other system, I get color, but no ansi.  I get hi
 MM> asci instead.  I've tried a couple of the emulation
 MM> settings, but no dice.
Nope.  Sorry, Mike.  I run DOS Maximus under WfW 3.11.  I _have_ had some 
experience with the Windows 3.xx terminal program and it was all bad. ;)  
I've simply told others not to use that and to pick up a *good* comm program 
instead. I've been told that hyper terminal is much better but I've never had 
a chance to try it.
 MM> Now, as I recall, back in the ancient DOS days, if one
 MM> wanted ansi to be enabled when dialing into a system that
 MM> displayed ansi, that one had to include ansi.sys in their
 MM> config.sys file.  Would you happen to know if I need to do
 MM> this somehow with Win95?  I'm not really concerned about it
 MM> -- just curious.  I haven't tried any standalone comm
 MM> software for Win95 yet to see if this problem is specific to
 MM> hyper terminal.  Probably won't either.
I really don't know.  I have ANSI.SYS loaded in config.sys here.  The best 
Windows comm program I've seen is QMProWin (QmodemPro for Windows) but it's 
commercial and I don't think there's a shareware version.
Cheers,
 -Jack
  ogre@nashville.com
--- Squish/386 v1.11
---------------