next »

[digidix]

I got myself a new mobo/ram and cpu, since the ram isn't part of the problem or question, I am using Windows 7 x64 atm with my current setup, would it be possible to use the current installation or would I have to install W7 all over again?

I have googled this and all people seem to be saying is that they have used either msconfig with the option of /set {current} detecthal yes or

BCDEDIT with the same option. I have searched the web as I am not quite sure what detecthal does, people have problems with the number of cores W7 seems to recognise on some pc. I know that HAL means Hardware Abstract Layer, and a particular file is needed too boot windows up. If I can boot up using the current installation, is that the right option to use msconfig, BCDEDIT etc..??

[Condor Baggins]

Providing you're using SATA/II you should be able to use msconfig just fine. It's your call at the end of the day, after all a W7 install doesn't take that long and you'll still keep the files on your HDD if you put the new install on a partition.

[digidix]

Providing you're using SATA/II you should be able to use msconfig just fine. It's your call at the end of the day, after all a W7 install doesn't take that long and you'll still keep the files on your HDD if you put the new install on a partition.

Its not the installation I'm worried about, it is the updates.....the endless hours of updating etc...I have adobe products as well that need updating after re-installation plus plus plus >.<

[Wooster]

I moved from a C2D based system to an i5 based one and kept the win7 x64 install I was using without any problems.

Put it this way, what have you got to lose?
If it doesn't work then you can install it afterwards. (Just make sure you have your backed up files on another drive beforehand)

[digidix]

I moved from a C2D based system to an i5 based one and kept the win7 x64 install I was using without any problems.

Put it this way, what have you got to lose?
If it doesn't work then you can install it afterwards. (Just make sure you have your backed up files on another drive beforehand)

Hours and hours of updates on a slow connection ^^

Did you use any of the commands on BCDEDIT or msconfig before you moved your pc unto the new mobo?

[Wooster]

Nope.
Just built the new rig, bunged in the old drives and fired it up.

There was the usual 'detected new hardware' thing that went on for a couple of restarts, but I used it for nearly a year without any issues.
The only reason that changed was when I installed an SSD drive and then changed my mind, but by that time I'd wiped the old install.

I don't know if going from one Intel based system to another helped at all, or if there would be different issues moving from AMD to Intel though. (You didn't say what your old CPU was.)

[digidix]

Nope.
Just built the new rig, bunged in the old drives and fired it up.

There was the usual 'detected new hardware' thing that went on for a couple of restarts, but I used it for nearly a year without any issues.
The only reason that changed was when I installed an SSD drive and then changed my mind, but by that time I'd wiped the old install.

I don't know if going from one Intel based system to another helped at all, or if there would be different issues moving from AMD to Intel though. (You didn't say what your old CPU was.)

Its Intel to Intel, at the moment I am not sure about AMD, maybe in the future when I decide I want another pc as backup

[keasy]

Just go for the install.

Don't format the drive, install to the same drive partition, W7 will back up the old install in a folder called 'windows old'.

All the files in that folder will still run and be recognised.


If you get fed up with the space that folder uses....copy the files across you need and delete windows old.

Worth a bash.

[digidix]

Right, it has been upgraded w/o new installation, now I am confronted by the activation $h*t no thanks to M$. Thought it was supposed to be 4 components not 3 regarding this

[gi joe]

Should activate fine.  Is it OEM?  Just call them up and explain, they should be fine with it.  Or you'll get the automated thing which should be fine as well.

[digidix]

Should activate fine.  Is it OEM?  Just call them up and explain, they should be fine with it.  Or you'll get the automated thing which should be fine as well.

It did activate fine, just found it annoying that after only two major component change that I had to activate it again

Word of warning, if you have any adobe software excluding lightroom, you need to deactivate the software before any component changes are made, because it will assume that you have installed it on another computer.

[gi joe]

Well not really as it being a new mobo and CPU, obviously it's gonna think it's on another machine.  It's not gonna know you've spent your hard earned cash on new bits.  A new mobo and/or CPU will do it every time.

[keasy]

There's a case for piracy.

[gi joe]

True.