USB router problem on new system

CF93 · 8 Feb 2007 at 12:59

A mate has jsut upgraded to a new Core2Duo system, but since then has been having problems with his internet connection - it keeps dropping every couple of minutes basically. Router is one of those BT Voyager things (don't know exactly which model though) that BT send out on signing up to their broadband package.

It worked fine on his old single core system, so I wondered if there could be a problem caused by the fact he's on dual core, as we had problems installing it using the supplied CD (the installer kept throwing up an error.) Just plugging it in and letting the new hardware wizard find the drivers on the CD worked fine though.

Would he need to have the drivers/device set to run on one specific core, or should that not be relevant? If it would help, how is it done?

Thanks.

melbourne720 · 8 Feb 2007 at 13:04

I doubt it would be the dual core, TBH. Isn't it a case with those USB modems (if it is a router, surely it would connect through the Ethernet port??) that you install the drivers and then connect the device (otherwise the wrong drivers get automatically installed)?

Try that.

CF93 · 8 Feb 2007 at 14:14

Cheers.

I called it a router as I think it's one of those with both USB and ethernet ports. Don't know for sure though.

We did try to do the "drivers first" thing, but the installer kept crashing. XP didn't install any drivers automatically when we plugged it in without the drivers installed, just brought up the "found new hardware wizard" - so I let it go looking for drivers on the CD which seemed to work.

Don't really want to muck around with it too much as it's a brand new XP install on a new build, but I wonder if there are different drivers on the CD that it should have picked. Didn't think of that. Can't seem to find any drivers online either

melbourne720 · 8 Feb 2007 at 15:18

CF93 said:
Cheers.

I called it a router as I think it's one of those with both USB and ethernet ports. Don't know for sure though.

If it has Ethernet ports then just connect via an Ethernet cable, and you won't need any drivers!

CF93 · 8 Feb 2007 at 16:28

Yeh, I did wonder if that might be the way to go. I'll have to check on the model he's got....

Of course it could still turn out to be an exchange/ISP problem. But that would be a pretty big coincidence given the problem only started when we did the new build.