Is it a sataII drive on a Sata I controller? If so you'll need to apply the appropriate jumper settings.
Is it a sataII drive on a Sata I controller? If so you'll need to apply the appropriate jumper settings.
Thank you for your reply.Is it a sataII drive on a Sata I controller? If so you'll need to apply the appropriate jumper settings.
I don't think it is a physical problem here, it's a laptop HD, and I have been able to detect it using the F6 driver load, and with OEMPREINSTALL turned off. The HD itself is fine.
Will give that a bash, thanksYep, had this issue with some Dell Latitudes recently - if you can, flip the SATA controller in the BIOS from AHCI to ATA mode.
Hi there,
Tried switching that, but can't do it I'm afraid.
I have also been trying to do this using the textsetup.oem and massstoragedrivers in winnt.sif.
Not working that way either!
This is getting to be a nightmare.....
Spoiled few CDs while getting everything exactly as said in you guide, [R4A]Bigman.
I took *.sys and *.inf files from SATA floppy downloadable at Asrock home page.
Substituted the lines from viamraid.inf where necessary:
Viamraid.sys
%PCI\VEN_1106&DEV_3249.DeviceDesc% = viamraid , PCI\VEN_1106&DEV_3249
%PCI\VEN_1106&DEV_3149.DeviceDesc% = viamraid , PCI\VEN_1106&DEV_3149
%PCI\VEN_1106&DEV_3164.DeviceDesc% = viamraid , PCI\VEN_1106&DEV_3164
VIA VT6421 RAID Controller
First disk spoiled because I did not copy the first square bracket to Winnt.sif file.
Second was, I forgot to put Viamraid.sys in i386 directory.
Third coaster was because I left line in [SCSI.LOAD] section without ",4" part.
Forth CD finally WORKED
I used XP installation with integrated SP2.
The next step would be to integrate drivers into CMDCONS.
Last edited by kurbads; 04-07-2007 at 03:10 PM.
Yeah right... you try installing Feisty on a raid set on an nvidia 680i chipset mobo... lol
I spent ages trying to get it to work and finally gave up and just installed it on a single SATA drive that was in my machine as well.
When they put a version of dmraid into the live cd and actually get gparted to work with it, that's when it'll be easy!
Matt
There is another way...
http://www.scan.co.uk/Products/Produ...roductID=43836
(\__/)
(='.'=)
(")_(")
Been helped or just 'Like' a post? Use the Thanks button!
My broadband speed - 750 Meganibbles/minute
Pardon the intrusion but i saw the title and thought wtf!
I have a sata II hard drive and when i first built the system it was fine. I'm now getting a new rig and going to chuck on vista premium.
Now reading this thread has got me worried. I was under the impression i could just connect everything up and install vista or xp with no problems, but this thread has me confused.
Have i missed something i should of done or should do?
Yes i'm thick
[QUOTE]Clunk - If you hold a bright light up to the grills on the back, with the monitor off, they will fly out, unless they are dead, in which case, they wont.[QUOTE]
Combat Revolution: www.combatrevolution.net
It does depend on motherboards, chipsets etc, but if you are getting new kit I would think you would be fine.
I have recently installed vista on my nvidia 680i mobo onto a raid pair of sata drives, no floppy disks needed, no sata drivers required. Vista installer picked up the raid array and installed straight to it.
XP might be different, but if you have a floppy in your rig it's a simple case of F6 in the installer, stick in the floppy for the sata drivers and away you go. However this thread is for peeps that don't have a floppy drive in their machine and it's a way of building an XP install disc that contains all the necessary files to boot the installer and have it see the sata drives without needing to F6 and use a floppy.
Matt
Gunwitch (05-07-2007)
Ah i se.
Thanks for clearing that up much appreciated.
It will be a vista build i'm doing so should be easy. And i appear to of gotten rid of my floppy a while ago.
But thanks again.
[QUOTE]Clunk - If you hold a bright light up to the grills on the back, with the monitor off, they will fly out, unless they are dead, in which case, they wont.[QUOTE]
Combat Revolution: www.combatrevolution.net
I have followed steps 1 through 3 completely and had no troubles. But the links provided for the bootfiles in step 4 are invalid. Where might I find these files? I've googled a bit and looked around the site the link takes me to, but I can't find anything.
Help appreciated.
<Not the best first post mate - even talking about warez is strictly forbidden on here. We prefer to pay people for their work - Agent>
<yes its a great post that's why it got deleted =D. You know you gotsta hide the good info.. cant let people know da truth ya feel?. Oh and about warez.. didn't i say I downloaded it? You must think its illegal.. jumpin to conlusions.. that's alright all the mods everywhere do... but i have an offsite ftp server that has a copy of basically all windows i've ever brought (ALL LEGIT) in iso format and I keep them in torrents tho b/c its faster than ftp and more reliable in resuming a download.. so yes you shouldn't even have touched my post ... but its ok. - Baalpeteor , Computer Network Specialist>
Last edited by baalpeteor; 08-10-2007 at 03:44 AM.
Hi,
I managed to solve my problem if anyone is interested
Basically after a LOT of searching I came across this link (apologies for not being able to link it properly- need 5 posts - the x's are w's) hxxp://xxx.windowsserverx64.com/CSK/technical_articles/hardware/56.aspx which descirbes in detail what all the stuff in txtsetup.sif does.
From careful reading of the bit about [sourcedisksfiles] i noticed that the string "si3112r.sys = 1,,,,,,_x,4,1" or in my case "iastor.sys = 1,,,,,,_x,4,1" is actually trying to load drivers from a directory on the root of the XP cd called AMD64.
Try creating this directory with your SATA drivers files in it, and see if that works.
It might also be worth adding you driver .inf file under SOURCEDISKSFILES with the string 1,,,,,,,20,0,0 after it e.g "iastor.inf = 1,,,,,,,20,0,0"
Finally, I have found that it's good to make sure all the cases in your diver files match- My disk wasn't working until I made ALL entries that use the words iaStor.sys into iastor.sys (as the actual driver file had no capital 's')
I hope this can help someone!
Hi All
For the past week I tried this approach to get XP to recognise a SATA HDD, without success. This morning: Eureka!!! I simply went into the BIOS and disabled the IDE channel. XP then immeiately installed successfully. Hope this is of use to someone.
There are currently 1 users browsing this thread. (0 members and 1 guests)