Quantum Fireball lct 30 gig problem

I have 2 Quantum fireball lct 30 gig hard drives (same problem on
both) that only be detected by the motherboard bios as 9 MB (yes, MB,
not GB). Windows 98 can see them as 9 MB in FDISK. I have tried many
motherboards (old and recent) with different kind of bios (Award,
phoenix, etc) and they all automatic detect the hard drive, but the
size is only 9 MB. I have also try Quantum DM (Disk Manager) software,
it also detects the drive as 9 MB. It allows me to manual change the
drive parameters, but will only increase the drive to 8.4 Gig. I also
did Virus Scan to make sure there is no virus in the boot sector of
the drive to cause the problem.

Any other idea?

these should be in warranty. Call testicle support.


"Pak Wan" wrote in message
om...
I have 2 Quantum fireball lct 30 gig hard drives (same problem on
both) that only be detected by the motherboard bios as 9 MB (yes, MB,
not GB). Windows 98 can see them as 9 MB in FDISK. I have tried many
motherboards (old and recent) with different kind of bios (Award,
phoenix, etc) and they all automatic detect the hard drive, but the
size is only 9 MB. I have also try Quantum DM (Disk Manager) software,
it also detects the drive as 9 MB. It allows me to manual change the
drive parameters, but will only increase the drive to 8.4 Gig. I also
did Virus Scan to make sure there is no virus in the boot sector of
the drive to cause the problem.

Any other idea?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Pak Wan wrote:

I have 2 Quantum fireball lct 30 gig hard drives (same problem on
both) that only be detected by the motherboard bios as 9 MB (yes, MB,
not GB). Windows 98 can see them as 9 MB in FDISK. I have tried many
motherboards (old and recent) with different kind of bios (Award,
phoenix, etc) and they all automatic detect the hard drive, but the
size is only 9 MB. I have also try Quantum DM (Disk Manager) software,
it also detects the drive as 9 MB. It allows me to manual change the
drive parameters, but will only increase the drive to 8.4 Gig. I also
did Virus Scan to make sure there is no virus in the boot sector of
the drive to cause the problem.

Any other idea?

If the drives are brand new and never used they may be defective.
Also, check the drives to see if they have a 'limit' jumper installed in the
master / slave jumper area.

These are often used if the drive is to be installed in an older machine
that can't see the drive's full capacity.

Have these drives been used in other machines, or have they (to your
knowledge) been used with disk compression software ?

Utilities such as Microsoft 'DoubleSpace', Stacker, or AddStor, create
"container" files on the disk and leave a small section non-compressed for
booting.

Another possibility is the prior use of disk integration software such as
OnTrack DiskManager. DiskManager, as I recall, offsets the sector mapping
by 63 sectors, 'hiding' the first 63 from the operating system.

You might try accessing the disk through a Linux machine's 'fdisk' utility.
It's far more capable than the utility supplied with any version of Windows
and can recognize around 92 partition table formats.


- --
Ron n1zhi

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAgnvxa9fyRcf4bIYRAq2AAJ49B05la9lEJIRnd/i+9GpkQA6TjwCfYbxS
JzixEtrcly4h9x3pS5eugI0=
=JyCR
-----END PGP SIGNATURE-----