[comp.sys.att] 6386E/33 goofiness with DOS and modem

aland@infmx.UUCP (Colonel Panic) (08/14/90)

I recently added an official AT&T modem (model 2224CEO) to a running
6386E/33, hooked up to COM2 (I had only a DB9 cable).  It works
just fine with "cu" on UNIX.

The next time I booted DOS, I got drastic slow-downs in screen
operations, scrolling, etc.  Plus, sometimes I get activity on
the modem, as if DOS was accessing the modem or vice-versa.

I suspect that the console redirection feature (COM2CONS), which 
just stays active in the CMOS (UNIX doesn't care; if it has a working
video card, it ignores the redirection via conflgs), is affecting
the machine's operation under DOS.  Will I have to manually disable
the redirection via conflgs whenever I want to use DOS?  The hotline
said no, but the behavior I'm getting suggests otherwise.

Thanks in advance for any info.

--
Alan Denney # Informix # aland@informix.com # {pyramid|uunet}!infmx!aland

 "The driver says, 'One more cup of coffee and I'll be all right...'
  'Pop a Bennie, another Bennie'..."             - The Bobs, "Bus Plunge"

jbreeden@netcom.UUCP (John Breeden) (08/14/90)

In article <4988@infmx.UUCP> aland@infmx.UUCP (alan denney) writes:
>I recently added an official AT&T modem (model 2224CEO) to a running
>6386E/33, hooked up to COM2 (I had only a DB9 cable).  It works
>just fine with "cu" on UNIX.
>
>The next time I booted DOS, I got drastic slow-downs in screen
>operations, scrolling, etc.  Plus, sometimes I get activity on
>the modem, as if DOS was accessing the modem or vice-versa.
>
>I suspect that the console redirection feature (COM2CONS), which 
>just stays active in the CMOS (UNIX doesn't care; if it has a working
>video card, it ignores the redirection via conflgs), is affecting
>the machine's operation under DOS.  Will I have to manually disable
>the redirection via conflgs whenever I want to use DOS?  The hotline
>said no, but the behavior I'm getting suggests otherwise.
>

You ONLY need console redirection if you arn't using a PC monitor and 
keyboard (the 'default' console). 

If you are using a monitor, you turn console redirection off for both
Unix and DOS (you still get the com ports as tty's under Unix, cu talks to
com2 and the modem still works under DOS).

The 'problem' you've noted isn't a bug, it's pilot ErRoR (mis-configuration) (-:

-- 
 John Robert Breeden, 
 netcom!jbreeden@apple.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden
 -------------------------------------------------------------------
 "The nice thing about standards is that you have so many to choose 
  from. If you don't like any of them, you just wait for next year's 
  model."

cmilono@netcom.UUCP (Carlo Milono) (08/15/90)

In article <4988@infmx.UUCP> aland@infmx.UUCP (alan denney) writes:
>I recently added an official AT&T modem (model 2224CEO) to a running
>6386E/33, hooked up to COM2 (I had only a DB9 cable).  It works
>just fine with "cu" on UNIX.
>
    There are two problems with UNIX and the CEO modem, the first is
    with the modem - it is almost totally software defined and unless
    you set the internal options correctly, the following will happen:

	1) Data Transparency - must be set to YES, otherwise certain
           character sequences may (will) set your modem into a variety
           of modes - Digital Loopback is one of them.
	2) Interactive - must be set to OFF - a dip in the front will
           seal your options - one result of this being off is hilarious:
		Port sends string from 'getty' - modem sees it as command,
	        modem responds with error message, 'login' accepts it,
		'password' from port - etc, etc., etc.  You now have the
	        modem talking to the port forever (or until you reset the
	        port/modem.

    The second problem is with MNP on the CEO - you must make sure that
    a 'uucp' is going to go to another modem that supports that protocol,
    or you may be able to upload, but not download.   There are several
    'Dialers' entries possible for the CEO, depending on how you wish to
    use it (MNP, or not...what class, etc.) - unfortunately, the one in
    the earlier version of UNIX is a bit off...email me if you want the
    scripts...

>The next time I booted DOS, I got drastic slow-downs in screen
>operations, scrolling, etc. 
    Do you have Simultask or VPIX?  The internal COM ports are not
    intelligent, and a 'deadly embrace' like I mentioned above would
    account for such behavior - VPIX gives you an 8086 machine.
>
    The console redirection may indeed play a part, but I would suggest
    a very close look at your CEO options, and ultimately at the script
    for Dialers.  There are five known configurations for Dialers, as
    follows:

	Config	Protocol	UUCP	MNP	SPEED
	1	E             enabled   4.8     2.9
        2       E             enabled   2.4     2.4
        3       G             enabled   4.8     2.4
        4       G             enabled   2.4     2.2
        5       G            disabled   2.4     2.2
 NOTE: each config has different entries in Dialers, Systems, Devices.
-- 
+--------------------------------------------------------------------------+
|                   Carlo Milono                                           |
|    Personal:    netcom!cmilono@apple.com   or   apple!netcom!cmilono     |
|    Business:    cmilono@iliad.att.com                                    |
|"Sometimes I think the surest sign that intelligent life exists elsewhere |
| in the universe is that none of it has tried to contact us." B.Watterson |
+--------------------------------------------------------------------------+

aland@infmx.UUCP (Colonel Panic) (08/19/90)

In article <11954@netcom.UUCP> jbreeden@netcom.UUCP (John Breeden) writes:
>You ONLY need console redirection if you arn't using a PC monitor and 
>keyboard (the 'default' console). 

True.  But this is the DEFAULT configuration.  As shipped, the machine
comes with console redirection to COM2 enabled (I've configured 6 of
these things, and it's been the same on each).

>The 'problem' you've noted isn't a bug, it's pilot ErRoR (mis-configuration) (-:
> John Robert Breeden

I disagree.  If the machine requires that the redirection be disabled
manually before using DOS, then that fact should be documented.
It's not.  (Nor are a number of other niceties about this machine.
A lot of the controlling utilities for configuration are not documented
at all, e.g. /etc/machid, /etc/isat386, chkconsole, etc. etc.)

BTW, I have since moved the modem to COM1 (once I got the right
wireable connectors), so this isn't a problem for me anymore...

--
Alan Denney      aland@informix.com      {pyramid|uunet}!infmx!aland

 "Girl, we couldn't get much higher."  -  Joe Isuzu