🚀 go-pugleaf

On 23 Dec 1995 15:52:13 GMT, David C Cooper <dcooper@tcp.co.uk> wrote:

>      I have been sucessfully using a Sportster 14400 
>internal modem on a 486SX board with WIN95, using the Microsoft
>dial-up software with a script, to access the Internet.
>      I have now assembled a new system using an ASUS P55TP4XE 
>board, transferred my Sportster and net software to it, set up
>the dial-up software as before, and tried it. No good.
>      The terminal window comes up, but almost every time
>nothing further happens ( just twice the login, password and
>protocol inputs were read, but nothing further happened )
>      I also tried using Trumpet Winsock, this always got
>through the login etc. but then locked up.
>      Quicklink always works OK to dial in to various bulletin 
>boards, no problem.

My guess is that TCP had a few problems when you were trying to log in. I have
had a similar thing happen occasionaly. Things sort themselves out after a sort
time.

Have you tried it again since?

--
------------------------------------------------------------
Gareth Blades  (gareth@blades.tcp.co.uk)
Homepage:      http://www.tcp.co.uk/~blades/index.html
PGP key available from hompage

      My problem is solved. See message from Todd Bitikofer
in 'comp.dcom.modems' shortly after this one. Apparently a bug
in Microsoft's S3 video card driver causes a device on COM4
to work incorrectly. And when upgrading I moved the Modem to
COM4. Putting it back to COM3 cured all.
       Thanks to Todd.
              David

> Apparently a bug in Microsoft's S3 video card driver causes a
> device on COM4 to work incorrectly.

That's wrong! It's not a bug in the software but a hardware problem with 
S3-based graphics adapters. On ISA and ISA-like behaving busses the I/O 
address space is limited to 12 address bits. S3-chips have a I/O port 
that conflicts with COM4 on such systems, but would not collide to 
systems with full 16 bit I/O address space like MCA (micro channel 
architecture).

  So long,
    -+- Dirk -+-

Dirk Ohme <dohme@cpu3> wrote:

> > Apparently a bug in Microsoft's S3 video card driver causes a
> > device on COM4 to work incorrectly.
> 
> That's wrong! It's not a bug in the software but a hardware problem with 
> S3-based graphics adapters. On ISA and ISA-like behaving busses the I/O 
> address space is limited to 12 address bits. S3-chips have a I/O port 
> that conflicts with COM4 on such systems, but would not collide to 
> systems with full 16 bit I/O address space like MCA (micro channel 
> architecture).
> 
>   So long,
>     -+- Dirk -+-

But the newest software drivers from most S3-based video card
manufacturers eliminate this problem. 

Best wishes,
Curt....



_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
         Curt's High Speed Modem Page:
 http://www.teleport.com/~curt/modems.html
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/     

Dirk Ohme <dohme@cpu3> wrote:

> > Apparently a bug in Microsoft's S3 video card driver causes a
> > device on COM4 to work incorrectly.
> 
> That's wrong! It's not a bug in the software but a hardware problem with 
> S3-based graphics adapters. On ISA and ISA-like behaving busses the I/O 
> address space is limited to 12 address bits. S3-chips have a I/O port 
> that conflicts with COM4 on such systems, but would not collide to 
> systems with full 16 bit I/O address space like MCA (micro channel 
> architecture).
> 
>   So long,
>     -+- Dirk -+-




But the newest software drivers from most S3-based video card
manufacturers eliminate this problem. 

Best wishes,
Curt....











_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
         Curt's High Speed Modem Page:
 http://www.teleport.com/~curt/modems.html
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/     

Dirk Ohme <dohme@cpu3> wrote:

>> Apparently a bug in Microsoft's S3 video card driver causes a
>> device on COM4 to work incorrectly.

>That's wrong! It's not a bug in the software but a hardware problem with 
>S3-based graphics adapters. On ISA and ISA-like behaving busses the I/O 
>address space is limited to 12 address bits. S3-chips have a I/O port 
>that conflicts with COM4 on such systems, but would not collide to 
>systems with full 16 bit I/O address space like MCA (micro channel 
>architecture).

And not with all S3 card. I have 4 series and 2 // in my computer and
it work. Just a thing, retailer told me, my S3 with 4Mo can have 16M
colors in 1200*1024. I still wait for a S3 driver wich support this
resolution !
Happy 
New              opworld@worldnet.fr
Year