systems2000
What? You Say It's Fixed. Hah
join:2001-11-29
Cyberspace
2 edits | reply to Qumahlin
Re: Comcast Summer 2005 Speed Upgrade Discussion
By the way it sounds that Comcast is handling this upgrade and price increase to Basic CATV subscribers, I'm ready to drop all Comcast services and go back to Dial-Up {since my only other option would be satellite).
I'm being charged almost $20.00 / month now for 22 channels of nothing that for more than six months have included network channels dropping out for hours, no stereo reception on several locals, video/audio sync problems all-day long on one or two major networks, and emergency radios interfering with a couple. To top all this off, the call center could care less.
As for the 4/384 service, Comcast call center can't even tell in real time if I'm on line or not and they consider a 95% uptime excellent (I had 100% with my old dial-up and no DNS lag).
The only way I would consider going back to Comcast is through a 1500/128 for $14.95 or 3000/256 tier for $19.95 and no CATV "Blackmail" fee.
Here's my current log:
This page displays detailed information intended for use by an authorized Motorola Cable Modem technician.
Time Priority Code Message
2005-07-12 14:55:04 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:55:03 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:55:03 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:55:03 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:55:02 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:55:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:55:01 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:55:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:58 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:57 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:41 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:41 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:29 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:24 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:22 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:22 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:54:18 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:54:17 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2005-07-12 14:54:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:53:46 3-Critical 0x0501BEF4 SYNC Timing Synchronization failure - Loss of Sync
2005-07-12 14:53:44 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2005-07-12 14:53:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:53:33 3-Critical 0x0501BE90 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2005-07-12 14:53:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:43:52 3-Critical 0x0501BE90 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2005-07-12 14:43:41 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2005-07-12 14:43:31 3-Critical 0x0501BE90 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2005-07-12 14:41:10 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:41:01 3-Critical 0x0501BE90 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2005-07-12 14:40:54 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2005-07-12 14:40:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:37 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:36 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:36 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:33 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:33 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:29 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:29 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:29 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:29 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:28 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:25 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:24 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:16 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:16 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:38:04 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:38:04 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:44 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:38 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:37 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:35 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:29 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:29 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:29 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:28 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:27 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:27 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:25 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:25 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:24 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:24 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:23 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:23 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-07-12 14:37:16 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-07-12 14:37:14 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
Event Log has reached maximum size. Older log entries are lost.
--
Personal Theme Song:
RUSH - Mystic Rythms from Power Windows.
Rush Radio Website -- WinAmp Stream 24/7 |
|
Amadeus
Premium
join:2005-05-02
Miami, FL | reply to oldTDNickell
that sucks. I guess i will have to give crapcast a call, i can't wait until fios comes to my area screw CRAPCAST.. |
|
travelguy
join:1999-09-03
Santa Fe, NM
1 edit | reply to Johkal
said by Johkal  :Marketing! The average broadband customer doesn't upload as much as download. No - control. The more upstream bandwidth Comcast allows, the less control they have over customers originating their own content.
fixed uneven quote tags. ~sorto' |
|
muecker
join:2003-07-20
Littleton, CO
1 edit | reply to dadkins
Just because OOL has a 4100 and gets 10Mb doesn't mean that Comcast will. There are a lot of variables.
There are multiple services out there that may or may not be turned on. These services WILL affect speeds. Some of these services will depend on modem capabilities such as:
Concatenation
Fragmentation
Prioritized, classified service flows
etc
If modems aren't capable, there might as well be a brick sitting in the customers' home.
There are also variables at play that someone outside the industry would have no clue of such as:
Modem vendor support/software upgrades - if the modem vendor decides to EOL a modem, then why would Comcast encourage their customers to get it?
Future service support - 1.1, 2.0, 3.0, PCMM, SIP, etc
Compatability with provisioning systems and CMTSs (including DHCP option 80)
Comparing one cable company to the other is almost like comparing apples and oranges especially in the content of this topic. OOL may or may not run services that Comcast has planned.
If OOL is running best effort traffic at 10Mb in a 1.0 provisioned modem, then there's not much more to offer.
Granted, most consumers wouldn't know about future services or care. "Give me 10Mbps or I'm going to cancel." Good for them.
But, there's some exciting stuff coming around the corner (in terms of time) that requires some companies to use current technologies. It seems to me Comcast is posturing themselves appropriately to cause less headaches for themselves (and ultimately their customers) in the future. |
|
imrf
Premium
join:2002-06-06
Utica, MI
 ·Comcast
·WOW Internet and C..
1 edit | said by muecker :Just because OOL has a 4100 and gets 10Mb doesn't mean that Comcast will. There are a lot of variables. Before jumping to conclusions, maybe you should read the list of approved modems then look at the list of the 4 modems that was posted that "won't work with this new upgrade" and see what's wrong. One thing is the Motorola SB series. They want the 4100s out but leave the 4200s in? They both use the same firmware and both have the same feature sets. It's obvious that whoever is making that list doesn't know what they are doing and an engineer who posts here regularly has confirmed this as well. |
|
QZ1
join:2005-03-24
| reply to dadkins
said by dadkins :Sorry, I don't work for Comcast(contrary to what I have been accused of), I get most of my info where we all can... Comcast.net. If I hear anything "new" I will post it here.  Right, I see now that you were just relaying that info. So, the mod at Comcast.net is not exactly right.
The link I provided was from the Comcast Press Room, (in case you didn't check it out), so I would say that it is official. |
|
dadkins
Can you do Blu?
Premium,MVM
join:2003-09-26
Hercules, CA
·Comcast
3 edits | Actually, the article you linked to is a copy from »www.prnewswire.com/ PRNewswire, a news service. Not from Comcast's PR Headquarters.
Direct link to the PRNewswire article:
»www.prnewswire.com/cgi-bin/stori···1&EDATE=
From Jason1 in the Comcast.net thread linked in my first post:
"The first post in this thread has come from the official announcement on the speed upgrades that were delivered to all Comcast HSI employees today and does contain the correct speed tier values."
Yes, I am just the messenger. 
EDIT: A tidbit from your linked article:
"* Comcast Standard Cable is made up of nearly 50 of the most popular cable networks such as CNN, Fox News, CNBC, MSNBC, ESPN, Discovery, History, The Learning Channel, and more."
Basic cable is 36 channels. Most(all?) of these listed channels are not included in Basic cable. |
|
muecker
join:2003-07-20
Littleton, CO
3 edits | reply to imrf
So, the 4100 and 4200 are exactly alike?
The 4200 uses the Broadcom 3345 Chip. The 4100 uses the 3350. So, go research the differences in these processors and get back to us.
It has to do with bugs in the processor and how it affects 1.1 services aka non-conformance issues.
I think you'll find some dramatic differences. |
|
madderhatter
Premium
join:2003-11-25
Tallahassee, FL | reply to dadkins
Tests are getting ready to begin in the Knoxville market at 16Mb down. |
|
imrf
Premium
join:2002-06-06
Utica, MI
·Comcast
·WOW Internet and C..
3 edits | reply to muecker
said by muecker :The 4200 uses the Broadcom 3345 Chip. The 4100 uses the 3350. So, go research the differences in these processors and get back to us. I'm well aware of the differences. In terms of the way they function on Comcast's network, they are identical.
The 4100 works fine in 1.1 mode with 10Mbps boot files, you are just guessing. |
|
Nerdtalker
Working Hard, Or Hardly Working?
Premium,MVM
join:2003-02-18
Tucson, AZ
clubs:
| reply to Johkal
said by Johkal :It would make sense to announce the modems that are only 1.0 & 1.1 may not achieve new speeds in a DOCSIS 2.0 environment. It happened to me. When they upgraded us to 2.0, my 1.0 modem maxed out at 3700. New DOCSIS 2.0 modem took me to 4700. I seriously doubt that, enormously. In fact, I'm 100% sure that just won't happen, period.
Particularly since DOCSIS 2.0 does nothing to increase downstream speeds, it adds no new downstream modulation schemes. 256QAM is the best you can get right now. Get used to 38 Megabits per downstream channel, because it'd stick if they moved to DOCSIS 2.0.
The coincidence you had with moving to a DOCSIS 2.0 modem improving speed only happened because you probably had one of the few modems that there were serious problems with, or that simply couldn't go over that speed because of hardware limitations. Not because it wasn't DOCSIS 2.0 certified.
--
"Some people never see the light till it shines thru bullet holes." -Bruce Cockburn
iPod Shuffle=iPos
I'm testing Gmail's spam filters: Broadbandreports1@gmail.com
Spam: 6200+ |
|
muecker
join:2003-07-20
Littleton, CO
1 edit | reply to imrf
They are NOT identical on the Comcast network. Go ask your engineer if Comcast uses Concatenation on their next-generation CMTSs. I KNOW the answer is NO. How would I know that if I didn't know the Comcast network? How do you know who I do/do not work for?
I'd like to see you get 10Mb down with no Concatenation (during a TCP session that requires ACK messages).
There is some thought behind this. |
|
Nerdtalker
Working Hard, Or Hardly Working?
Premium,MVM
join:2003-02-18
Tucson, AZ
clubs:
| reply to Johkal
said by Johkal :said by briandg :why don't they turn up the upload as well?!?!?! everyone else is doing it, why can't they? I can't wait til they light that fiber in my front yard. Marketing! The average broadband customer doesn't upload as much as download. Sadly, it's much more than that.
There are a number of reasons. Comcast doesn't want to do because increasing the upstream cap would:
•Increase/Encourage P2P use, especially BT
•Make Comcast HSI subscribers more attractive as "zombie" machines
•Either overload the 1.6 Mhz wide QPSK or 16QAM modulated upstream channels (2.3 megabits and 4.6 megabits of bandwidth respectively) which are already small enough and would seriously degrade all traffic, or require more upstream channels to be added
Plus, I seriously doubt that it'd be harder to market a higher number over a lower one, even if the customer doesn't know what benefit that gives.
I also already posted (in the last upgrade thread) that I received word from a very reputable source that comcast would be gradually moving to faster upstream speeds coinciding with this already publicly acknowledged downstream speed upgrade.
--
"Some people never see the light till it shines thru bullet holes." -Bruce Cockburn
iPod Shuffle=iPos
I'm testing Gmail's spam filters: Broadbandreports1@gmail.com
Spam: 6200+ |
|
imrf
Premium
join:2002-06-06
Utica, MI
·Comcast
·WOW Internet and C..
1 edit | reply to muecker
said by muecker : I KNOW the answer is NO. How would I know that if I didn't know the Comcast network? How do you know who I do/do not work for? They do use Concatenation on their "next-generation" CMTSes.
I'd like to see you get 10Mb down with no Concatenation (during a TCP session that requires ACK messages). Anyone can read the OOL forum and see that the modems would top out a roughly 5.5Mbps with it off. |
|
muecker
join:2003-07-20
Littleton, CO
1 edit | I will tell you something, you are wrong when you say they do use concatenation on their next gen cmtss....especially in 1.0 mode and some in 1.1 mode (even though an RTP could be set up in the boot file to turn it off) because one of their next gen CMTS vendors doesn't not support turning off concatenation via registered MAC state (1.1 vs 1.0).
Please note that the Cisco 7246 is not a next gen cmts.
You've stated no facts here and I've overloaded you with them. I can't wait for you to confirm with the engineer you have conversations with. |
|
Abiosis
join:2003-09-25
Covina, CA
·RoadRunner Cable
| reply to lazsheriff
said by lazsheriff :I checked the comcast site the basic cable package was around 9 bucks and includes about 25 channels and then theres the standard cable package that was around 54 a month which has mtv, vh1, etc etc. ok,mate,I'm on "standard cable tv" plan which pay 49.99 per month with 4/384 HSI for 19.99 with 2 more months left,is that mean I''ll be upgrade to 6/384 when it come to my area?I'm in Covina,CA,please advise,appricated...
--
"Blessed're those who can believe in something even if it's nothing..." |
|
imrf
Premium
join:2002-06-06
Utica, MI
·Comcast
·WOW Internet and C..
| said by Abiosis :ok,mate,I'm on "standard cable tv" plan which pay 49.99 per month with 4/384 HSI for 19.99 with 2 more months left,is that mean I''ll be upgrade to 6/384 when it come to my area?I'm in Covina,CA,please advise,appricated... Yep, you'll get the upgrade to 6Mbps when it comes. |
|
Scott W
Premium
join:2003-08-09
Beaverton, OR
| reply to djdanska
said by djdanska :Nothing like screwing those of us who don't want cable tv. Im not paying an additional $46.99 for expanded cable tv to get 8 Mbps down. Sad... If the prices listed at the beginning of this thread are right, they are REALLY gouging the people who don't want their crappy cable tv service. I'm not impressed with this at all. |
|
Naediel
join:2003-02-08
Chalfont, PA
| reply to dadkins
6mbps/384kbps? That is kind of cheap to me. Comcast is very very stingy with upload. Seems to me like they should be upgrading everyone (with the comcast cable tv) to 6mbps/768kbps and then with the 8mbps one the upload should be even faster. Sigh. I thought I was going to get faster upload. |
|
Abiosis
join:2003-09-25
Covina, CA
·RoadRunner Cable
| reply to imrf
said by imrf :said by Abiosis :ok,mate,I'm on "standard cable tv" plan which pay 49.99 per month with 4/384 HSI for 19.99 with 2 more months left,is that mean I''ll be upgrade to 6/384 when it come to my area?I'm in Covina,CA,please advise,appricated... Yep, you'll get the upgrade to 6Mbps when it comes. Thanks,mate
--
"Blessed're those who can believe in something even if it's nothing..." |
|
