I have an HP DV7 notebook that I recently added a second SATA 500 G
hard drive in the expansion bay. The purpose of the drive is to serve a
a data drive. I also intend to store an image of my system disk on thi
internal expansion drive so that I can restore my system and apps when
am in the field. For most purposes the drive seems to be functionin
normally.
However, I recently noticed that, without my instructions, HP Update
were installing suipport files on my expansion disk rather than on m
system disk and I have become concerned that Windows Updates may als
end up on the expansion drive (so far they appear not to have don
this). On further inspection in Computer Management – Disk Managment
discovered that when I put the expansion drive into the 2nd bay, m
original system disk was automatically bumped from the Disk 0 positio
to the Disk 1 position and my expansion disk became the new Disk 0
In Computer Managment – Disk Management the system currently looks lik
Disk 0 – F: Expansion Drive – Healthy, Primary Partitio
Disk 1 – C: – Healthy, System, Boot, Page File, Active, Crash Dump
Primary Partition
If I physically pull out the F: drive from the machine the C: driv
returns to the Disk 0 position
I am concerned that my system and application updates are going to ge
splattered across two drives when I want them to remain on the origina
C: drive
I can find no way in BIOS or Computer Management – Disk Management t
assign the Disk # and physically swapping the drives makes the syste
disk unbootable
1) Am I at risk of splattering my Window updates across two drives
2) Should I instruct Vista to regard my system disk C: as Disk 0 an
how to I do this
Thanks in advance for any suggestions
—
TangentRW
