🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.comp.dcom.modems
Article #145

Re: HELP! 56K connects @ 26.4

#145
From: Kevin Gee
Date: Wed, 11 Nov 1998 00:00
48 lines
3299 bytes
another thing that helps is a GOOD QUALITY modem
I had an IBM rockwell 56K that could connect at 54K consistently...had a
small accident with it and eneded up buying a diamond supra express or
something like that and could only get 44K max same ISP and everything
it's all about quality
finally got smart though...thank god for cable =oP
Paul Holloway <pauldh@telapex.com> wrote in message
news:36499F2F.B4C10A4F@telapex.com...
>Dave wrote:
>>
>> Julio Alano wrote:
>> >
>> > Is anyone else suffering from this or is it just me?
>> > Any comments are welcome.
>> > I am in Washington State area. I connecting using an internal 56k pci
modem.
>> > It will only connect at 26.4k (reported by DUN)
>>
>> You are NOT alone.  I, too, have been taken in by this "56K" scam.
>>
>> My 33.6 USR winmodem consistently connected at 31.2
>>
>> My X2 USR winmodem usually connected at 28.8 (to USR X2 dialup)
>>
>> My V.90 USR winmodem usually connects at 26.4 (to USR V.90 dialup)
>>
>> USR, to its shame, blames my phone line.  I wonder how my phone line
>> knows to degrade itself every time I get a supposedly-faster USR modem???
>>
>> --
>>
>> - Dave
>
>There is no 56k "scam".  56K technology is based upon several premises,
>namely that your phone lines support 56K transfer rates.  Instead of
>moaning about beings "scammed" etc, you should work towards finding out
>why you aren't able to get better than V.34 connections, and then go
>about solving the problems.  If you phone lines are capable, and you
>have a 56k modem and are dialing into a compatible ISP and both ends are
>using compatible firmware versions, you should get a 56k connection.
>Given that those same USR modems will get 56k connections at a variety
>of spots in the world, then I would look to your phone lines before I
>looked to your modem as the culprit.
>--
>Paul Holloway
>Customer Service Representative
>Telapex Internet
>pauldh@telapex.com
Technical Details
Message-ID: <Eon22.1212$FY5.8140001@storm.twcol.com>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <Yg502.17549$357.345@news-reader.bt.net> <36491A4A.291F@all.com> <36499F2F.B4C10A4F@telapex.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 161832,291037ed63bab9cc
X-Google-Attributes: gid161832,public
X-Google-Thread: 102a94,291037ed63bab9cc
X-Google-Attributes: gid102a94,public
X-Google-Thread: 104560,291037ed63bab9cc
X-Google-Attributes: gid104560,public
X-Google-Thread: 10beba,291037ed63bab9cc
X-Google-Attributes: gid10beba,public
X-Google-Thread: 10cb69,291037ed63bab9cc
X-Google-Attributes: gid10cb69,public
X-Google-Thread: 100fd6,291037ed63bab9cc
X-Google-Attributes: gid100fd6,public
X-Google-Thread: 1108fc,291037ed63bab9cc
X-Google-Attributes: gid1108fc,public
From: "Kevin Gee" <kgee@columbus.rr.com.no.spam>
Subject: Re: HELP! 56K connects @ 26.4
Date: 1998/11/11
Message-ID: <Eon22.1212$FY5.8140001@storm.twcol.com>
X-Deja-AN: 410851595
References: <Yg502.17549$357.345@news-reader.bt.net> <36491A4A.291F@all.com> <36499F2F.B4C10A4F@telapex.com>
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800
X-Trace: storm.twcol.com 910820004 204.210.239.194 (Wed, 11 Nov 1998 16:33:24 EDT)
Organization: Time Warner Communications Columbus
X-MSMail-Priority: Normal
NNTP-Posting-Date: Wed, 11 Nov 1998 16:33:24 EDT
Newsgroups: alt.comp.dcom.modems,alt.net.and.modem.games,comp.dcom.modem,comp.dcom.modems,demon.tech.modems,netcom.modems,netcom.uk.support.modems