after transferring harddisc to another PC: files seem to be corrupted (but are not!)

  • Thread starter Thread starter Andi
  • Start date Start date
A

Andi

I purchased a new PC and installed my data HDD as a secondary IDE device
(more accurately: as slave on the primary IDE channel) into this new PC.

Now, Windows 2000 is able to browse through the hdd, all seems well, but
a big deal of the files seems to be corrupted: the applications (Word,
CorelDraw,...) tell me "file corrupted" when I try to open these files.

But they are NOT corrupted: when I removed the HDD from the PC and put
it back into the old PC, all files are there and working. After
installing the HDD back into the new PC, they are NOT working and seem
corrupted. How can this be?

So, this seems like a hardware incompatibility issue of some kind. Has
anybody heard of such effect and some useful tipps for me?

Thx,
Andi
 
Andi said:
I purchased a new PC and installed my data HDD
as a secondary IDE device (more accurately: as
slave on the primary IDE channel) into this new PC.
Click to expand...
Now, Windows 2000 is able to browse through the hdd,
all seems well, but a big deal of the files seems to be
corrupted: the applications (Word, CorelDraw,...) tell
me "file corrupted" when I try to open these files.
Click to expand...
But they are NOT corrupted: when I removed the HDD from
the PC and put it back into the old PC, all files are there and
working. After installing the HDD back into the new PC, they
are NOT working and seem corrupted. How can this be?
Click to expand...
So, this seems like a hardware incompatibility issue of some kind.
Has anybody heard of such effect and some useful tipps for me?
Click to expand...

The main thing that can produce an effect like that is different
drive mapping in the two PCs. You should be using the same
details in the drive type entry for the drive in the bios.

If you cant get that to work, one obvious approach is to
network the two PCs together to get the files off that drive.
 
Found out the reason for this: it is a 160GB drive and under Windows
2000, support for "Big LBA" for drivers larger than 137 GB (48bit
addressing mode) is not enabled by default. So, access to the area >
137GB did not work, instead there was a "wrap around" to the first
tracks of the disk.

However, there is just one registry entry I had to set and the problem
was fixed:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters
\EnableBigLba = 1

This solved my problem.

Andi
 
Andi said:
Found out the reason for this: it is a 160GB drive and under Windows
2000, support for "Big LBA" for drivers larger than 137 GB (48bit
addressing mode) is not enabled by default. So, access to the area >
137GB did not work, instead there was a "wrap around" to the first
tracks of the disk.

However, there is just one registry entry I had to set and the problem
was fixed:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters
\EnableBigLba = 1

This solved my problem.

Andi
Click to expand...


Hello, Andi:

Thanks, for the update!


Cordially,
John Turco <[email protected]>
 
Back
Top