MT2834MR Vs. 1.14E / 3.14E Release Notes
		 Changes from x.14B -> x.14E

		 **NOTE** WHAT CHANGED WHEN
		          (x.14C was never released.)
		          (x.14C1 was never released.)
		          (x.14D was never released.)
		          Items 1 - 7 were changes from x.14B -> x.14C.
		          Item 8 was changed from x.14C -> x.14D.
		          Item 9 was changed from X.14C -> X.14C1
		          All of these changes apply for x.14B -> x.14E.


1) In fax mode added a 10mS timer at the end of the Tx page to wait for the
   "RTC Data" to be transmitted.  TQT

2) There was a problem for some MR3 cards, where when the controller would
   reset the modems, some would intermittently go off-hook and stay that way
   until an ATH0 was issued.  There was a memory location that was getting
   initialized for the MR6 but not the MR3.  When the memory location was
   not getting initialized, this off-hook problem would show up randomly
   on some MR3 boards.  GTA

3) It was seen that when the MR3 answered a ring, never connected to any
   modem, therefore putting out a NO CARRIER after S7, the modem would then
   send two disconnect faults to the controller instead of one.  The second 
   bad disconnect fault would show "probable wrong number/busy" which is
   incorrect.  Fixed this in the disconnect routine by commenting out an
   un-needed call to the routine "ctk_BuildNoConnectPacket".  The routine
   "ctk_BuildDisconnectPacket" takes care of building the disconnect packet,
   so don't know why the call to "ctk_BuildNoConnectPacket" was ever called
   in answer mode.  GTA

4) On disconnect, now cleared the in dial backup flag.  The problem was
   compatibility with the MT5600BA/BL.  The MT5600BL actually hangs up the
   dial backup connection when trying LL restoral.  That shouldn't matter
   but when leased line is restored the in dial backup flag was still set
   and after S18 amount of time the MT2834xx would disconnect the leased
   line connection which is not desirable.  GTA

5) Previous version, dial backup through the MMM software (not switches) did
   not work.  It would do one leased line connection then return to idle AT
   mode.  Basically the way this is to work is that the controller sends an 
   &L2 or &L4 and the modem believes it is in leased line by the switches.
   Some LL ram check code was previously put in place to compare the switch
   memory to the actual switches to see if memory was corrupted and watchdog
   the modem if that was the case, which broke leased line and dial backup.
   Now to fix this a flag was added so when an &L2 or &L4 was issued, the
   flag would get set so as to indicate to the ll ram check code to not
   conduct it's test during software dial backup.  GTA

6) For all International MRIs, Bell 103 was sent to the backplane instead of
   V.21.  The data pump seems to indicate Bell 103 when it was actually a
   V.21 handshake.  Fixed by sending V.21 to the backplane when ever a
   300bps connection was made for the Internationals.  GTA

7) There was a problem found where the ROM based MR3 modems would get into a
   state where the modems wouldn't detect dialtone anymore.  It was found
   that the ROM based MRs were not getting hard resets from the Z182
   controller.  JPD

8) The problem occurred when a busy number was dialed continuously.  The
   symptom was when the problem occurred then 'AT' commands via the RS232
   wouldn't work.  The problem was that the phone buffer was overflowing
   when the busy number was dialed over and over.  Now fixed.  JPD

9) Change so when S0 is equal to 255, there is no ring detection for the
   MR modem.  GTA