Should I apply this BIOS update

My Toshiba Service Center shows BIOS 6.10 update released 10-29-2012.
Present version is 1.30 with release date 4-26-2012.
Should I apply this BIOS update?
Toshiba Satellite P875-S7200 / Windows 7

If I were you, Niki, I would NOT apply the BIOS update unless you are having some kind of problem that you think a BIOS update will cure. Don't try to fix something that ain't broke!!!  In this case, most of the changes from your version 1.30 to the 6.10 version have to do with Windows 8, not the Windows 7 you are using.
C.B.
C.B.
Toshiba Sat. C75D-B7260 Win 8.1 64 Bit--Toshiba Sat. L775D-S7132 Win 7 HP SP1 64 Bit and Win 10 PRO Technical Preview--Toshiba Sat. L305-S5921 Win Vista SP2 32 Bit

Similar Messages

  • Should I apply A1107 OTA update?

    My WiFi quit working and I had to send my tablet to Lenovo for repair. When it came back, they had installed ICS on it (I had put GB on to avoid potential warranty issues). It was a slightly different version than the one you can download from here - some additional apps, mainly. After a couple of days, to my surprise, it told me there was a system update available - this never happened before. I had always thought that the version of ICS from this forum was all the upgrade we were ever going to get. Does anyone know what's in this update, and is it a good idea to apply it? My tablet is now at build number
    A107I0_A404_001_010_0114_US, kernel version 3.0.8-00047-gf747a8c user@ubuntool # 1
    Thanks in advance.
    Solved!
    Go to Solution.

    The latest version on Lenovo's ICS download site - http://download.lenovo.com/slates/a1/ICS_OTA/
    is A107I0_A404_001_013_0116_US.zip. However, if your A1107 is working in a way that you're happy with, I wouldn't apply the update. The factory could have loaded 0116 if they wanted to do so. They probably did not for a reason.

  • Recent BIOS Update maybe bricking M93p Tiny systems?

    We've just applied this BIOS update (http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS035753) on 4 M93p Tiny machines.
    1 of the machines is getting a blinking cursor at boot up (bricked?)
    3 of the machines can no longer boot to the hard drive.
    In the 3 machines that are not seeing the hard drive to boot, they occasionally show in the BIOS boot order, but when you try to include them in the boot order they disappear.
    Hard drives are a recently Windows 7 64-bit image that worked before BIOS update.
    If we network boot into a PE we can see the hard drive contents.
    Called Lenovo support but got bounced around... any one see any issues like this?
    Solved!
    Go to Solution.

    If you just have a blinking cursor you may be able to do a CMOS reset to get it to a working BIOS. That worked for me. The other ones that just couldn't boot to the hard drive needed to have the board replaced, tho.
    See page 293 of the HMM http://download.lenovo.com/ibmdl/pub/pc/pccbbs/thinkcentre_pdf/m83m93p_hmm.pdf "Recovering from POST/BIOS failure"

  • Bios update e430 problem

    Hi i have e430 , when i update bios win restarted and show black screen what do I do?

    Thanks for the good reply! Upon reflection I kinda thinking if the Phoenix WinPhlash will not even display itself properly, chances of it working properly are pretty slim. the only reason I was looking to update BIOS was for,
      (New) Update for the 3000 N100 (Windows XP Preload Models) BIOS Ver. 2.05 (61ET36WW) for the following updates.
    ***** IMPORTANT *****
    This BIOS contains a critical processor microcode update to improve system reliability. Lenovo highly
     recommends that you apply this BIOS update.
    I've always experienced "intermittant / random" hangs on boot and hangs on shutdown the entire time I've owned my laptop, not real bad, but frequent enough to make one say "huh, what up with dat". HOWEVER not one to jump out of a running airplane, and ever disobey the Cardinal Rule of "if it ain't broke, don't fix it" I thinking just let it ride may be a wise man's move. Any wise persons out there agree or disagree?
    Thanks much!
    Rick

  • BIOS updates? -- Syslinux problems

    Are BIOS updates even possible/safe in Linux?  I bing'd it and read an article about using flashrom, so I did a quick
    $ pacman -Ss flashrom
    and noticed that we've got it in our repos, which I remember already knowing, so I'm now wondering why did I even bother to search for it...
    anyway, so would it be safe to try to use flashrom to do a BIOS update for my ACER laptop, because it REALLY needs one.  It can't even run Syslinux--Syslinux starts up and then just sits there like a bump on a log.   My other option is to reinstall Windows 7, which stopped working after I changed my HDD's part table to GPT and moved the Windows Paritions to the end where they could sit and do... nothing, I guess. 
    Any ideas?
    Oooh, quick note.  It seems that Syslinux does not work when booting from a USB, but does when booting from a DVD or CD, how odd.
    Last edited by lspci (2012-09-20 08:02:03)

    Pres wrote:
    I checked and you are right, they don't seem to provide a DOS method for updating to 1.10 for your laptop. However, the fact that several of the older BIOS versions on their site were larger files caught my interest, so I downloaded one. Looks like they provided DOS files for every version up to 1.09.
    Might want to call them and ask why the DOS method was removed for 1.10.
    Good idea, I'll ask 'em what's up.
    Lol, so here's what their representative told me during my chat with, I guess her. 
    Govindan Sharanji: Hi, my name is Govindan Sharanji. How may I help you?
    lspci lsblk: Hi, I wanted help with doing a BIOS update. I know that the download/support page for my laptop says that I should only do this when instructed but I'm hoping that the newer BIOS will be nicer than the old ones and that they might somehow magically support Syslinux.
    Govindan Sharanji: I will certainly provide you the required information.
    lspci lsblk: I don't use Windows 7, though; so I asked around in the Arch Linux community for advise and one of the guys on there said that yall might have a DOS executable that I could use to do the update with.
    lspci lsblk: oh, okay.
    lspci lsblk: uh.. well, what I've been saying so far is really just background information--leading up to my real question, as it were.
    Govindan Sharanji: I understand that you require the information to download and install the BIOS update.
    Govindan Sharanji: Let us check the BIOS version of your notebook.
    Govindan Sharanji: Please open System Information by clicking the Start button. In the search box, type System Information, and then, in the list of results, click System Information.
    lspci lsblk: I don't use Windows.
    lspci lsblk: I don't have a start button or any of that, I'm afraid. I use Arch Linux.
    Govindan Sharanji: Okay.
    lspci lsblk: I already downloaded the BIOS, I just wanted to know if you knew why yall dropped support for the DOS method of updating the BIOS. Like, one of the guys of the Arch Linux Forumns said:
    lspci lsblk: "Looks like they provided DOS files for every version up to 1.09.
    Might want to call them and ask why the DOS method was removed for 1.10."
    Govindan Sharanji: Let me check the database.
    lspci lsblk: okay.
    Govindan Sharanji: As per documentation the latest BIOS update can only be installed from windows.
    lspci lsblk: hmm, okay. :/
    lspci lsblk: I tried installing Windows, just for the sake of doing the update, but the installation process said that Windows could not be installed to a GPT partition table.
    lspci lsblk: (I use GPT instead of the usual Master Boot Record table, I believe.)
    Govindan Sharanji: Since you have installed Arch Linux you need to clean format the hard disk using any third party application.
    Govindan Sharanji: After formatting you may use the recovery discs to install windows operating system that was shipped with your computer.
    lspci lsblk: o.O Heavens, no. It'll take me over a week to reinstall it after words and get everything back to normal.
    lspci lsblk: What about version 1.09?
    lspci lsblk: did that one come with a DOS executable?
    Govindan Sharanji: Let me check.
    lspci lsblk: okay
    Govindan Sharanji: Yes 1.09 08/20/2012 can be updated in DOS mode.
    Govindan Sharanji: http://global-download.acer.com/GDFiles/BIOS/BIOS/BIOS_Acer_1.09_A_A.zip?acerid=634810224904845613&Step1=NOTEBOOK&Step2=ASPIRE&Step3=ASPIRE V3-571&OS=ALL&LC=en&BC=ACER&SC=PA_7
    lspci lsblk: yay, excellent.
    lspci lsblk: okay, thank you very much.
    Govindan Sharanji: Please click on the above link to download and install the BIOS update version 1.09 08/20/2012.
    lspci lsblk: Oh, wait that reminds me. Do you know if yall will have the Recovery Disks for my laptop anytime soon?
    Govindan Sharanji: After extracting the BIOS file you will find an readme file with instructions to install the BIOS update in DOS mode.
    Govindan Sharanji: The Restore CD costs approximately $19.95 (plus taxes) including shipping and handling on your Credit Card.
    lspci lsblk: save your breath, I know how to take care of the DOS thing. No, I mean do yall have it in yall's Acer Store thing yet? Last I checked it wasn't available for my product.
    lspci lsblk: or for yall's product that I bought, I should say.
    Govindan Sharanji: The Recovery Media is not immediately available.
    lspci lsblk: okay..., any idea when it will be?
    Govindan Sharanji: Yes it will be available soon.
    Govindan Sharanji: You may contact Acer Ecommerce department at 1-800-910-2237, Mon-Fri 8:00am - 5:00pm CST to purchase the recovery disc.
    lspci lsblk: my hopes are that I might be able to use the Discs to recover the factory installation of Windows and so by pass all of the problems in terms of updates that I am currently faced with.
    lspci lsblk: well, I was really more interested in a simple yes, and the date, or a no. But that works too, I guess.
    lspci lsblk: Anyway, that about wraps up my list of questions, so thank you for all the help. :)
    Govindan Sharanji: You also have the option to send the computer for warranty service the reload the factory shipped operating system.
    lspci lsblk: hmmm...
    lspci lsblk: I might do that... but.... it'd still be a pain in the butt to reinstall Arch Linux and all the software that I've either compiled or installed on here using the package manager
    Govindan Sharanji: I appreciate you for spending your valuable time with us in diagnosing the issue.
    Govindan Sharanji: If any further information is needed please contact us again and I will be happy to assist you.
    lspci lsblk: *sigh* I think that I may just make due with the vesion 1.09 update... oh, and just for the record why did yall drop support for the DOS method for version 1.10? You really didn't specify exactly why.
    lspci lsblk: you mentioned something about documentation, but what documentation and why?
    Govindan Sharanji: The dos version of this BIOS update was not released since this update was for some windows driver issue.
    lspci lsblk: Ooooh
    lspci lsblk: so yall didn't just drop it 'cause yall decided to only support Windows from now on?
    Govindan Sharanji: No.
    Govindan Sharanji: It has been a privilege assisting a valuable customer like you!
    Govindan Sharanji: It was a pleasure assisting you.Thank you for using Acer Live Chat.
    Govindan Sharanji: Have a pleasant night. Goodbye.
    lspci lsblk: okay, bye.
    Govindan Sharanji has disconnected.
    So as it turns out version 1.10 only comes in Windows-flavor for a reason. 
    lspci lsblk: *sigh* I think that I may just make due with the vesion 1.09 update... oh, and just for the record why did yall drop support for the DOS method for version 1.10? You really didn't specify exactly why.
    lspci lsblk: you mentioned something about documentation, but what documentation and why?
    Govindan Sharanji: The dos version of this BIOS update was not released since this update was for some windows driver issue.
    lspci lsblk: Ooooh
    lspci lsblk: so yall didn't just drop it 'cause yall decided to only support Windows from now on?
    Govindan Sharanji: No.
    Apparently there was a Windows driver issue and the BIOS update was developed in an effort to fix that, which is why there's no DOS version since the update only applies to Windows.
    So do I just need to download FreeDOS now and boot up with that or will they include their own custom version of FreeDOS in the zip archive?
    Last edited by lspci (2012-09-21 14:16:06)

  • T500 20552CU BIOS Update and Hotfix KB937500

    Hello,
    I am using a T500 with a quite old BIOS (1.13-1.0) and now I want to update it,
    the installation notes suggest the following:
    "If you use Windows Vista, before applying this BIOS into the system, you should install Windows Vista KB 937500. The information of KB937500 is located at Microsoft's Web site."
    But I cannot install the hotfix, the Update Manager tells me that this Hotfix is not applicable to my system.
    So can I update my BIOS without this hotfix?
    Thanks!

    From the information in Microsoft's description of KB937500, that hotfix applies to Vista pre-SP1:
    " Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1."
    If your system has Vista SP1, that's probably why the hotfix will not install.

  • Satellite A300 - After BIOS update black screen

    Hello all,
    I just applied the BIOS update on my Satellite A300. After the update successful, the system does a reboot. Now when I try to power it up I get no display, I can hear the hear running, the CD Drive reading the DVD, led blinking.
    The Toshiba ASP tolled me (phone call) the mainboard should be replaced after a unsuccessful bios update, but it's very expensive for me, :(
    Please can you tell me if they are any way to fix it without mainboard replacement? The bios is a Insyde and according to the website the bios has bios [Recovery Technology|http://www.insydesw.com/press/2008/press_060308.htm]. I guess that the ASP doesn't know that.
    Please can you tell me how to start the recovery procedure if it's possible (key combination?),
    Any help about fixing the laptop without mainboard replacement will be much appreciated.

    There are cases when the chip that containes the bios is removed from the motherboard and with a memory writing device (special to do this) it is posible to rewrite the bios(in my country, Romania it is not possible at the Toshiba Service, they change the motherboard wich cost 400-500 euro, but there are guys in electronics who do things like this...).
    This is the happy case to rewrite, when this is possible. But there are exceptions when you can't do anything and you have to change the motherboard.(bad bios update coud burn your entire motherboard or several components /parts).
    In what I've read " For example, on other manufactures PC compatible systems with Award BIOS and AMI BIOS there is dedicated small area, often about 8 kiB or so, called bootblock which starts first" , if your bios si from award or ami they have lets say a small progam which starts first, checks if bios is oki then is booting normal , if not it tries to recover it and boot.
    In your case this is not possible even if you have the specific computer with that kind of bios because the screen doesn't start.
    *Your case is simillar to mine* so you could hope that your video card is broken and not your motherboard.
    My advice to you is to go to the service and diagnostic the problem and see what is the solution.

  • 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.<br />
    <br />
    It's not dead, certainly.<br />
    <br />
    The steps that I put in my procedure were:<br />
    <br />
    --&gt; There are two memory sims, that I am going to identify as M1 and M2<br />
    --&gt; There are two memory banks, that I am going to identify as A and B<br />
    <br />
    Next step in order to identify if there are some module or bank that is not working properly are:<br />
    <br />
    The modules were installed as:<br />
    <br />
    M1 --&gt; A<br />
    M2 --&gt; B<br />
    <br />
    <strong>1--&gt; Boot without any memory chip.</strong><br />
    <br />
    <blockquote>
    A--&gt; X<br />
    B--&gt; X<br />
    </blockquote>
    <br />
    <strong>2--&gt; Boot with ONE module</strong><br />
    <br />
    <blockquote>
    A--&gt;M1<br />
    B--&gt;X<br />
    </blockquote>
    <br />
    <strong>3--&gt; Boot with the OTHER module</strong><br />
    <br />
    <blockquote>
    A--&gt; X<br />
    B--&gt; M2<br />
    </blockquote>
    <br />
    <strong>4--&gt; Boot with BOTH modules swapped:</strong><br />
    <br />
    <blockquote>
    A--&gt; M2<br />
    B--&gt; M1<br />
    </blockquote>
    <br />
    <strong>5--&gt; Boot with ONE module swapped:</strong><br />
    <br />
    <blockquote>
    A--&gt; M2<br />
    B--&gt; X<br />
    </blockquote>
    <br />
    <strong>6--&gt; Boot with the OTHER module swapped:</strong><br />
    <br />
    <blockquote>
    A--&gt; X<br />
    B--&gt; M1<br />
    </blockquote>
    <br />
    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:<br />
    <br />
    1--&gt; Boot without any memory chip.<br />
    <br />
    A--&gt; X<br />
    B--&gt; X<br />
    <br />
    <strong>NOT BOOTING</strong> 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.<br />
    <br />
    2--&gt; Boot with ONE module<br />
    <br />
    A--&gt;M1<br />
    B--&gt;X<br />
    <br />
    <strong>BOOTED NORMALLY</strong> 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.<br />
    <br />
    3--&gt; Boot with the OTHER module<br />
    <br />
    A--&gt; X<br />
    B--&gt; M2<br />
    <br />
    <strong>NOT BOOTING</strong> 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.<br />
    <br />
    4--&gt; Boot with BOTH modules swapped:<br />
    <br />
    A--&gt; M2<br />
    B--&gt; M1<br />
    <br />
    <strong>NOT BOOTING</strong> Just like previous to test condition. Beep code 3-1-1, no boot at all.<br />
    <br />
    5--&gt; Boot with ONE module swapped:<br />
    <br />
    A--&gt; M2<br />
    B--&gt; X<br />
    <br />
    <strong>NOT BOOTING</strong> 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.<br />
    <br />
    6--&gt; Boot with the OTHER module swapped:<br />
    <br />
    A--&gt; X<br />
    B--&gt; M1<br />
    <br />
    <strong>BOOTING NORMALLY</strong> 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?<br />
    <br />
    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.<br />
    <br />
    What I am thinking now is what about this BIOS upgrade makes the motherboard not to recognize one of the modules for some reason?<br />
    <br />
    <img class="jive-emoticon" src="images/emoticons/happy.gif" border="0" alt=":)" /><br />
    <br />
    I will continue my research, but certainly the memory made the difference.<br />
    <br />
    I am not sure why I didn't discover this before, I think I didn't perform this test before, for two reasons:<br />
    <br />
    (1) I tried to boot with no memory, and this was impossible, so I assumed that the problem was not at the memory.<br />
    <br />
    (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).<br />
    <br />
    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.<br />
    <br />
    Thank you very much for your help. I'll keep you informed. Until we get to a final diagnosis and solution.

  • Satellite L650 - Touchpad won't disable after BIOS Update

    Hello,
    I've recently got a new laptop, a L650-1CN,
    I run the various kinds of software from Toshiba, and one of them is Tempro,
    It shows me messages when a new update is available.
    Today I got saw the message that a new BIOS update v.1.80 was available.
    I downloaded it, and installed it. After installing my laptop shut down. Then I booted it again.
    But after a few minutes I noticed that my touchpad didn't disable itself anymore.
    I usually use a logitech wireless mouse.
    Now I'm wondering if I should do a system recovery and not install this BIOS update, or find another solution to fix this. Because it's really annoying.
    Thanks in advance.

    Hi buddy,
    Usually the touchpad disable it automatically if an external mouse is connected but only if you enable this option in touchpad settings.
    I also use an external mouse from Logitech and have activated this option. You can find it in control panel > mouse. Go to tab Device Settings and mark the option Disable internal pointing device when external USB pointing device is attached.
    I hope it works :)

  • V570 Bios update (Windows 8)

    Can I use this Bios update file for the v570 in Windows 8? It only lists up to Windows 7 in operating systems.
    http://support.lenovo.com/en_US/downloads/detail.p​age?DocID=DS027341
    Also is this the correct MD5 for the Bios update:
    A67CD81FC9340D98C9C7E8BC2BC6EF81

    Hi
    The bios should be updated in windows 7 only and shouldn't be updated in any other os other than windows 7.
    Ishaan Ideapad Y560(i3 330m), Hp Elitebook 8460p!(i5-2520M) Hp Pavilion n208tx(i5-4200u)
    If you think a post helped you, then you can give Kudos to the post by pressing the Star on the left of the post. If you think a post solved your problem, then mark it as a solution so that others having the same problem can refer to it.

  • Equium L40 (PSL49E) - Is the BIOS update compatible?

    Simple question:
    I have a Equium L40 PSL49E laptop with Vista. There is a BIOS update available - but only for models with Modelnumber PSL48x, PSL49x, PSL4Bx or PSL4Cx.
    So, my question is: Does that include my model?
    Is PSL49E = PSL49x?
    It would also be a bonus if someone could explain, which function exactly these updates have? And if there is anything I should be aware of in that context?

    Yes, the update is compatible with your notebook. I have also checked the Toshiba website for the PSL49E and I can see this BIOS update.
    PSL49x means that this update is compatible with all models that start with PSL49

  • Portege R500 BIOS update 1.60-WIN

    Hello
    I was looking at the 1.60-WIN BIOS update available on the download pages since 25/03/08.
    Anybody know what the update does?
    The explanation on the download page just says: +"This Bios Update adds increased functionality to your system."+
    Thanks in advance.

    Yeah, 0,85V is locked by the CPU. It's Intel's mistake that the CPU runs so hot and doesn't accept halt commands. I tried maybe 5-6 available apps and no luck. Also, Win XP makes the R500 much snappier and faster, and even thought it consumes less resources than Vista the CPU gets to 62C and fan start whining. Then the temp drops to 55C and the fan stops. It takes3-5 mins and the temp rises again to 62C and this goes on and on. With an idle system and the lowest cooling method! Crazy!! I'm afraid BIOS update and the higher temp threshold would not help because the limit should be somewhere near the absolute max temp that the CPU can handle and that would make the whole laptop very very hot. 80-90C?
    I wonder is it possible to force (hack) the CPU to accept low voltages like couple of years ago pencil tricks worked nicely.. or custom code for the halt command...

  • Express bios update last status i failed

    i have sccm 2007 and clients win 7 64 bit, on two clients win 7 64 bit, in advertised programs last status of express bios update (HP) is failed, but the bios install succesfully, when the bios upgrade from advertised programs computer reboot and bios
    install with status successfully, when komputer system win 7 run in advertised program last status is failed, help me

    Yes, I know this is an old post, but I’m trying to clean them up.
    When you applied the BIOS update, Did it reboot the computer without telling CM07?
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Bios Update Fail - Under Warranty but No Support

    Hi,
    New to the board and looking for some help. I have a w500 still in warranty. We have been having issues with running Vista and the machine not rebooting after hibernation. Today I found some time to run updates using the pre-loaded ThinkVantage software on the machine. There were quite a few on there including a Bios update... upon running the updates and the machine restarting at the end, I get a black screen....  and nothing... the power lights are on but not more. 
    I have called Lenovo tech support and they advised me that because I did the Bios update (as part of the many updates that were suggested I required) I have voided my warranty support for this problem.... apparantly I was made aware of this as part of the disclaimer prior to running the updates!!!  
    Does anyone have any suggestions on steps forward from this point?
    Solved!
    Go to Solution.

    In there you have the old bios versions : http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-74858#version
    NO!!! Don't install that update (assuming the installer allows you to do that.)
    That link is to the BIOS update for the ThinkPad W510 No wonder your machine may fail to boot correctly after installing that.
    You want to create a bootable CD with the latest BIOS for the ThinkPad W500 which can be found at http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-70354 There are links to earlier versions of the BIOS for the W500 at the bottom of that page as well, if you want to go back to the original version delivered out-of-the-box, but there's no real reason to do that.
    Booting from a CD is probably the safest method of updating the BIOS, since it does only that update without interference from any other updates or software (Lenovo's system Update should really only allow BIOS updates to be installed separately from other updates). However, I don't know what happens when the updater finds that the existing BIOS on the machine is for another machine type (W510), assuming you've already tried installing the wrong update referenced in the posting above.

  • K8N Neo4/SLI Bios Update for a Newbie

    This is the first MSI motherboard that I've bought and I love it. I've been wanting to upgrade to the latest bios, but I'm not entirely sure which one to get. I have the MSI K8N Neo4/SLI board, but when I go to the downloads section to get my bios update, I don't see my motherboard listed. I only see K8N Dimamond, K8N Platnium, and K8N SLI. http://www.msi.com.tw/program/support/bios/bos/spt_bos_list.php?kind=1&CHIP=Socket%20939%20(AMD%20K8)&ID=2 Which one of these would work on my motherboard, or would none work? If none of these work, where can I find one that will work?
    Also, how is this bios update applied? Is it applied in Windows or through a floppy disk? Are there any recommendations over one or the other?
    Any help in the matter is greatly appreciated. Thanks!

    If you fill out your specs in your sig, we can see what you have. You'll probably find your board at the US site here
    Also, no need to risk disaster in a bios flash if all is well. There are many stickys on this site re: flashing. It probably needs to be trimmed up a bit .
    There are three ways to flash the bios. One is somewhat risky (floppy), another safe (ramdrive), and the last can be unpredictable (LiveUpdate).
    I highly recommend the ramdrive or ntfs method as described here
    EDIT: another good item to have on hand before you try this is the BIOS SAVIOR
             This model fits my nf4 board

Maybe you are looking for

  • Can two iCal users edit the same published/shared calendar

    Can two iCal users (obviously different mobileMe accounts) edit the same published/shared calendar? I want to have a calendar running which we can both edit remotely but for it to be synced so we both know what each other is doing. Maybe I can share

  • HT4972 update without losing all info

    I really need to update my iphoe 4 but I don't want to lose all my music, photos and apps, how do I back them up first?

  • Is there a possibility to download files directly to the external usb drive in Firefox for Android?

    I have the Android device that support external usb hard drive, when I want to download some files via Firefox there are only two possible "places" where I can put the files - external memory or SD card. It will be nice if there would be an option to

  • Where to repair Powerbook G4 display

    I have a powerbook G4 with screen problems. the lower half of the screen is grayed out but displays to an external screen fine (i.e. projector in a lecture hall). I have taken it in to an Apple Authorized re-seller/repair but they say the machine is

  • Web Service Consumption + SM59 ( HTTPS)

    Hello ABAP Gurus, I have issue to consume web service. I am trying to consume web service form external plm server. it has https protocol. For this i tried to create rfc type G for external server but I am wondering that what i need to know to create