Partition Magic 8.01 and HDD larger than 137 GB

  • Thread starter Thread starter Jannik Ebbe Brich
  • Start date Start date
J

Jannik Ebbe Brich

Hi

Just bought a Seagate Baracuda 160 GB ATA100 HDD.

I have some ? 4 u guys :-)

1. When running HDD benchmark in DR. Hardware 2003 I get a performance diff
in the scale of 800 %. The problem is that my old drive apparantly runs 8
times faster than the new :-( . Whats going on ?? I'm assuming that this a
faulty reading ??

2. As a result of the above I tried changing the Cluster size from present
512k to the usual 4k in NTFS. Btw. how large NTFS partitions can one make
and keep the 4k Cluster size ?
However PM 8.01 will not accept the disc. It can see the HDD alright, but
there r strange symbols in the disc label field. And I keep getting errors
when trying 2 get info on the selected partition.

Is there a max size 4 PM 8.01 ?

Specs:

Asus P4PE BIOS 1005
512 MB DDR Ram
HDD 1 Maxtor Diamond Plus 9 Fluid 80 GB
HDD 2 Seagate Baracuda 160 GB (Part 1 5 GB, Part 2 146 GB)
Win XP SP1

Jannik
 
From PQ website: *Partition size: Tested on partition sizes up to 160 GB
when partition is less than 90% full.
 
Thx Joep :o)

That was also what I found. But why does it not work then ??

Jannik
 
Thx Joep :o)
That was also what I found. But why does it not work then ??

Uhhh ...
However PM 8.01 will not accept the disc. It can see the HDD alright, but
there r strange symbols in the disc label field. And I keep getting errors
when trying 2 get info on the selected partition.

Any specific error codes then? And you do have normal access to this drive,
I mean the OS can read/write from/to it? Also PM also install Partitioninfo
and this allows to save partition table and boot sector info to a textfile,
can you make this textfile.

--
Joep


Jannik Ebbe Brich said:
Thx Joep :o)

That was also what I found. But why does it not work then ??

Jannik
 
Partition Magic 8.01 fails with error 11117. Can't even get properties.

All errors > 10000 are actually errors reported by the OS and are just
passed on by PM. To get the actual number of the OS error substract 10000
from the error message as PM adds 10000 to it.

Then by using the net helpmsg from the command prompt you can see what
Windows has to say about the error ... which in this case doesn't help a
lot:

C:\Documents and Settings\Owner>NET HELPMSG 117
The IOCTL call made by the application program is not correct.

What if you ONLY have the 15 Gb partition? Same results?
 
All errors > 10000 are actually errors reported by the OS and are just
passed on by PM. To get the actual number of the OS error substract 10000
from the error message as PM adds 10000 to it.

Then by using the net helpmsg from the command prompt you can see what
Windows has to say about the error ... which in this case doesn't help a
lot:

C:\Documents and Settings\Owner>NET HELPMSG 117
The IOCTL call made by the application program is not correct.

What if you ONLY have the 15 Gb partition? Same results?

IIRC, don't you need (besides having a BIOS capable of handling a
drive >137GB) to turn on 48-bit addressing for XP to work with it
properly? The ability is there with SP1 but it's not enabled by
default, is it?

The original poster might want to check this registry key,
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Atapi\Parameters\
and make certain that the DWORD value "EnableBigLba" is set to 1.
 
Thx for the reply

Actually it IS enabled by default in XP SP1

The regkey u mention does NOT exists in SP1 and further more it will be
ignored anyway.

Jannik
The original poster :o)
 
Thx for the reply

Actually it IS enabled by default in XP SP1

The regkey u mention does NOT exists in SP1 and further more it will be
ignored anyway.

Jannik
The original poster :o)

Jannik: coldcomfort I know but I'm in exactly the same position. Can't
get my 180gb Deskstar recognised by XP (SP1) and getting the same error
on Partition Magic. If I stumble on the answer, I'll let you know.
Perhaps you could do the same for me? Ta..

Caroline


Caroline Picking, (e-mail address removed)
Milton Keynes, England.
 
Actually it IS enabled by default in XP SP1

really? thought i read it wasn't somewhere ... guess you have double checked
the key to make sure?
 
Problem solved :o)

Actually I did 2 things, but I think it was the latest one.

First I used Seagates Drisktool
2 write 0's 2 the HDD. (Didn't have patience 2 more than 10 min cause it
did not even reach 1 %)

Secondly I updated Intel Applikation Accelerator.
Began reading about this appl. And what do u know...... This appl did alot
more than I thought. It acts as some kinda filter/translator/driver between
the OS and the Controller.

Anyway it worked !!! :o)

Thx 4 all the help guys :-)

Jannik
 
Back
Top