Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!security!genrad!decvax!microsoft!uw-beaver!tektronix!ogcvax!omsvax!icalqa!hplabs!sri-unix!Little.Fleas@hi-multics
From: Little.Fleas%hi-multics@sri-unix.UUCP
Newsgroups: net.micro
Subject: Request for help (long msg)
Message-ID: <12963@sri-arpa.UUCP>
Date: Tue, 25-Oct-83 22:47:00 EST
Article-I.D.: sri-arpa.12963
Posted: Tue Oct 25 22:47:00 1983
Date-Received: Thu, 3-Nov-83 22:45:47 EST
Lines: 31

From:      Gary Little <Little.Fleas@hi-multics>

The initialization you show is rather "magical".  How it could
intitalize anything is amazing.  The CRT should not need to be worried
about since your monitor or another power up sequence will bring it up
properly -- in fact it may be memory mapped instead of an asynch
controller and would different initialization.  BUT, the modem is
guaranteed to need some fancy (not magical) massageing.  The process is
as follows:

          output reset code to async controller (hex 03 for a MC6851)
          output clock, parity, framing bits, and data size to controller
                    (clock = 1/1, 1/16, 1/64)
                    (parity = odd, even, none)
                    (data size = 7 or 8 data bits)
                    (framing bits = number of start, stop bits)
          output interrupt status (on/off, hi to low, low to hi, etc.)
          
NOW you can read the port "ah cupple times".  Resetting the port should
drop DTR, CTS, RTS, and maybe even DCD.  The Hayes will probably respond
to one of these changing state.  IF that don't work then try sending a
break:

          output break code to port 
          do for 200 milliseconds
          end do
          perform standard port initialization  

More than likely toggling DTR will do the trick.

                    Gary Little