"Juan Wei" needs more info:
Timothy Daniels has written:
Well, I restarted the computer and got a boot menu. I then selected the
SSD and it did boot.
I would certainly volunteer all those things if I had enough knowledge
to recognize them without having them pointed out to me.
It helps a lot to know the boot process, at least the legacy BIOS
boot process -
First, the BIOS runs the hardware-finding process, and eventually
it goes down the boot priority list looking for a device with an MBR
(Master Boot Record).
When it finds a valid MBR, it passes control to it.
The MBR inspects the partition table on the device to see which
primary partition is marked "active".
The MBR passes control to the boot sector of that primary partition.
The boot sector has a boot manager which looks at the boot menu
to see where the OS is that should be booted.
The boot manager passes to the loader the location (or identity) of
the partition that contains the OS to be booted, and the loader loads
and launches the OS.
In your case, you cloned the OS-containing partition contents to
the new partition in the SSD, and there aren't any boot files there to
boot it because it doesn't have a boot sector and the SSD probably
doesn't have an MBR. You also probably haven't designated the SSD
as having the highest boot priority, so control still goes to the MBR
on the HDD, which still points to the 100MB system partition on the
HDD. Somehow, it's smart enough to look around and see the SSD
and to put it on the boot menu - if I understand you correctly - but
that partition on the SSD still doesn't have a boot sector, so it doesn't
boot when you choose it manually for booting.
So, after you cloned the OS-containing partition on the HDD to the
new partition on the SSD (or even after you created the new partition),
you should have marked that partition on the SSD "active". Then you
should have done the following 2 procedures (order being unimportant):
1) restarted and entered the BIOS and either disabled the HDD
or set the SSD as the highest priority drive in the boot priority.
2) Used the utilities in the Win7 installation DVD to place an MBR
at the head of the SSD, and to make a boot sector in the new
partition with boot files in it. There are a couple automatic processes
that are available on the installation DVD, but when they run you don't
know what they're doing. It's best to run the Command Prompt utility
and to then run explicit command line utilities yourself. You may have
to experiment a little bit, but that's OK because mistakes here are not
destructive. Utilities to try are:
"bootrec /fixmbr" to put an MBR in the highest priority drive (which is
at this time the SSD), or . . . into the only drive enabled (I don't know
which condition is necessary)
"bootrec /fixboot" to put a boot sector and its files in the partition
that is marked "active".
You could also use "bootsect" to do the latter, or
"bcdboot" to set up the BCD's boot menu - you'll have to experiment.
You could also could have used "diskpart" to create the new partition
on the SSD and to mark it "active" - as usual, there are several ways to
do everything. When in doubt, use the /help option with the command
to get help with the syntax.
Once you got the OS on the SSD running for its first time in
isolation (i.e. without a view of its "parent" OS), you can shutdown and
re-enable the HDD (if it had been disabled), assuring that the SSD is
at the highest boot priority, and then letting the clone OS on the SSD
boot up. In such a scenario, the "parent" OS will not be running, and
will be viewed by the clone as just a hierarchy of files. It helps at this
time put folders on the desktop of each OS with names that tell which
OS it is since both will look identical and each will think of itself as the
"parent" of the other. And remember that when each runs, it will call
its own partition "C:".
If you want to run the 2 OSes in a dual-boot situation, you can run
BCDedit from the OS command prompt (as administrator) to build the
boot menu, but that's a tutorial for another thread. Otherwise, you can
choose which OS to run simply by controlling the drive enablement or
the drive boot priority in the BIOS during startup. (Remember that
having other devices with media - e.g. optical drive, USB drive - can be
confusing, so leave those unoccupied.)