Article View: comp.dcom.modems.cable
Article #546Re: New cox cable managed network
From: atakicker
Date: Sat, 16 Feb 2002 01:52
Date: Sat, 16 Feb 2002 01:52
17 lines
2959 bytes
2959 bytes
"PC Medic" wrote in message
> The person dropping the cable should not be the same person installing the
> cable modem.
> If you do not have a drop already in the room where the PC will be, it
> should have been scheduled separate from the PC and modem configuration.
Not in my world. I had cable TV and internet installed on the same day.
One guy came out and ran the drop from the pole to the house and hooked up
the TV. Later that day another one came out and ran from the box under the
eave of the house (which was installed by the first guy) to the computer,
which is in a different room. The only thing he didn't do was drill through
the cinder block wall. I did it for him because I have a 100 pound mean a__
dog in the yard. (But I did use his tools). And he did have a problem, he
screwed up my irq settings and couldn't get my sound card to work. After 45
minutes of watching him scratch his head and three calls to someone (?), I
ran him off and reset everything myself.
Technical Details
Message-ID:
<gXib8.10520$SJ3.387856@news1.east.cox.net>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!hub1.nntpserver.com!peer1-sjc1.usenetserver.com!usenetserver.com!newsfeeds-atl1.usenetserver.com!cox.net!news1.east.cox.net.POSTED!53ab2750!not-for-mailReferences:
<I0VX7.10375$B61.4953680@news1.rsm1.occa.home.com> <3C314C9C.DEDF0FCC@reece.net> <82lY7.33203$K36.11443500@news1.rdc1.va.home.com> <3C334AC0.7C6370B@reece.net> <bc5b60f8.0201170659.1fb61766@posting.google.com> <m_V48.3805$zR3.251588@news2.east.cox.net> <bc5b60f8.0201272107.82cbac8@posting.google.com> <dQo68.4657$Xk4.242975@news1.east.cox.net> <ggS68.7796$Xk4.425111@news1.east.cox.net> <y3U68.8160$Xk4.436368@news1.east.cox.net> <3%Z98.7525$zb.402885@news1.east.cox.net> <jQxa8.2975$SJ3.111671@news1.east.cox.net> <ShIa8.4164$SJ3.170583@news1.east.cox.net> <nnPa8.6168$SJ3.212179@news1.east.cox.net> <S4Ra8.6327$SJ3.221438@news1.east.cox.net> <Cagb8.10394$SJ3.374222@news1.east.cox.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1136e3,710aa4d82544bdbb X-Google-Attributes: gid1136e3,public X-Google-Thread: 10f392,a7865c87070b0fcc X-Google-Attributes: gid10f392,public X-Google-Thread: 113850,a7865c87070b0fcc X-Google-Attributes: gid113850,public X-Google-ArrivalTime: 2002-02-15 17:55:18 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!hub1.nntpserver.com!peer1-sjc1.usenetserver.com!usenetserver.com!newsfeeds-atl1.usenetserver.com!cox.net!news1.east.cox.net.POSTED!53ab2750!not-for-mail From: "atakicker" <nospam@nospam.net> Newsgroups: comp.dcom.modems.cable,cableinet.cable_modems,cox.internet.discussion.athomeconversion References: <I0VX7.10375$B61.4953680@news1.rsm1.occa.home.com> <3C314C9C.DEDF0FCC@reece.net> <82lY7.33203$K36.11443500@news1.rdc1.va.home.com> <3C334AC0.7C6370B@reece.net> <bc5b60f8.0201170659.1fb61766@posting.google.com> <m_V48.3805$zR3.251588@news2.east.cox.net> <bc5b60f8.0201272107.82cbac8@posting.google.com> <dQo68.4657$Xk4.242975@news1.east.cox.net> <ggS68.7796$Xk4.425111@news1.east.cox.net> <y3U68.8160$Xk4.436368@news1.east.cox.net> <3%Z98.7525$zb.402885@news1.east.cox.net> <jQxa8.2975$SJ3.111671@news1.east.cox.net> <ShIa8.4164$SJ3.170583@news1.east.cox.net> <nnPa8.6168$SJ3.212179@news1.east.cox.net> <S4Ra8.6327$SJ3.221438@news1.east.cox.net> <Cagb8.10394$SJ3.374222@news1.east.cox.net> Subject: Re: New cox cable managed network Lines: 19 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Message-ID: <gXib8.10520$SJ3.387856@news1.east.cox.net> Date: Sat, 16 Feb 2002 01:52:12 GMT NNTP-Posting-Host: 68.11.73.173 X-Complaints-To: abuse@cox.net X-Trace: news1.east.cox.net 1013824332 68.11.73.173 (Fri, 15 Feb 2002 20:52:12 EST) NNTP-Posting-Date: Fri, 15 Feb 2002 20:52:12 EST Organization: Cox Communications