And making the single drive false raid 0 array would be done in the advanced bios settings? If not I would guess I enter the define array and set the 0 array up which does nothing but lets me add a new sata drive to the mix which is the damaged one and not copy any files from the existing hard drive running on the MSI onto it and then hopefully will be able to then read the data I want off of it. One other thing, have you tried to run WD Data Lifeguard to see what it shows as far as what might be wrong wih the drive? It’s all explained there. I would guess the drivers not installed controls this correct? Instead of trying to get it to work in your PC there is another option. But you can do slipstream XP installation disk and to include the necessary drivers.
|Date Added:||26 September 2012|
|File Size:||23.18 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
The first one with the 3 ide.
ShieldSquare reCAPTCHA Page
Double check ‘Drive Assignment’ that it shows: Ok, set it up in the array settings on boot. What I am seeing now with the fastbuild Utility in promise Technology is I think you are saying J7n2 can use this to copy the data from a bad drive to a new drive if i set it up that way and save the whole hard drive to a new hard drive.
Your computing wife will need another disk, so you could wait and attach the suspected drive later to her system. Please login or register.
Suspicious Activity Detected
I think what will happen now is install windows again and then make the bad drive a second and use some type of data recovery program to try and get the data my wife needs back. Thank you very much for response.
Saga as XP can look for drivers in a floppy only. Thanks again sats all the help. One option is to hit ctrl-Y to save this setting which i am guessing to do. Time will not increase the problem if the disk is kept in a cool place. Do not have the floopy that came with board although i did buy it new and would not matter because I do not have a floopy drive attached to machine.
To get the ser1 input to work by doing this array thing seems to be confusing or am I not setting up the array correctly?
You will then need to settle which disk to boot from – not a big issue. And none of those options after entering them has promise Raid.
MSI K7N2 DELTA2-FSR – motherboard – ATX – Socket A – nForce2 Ultra Overview – CNET
The sata setup was just to have the ability to read the drive and thus wanting to have sata running. If you don’t do that you will not even be able to read the drive. The size wouldn’t be a problem. Yes, we know she’s hot! SATA drivers and if k7n22 where would I find them? If you don’t have the Promise floppy that came with the MB you can download here: You posted while I was still typing but as kk7n2 above it seems you need to download the drivers if you don’t have the floppy.
Never rely on HDD for permanent storage of important stuff. You are correct Sharp about it setting up at the cluster size of 64 KB and was not aware it could hurt the existing drive with info on it.
MSI K7N2 DELTA2-FSR – motherboard – ATX – Socket A – nForce2 Ultra 400
It’s all explained there. Because I am guessing in this setup, really do not sqta windows right now for anything so I get a new hard drive and copy the damaged drive info to it using this sataraid set up? It did not recognize the drive.
Thinking I had to install a new drive no matter what, I bought a new sata drive and went into the array setup and was able to add it as a drive and recognize it. Am I correct on all this? I just need to get it working so I can try a few programs I have to extract data off of bad hard drives. If not I would guess I enter the define array and set the 0 array up which does nothing but lets me add a new sata drive to the mix which is the damaged one and not copy any files from the existing hard drive running on the MSI onto it and then hopefully will be able to then read the k7b2 I want off of it.
So no worry about re-formating the damaged drive before I get the info from it.
Also mentioned was ensuring drivers were loaded in c drive. Plugged it into the SER1 on my board and booted up.