New Hard Drive Will not boot my PC
Started by
bigdog1100
, Jun 30 2005 12:10 PM
#16
Posted 30 June 2005 - 02:10 PM
#17
Posted 30 June 2005 - 02:12 PM
try taking the cmos battery out like i said earlier and see if that kicks it...sometimes it does
#18
Posted 30 June 2005 - 02:25 PM
Any side effect to that?
#19
Posted 30 June 2005 - 02:26 PM
no it just clears your bios
#20
Posted 30 June 2005 - 02:28 PM
Clears it?
#21
Posted 30 June 2005 - 02:29 PM
well it's physically impossible (short of smashing it) to clear bios... your standard BIOS info is stored on a CMOS chip by hard wiring it in. you can change this and flash it because those changes get stored somewhere else but the basic config is always there
#22
Posted 30 June 2005 - 02:31 PM
So it will not affect anythng correct?
#23
Posted 30 June 2005 - 02:32 PM
well...hopefully it Will effect your ability to boot on that drive.
#24
Posted 30 June 2005 - 02:34 PM
Well I mean if I want to digress to old drive, will I still be able to?
#25
Posted 30 June 2005 - 02:41 PM
I am going to log out now. Thank you for your support. I'll ee you posted.
#26
Posted 30 June 2005 - 02:51 PM
yeah if you want to just put the old one back it should work
#27
Posted 30 June 2005 - 02:52 PM
Howdy:
You may be SOL here as far as your new hdd is concerned ..
Below is an exerp from the following url.. http://ghost.radified.com/ghost_4.htm
"As I understand this issue, Windows XP "knows" which hardware was installed when it is shut down. XP has attached a volume identifier to each volume. When XP is restarted, it redetects the hardware and if the same, all is well.
When a disk is cloned, disk-to-disk, there will be two volumes with the same volume identifier. If the computer is restarted with both harddisks (the "source" and the "clone") installed, XP will start from the "source", detect the "clone" as new hardware and change the volume identifier since there can not be two volumes with the same volume identifier.
Nothing will be detected by the user until he/she takes out the "source" and makes the "clone" the boot drive. Now, XP can not boot because of the changed volume identifier.
The solution is simple when Ghost 2003 is used to do the disk-to-disk cloning. You don't let Ghost reset the computer and restart Windows but turn off the computer and remove the "clone" before restarting."
Bet you didn't !!
Murray
You may be SOL here as far as your new hdd is concerned ..
Below is an exerp from the following url.. http://ghost.radified.com/ghost_4.htm
"As I understand this issue, Windows XP "knows" which hardware was installed when it is shut down. XP has attached a volume identifier to each volume. When XP is restarted, it redetects the hardware and if the same, all is well.
When a disk is cloned, disk-to-disk, there will be two volumes with the same volume identifier. If the computer is restarted with both harddisks (the "source" and the "clone") installed, XP will start from the "source", detect the "clone" as new hardware and change the volume identifier since there can not be two volumes with the same volume identifier.
Nothing will be detected by the user until he/she takes out the "source" and makes the "clone" the boot drive. Now, XP can not boot because of the changed volume identifier.
The solution is simple when Ghost 2003 is used to do the disk-to-disk cloning. You don't let Ghost reset the computer and restart Windows but turn off the computer and remove the "clone" before restarting."
Bet you didn't !!
Murray
#28
Posted 30 June 2005 - 03:06 PM
WOW......that friggin sucks
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users