Silicon Image 3132 BIOS update

Hi all
I have a K8N Diamond mobo (latest BIOS) and want to update the BIOS of the Silicon Image 3132 SATA/RAID controller. This is in the vain attempt it will solve my Plextor 716SA problems.
I have downloaded the latest BIOS from the Silicon Image website but dont hpw to use it.
Can anyone give me a noobs guide to Silicon Image BIOS flashing?
cheers guys

It 's possible to include/replace the SIL 3132 pci rom in the MSI Diamond bios with the
newest one from here :
http://www.siliconimage.com/support/downloadresults.aspx?pid=32&bios=1&drivers=0&sataraid=0&
2'nd download and the 7223.bin in that archive .
Current MSI bios 1.7 for diamond has the 7218 SIL embedded bios version .

Similar Messages

Beta Silicon Image 3132 eSATA driver

Has anyone tried the beta Sil 3132 eSATA driver on Snow Leopard yet?
http://www.siliconimage.com/support/searchresults.aspx?pid=32&cat=3
This has been the one thing holding me back from upgrading because I require use of an eSATA drive for my work. I'm not sure if I want to trust a beta driver with important data, so I'm looking for some first hand reports of the driver quality.
Any info would be appreciated.

I was having kernel panics whenever I tried to eject my Meritline (Silicon Image) Sil3132 dual port ExpressCard in OS X 10.5.11 "Leopard" which I tried a couple of different drivers but couldn't eliminate these CRASHES... Very disappointing.
When I upgraded my OS to OS 10.6.2 "Snow Leopard" Apple's installer removed my Sil3132 drivers so I did some "recon" on Google and found the newly released "SiI 3132 Mac OS X 10.6 & 10.6.1 BASE (non-RAID) BETA" v1.1.11 driver here: http://www.siliconimage.com/docs/SiI31321.1.11u_Sil_PkgBETA.zip
Installed it, restarted and EVERYTHING WORKS!!! The key to removing the ExpressCard is to follow these simple steps:
1. Eject the hard drives connected via the ExpressCard from OS X
2. Power Off card from the Sil3132 menu in the top menu bar
3. Remove card
What is REALLY cool is the VERY inexpensive (a.k.a. CHEAP) RAID 10 configuration I created using two SimpleTech Duo Pro Drive eSATA / USB enclosures I bought a while back off DealMac.com. Each of these enclosures has its own HARDWARE RAID controller that EACH enclosure connects TWO Western Digital drives internally in either a RAID 0 ("stripe" for SPEED) or RAID 1 ("mirror" for REDUNDANCY) configuration. I set them up for RAID 0 for speed then created a RAID 1 ("mirror") of these two RAID 0 enclosures for a LIGHTENING quick 4-drive RAID 0+1... Advantages of both RAID 0 & 1, faster than RAID 5 and for me CHEAP since I already had 3 identical WD drives lying around from Mac Pro "pulls" and got a brand new 4th drove from CraigsList for $40!
I "tested" it by writing my 24Gb Parallels 5.0 "WinXP Pro SP3.pvm" file and it worked perfectly. Now I'll use this RAID for a FAST SuperDuper or Time Machine backups... HIGHLY RECOMMENDED!

How to retrieve data from Silicon Image striped disks on NVRAID?

Hello,
I used to have MSI K8N Diamond motherboard and had to claim it. They returned to
me MSI K8N SLI Platinum saying they couldn't get K8n Diamond anymore. However, K8N SLI Platinum doesn't have a Silicon Image 3132 RAID Controller I had used for my striped disks, so I'm trying to use NVRAID. NVRAID config says RAID status is OK (healthy),
but I cannot see any data on the RAID disk in Windows XP (it says the disk is not formatted). Can anybody help me with this problem? If the two RAIDs (Silicon X NVRAID) use different formats for writing data onto disks, is there any utility I could use to retreive my unavailable data from the disks, that used to be in Silicon Image RIAD?
Thank you very much for your time.

This is the problem with 2 threads that don't get merged, someone needs to merge these.
https://forum-en.msi.com/index.php?topic=100574.0
Since this seems to be the more popular of the 2 I will repost below what I said in the other thread. Personally I would try the destriper before attempting what Hans suggest as it is destuctive(not saying it won't work just saying it will write metadata to the drives, and any writing at this point can have bad consequences).
Quote
So the NVRAID see the 2 drives as a striped set? This is suprising. You could try to run a data recovery tool like getdataback and see if it sees anything on this new NVRAID array. But other then that your only chance to recover without using the above suggestion(get access to another SiImage which is probably the easiest)
is try a software destriper. Here is an example: http://www.runtime.org/raid.htm
The destripers are only as good as their authors write them, they have to know where for example where SiImage puts the metadata, it sounds like this software will try all combinations it knows(non-destructive),but can possibly recover data in your situation. You may even have to use a data recovery tool after the destriping depending on where you are at now.
Whatever you do, don't go configuring anything as any writing to the disk could make data hard if not impossible to get back.
I think it's easier to get another controller but in theory a de-striper will do it. Good luck I'm curious to see how things work out.

Bios update failure - bios image needed - lenovo S10-3

hello!
i`m in big trouble now
I just have reinstalled win7 and thought that i have to install the driver AND to do a bios update. I dont know why, but now my netbook can't start up (display is off, blackscreen).
Now i read some threads how to recover the bios, BUT i dont have a bios image (oh god, i am so stupid...).
Is there any possibility to solve this problem? Maybe by getting a bios image from a other S10-3 user?
Btw, my lenovo has the Atom N550, 1GB DDR3 Ram.
Please help me. I am thankful for any advice.

hi sasa22
you can download the bios file from the link below. after downloading, right click and select 'extract files' to get the files you need.
http://consumersupport.lenovo.com/uk/en/DriversDownloads/drivers_show_2521.html
hope this helps.

K8N Diamond Silicon Image SATA problem

Hi everyone,
I have a problem with my Silicon Image controller,
when I installed WinXP and tried to install drivers for the
Silicon Image controller (in SATA mode) it don't exept
Silicon Image SiI 3132 SATALink Driver 1.0.0.9.
The only drivers Win exept is RAID drivers. But then I can't use them because
I dont use RAID array.
I have tried to update the BIOS without any luck.
Is it the MB thats is broken or is it Win that has f***ed up?
My specs:
AMD Athlon 64 3700+
MSI K8N Diamond
4x Kingston HyperX 512MB DDR PC4000 CL3 (3-4-4-8-1)
HIS Radeon X850XT PE 256MB VIVO
1x WD Raptor 36GB 10000RPM
1x Maxtor DiaMax Plus9 120GB
1x Maxtor DiaMax Plus10 300GB
1x WD Caviar SE 250GB
3x Maxtor MaXLine Plus II 250GB
(all SATA HDD)
Creative Labs SoundBlaster Audigy 4 Pro
Plextor PX-716A DVD-R/RW/DL
Windows XP SP2
Zalman Reserator 1

On K8N Diamond the Sil3132 is a Raid5 controller. You can only install Raid5 driver (SataLink and SataRaid drivers don't work, only SataRaid5).
Use the latest driver version 1.2.3.1. You can download it from MSI.
If you don't use Raid, then you must go into the Silicon Image bios setup utility (CTRL+S or F4, when displayed) and set for each drive a JBOD array (Create Array -> JBOD).
(On newer bios JBOD has changed to CONCATENATION.)

Satellite A110: Graphic card is only at 64MB after traditional 1.70 Bios update

Hi!!
I have toshiba satellite A110. I've upgraded my bios to 1.70 version but now my video card is only at 64MB.
What can I do to make my video card back to 128mb or where can I find the traditional bios update for this version of bios.Thanks

Intel(R) Graphics Media Accelerator Driver for Mobile Report
Report Date: 06/25/2007
Report Time[hr:mm:ss]: 10:41:16
Driver Version: 6.14.10.4833
Operating System: Windows XP* Professional, Service Pack 2 (5.1.2600)
Default Language: English
DirectX* Version: 9.0
Physical Memory: 502 MB
Minimum Graphics Memory: 8 MB
Maximum Graphics Memory: 64 MB
Graphics Memory in Use: 8 MB
Processor: x86 family 6 Model 14 Stepping 8
Processor Speed: 1862 MHZ
Vendor ID: 8086
Device ID: 27A2
Device Revision: 03
* Accelerator Information *
Accelerator in Use: Mobile Intel(R) 945 Express Chipset Family
Video BIOS: 1264
Current Graphics Mode: 1280 by 800 True Color (60 Hz)
* Devices Connected to the Graphics Accelerator *
Active Notebook Displays: 1
* Notebook *
Monitor Name:
Display Type: Digital
Gamma Value: 2.20
DDC2 Protocol: Supported
Maximum Image Size: Horizontal: Not Available
Vertical: Not Available
Monitor Supported Modes:
1280 by 800 (60 Hz)
Display Power Management Support:
Standby Mode: Not Supported
Suspend Mode: Not Supported
Active Off Mode: Not Supported
* Other names and brands are the property of their respective owners.
I hope this is helpfull.

Satellite 1410-604 - BIOS update Incorrect BIOS update in the web?

Hi there again!
Now with a new and weird matter.
We all know that old say... "If it is not break, don't fix it". And if you put it into more informatic terms, "specially if it is a BIOS".
Yes, we all know that the BIOS is something quite dellitate to handle. For some reason we normally feel like if we were handling something like nitro-glycerine, or some radioactive product. And this is because we all know what is being put in risk in that moment: our (or sometimes others) computer, the full system could end as dead as some pieces of metal, plastic, and wires.
Well. I passed through all of that more than ten times in my life, and only once it went wrong. But since that old motherboard was already dead, It was not important. But I allways was EXTREMELY care. I allways cross checked everything before doing anything, allways got a backup and a way to restore that backup... and allways did this in COMPAQ systems, that were prepared that way. Updating a BIOS was just about preparing a disk, turn on the PC with the disk in the diskette drive, and wait. And if you didn't like the results, you simply click "return to previus BIOS" and that was it... very nice. And easy.
Few days ago, a friend brought me a Toshiba Satellite 1410-604 to solve some issues that were driving him crazy. After removing an expired Norton Internet Security, install avast and scan, I found more than one hundred files infected with a wide variety of virus, malware, trojans, and whatever you could imagine. Avast removed them all, but the remains of the operating system was so unstable that we decide to format and install from scratch.
I asked for the restoration disks, that obviously he don't have because they were lost in one of his movings. After we got the confirmation from Toshiba reps that there are no recovery disk available for this model, because it is too old, we decided to install from scratch like any other normal PC, and resigned to loose some of the utilities that come with that CDs and that are not available for download in the website.
I downloaded all of the software available for this model, including two BIOS updates. (Actually only one update, but in two versions: Windows and Traditional), and prepared a CD with all the drivers and programs just like if it were a brand new system install. And everything went very well, no problems at all. Until we got to the Wireless LAN card, but that is another issue that is already solved (the mini PCI card for the WLAN does not support WEP or WAP encription, and it is not possible to connect to any wireless LAN encripted).
At this point, and when I started configuring and enabling PCMCIA devices, and USB devices (this computer only supports USB 1.1 not 2.0) I discovered this text in the Toshiba Website:
"This Bios Update adds increased functionality to your system.
(BIOS is an acronym for Basic Input and Output System. This program is stored in a Read-Only Memory chip on the motherboard.
When the computer powers up, the BIOS is launched to perform various start-up functions.)
For detailed update information please refer to Toshiba BIOS-Update Information"
(you can find this here:
[http://eu.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=EU] you have to look for:
Archive
Satellite
Satellite 14xx
Satellite 1410-604
PS141E
Quite specific. Isn't it?)
According to the information in that same website, the BIOS available fits the following models:
"Satellite 2410-414, Satellite 1410, Satellite 1410-654S, Satellite 1410-814, Satellite 2410-303, Satellite 2410-304S, Satellite 1410-354, Satellite 2410-601, Satellite 1410-401, {color:#ff0000}*Satellite 1410-604*{color}, Satellite 2410-404, Satellite 1410-301, Satellite 1410-304, Satellite 2410-S403, Satellite Pro 2100, Satellite 1410-S203, Satellite 2410-304, Satellite 1410-554, Satellite 1410-S102, Satellite 1410-354E, Satellite 2410-703, Satellite 1410-303, Satellite 2410-S203, Satellite 1410-801, Satellite 2410-603, Satellite 1410-902, Satellite 1410-313, Satellite 1410-802, Satellite 1410-714, Satellite 2410-354, Satellite 2410-514, Satellite 1410-614, Satellite 1410-704, Satellite 2410-515, Satellite 2410-504, Satellite 2410-702, Satellite 1410-S103"
Yes... it's there!
Now, when you go to the "Toshiba BIOS-Update Information", you get:
"FAQ Ref.: TRO0000000b07
A BIOS update is a {color:#ff0000}*relatively simple operation and can be carried out by most competent computer users*{color}. All BIOS upgrades can be obtained from "BIOS Update" Download Section click here..
Note: The BIOS files are machine specific so the correct BIOS for your machine must be used."
Please note that Toshiba does not disencourage the handling of BIOS, on the contrary: they even encourage people to do so. This is not necessary bad, but at the same time they encourage people to 'play around' with such a delicate matter, at the end of that same page, in little letters they say:
"Toshiba provides this information "as is" {color:#ff0000}*without warranty of any kind*{color}, either expressed or implied, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Toshiba shall not be responsible for the topicality, correctness, completeness or quality of the information provided. {color:#ff0000}*Toshiba is not liable for any damage caused by the use of any information provided, including information that is incomplete or incorrect*{color}."
This should trigger yellow alarms in our minds.
+"Human error is inherent to humans, and it is not possible to erradicate. It will allways appear, sooner or later" (Prof. James Reason).+
And finally I made the mistake. Even though I read that warning, I remembered all those successfull BIOS update with COMPAQ, and relied in Toshiba. That update was available there, and Toshiba was telling me that it was for this computer. Great!
So finally I unplugged all devices (USB), removed the PCMCIA (WLAN),plugged the battery charger to avoid any possible battery problem, restarted windows, and then from within windows I started the updater (windows version, as recommended by Toshiba). Everithing looked fine, nothing different of what I used to see on those old COMPAQs.
As warned by the updating program, the system was going to reboot. And actually it did so.
Windows closed quite normally (a bit quicker than normal, but without errors, and since there were no other programs than the essentials -even the antivirus was not running-), the computer switched of, all lights off (normal), and then it switched on again...
{color:#0000ff}*BEEEEEEEEEEEEP... BEEEP... BEEEEP...*{color}
OMG! I never espected something THAT bad. 3-1-1!
And now... What a 3-1-1 stands for here? Award BIOS would mean no video card or deffective video card, but it is not true, since it was working up to 20 seconds ago. It must be the BIOS.
It never came again to life. It is still beeping 3-1-1.
But now comes the investigation of the human-factors involved in this accident.
I found I commited the following failures:
*(1)* To rely in the manufacturer, even though they WROTE their information could be wrong or incomplete. (BAD if I were a QA&QC inspector).
*(2)* I didn't cross checked deeply enough (until it was already too late).
*(3)* I didn't looked previously for the way to make a backup of the BIOS, in order to restore should anything go wrong.
*(4)* Let Toshiba lead me to a path I didn't want to walk, just because of their offer of "increased functionality".
*(5)* Beleave in Toshiba when they said "relatively simple operation and can be carried out by most competent computer users"... they never said it is failproof.
Then I started the most interesting part of the investigation.
{color:#0000ff}*"What went wrong?"*{color}
Obviously, the BIOS update failed somehow, somewhere. And I wanted to know what and where.
First thing I discovered was that there are another search engine in Toshiba called "askiris" ([http://askiris.toshiba.com]) and I looked there in order to see if for any chance I could get the old 1.20 BIOS version that was installed originally in that machine.
And I found something... VERY interesting:
bq. {color:#800080}*From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.10 for Satellite 1410/1415/2410* \\ {color}{color:#800080}* bios for these models. TAIS. Downloads. DL. 105481 289838 289838 ACPI Flash BIOS version 1.10 for Satellite 1410/1415/2410. 2002-10-04. 105589...* \\ {color}{color:#800080}* Published 10/4/02* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.40 for Satellite 1410/1415/2410/2415* \\ {color}{color:#800080}* FDD Version 1.30 TAIS. Downloads. DL. 105481 357972 357972 ACPI Flash BIOS version 1.40 for Satellite 1410/1415/2410/2415. 2003-01-31. 105589 PUB...* \\ {color}{color:#800080}* Published 1/31/03 | Rating:* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.20 for Satellite 1410/2410* \\ {color}{color:#800080}* error message during BIOS TAIS. Downloads. DL. 105481 305240 305240 ACPI Flash BIOS version 1.20 for Satellite 1410/2410. 2002-11-01. 105589 PUB...* \\ {color}{color:#800080}* Published 11/1/02 | Rating:* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.30 for Satellite 1410/1415/2410* \\ {color}{color:#800080}* 1) Changed the content TAIS. Downloads. DL. 105481 330963 330963 ACPI Flash BIOS version 1.30 for Satellite 1410/1415/2410. 2003-01-03. 105589...* \\ {color}{color:#800080}* Published 1/3/03 | Rating:* {color}
Those are: V110, V140, V120 and V130 for series 1410/15 and 2410.
GOOD! Or not?
Let's take a look:
First thing I did was download everything all four files.
Then I took the same version that made the crash: 1.40
Than I uncompressed the file, and I found:
06/05/2009 00:17 <DIR> .
06/05/2009 00:17 <DIR> ..
31/01/2003 08:38 1,605,632 11410v14.iso
31/01/2003 08:38 511,764 1370D14.EXE
{color:#ff0000}*08/01/2003 17:03 724,480 2410a9v140.exe*{color}
09/01/2003 09:32 250,663 biofca9t.com
08/10/2002 05:26 30,697 chgbiosa.exe
31/01/2003 08:36 1,087 instinfo.bat
13/05/2002 15:25 378,175 launcher.exe
31/01/2003 08:36 433 launcher.ini
06/05/2009 00:17 0 list.txt
31/01/2003 08:36 14,768 readme.com
*{color:#ff0000}31/01/2003 08:36 12,513 readme.txt{color}*
11 archivos 3,530,212 bytes
3 dirs 9,404,600,320 bytes libres
And I got my first surprise here: There is a {color:#ff0000}*README.TXT*{color} that was not present in the file I downloaded previously from the drivers repository.
So I went to the readme.txt and I found this:
"README.TXT 01-31-2003 CDC
Flash BIOS version 1.40 for Satellite 1410
This BIOS is applicable to the following models:
Satellite 1410-S105
Satellite 1410-S106
Satellite 1410-S173
Satellite 1410-S174
Satellite 1410-S175
Satellite 1410-S176
Satellite 1415-S105
Satellite 1415-S106
Satellite 1415-S115
Satellite 1415-S173
Satellite 1415-S174
Satellite 1415-S175
Satellite 1415-S176
Satellite 2410-S203
Satellite 2410-S204"
Please note that the model 1410-604 is *NOT* listed.
I thought "well, it must be another archive..."
But then I realized of a name that sounds familiar, it was there, in the directory where I uncompressed this 1.40 file, and the name is:
{color:#0000ff}*2410A9V140.EXE*{color}
So I took the other file, the BIOS_Win update, and I discovered that the file name is:
*{color:#0000ff}2410A9V140.EXE{color}* (Ups!)
So I uncompressed it again, to find:
El volumen de la unidad D no tiene etiqueta.
El n£mero de serie del volumen es: 8838-E175
Directorio de D:\Shared\diskette\2410A9v140
06/05/2009 00:43 <DIR> .
06/05/2009 00:43 <DIR> ..
*{color:#0000ff}09/01/2003 09:32 _250,663_ BIOFCA9T.COM{color}*
17/07/2002 03:38 35 biosupd2.ini
13/07/2001 13:22 6,277 chgbios2.vxd
*{color:#0000ff}08/10/2002 04:26 _30,697 _CHGBIOSA.EXE{color}*
09/11/2001 09:14 134 clean2.reg
17/07/2002 03:35 342,064 install2.exe
16/07/2002 06:55 241,664 nchgbios2.exe
18/08/2001 11:41 3,435 nchgbios2.sys
23/10/2001 18:55 11,476 nchgbios2NT.sys
26/08/2001 09:00 49,152 nchgbios2svc.exe
13/07/2001 17:05 49,152 tbdecode.dll
14/03/2002 06:42 49,152 TCHGBIOSInfo.dll
21/06/2002 11:25 1,796 tosclean2.bat
09/11/2001 12:01 967 tosclean2.pif
21/06/2002 11:34 1,841 toscleanAUTO2.bat
21/06/2002 11:44 1,796 toscleanSMS2.bat
21/06/2002 08:51 2,038 tosntclean2.bat
21/06/2002 08:51 2,084 tosntcleanAUTO2.bat
21/06/2002 08:52 2,038 tosntcleanSMS2.bat
20 archivos 1,046,461 bytes
2 dirs 9,402,793,984 bytes libres
No readme file...
Then another question arised in my mind: What about the other 1.40 file? What does the other 2410A9V140.EXE have inside?
This:
El volumen de la unidad D no tiene etiqueta.
El n£mero de serie del volumen es: 8838-E175
Directorio de D:\Shared\diskette\comparacion_toshiba\askiris\241 0a9v140
06/05/2009 00:46 <DIR> .
06/05/2009 00:46 <DIR> ..
*{color:#0000ff}09/01/2003 09:32 _250,663 _BIOFCA9T.COM{color}*
17/07/2002 03:38 35 biosupd2.ini
13/07/2001 13:22 6,277 chgbios2.vxd
*{color:#0000ff}08/10/2002 04:26 _30,697 _CHGBIOSA.EXE{color}*
09/11/2001 09:14 134 clean2.reg
17/07/2002 03:35 342,064 install2.exe
16/07/2002 06:55 241,664 nchgbios2.exe
18/08/2001 11:41 3,435 nchgbios2.sys
23/10/2001 18:55 11,476 nchgbios2NT.sys
26/08/2001 09:00 49,152 nchgbios2svc.exe
13/07/2001 17:05 49,152 tbdecode.dll
14/03/2002 06:42 49,152 TCHGBIOSInfo.dll
21/06/2002 11:25 1,796 tosclean2.bat
09/11/2001 12:01 967 tosclean2.pif
21/06/2002 11:34 1,841 toscleanAUTO2.bat
21/06/2002 11:44 1,796 toscleanSMS2.bat
21/06/2002 08:51 2,038 tosntclean2.bat
21/06/2002 08:51 2,084 tosntcleanAUTO2.bat
21/06/2002 08:52 2,038 tosntcleanSMS2.bat
20 archivos 1,046,461 bytes
2 dirs 9,402,781,696 bytes libres
*{color:#ff0000}They both have 20 files, and 1,046,461 bytes. I asumed they are both the SAME file{color}*.
And the readme file does not list the model 1410-604 in its readme file, therefore I cannot explain this except as a mistake from Toshiba. *{color:#ff0000}They put an incorrect BIOS in their website, and suggested the update, and somehow leaded to this kind of errors.{color}*
(Except in the case that one of those models is a different name of the 1410-604 model, and if it is the case... now I don't know why this BIOS do not work with this computer).
The worst part is that neither of those other files (V1.10, 1.20 and 1.30) lists the 1410-604, therefore there seems no possible workaround for this problem. I need an original v1.20 for this CMOS, and Toshiba seems not to have it. They offered me to solve the problem, by leaving the notebook at an ASP, and paying only 95€ for the work and about 280€ for a motherboard replacement, I will get it solved. But they offer no warranty of their possibilities because is a model 'too old' and 'discontinued' and with 'no support'...
In other words, they said "don't bother with this, just go out there and buy a new one" (something absolutely out of my scope in this crisis-time) :P
Thank you for reading soooo far.
Now what I need is to get any ideas of a workaround for this, my ideas are:
(1) This CMOS has a boot-part that still works (it allows a roll-back if you have the appropriate file). So I need a good BIOS to burn into the CMOS, from the VERY SAME model (a BIOS backup) but the backup must be adequate for the burning program (CHGBIOSA.COM).
(2) It is still possible that the BIOS could be OK but the data on the CMOS got somehow corrupted. If so, clearing the CMOS could solve de problem. But I was not able to find a clear cmos button from outside, and after disasembling I took of the battery, with no good results. I have to try leaving the MOBO without battery for longer period (I left it about 20 seconds) just in case 20 seconds don't allow all the capacitors to fully go to zero values. I have not much hope in this point.
(3) Try to get a REAL good update from Toshiba. I contacted several times technical support, and I was able to verify they are only phone-operators, with a script in front of them, and when the problem goes-out-of-scope they fall always in the same answer: "you have to go to an ASP". I still have a low hope to find someone who really knows a bit, and could enlighten with a good BIOS to put in this disks.
(4) As far as I could find, this BIOS is not from any known BIOS-maker. It seems it has been developed by Toshiba (own brand), therefore the Crisis Recovery Disk from Phoenix will not be of any help here. As well as any other BIOS recovery tool not designed for Toshiba's BIOS. But I'm open to any ideas, that could be tested more or less safely. (Remember that the 'BIOS-BOOT-PART' feature is still working, I don't want to loose this only possibility of redemption).
Wwwaaaaoooowww... what a long-post falks! Sorry for that!
Forgive me, but I wanted to be really clear.
Should anyone give some hints or advice, will be greatly appreciated.
Please don't say what I shouldn't do... I already know that. I already researched and already found my mistakes, in order not to repeat them. Now I need to move on, to advance, and to try to solve this, or at least learn how to solve similar things. As much as possible.
Thank you again, in advance, and sorry again.
FenixDigital
Message was edited by: Fenix_D
Changed subject to beter reflect what is the matter about (apparently erroneous BIOS file in Toshiba download center).

Well. 
 
It's not dead, certainly. 
 
The steps that I put in my procedure were: 
 
--> There are two memory sims, that I am going to identify as M1 and M2 
--> There are two memory banks, that I am going to identify as A and B 
 
Next step in order to identify if there are some module or bank that is not working properly are: 
 
The modules were installed as: 
 
M1 --> A 
M2 --> B 
 
1--> Boot without any memory chip. 
 
<blockquote>
A--> X 
B--> X 
</blockquote>
 
2--> Boot with ONE module 
 
<blockquote>
A-->M1 
B-->X 
</blockquote>
 
3--> Boot with the OTHER module 
 
<blockquote>
A--> X 
B--> M2 
</blockquote>
 
4--> Boot with BOTH modules swapped: 
 
<blockquote>
A--> M2 
B--> M1 
</blockquote>
 
5--> Boot with ONE module swapped: 
 
<blockquote>
A--> M2 
B--> X 
</blockquote>
 
6--> Boot with the OTHER module swapped: 
 
<blockquote>
A--> X 
B--> M1 
</blockquote>
 
At this point I got a great difference. It booted, finally. But in order to make a diagnostic, I have to complete the full test, and the results were: 
 
1--> Boot without any memory chip. 
 
A--> X 
B--> X 
 
NOT BOOTING Actually the computer not even tries to read the disk. Only the power led turns on, but even prior to press the 'on/off' button. I think this indicates 'no memory installed'. I would have expected a post failure beeps, but there were no beeps at all. 
 
2--> Boot with ONE module 
 
A-->M1 
B-->X 
 
BOOTED NORMALLY Well. This obviously means that the 3-1-1 beep code means memory error, or one bank failing of two installed. Now I didn't know if the problem was the module, or the bank B. 
 
3--> Boot with the OTHER module 
 
A--> X 
B--> M2 
 
NOT BOOTING Just like the condition in 1. Like no memory installed, therefore there are two possibilities: The bank B is not working, or the memory module M2 is not working. 
 
4--> Boot with BOTH modules swapped: 
 
A--> M2 
B--> M1 
 
NOT BOOTING Just like previous to test condition. Beep code 3-1-1, no boot at all. 
 
5--> Boot with ONE module swapped: 
 
A--> M2 
B--> X 
 
NOT BOOTING This was the important test, because it finally let me determine that the problem is at the module 2 (M2) not at the bank B. But still there could be a failure IN THE BANK B and IN THE MEMORY MODULE 2. Have to do the other test. 
 
6--> Boot with the OTHER module swapped: 
 
A--> X 
B--> M1 
 
BOOTING NORMALLY This really confirmed there is nothing wrong with ANY bank, but one of the modules is not working, actually is not being even detected. This is quite weird, because this computer was working perfectly with those two modules, and in the moment of the BIOS upgrade it seems to fail... How come? 
 
Something weird happened here. I don't know what, but something ruined one memory module (fortunately only one), what I would like to know now is what happened. But at least I have the machine running, with very low memory, but running. 
 
What I am thinking now is what about this BIOS upgrade makes the motherboard not to recognize one of the modules for some reason? 
 
<img class="jive-emoticon" src="images/emoticons/happy.gif" border="0" alt=":)" /> 
 
I will continue my research, but certainly the memory made the difference. 
 
I am not sure why I didn't discover this before, I think I didn't perform this test before, for two reasons: 
 
(1) I tried to boot with no memory, and this was impossible, so I assumed that the problem was not at the memory. 
 
(2) When I heard the beep code (3-1-1), somewhere I read it was a video problem, and I asume most probably it was a video problem (since no video at all was being displayed) but I should have take into consideration that Phoenix BIOS also means with the same 3-1-1 a DMA problem (memory problem). 
 
Okis... It's a pitty having to wait so much between a post and it's approval. I posted my answer two days ago, and since it didn't appear, I believe It didn't upload, so I replied again, and also didn't appeared... until now. It is obvious that a moderator approval is required. That's why I have to wait 24 hours or more to read my post. This slows this forum effectiveness. 
 
Thank you very much for your help. I'll keep you informed. Until we get to a final diagnosis and solution.

Silicon image sil 3112 and seagate 200GB sata

hey everyone..
im trying hard to get dma activated on my sata drive..i dont need raid(and cant have it..only one sata drive ...but hdparm -tT shows slower performance on the sata drive
/dev/sda = sata
/dev/hda = pata
/dev/sda
hdparm -Tt /dev/sda
/dev/sda:
Timing cached reads: 1008 MB in 2.01 seconds = 502.32 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device
Timing buffered disk reads: 58 MB in 3.05 seconds = 19.04 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device
hdparm /dev/sda
/dev/sda:
IO_support = 0 (default 16-bit)
readonly = 0 (off)
readahead = 256 (on)
geometry = 24321/255/63, sectors = 390721968, start = 0
hdparm -i /dev/sda
/dev/sda:
HDIO_GET_IDENTITY failed: Inappropriate ioctl for device
the results for the pata drive are
/dev/hda
hdparm -Tt /dev/hda
/dev/hda:
Timing cached reads: 996 MB in 2.00 seconds = 497.58 MB/sec
Timing buffered disk reads: 120 MB in 3.00 seconds = 39.97 MB/sec
im able to enable dma/set Xfer mode/IO/ only in the pata drive, not in the sata drive..in kernel config ive enabled "scsi low-level->sata support->silicon image sata support" and also enabled "silicon image chipset support under ATA/ATAPI/MFM/RLL support"
im right now using sata as root and the drive is stable..just need dma..thanks in advance

According to Jeff Garzik's sata pages the drivers for the Sil 311x chipsets have beta status.
I had worse luck with my no-name PCI Sil-SATA controllers: as soon as I connected a hard disk the kernel would not boot anymore when using libata drivers. I can only use the allegedly deprecated IDE drivers, these work fine for me.
The libata drivers should set the proper DMA modes automatically, but things are slightly different with SATA. Anyways, 20MB/s is proof enough that some sort of DMA is actually there. Performance would be much worse without any DMA at all.
If you really want to use the libata driver you should try a 2.6.12rc kernel, libata has seen quite a many updates since 2.6.11
Cheers,
Dominik

Dell Venue 11 Pro (5130 64Bit) BIOS update in WinPE 5.1 x64

I have encountered an issue while trying to upgrade BIOS on Dell Venue 11 Pro (5130 64Bit) in WinPE 5.1 (64-bit). To pre-empt any questions why not use BIOS update option available from boot menu: while it may be quite elegant solution for home use, it doesn't fit well in production environment where the action needs to be repeated hundreds of times, custom audit trail required and some other (automated) post-upgrade tasks need to happen.
After running the executable I receive the following error message:
The subsystem needed to support the image type is not present.
This would point to 32/64 bit application incompatibility and/or limitations of WinPE itself. I have following packages present in my image, as well as CCTK HAPI installed:
Feature Name
SMB1Protocol
WinPE-HTA
WinPE-WMI
WinPE-NetFx
Microsoft-Windows-NetFx-Shared-Package-WinPE
WinPE-PowerShell
WinPE-DismCmdlets
WinPE-SecureBootCmdlets
WinPE-SecureStartup
WinPE-TPM
WinPE-Scripting
WinPE-WDS-Tools
WinPE-EnhancedStorage
Unfortunately I cannot run the update from a "proper" copy of Windows as we need to upgrade BIOS for one of our customers without installing OS (we are shipping devices with default Dell preloaded version of Windows). The way I see it, before I am forced to go down the route of upgrading BIOS from boot menu, I have two options:
- Get a grip of what the exact issue is in x64 PE. Would anyone be able to help out here? Is this something I can fix by adding any components to my PE image?
- Try running update in x86 PE (I believe the executable is 32-bit despite "64bit" string in the name). Currently I can only boot using x64 image as BIOS is set to UEFI mode. I am reluctant to change boot mode to Legacy just to give it a go. Will I be able to safely go back to UEFI without any additional recovery work? I am not intending to change the contents of the HDD. Also will cctk be able to change boot mode back to UEFI automatically, or will I have to implement it as a manual step at the end of the process?
Due to other restrictions and time scales involved Windows To Go is not an option as well. Any help with this will be much appreciated.

The issue is that the subsystem required to support 32bit apps does not exist in the WinPE 64bit, and there is no way to add it. You'll either have to use WinPE 32bit, or update your BIOS after the OS has been installed. Other manufacturers provide x64 BIOS update executables, so I don't know why Dell can't get their act together and do the same.

[SOLVED] MSI Z97 Gaming 9 AC - Bios Update Fail

Hi,
today i decided to do a bios update of my board.
A friend of me told me NOT to use the Windows-Flash tool cause he killed two borads with it.
Ok so i used the flash utility from the bios/uefi menu with a usb-stick (M-Flash).
Everything looked ok - flash tool was running and told me success/complete and it will now reboot/reset.
At this time i wasn't able to boot anymore
It was like the board tried to read the flash but failed, reset, failed ...
Lucky for me there is this little switch for the bios chip.
Everything worked with the backup chip and i tried to reflash the broken master chip.
-> Using the MSI E-Setup with Mode "In DOS Mode. (USB)".
Booting up the usb stick and switched to master bios chip when i was seeing the "alert - only continue when you know what you are doing bla bla"-message.
Wasn't able to flash anything cause of error:
Quote
ROMID is not compatible with existing BIOS ROMID
Asking google i should use the /X option (/X - Don't Check ROM ID).
Now i got a new error
Quote
Rom image layout detected RomHole is redesigned
With this message i should use the /K option (/K - Program all non-critical blocks) i was told ... now a was able to flash the chip
And the result was: fail
I found the "HQ USB flashing tool" here and tried to flash the broken chip again (switching the bios switch from backup to master after booting), but also no luck for me ...
After a break i had an idea - at which time i can switch from the backup chip to the master chip?
The bootcode "A2" was the right for me
At the bios/uefi setup all my fans were running at full speed and i was sure this is because of the broken master chip.
So again i tried the M-Flash tool from the setup - f**k it will reset/reboot before the flash progress will start - but now i know the time to switch from backup to master chip
The tool started and i saw the same messages (everything ok, reset/reboot) as i tried it the first time.
Reboot - SUCCESS!
I wasted about three hours of my live to brick and unbrick the master chip, but i don't know why this happend
Maybe this post will help someone to fix a failed bios update.
YourName

Thanks for sharing
I used M-Flash a couple of times, just remember DON'T remove usb-stick until it reboot successfully to os....

Pavilion g6-2235us bios update failed - error msg on boot

I've had trouble updating to Windows 8.1, so I did a bios update, as recommended by the HP Web Site, but it failed, and now the laptop won't boot. It displays error message "Your computer needs to be repaired:\bcd, error code 0xc0000034..." Additional info is available by hitting escape, and I can get into a black screen with options:
f1 System information
f2 System diagnostics
f9 Boot device options
f10 BIOS setup
f11 system recovery
I've been down all those paths, with no luck on proceeding any further. f10 shows me all the bios setup screens and the bios version shown is F29, the version that I tried to upgrade to.
I've tried removing the big battery and pressing the start button for one minute - no joy.
I've tried holding Windows+B+start - no joy
I guess I'm down to trying to create a USB Key with the BIOS on it, and that's where I am stumped. The BIOS softpaq for this machine is sp66880.exe. I've got that on a fat32 usb stick with the volume label HP_Tools, and I've got HP tools on the stick too. When I try to boot with the stick by pressing windows+b+start, the light on the USB stick flashes a lot, but ultimately I get the message "The system bios recovery failed. Unable to open bios image file." I have the feeling that I just don't have the proper setup on that USB stick. I tried to run sp66880.exe on another computer, but it tells me that it is going to immediately flash the bios, which I definitely don't want to do (on my Toshiba laptop!).
I would greatly appreciate any help you all can give me on how to create the recovery USB stick in the proper format. Thanks in advance.
This question was solved.
View Solution.

Fixed!
It turns out that the bios update actually succeeded, but something in the hard drive boot files got corrupted. I was able to make a Windows 8 Recovery USB stick on another machine, and finagle around to have the HP laptop reformat the hard drive to original factory condition. Fortunately, I made a very recent Macrium image before this most recent problem started, so the next step is to restore that image. With the new v. F29 bios, hopefully this beast will finally upgrade to Windows 8.1.

Hard drive failure after running bios update.

While attempting to update the bios on my A215 S5824 laptop, there was a small POP sound and everything went dead. Everything seems to be working except the hard drive and screen. I was having intermittent blank screen issues, thus the bios update attempt. Any thoughts would be helpful.
P.S. Running windows vista home premium.
AMD 64 athlon x2 w/ati radeon graphics

I would search these forums and the web for Toshiba BIOS Crisis Recovery,it may be possible to boot the BIOS in repair mode (using certain key combinations) to access a BIOS image that's on a bootable media or thumb drive.
You can also trying to contact Toshiba to see if they will cover this repair
You can also contact aqstech.com to do the BIOS repair for about 100 bucks.

MSI-6712 BIOS update issues

I have a PC, running XP Pro SP3, which was built for me nigh on 9 years ago.
Motherboard: MSI-6712 (KT4V-L) Version 1.0 (North Bridge KT400A Rev 80, South Bridge VT8235 Rev 00)
CPU: AMD XP2800+ CPU (Socket A 462, 3000 MHz)
Memory: 1.0GB DDR
GPU: nVidia GeForce FX-5200 (128 MB)
About 4 years back I considered updating the BIOS, but the MS LiveUpdate utility (v 3.5 I think it was) no longer worked (wrong URL). Tried updating it, but the update (can’t remember the version) shut down my system whenever I tried to use it. So I rolled back and left it.
Recently, a program I was evaluating (running on .Net 4 Client Profile) caused my PC to freeze up and after uninstalling I discovered all manner of problems with USB peripherals (recognition and auto-play issues).
Tried to restore a backup (Retrospect Express HD) from a Maxtor One Touch III external drive but it wasn’t having it, presumably because of the drive recognition issues, and a straight System Restore wouldn’t complete (because XP would freeze at log off).
I feared there had been hardware damage, but decided to try a clean re-install of XP Pro. The person who built the PC had left a folder of system set up files (VIA chipset 4in1, LAN, RealTek AC97, nVidia drivers, utilities etc) on the hard drive (which I backed up) but when it came to installing XP, I couldn’t figure out which chipset drivers to install, as there were multiple versions (presumably for his purposes). So I let XP install the default windows drivers and then replaced them with the latest VIA 4in1 set for the KT4V-L from the MSI download page (can’t post link) – driver version 5.11a, release 20.4.2007
Seemed to go well, but it was suggested to me that it might be a good time to update the BIOS. So I installed MSI Live Update 5 and ran a scan. Strange thing is that an automatic scan (which pulls up just the nVidia driver and utilities) reports that none are installed and a manual scan reports that the BIOS, Drivers and Utilities are the latest version and no there is need to update. How can that be? I’ve never updated the BIOS and the only other utility I re-installed is PC Alert 5.
Yet when I run a SIW (System Information for Windows) scan and it reports the following:
BIOS Properties
BIOS Vendor American Megatrends Inc.
Serial Number 00000000
BIOS Version Version 07.00T
Firmware Version 101.114
BIOS Date 04/02/01
BIOS Size 256 KB
BIOS Starting Segment F000h
DMI Version 2.3
Characteristics
supports ISA Yes
supports MCA No
supports EISA No
supports PCI Yes
supports PC Card (PCMCIA) No
supports Plug-and-Play Yes
supports APM Yes
upgradeable (Flash) BIOS Yes
allows BIOS shadowing Yes
supports VL-VESA No
ESCD support is available Yes
supports booting from CD-ROM Yes
supports selectable boot Yes
BIOS ROM is socketed Yes
supports booting from PC Card (PCMCIA) No
supports Enhanced Disk Drive specification Yes
supports INT 13 for Japanese NEC 9800 1.2M floppy (3.5-inch, 1024-byte sectors, 360rpm) No
supports INT 13 for Japanese Toshiba 1.2M floppy (3.5-inch, 360rpm) No
supports INT 13 5.25-inch/360K floppy services Yes
supports INT 13 5.25-inch/1.2M floppy services Yes
supports INT 13 3.5-inch/720K floppy services Yes
supports INT 13 3.5-inch/2.88M floppy services Yes
supports INT 05 print-screen Yes
supports INT 09 and 8042 keyboard services Yes
supports INT 14 serial services No
supports INT 17 printer servicesYes
supports INT 10 CGA/Mono video services Yes
NEC PC-98 No
supports ACPI Yes
supports legacy USB Yes
supports AGP Yes
supports booting from I2O device No
supports booting from LS-120 Yes
supports booting from ATAPI ZIP drive Yes
supports booting from IEEE 1394 deviceNo
Smart Battery supported No
BIOS Boot Specification supported Yes
Function key-initiated Network Service boot supported No
Enable Targeted Content Distribution No
How is it that Live Update 5 doesn’t pick this up?
So, apologies for the convoluted post (thought it best to explain the events leading to this), but what to do?
1.   Do I need to update the BIOS, given that it has never been done and I now have the latest VIA 4in1 drivers installed?
2.   Why is Live Update 5 not reporting the status correctly and is there anything I can do to correct this.
3.   Otherwise, if a BIOS update, is warranted, should I go ahead and download directly from the Global MSI webpage and then which version? (can’t post link). I note from the version descriptions that it was v1.7 (26/12/2002) that added support for AMD XP 2800. Strange then that the guy who put together my PC, would not have updated the BIOS from v1.0 to 1.7 at that time!!
4.   Should I also update the nVidia driver, and if so, when? Before or after a BIOS update or is that irrelevant?
Video Adapter NVIDIA GeForce FX 5200 (Microsoft Corporation)
Code Name NV34
Video Processor GeForce FX 5200
Technology 0.15 0m
Adapter DAC Type Integrated RAMDAC
PCI ID 0x10DE / 0x0322 (nVidia Corporation / GeForce FX 5200 [NV34.3])
PCI sub ID 0x1462 / 0x9360 (Micro-Star International Co., Ltd. / MS-8936 (FX5200-T128))
Memory128 MBytes
BIOS String Version 4.34.20.22.00
BIOS Date 08/01/03
PnP Device Id PCI\VEN_10DEDEV_0322SUBSYS_93601462REV_A1\41FEB96E400008
Video Mode Description 1440 x 900 x 4294967296 colors
Driver Version 6.14.10.5673
Driver Date 2004-08-03 22:29:56
DirectX DirectX 9.0c (4.09.0000.0904)
Driver Name nv4_disp.dll
Driver Description NVIDIA GeForce FX 5200 (Microsoft Corporation)
Edit: Actually, looking at the original SIW scan report I see that there are some errors relating to DirectX. Not sure if I need to update DirectX (surely MS Update does that automatically) and/or the nVidia driver.
5.   One other thing that concerns me is that the SIW scan reports that the BIOS is reporting wrong values for the DDR memory. What’s that about?
Memory Summary Reported by BIOS
Warning! Wrong values reported by BIOS
Maximum Capacity 3072 MBytes
Maximum Memory Module Size 1024 MBytes
Memory Slots [unknown]
Error Correction
Memory Timings 3-3-3-8 (CL-RCD-RP-RAS)
Device Locator Slot 1
Manufacturer Silicon Technology
Capacity 512 MBytes
Memory Type DDR (PC3200)
Speed 200 MHz
Supported Frequencies 166.7 MHz, 200.0 MHz
Memory Timings 2-3-3-7-0 at 166.7 MHz, at 2.5 volts (CL-RCD-RP-RAS-RC)
Memory Timings 2-3-3-8-0 at 200.0 MHz, at 2.5 volts (CL-RCD-RP-RAS-RC)
Data Width 64 bits
EPP SPD Support No
XMP SPD Support No
Device Locator Slot 2
Manufacturer Silicon Technology
Capacity 512 MBytes
Memory Type DDR (PC3200)
Speed 200 MHz
Supported Frequencies 166.7 MHz, 200.0 MHz
Memory Timings 2-3-3-7-0 at 166.7 MHz, at 2.5 volts (CL-RCD-RP-RAS-RC)
Memory Timings 2-3-3-8-0 at 200.0 MHz, at 2.5 volts (CL-RCD-RP-RAS-RC)
Data Width 64 bits
EPP SPD Support No
XMP SPD Support No
Hope someone can advise me on this.
Cheers.

Sorry for cross-posting to another forum, but this has got me in a twizzle
http://www.windowsbbs.com/pc-hardware/89688-need-ram-recommendations-msi-kt4v-l-2.html#post493343
According to the poster (Post #30), the KT4V-L can support 3gB DDR400.
I looked at the MB in my PC and it is in fact stamped MS-6712 KT4AV v10A (assumed 1.0A ). Both CPU-Z and SIW report it as a MS-6712 v1.0 (BIOS 07.00T 04/02/01, Firmware 101.114)
According to the MSI product webpage, the only difference between the KT4AV and KT4AV_L is that the latter includes an (optional) on-board 10/100 LAN.
http://www.msi.com/product/mb/KT4AV.html#/?div=Detail
The ethernet port on my PC is (as described in Device Manager) is a Via Rhine II Fast Ethernet Adapter, whereas in the listed MSI specifications, the optional 10/100 LAN is stated to be a VIA VT6103 LAN controller. So possibly then I was mistaken in assuming that my MB is a KT4AV-L.
Even so, if the statement about the KT4AV-L supporting 3gB DDR400 is true, surely this also applies to the KT4AV ?
Looking at the available BIOS updates on the MSI page, I can see no mention of an upgrade in DDR400 capacity:
http://www.msi.com/product/mb/KT4AV.html#/?div=BIOS
Edit: Ah, the guy in the post specifically refers to a KT4V-L v1.1 not KT4AV-L and I see that it is different product:
http://www.msi.com/product/mb/KT4V---KT4V-L--v1-0-.html#/?div=Detail
What's confusing is that they all designated as MS-6712. So if anyone, like me, does a look up under MS-6712 they could pull up either version, and since the KT4AV/L and KT4V/L have different BIOS update series, I can see how someone could easily flash the wrong BIOS.
That aside, the memory specifications for the KT4V/L are essentially the same as those in the User Guide that came with my KT4AV:
Supports up to 3GB PC1600/2100/2700/3200* DDR SDRAMs
*See Glossary for recommended DDR400 modules - with the largest listed module capacity being 2 x 512MB
So where does this "up to 3GB DDR400 capacity" notion come from. I'd really want to believe it. And if the guy in the PC shop is to be believed, I'd settle for just 2GB.
Edit 2: Oh, boy, so there is a separate product listing for the KT4V-L v1.1:
http://us.msi.com/product/mb/KT4V-L--v1-1-.html#/?div=Detail
Yet, the memory specifications appear to be the same as those for the other MS-6712 versions and BIOS updates are the same as those for the KT4AV-L (very confusing). In fact the downloadable User Guide is the same - 'KT4AV MS-6712 (v1.X) ATX Motherboard'.
Am I missing something here?

Diamond Plus- Silicon Image controller set up single SATA 2 non raid "HELP"

Could somebody please tell me what drivers exactly do you have to load for Windows install off of the floppy? I loaded the silcon image 32 drivers at the install but the boot into windows takes a long time ! In bios SATA 1 SATA 2 are enabled -non raid for Silicon Image controller. Is their any kind of special procedure or trick for for useing the the controller non raid mode? Just added another HDD to my system formatted first with WD Lifeguard Tools and unhooked my othet drives and 1 of my dvd burners but for some reason It took like 2hrs 20 min too load windows when I specified additional drives their wer like 4-5 to choose from and the only non raid refference 1 was the first which I belive silicon image sys32 do you have to install all of them like the nvidea ones? man I had absolutely no problems setting up my 2- 80gb WD Caviars in raid 0 but the new 250gb WD caviar se16 is another story. ALL ARE SATA 2 DRIVES so I know that SATA 2 works on my board im useing it right now! Could any of the lLocal Forum Gurus with prior experience with the controller tell me exactly how to configure the set up NON RAID! PLLLLLLEASE.........
Thanks in advance

Thanks for all of you help Bas, and the quick responce! I was asking about which would be the prefered set up raid 0 on silicon image and sigle drive non raid on port 3-4 Nvidea or vice versa. I'm sure that it is a matter of prefference, but I do plan to overclock slightly when it cools down and I have done more reading on it! My primary goal is Stabilily and performance in harmonic balance whith out data corruption, or risking blowing things up! Any way hows life in Belgium? I have yet to travel to Europe, traveled to just about all of the states and lived on 2 of the Hawaiian Islands. So as you can tell Bas I am more partial to warm weather. I am quite a bit more in tuned with European culture than most people. My folks are from Australia and New Zealand so i'm not youre typical American! Shoot's Bro thanks for all of youre help and have a good weekend!!
Campbell

Satellite C870-196 - Long launch after BIOS update

Hello
I went to u BIOS 6.00 to 6.70 and I have a very long black screen between the TOSHIBA logo and the launch of my session I had not before!
I delivered the default settings in the BIOS (F9) as shown.
Where can this come and what to do?
Thank you
Kind regards

Well, new BIOS updates contain always some changes and probably something has been changed in new version and therefore the time between Toshiba logo and appearance of the image is a little bit longer.
What to say its not know to me that you could modify this delay so you will need to accept this BIOS change

Silicon Image 3132 BIOS update

Similar Messages

Maybe you are looking for