SSD too quick

Soldato
Joined
30 Jan 2007
Posts
15,512
Location
PA, USA (Orig UK)
Well I have just got an SSD from a friend (An OCZ Vertex Sata II), and it all seems good, 100% health etc.

However, has anyone else noticed an issue where the PC is booting into windows so quick, that DHCP doesn't have time to assign an IP address quickly enough, so things like MSN Messenger/Origin etc can't sign in.
 
Last edited:
Home network?

Set you pc to have a static ip at the top of the range and exclude it from the scope.

Maybe also set the net card to 100full duplex ( or what ever the router supports) to save on the auto negotiate time which takes a while on some cards ( a while being a few seconds)
 
lol I never thought I would hear someone complaining that their computer started too quickly. A static IP address would probably solve your problem
 
If you can't assign a static IP, you can issue a "ipconfig /renew" in the command prompt.

Would be easy enough to then drop this into your startup so it runs 30 seconds after you have booted.
 
There is no such thing as "too fast".

I want my PC to boot before I even switch it on, and the apps that I want to use should launch about 5 seconds before I start using them. :D

Until that is possible, I'll settle for an SSD.
 
If you can't assign a static IP, you can issue a "ipconfig /renew" in the command prompt.

Would be easy enough to then drop this into your startup so it runs 30 seconds after you have booted.

You can always set a static IP in the network connection config, just the router way is a bit more elegant
 
lol, I'd actually expected the static IP answer. If that's the only real answer, then I'll do that, still think it's it's a little nuts though.

It's very annoying because all these clients are a pain in the ass when they can't login as they typically forget the password deliberately on a failed login. (Well.. I'll rephrase that.. origin and steam typically).

I will assign either 1000 or 100 in a sec and see how it goes before resorting to a fixed IP (not that that's really an issue btw... I just like having full DHCP)
 
However, has anyone else noticed an issue where the PC is booting into windows so quick, that DHCP doesn't have time to assign an IP address quickly enough, so things like MSN Messenger/Origin etc can't sign in.
Yes i get this problem with steam sometimes..
 
I dont see how you have this problem?
The second i login i click firefox and it opens up instantly with the internet fully functional.
Im with Sky and dont currently have a static IP.
 
I think you misunderstand seanyc5. They are not talking about they internet connection with a static IP, they are talking about my internal (home) network, where my router acts as a DHCP server, assigning IP Address automatically (and variably) to devices that register on the network. As I boot into windows, there is a little negotiation going on to 'get' an address from the DHCP server (the router), and once it has an IP address it's all good.

So in this instance, I boot into windows, origin/steam tries to connect to the network, but as I don't have an IP address assigned to my PC yet it can't get access, so they bail out. A few seconds later... the PC has got it's address, but it's too late. I now have to type in the password for origin/steam.

This likely wouldn't be a problem if I had another user account on the PC, so it sat at the login menu first.
 
I see, you boot straight to desktop without a password. Is it not possible to just set origin/steam tonot login automatically as dont launch them to open your game anyway? I dont use either so wouldnt no.
 
I see, you boot straight to desktop without a password. Is it not possible to just set origin/steam tonot login automatically as dont launch them to open your game anyway? I dont use either so wouldnt no.

Yes, I can set it to not auto start. This time it was MSN that didn't quite work.

I checked for a static IP, and it's already set to static on the BT Homehub ("Always user this IP Address"). I have changed to always be 1Gbps as well. (And yes, it was a fresh install of win7 64 bit ultimate).
 
Last edited:
Yes, I can set it to not auto start. This time it was MSN that didn't quite work.

I checked for a static IP, and it's already set to static on the BT Homehub ("Always user this IP Address"). I have changed to always be 1Gbps as well. (And yes, it was a fresh install of win7 64 bit ultimate).

That just means that the router will give you the same IP each time it receives the DHCP request from your computer. You will still experience the delay where your DHCP client requests an IP address from the network and has to wait for the router to reply and give the same IP address.

What we mean by static IP is manually configuring the TCP/IP settings of your network adapter so that when Windows starts, it uses the manually set IP address straight away without even considering send a request out to the network. Your router doesn't care if your IP address was assigned by DHCP or not, as long as it's on the same subnet as the LAN side of the router, Windows will have internet connectivity as soon as it starts.
 
Back
Top Bottom