Re: XP killed my new harddrives
- From: "Paul Randall" <Paulr901@xxxxxxxxxxxx>
- Date: Mon, 24 Aug 2009 07:58:33 -0600
I was trying to find out what you meant by:
adding it to my computer changing the positions
around on the cables.
I was basically trying to coax enough information from you so that someone
with a better background than me could figure out what the root cause of
your problem is, and perhaps a remedy.
IDE drives can typically be pinned to be master or slave or use Cable
Select. Cable select means the drive at the end of the cable is the master
and the drive at the middle is the slave. If one drive is pinned as master
or slave and the other is pinned as cable select, then there could be
confusion. Depending on how the BIOS handles such confusion, perhaps your
symptoms could be the end result. Boot order is typically determined by
first by IDE cable number and then by master/slave. And partitioning can
also be a factor.
The more modern BIOSs can store some other specific order in which the hard
drives are tested for bootability. Your seven year old machine may have
that capability, especially if you have done a flash upgrade of the BIOS.
If the data drives had been bootable and the BIOS boot order was to choose
them first, then you may not have booted from the drive you intended to boot
from.
I don't have any suggestions on where to look for help on getting your data
back. The data recovery procedure you have already done has probably wiped
out the info in both original directories, meaning that it fixed them as
well as it could and probably made them the same. Commercial data recovery
is quite expensive but expensive is a relative term that has to take the
value of your data into account.
-Paul Randall
"Arron" <Arron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:040DCC7F-C9D5-4B9E-9EE0-C3667FE76024@xxxxxxxxxxxxxxxx
Paul,
The computer I built myself back in 2002.
It is a Gigabyte GA7dx motherboard.
the original arrangement was
primary IDE
master = 10gb drive with winxp
slave = 120gb drive with data (end of cable)
secondary IDE
master = cdrom (end of cable)
slave = cdrom
new configuration when it messed up
Primary
master = 10gb drive with winxp
slave = 120gb drive (end of cable)
secondary
master = 80gb drive (end of cable)
slave = cdrom
I believe all jumper settings were correct. I am curious how you use this
information to tell me how I could correct what happened to my 80 and
120gb
harddrives?
"Paul Randall" wrote:
Comments inline
"Arron" <Arron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CA0617FC-A0CC-4666-A406-D14BC9163904@xxxxxxxxxxxxxxxx
I installed windows XP home edition onto a 10gb NTFS harddrive on a
computer
with an existing 120gb FAT32 drive almost full with data. Everything
went
smooth and worked great for about a month.
What is the brand and model and approximate year of the computer?
Is the BIOS the original shipped with the computer or has it been
upgraded.
Are the drives all IDE, Sata, or a mix of the two?
For each drive, including CD/DVD drive, how were they jumpered at this
time
(master, slave, cable select) and at what cable position were they
plugged
in (middle or end of first or second motherboard IDE/Sata connector, as
listed in BIOS?
I tried taking an 80gb FAT32 drive
almost full of data and adding it to my computer changing the positions
around on the cables.
For each drive, including CD/DVD drive, list the same info for all the
drives at the time of this first boot.
At the time of this first boot, were either of the 80 & 100 GB drives
bootable on this or some other motherboard, or had they ever been
bootable?
-Paul Randall
Upon the first boot after the new harddrive was added Windows XP
appears
to
have done something to both of my fat32 drives and now they show
nothing
but
gobly gook, I can't access my files. Just random characters show up. It
looks
as if XP wrote new file allocation tables to the drives or screwed up
the
MBR's all in one motion. The drives still show under properties as
FAT32,
and
the correct used size and free space show up, but everything is
gibberish.
WHAT HAPPENED? I put everything back to normal and my 80gb drive back
in
my
old comptuer but the drives are still messed up. I tried a system
restore
to
no success. One of the drives I ran scandisk and it said there were 2
copies
of the file allocation table that do not match and when it tried to fix
it,
the problem just looks worse. I downloaded Getdataback and it only
recovered
30% of the files it appears with the shareware version.
Can anyone explain to me why windows xp decided to screw up the
harddrive
structures? And the best solution to at least recovering as much data
as I
can? Is there a way to view the 2 copies of the file allocation table
and
try
changing them to primary position without deleting them? Could
something
else
be fixed that was messed up? Is file recovery software my best bet?
I would really appreciate any help recovering my data, and am greatly
disturbed by this fact of windows xp. Thanks.
.
- References:
- XP killed my new harddrives
- From: Arron
- Re: XP killed my new harddrives
- From: Paul Randall
- Re: XP killed my new harddrives
- From: Arron
- XP killed my new harddrives
- Prev by Date: Re: Move pagefile to faster drive ?
- Next by Date: Re: online backup
- Previous by thread: Re: XP killed my new harddrives
- Next by thread: Re: XP killed my new harddrives
- Index(es):
Relevant Pages
|
