- #Sata raid driver toshiba manuals
- #Sata raid driver toshiba install
- #Sata raid driver toshiba update
- #Sata raid driver toshiba manual
- #Sata raid driver toshiba archive
Manuals are accurate for windows 7, booleans, toshiba.
#Sata raid driver toshiba update
I will be installing XP on this laptop in a week or so and will update then.Download Now TOSHIBA PORTEGE M400 SATA RAID DRIVER
#Sata raid driver toshiba install
I would bet that XP would install now with the toshiba drivers unzipped and in the root of a thumb drive. I have not reproduced the steps above to see if what I remember is truly how I remember it but I am 90% sure the issue is the JBOD vs RAID setting. I finished the install and after 95 updates it is running like a champ. I had the XP drivers on a memory stick still in the USB port and a windows 7 disk in the drive and after the reboot windows 7 started the install process and asked if I wanted to install it on the 40G HD!!!!!!! Just for th heck of it I typed "1234" and hit "Enter" (I might have hit space?) and as if by magic the disk was now listed as "1RAID-0" I hit the space bar yet again and another warning popped up, "If 'Yes" please type the key string which is written in manual" What manual? I looked at what Toshiba had online and did not find a "string" I hit the space bar again and more text popped up "Do you really want to do this?" So having nothing to lose I hit the space bar which popped up a warning to the effect "Are you sure all data will be lost" I arrowed to "JBOD" and hit the space bar to change it. My PC had the disk listed as a JBOD (I think it defaults to JBOD.YA I have never heard of it either! ) Windows 7 could not see the HD.įinally after messing with every setting in bios I stumbled on the following:
I figured Win 7 would have the SATA drivers built in. I unzipped the files and after following their directions to no avail decided to try a copy of windows 7. I remembered to hit F6 to load SATA drivers for XP and downloaded the latest from Toshiba. It did not have a HD so I popped one in and started the process of trying to install XP (sp2.)Įvery thing looked good,I verified the HD was functional on another PC, the toshiba Portege S100 bios could see the HD, but during the install, Windows could not see the HD. I have solved the problem (at least for my situation.) Not sure what else to suggest at this point, the research I just did would be what I'd do if that were a customer's machine and I was trying to get it operational with a clean install of Windows XP SP3 myself. Try that using the contents of just those folders and just those 7 files in the root directory of the floppy and see what happens. The only thing that should be in the root directory of that floppy are the 7 files (replace the I with N for those versions):
#Sata raid driver toshiba archive
If you have access to an actual floppy drive (you sorta hinted at that in the first post), what you need to do is copy the contents of either of those folders to the floppy - you don't extract the entire archive to the floppy because XP can't search the contents, it's not like Vista and Windows 7. Inside that are two folders: KR10I and KR10N. If you grab the 1.3.8.0 version of the RAID driver from Toshiba's support site (that was the last driver available), and you extract the contents, you'll end up with 2 files and a \drivers folder. 2653 shows a simple Intel SATA controller as expected, and 27C5 is listed as an AHCI controller specifically - no mention of SATA there but obviously it's SATA as AHCI is part of the spec. The drivers are a bit weird - they reference Intel PCI vendor ID codes (8086) and two different device IDs (2653 and 27C5).
#Sata raid driver toshiba manual
The User Manual says that Portege S100 was made way back in 2005-2006 or so, if it's a real Portege S100, and it has an Intel ICH6 chipset (for some reason, that laptop even supported RAID operation, go figure).
I say that because (as I mentioned in that guide I linked above, another reason it's so wordy) most people end up choosing the wrong driver (the Windows-based driver instead of the real-mode driver) but they typically choose the wrong SATA controller driver too as demonstrated in that guide, a typical Intel SATA controller based on a given chipset could have upwards of 7 different variations and if you don't choose the precise one required, it won't work. Only thing I can suggest is to use a Linux LiveCD and boot that laptop off it, once you're up and running, open a Terminal and do the lspci command to see precisely and exactly what hardware is in the laptop with respect to the hard drive controller. Then you a) didn't slipstream the correct driver (needs to be the real-mode driver, not the Windows-based driver) or b) the driver chosen isn't the correct one in the first place.
0 kommentar(er)
