Re: (PMOD) Emachines/Etowers

I don't work for Lucent RABU (livingston@iav.com)
Fri, 25 Jun 1999 18:11:58 -1000 (HST)

On Fri, 25 Jun 1999, Ed Schulz wrote:
> I don't work for Lucent RABU wrote:
> > On Thu, 24 Jun 1999, Bullit wrote:
> > > Daniel
> > > I understand the false UART to be caused by the use of WinModems. To the
> > > best of my knowledge, WinModems do not use a serial port, therefore no UART
> > > is even being used, so it doesn't really matter what the UART says.
> >
> > *BEEP* Unfortunately, winblowz does care what it sees as a UART.
> >
> > Look at Compaqs! When 8250 is listed the modem is total crap. When you
> > do the fix... posted in archives or portmaster-users I believe, then it's
> > only semi-crap ;)
>
> You're using faulty logic here. Just becuase driver1 shows 8250 and driver1
> is crap does not imply that the crap is caused by the display of 8250.
> Especially when there's an example of a Windows modem driver (ours) that
> also displays 8250 but is not crap.

Actually I generalized and as such I apologize...

While I'm no windows code tech, for Compaqs changing the resources so that
16550 is the recognized UART fixes problems. Hmm, I seem to recall
another modem that had a similar problem, but it most likely was a
Rockwell HCF also.

> I believe that there are far more important issues to chase than this one.
> (And perhaps we could be somewhat more precise in our problem description
> than "crap.")

8) Crap as in a pile of sh^t ... Well more descriptive, modems will not
negotiate typically 5-7 of Modem not responding on other side, or a
Network connection could be established. Then when it does connect, will
disconnect within a few minutes. .110 seems the worst and .135 didn't
have much improvements, maybe 3-4 no response and 5 minutes until a
disconnect. But that's old history and I'm waiting to see a revision
higher than .156 to pop out ;)

In all, making sure UART is reported correctly and have .156 for HCF is
wonderful.

Using 5.49 for lt modems is awesome for all of my customers but one (so
far). That one I'm thinking is a telco routing problem since he connects
to Sprintnet at consistent 50666 and 19 out of 20 times connects first
attempt... No biggie, since we're his backup link for now.

--
Aloha from Paradise,

Sherwood Got Clue? If so: ISPF! The Forum for ISPs by ISPs, <http://www.ispf.com>

- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-modems' in the body of the message.