Page 1 of 2

Replacing E6850 with Q6600.  Need to reinstall XP?

PostPosted: Thu Jan 24, 2008 3:35 pm
by raptorx
I am replacing my dual core E6850 with a quad core Q6600.  Do I need to tweak windows or FSX or anything else on my system?  Can I just switch the CPU out and Rock & Roll?

-Thanks,

-Jim

Re: Replacing E6850 with Q6600.  Need to reinstall XP?

PostPosted: Thu Jan 24, 2008 6:40 pm
by M.R.Maiornikov
well i changed my e6600 to q6600 and it was all plug 'n' play, had to verify the bios if xp decetced it, but it did so no problem there.

Re: Replacing E6850 with Q6600.

PostPosted: Thu Jan 24, 2008 9:06 pm
by NickN
As long as you are gong from a dual to a quad (or higher) you are good to go. make sure the BIOS supports the processor

The only time you will need t reinstall is going from a single to a multicore. Windows may or may not properly detect it but since the HAL in installed when Windows installs and since a MCP is different than a single when it comes to the HAL, its bet to reinstall Windows if you go from a single to a multi

Re: Replacing E6850 with Q6600.

PostPosted: Thu Jan 24, 2008 10:22 pm
by raptorx
Beautiful!  Thanks.

Re: Replacing E6850 with Q6600.

PostPosted: Thu Jan 24, 2008 10:24 pm
by raptorx
Nick,  for the Q6600, is the OEM version any different then the retail?  I don't need the heatsink but I don't want a bunk OEM cpu if the retail is better.  -Jim


As long as you are gong from a dual to a quad (or higher) you are good to go. make sure the BIOS supports the processor

The only time you will need t reinstall is going from a single to a multicore. Windows may or may not properly detect it but since the HAL in installed when Windows installs and since a MCP is different than a single when it comes to the HAL, its bet to reinstall Windows if you go from a single to a multi

Re: Replacing E6850 with Q6600.

PostPosted: Fri Jan 25, 2008 10:11 am
by NickN
no different as long as the OEM and the retail are from the same stepping family, something you probably can not tell unless the retailer posts the step code

The Q6600 has an old and new lot-batch. The newer lots are of a different stepping which changes the thermal specs on the CPU but the performance is is the same. the newer ones can run a bit warmer without problems.

Re: Replacing E6850 with Q6600.

PostPosted: Fri Jan 25, 2008 10:16 am
by raptorx

no different as long as the OEM and the retail are from the same stepping family, something you probably can not tell unless the retailer posts the step code

The Q6600 has an old and new lot-batch. The newer lots are of a different stepping which changes the thermal specs on the CPU but the performance is is the same. the newer ones can run a bit warmer without problems.


Cool.  I ordered the OEM from Newegg.  It looks like it will be the G0 stepping from what all the reviews say.  If all G0 stepping OEM are the same then I'm happy.

Thanks Nick!

P.S.  I'm really looking forward to your updates for the GEX and UTX nightlighting.  I've been following the Flight1 forums and that update and I can't wait!

-Jim

Re: Replacing E6850 with Q6600.

PostPosted: Fri Jan 25, 2008 3:18 pm
by Ivan
As long as you are gong from a dual to a quad (or higher) you are good to go. make sure the BIOS supports the processor

The only time you will need t reinstall is going from a single to a multicore. Windows may or may not properly detect it but since the HAL in installed when Windows installs and since a MCP is different than a single when it comes to the HAL, its bet to reinstall Windows if you go from a single to a multi

You can change that in 'device manager' afterwards... dunno if that does a 100% fix though

Re: Replacing E6850 with Q6600.

PostPosted: Sat Jan 26, 2008 1:06 am
by raptorx
The quad is in!  Now do I add the "job scheduler" line to the fsx.cfg and set it to "15"?

Re: Replacing E6850 with Q6600.

PostPosted: Sat Jan 26, 2008 8:56 am
by NickN
As long as you are gong from a dual to a quad (or higher) you are good to go. make sure the BIOS supports the processor

The only time you will need t reinstall is going from a single to a multicore. Windows may or may not properly detect it but since the HAL in installed when Windows installs and since a MCP is different than a single when it comes to the HAL, its bet to reinstall Windows if you go from a single to a multi

You can change that in 'device manager' afterwards... dunno if that does a 100% fix though


Its not. The HAL only installs when Windows installs clean. One of the reasons XPSP2 was such an issue as an update prior to being released slipstreamed on the XP disks was because of the changes to the HAL it made. Network Admins knew the best way to apply SP2 was to make their own install disks specifically for that reason and perform a clean install.

It will work but I have also personally seen the difference in just swapping to a multicore processor and doing an entire Window reinstall on the new multicore.

Its better to do the install when going from single to multi

Re: Replacing E6850 with Q6600.

PostPosted: Sat Jan 26, 2008 12:04 pm
by raptorx
Nick, just so I'm clear on this;  Replacing the E6850 dual core with the Q6600 quad core does not require a reinstall of XP to get the FULL functionality of the quad core, correct?

-Jim


As long as you are gong from a dual to a quad (or higher) you are good to go. make sure the BIOS supports the processor

The only time you will need t reinstall is going from a single to a multicore. Windows may or may not properly detect it but since the HAL in installed when Windows installs and since a MCP is different than a single when it comes to the HAL, its bet to reinstall Windows if you go from a single to a multi

You can change that in 'device manager' afterwards... dunno if that does a 100% fix though


Its not. The HAL only installs when Windows installs clean. One of the reasons XPSP2 was such an issue as an update prior to being released slipstreamed on the XP disks was because of the changes to the HAL it made. Network Admins knew the best way to apply SP2 was to make their own install disks specifically for that reason and perform a clean install.

It will work but I have also personally seen the difference in just swapping to a multicore processor and doing an entire Window reinstall on the new multicore.

Its better to do the install when going from single to multi

Re: Replacing E6850 with Q6600.

PostPosted: Sat Jan 26, 2008 2:21 pm
by MWISimmer
If anything does go belly up when you swap CPUs you can always do a repair with the windows disk, that should cure any problems you have. I'm sure a full reinstall isn't necessary, but remember that may get rid of some unwanted junk, so may well be the better option.

Re: Replacing E6850 with Q6600.

PostPosted: Sat Jan 26, 2008 5:26 pm
by raptorx
Well, it's in and running along nicely at 3.42 GHz.  I did a virus scan with NOD32 and saw at least 3 cores being used at times.  I'm not even done overclocking yet.  At 2.4 Ghz my system seemed a lot slower than my E6850 running at 3.8 GHz.  But once I clocked it up past 3.0 GHz I couldn't tell the difference anymore-and it is smokin fast right now at 3.4 GHz.  Task Manager sees it-I like looking at 4 usage graphs!

I need to fly now.

Re: Replacing E6850 with Q6600.

PostPosted: Sun Jan 27, 2008 2:22 am
by NickN
If anything does go belly up when you swap CPUs you can always do a repair with the windows disk, that should cure any problems you have. I'm sure a full reinstall isn't necessary, but remember that may get rid of some unwanted junk, so may well be the better option.



Sorry, thats incorrect

A repair will not install/update a HAL. The HAL is only fully installed during a clean Windows start

Not everyone will have problems going from single to multi, but I have seen more than its worth even trying.

Also, some cat tell the difference or even know they are not running properly. Since they have no experience with the new processor they have no idea just how poorly they are running and never suspect there is an issue.

Re: Replacing E6850 with Q6600.

PostPosted: Sun Jan 27, 2008 2:25 am
by NickN
[quote]Nick, just so I'm clear on this;