Windows7 Home Premium, 4gb (8 ready to go), 2.4ghz dualcore
I have two disks from Microsoft - one is labled 32bit which I used to install the current OS. The other is labeled 64bit. I wanted to see if I had any issues before proceeding with the real upgrade. I booted from the 64bit disk to C: ok. However, after going through file loading, it started Windows and simple hung with a larger cursor on the screen.
So, do I have to totally erase the C: drive to load the 64bit OS from the 64bit disk?
Or, should I create a new partition on the C: drive instead, and boot to that?
I read a few years ago about partitions reducing disk performance so that needs to be verified?
Or, I could boot to the G: drive where I have a new 80% empty disk with two train sims and X-Plane on it?
The G: drive looks like the best approach in terms of safety but does placing the 64bit OS on a non-C: drive
create other problems?
Thanks
I have two disks from Microsoft - one is labled 32bit which I used to install the current OS. The other is labeled 64bit. I wanted to see if I had any issues before proceeding with the real upgrade. I booted from the 64bit disk to C: ok. However, after going through file loading, it started Windows and simple hung with a larger cursor on the screen.
So, do I have to totally erase the C: drive to load the 64bit OS from the 64bit disk?
Or, should I create a new partition on the C: drive instead, and boot to that?
I read a few years ago about partitions reducing disk performance so that needs to be verified?
Or, I could boot to the G: drive where I have a new 80% empty disk with two train sims and X-Plane on it?
The G: drive looks like the best approach in terms of safety but does placing the 64bit OS on a non-C: drive
create other problems?
Thanks