O
Ocie Hudson
WinXP AutoUpdate has been activated since I took delivery
on this computer (9/11/03); usually it has done its work
while I'm logged-on via dial-up to my ISP, but sometimes
it apparently dials-out without any by-your-leave (I can
hear the modem initiation) when I'm offline. Recently,
I've connected my computer via an Ethernet NIC (on the
mainboard) & cable to a router that is connected to my
landlord's Comcast cable modem, and I'm getting broadband
Internet with no problems so far. However, AutoUpdate
apparently ignores the LAN and still dials-out. I've
removed the "default" status of the connectoid, but
AUPDATE.EXE still dials-out. Is this a bug?? If not,
then how can it be "persuaded" to use the broadband LAN
connection??
on this computer (9/11/03); usually it has done its work
while I'm logged-on via dial-up to my ISP, but sometimes
it apparently dials-out without any by-your-leave (I can
hear the modem initiation) when I'm offline. Recently,
I've connected my computer via an Ethernet NIC (on the
mainboard) & cable to a router that is connected to my
landlord's Comcast cable modem, and I'm getting broadband
Internet with no problems so far. However, AutoUpdate
apparently ignores the LAN and still dials-out. I've
removed the "default" status of the connectoid, but
AUPDATE.EXE still dials-out. Is this a bug?? If not,
then how can it be "persuaded" to use the broadband LAN
connection??