Installed JMicron Drivers - HDD Unreadable! Help!

[LUCI5R]

Ave,

I just put together my brand new rig a couple of days ago. ASUS P5W DH Deluxe Motherboard, Pentium D 930.

This is how my drives are setup:

PRIMARY_IDE: Pioneer Burner (Master) & Optorite Burner (Slave)
PRIMARY_EIDE: Maxtor 40GB (Master)
SATA: Seagate 320GB (Operating System, Boot Drive)

The PRIMARY_EIDE is a JMicron controller for secondary ide devices or raid.

When i put my system together...installed Windows XP on SATA... everything was working absolutely fine. All my Hard Drives were recognized and functional. The Maxtor IDE is an old drive which has all my data on it which i needed to transfer to my new drives.

Today i installed the ASUS CD with all the drivers and everything. When it installed the JMicron drivers, the system had to reboot... when it came back... i could no longer open my Maxtor IDE. It says "The file or directory is corrupted or unreadable"!!! It has all my data on it and i can't even open it anymore!!!

I tried switching the drive to PRIMARY_IDE but still the same issue. I put in another HDD on the jmicron controller and that works. Only this HDD has been corrupted or so it seems, right after the jmicron controller drivers were installed.

I can't loose all my data on this drive... what do i do? Please help!!

Mickey

[Richard Dower]

It's probably how you have the options setup in bios, hard disk boot priority or something with advanced bios options.

Otherwise you can try the Gigabyte JM363 drivers, more recent version.

[LUCI5R]

I've checked everything in the BIOS... i didn't change anything at all since i first set the options in the BIOS and everything was working fine at that time. It's only since installing the JMicron drivers that the HDD is unreadable.

Googling it i came to learn that the HDD is actually corrupted if you get that error... and that it usually happens on a hard boot, electric shock, something like that. People have used Recovery Tools to recover the data and format the HDD. I might have to go that route.

But if there's anyone here who feels that this is a Setting or Drivers issue and i can get my drive working again... please, please respond!!

Thanks.