weird startup issue in vista hp 32bit

Soldato
Joined
25 Nov 2006
Posts
2,686
Location
Ipswich, Suffolk
hi,

normally my laptop starts up fine and dandy. but since installing objectdock it takes ages to startup!

the issue seems to be that the laptop thinks the network cable is unplugged when it restarts (when in reality it isn't). so when it boots into windows the network icon has a red cross over it and it takes a few seconds to detect the network, obtain the ip from the router etc, and then get through to the net. while all this is happening the nod32 splash screen is stuck on the screen as it requires an internet connection to load fully (as it checks for updates).

objectdock has full access via my firewall so it's not that that's causing it.

this also happens when i use rocketdock instead.

i'll have to stop using the dock programs for now, which is a shame as i like them...unless anyone has any ideas what's going on?
 
When my HP boots, it always has a red cross over the network connection to begin with, and then shortly after it shows connected. It has always been like this, ever since I started using Vista back in January.
 
yeah i've noticed it doing it even without objectdock installed now! maybe it did it beforehand then?

it just seemed more noticeable when i installed objectdock.
 
Does it on both my machines, only takes around 2seconds from the red cross to show the globe so it isn’t an issue to me, can’t say I’ve ever noticed it connected straight away.
 
Okay thats an issue then :p Could be your router? how are you connecting to the net?

i use a fairly old westell router (it's about 3yrs old).

i have a network cable run from my laptop to a network switch and then from the switch to the router. then the cable from the router goes straight into the main phone line for the house.

i'm changing up to wireless soon so maybe this will sort it out. i currently have the wireless network adaptor (atheros AR5007EG) disabled in the device manager.
 
I was going to say perhaps it’s the wireless (My old laptop took a while to get an IP address) but your connecting via cat cable so this shouldn’t be an issue, have you checked if there are any updated drivers for the Ethernet card? Maybe try and set your IP address manually rather than DCHP worth a shot.
 
i should have said...ip address is set manually :)

drivers for the network card (an nvidia nforce networking controller) were updated about 10 days ago, but i'll check for more as the update came via windows update.
 
Last edited:
i should have said...ip address is set manually :)

drivers for the network card (an nvidia nforce networking controller) were updated about 10 days ago, but i'll check for more as the update came via windows update.

Ah okay, may well be just one of those little annoyances that don’t get sorted :( My only other suggestion is that the router/switch has seen better days, is there a possibility you could try another? Or perhaps connect directly to the router bypassing the switch?
 
Ah okay, may well be just one of those little annoyances that don’t get sorted :( My only other suggestion is that the router/switch has seen better days, is there a possibility you could try another? Or perhaps connect directly to the router bypassing the switch?

it could be one of those things. i mean it'll only be the first boot of each day as i'll rarely re-start once it's all running. it's just one of those little annoying things that will bug me!

i could try another port on the switch as a test, and if that doesn't sort it i'll plug straight into the router (not for long though as my 360 and printer are on the network as well).

edit...quick update. a different port on the switch didn't sort it, and going straight into the router didn't either. so i've reset the router and the network adaptor to see if that makes a difference.

otherwise, it's one of those "things!"

another edit...just come home from t'pub and it was better this time. weird, but there you go. that's pc's for you!
 
Last edited:
Back
Top Bottom