Link for Bios Flash protection info?

Can anyone refer me to a MSI link to determine whether PT 880 Neno MS - 7008 ver. 1.0A contains "Bios Flash Protection" option in Bios...
Thanks!

try the "search" engine?

Similar Messages

  • Can you please update the link for the flash player standalone installer?

    Can you please update the link for the flash player standalone installer?
    Link: http://fpdownload.macromedia.com/pub/flashplayer/updaters/11/flashplayer_11_plugin_debug_3 2bit.exe
    Source: http://kb2.adobe.com/de/cps/191/tn_19166.html#main_ManualInstaller
    Source: http://forums.adobe.com/thread/889580

    Dogs Key wrote:
    Source: http://kb2.adobe.com/de/cps/191/tn_19166.html#main_ManualInstaller
    That is an old document (Flash Player 10.3) that shouldn't be there anymore.  (The English document redirects to the link below.)
    The download links for the offline installers for FP 11.2 are here http://helpx.adobe.com/flash-player/kb/installation-problems-flash-player-windows.html#Ins tall_in_a_firewall_proxy_server_environment
    I have updated the download links for FP 10.3 in http://forums.adobe.com/thread/889580

  • Linking for a flash movie

    I am using the Adobe work around for the "click to activate"
    issue, and the flash movie that I want to launch is going to be
    launched from a link.
    here is what I have:
    javascript:
    function demo()
    document.write('<object
    classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
    height="200">\n');
    document.write('<param name="movie" value="demo.swf"
    />\n');
    document.write('<param name="quality" value="high"
    />\n');
    document.write('<embed
    type="application/x-shockwave-flash" src="demo.swf"
    height="200"></embed>\n');
    document.write('</object>\n');
    and the link looks like this:
    <a href="javascript:demo()" target="_blank">View Demo
    here</a>
    what am I doing wrong? the window launchs, but the movie
    won't play
    I need help with this immediately as it has to go live this
    afternoon!!!!!

    Can you show us what you have tried? Which version of Flash
    are you using? Which version of Actionscript?

  • Tips and links for using Flash to create a CD

    Hi,
    Does anyone have any tips or links to share concering the creation of a CD?  Should I use AIR or a Projector file?  Any tips are welcome : )
    Cheers.

    Do you need to access the filesystem to save files or integrate with the OS? Are you familiar with AIR at all? If you just want to put a flash presentation on a CD you don't need AIR, a standard Projector EXE will do fine.
    There's nothing special to explain besides choose if you want it to go fullscreen or not. Look into autorun.inf for Windows machines so your disc will appear with an icon (if you choose) and/or auto-start the projector when inserted.
    Otherwise it's just like building any standard flash presentation. You just burn it to a data disc.
    If you have any specific questions fire away. I've made hundreds of projector-esque multimedia CDs with flash.

  • Why no floppy for bios flash?

    The instructions for flashing the bios are confusing. On the MSI site there is a description how you can flash from floppy, but when I download the update (K8N Neo Platinum) it says don't flash from floppy. Why?
    Using XP with NT file system and not having a Windows 98 boot disk, I had no choice. So I flashed from floppy typing program name + flashfile name + enter. Then the pc wouldn't start. Got a garbled start up logo. Somehow after several flashes and turning off full screen logo, I got the pc to work. As far as I can see it works alright now. But can I trust this, or should I get a 98 boot floppy and flash once more?

    Just follow the instructions here
    Flashing the BIOS for Users using NON FAT file system as you'll see you don't strictly speaking flash from floppy but from ram drive.
    Get a boot image from BootDisc Don't get a no ramdrive 1
    when flashing I usually have a batch file
    @echo off
    if exist oldbios.bin goto old
    awfl833d.exe W7030NMS.158 oldbios.bin /py /sy /cc /cp /cd /sb /r
    goto end
    :old
    awfl833d.exe oldbios.bin /py /sn /cc /cp /cd /sb /r
    :end
    & just change the filename Of the bios each time.
    Just copy the 3 files to the ramdrive & run the bat file.
    luck

  • AMI utility for BIOS flashing?

    Ok. I have an kt3-Ultra ARU.  I want to go to the latest BIOS.  I downloaded the latest zip (ver 5.6) got my boot floppy (system is Win2k) & then ..confusion.  The readme for AMI says:
    7. When you get the A: prompt, type the following sequence:
    C:
    cd   est
    C:   est> amifl827 BIOS file
    (to save or not to save old BIOS is the user’s decision)
    where is this amifl827..I am assuming that is the flash utility (like awflsh is for award)..I got f827_38.exe That appears to be a windows only program or does it also work in a regular dos environment.  Thks in advance

    I think you should go to this page and download the BIOS file correctly. For KT3 Ultra ARU there is no BIOS file named f827_38.exe
    http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=30&NAME=MS-6380E
    Download the file, and run the file in Windows. If you use DOS to surf net and download, then download RAR and extract the EXE file.

  • I cannot find the download link for Adobe Flash Media Live Encoder

    I have been looking at the page for a while now and i cannot find the link to download the software.

    Hi chbachman,
    The link is currently broken at : https://www.adobe.com/cfusion/entitlement/index.cfm?e=fmle3
    We are working to resolve this at the earliest.

  • Link for Adobe Flash player offline installers

    Does Adobe.com have an offline installer for the latest version of Adobe Flash player?

    Please try installing from the appropriate standalone Windows installers located at the help page below. 
    Simply scroll to the bottom of the page to the "Still having problems" section and download the installer for your browser.
    Installation Problems - http://adobe.ly/YiOXAS
    Thanks,
    Chris

  • DV4-1125nr black screen on boot up looking for bios flash file taken off hp site or solution

    have black screen looking for sp41969.exe for dv4-1125nr to do blind flash.  on board diagnosis is 4 flashes (graphics controller malfunctioning) with amber sound and wireless lighting up by keypad not very good with computers so any help in dummy terms would be appreciated if you have the file i need please email to {Personal Information Removed} thanks

    HI,
    bmbrsoccer4 wrote:
    have black screen looking for sp41969.exe for dv4-1125nr to do blind flash.  on board diagnosis is 4 flashes (graphics controller malfunctioning) with amber sound and wireless lighting up by keypad not very good with computers so any help in dummy terms would be appreciated if you have the file i need please email to {Personal Information Removed} thanks
    Try the troubleshooting procedures on this HP web page.
    Best regards,
    erico
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • User guide: MSI HQ USB BIOS Flash Tool

    Guide based on USB tool v1.17c
    HOW TO properly use the MSI Forum HQ USB Flashing Tool to update your BIOS
    This user guide provides a step-by-step explanation for properly using the >>MSI Forum HQ USB Flashing Tool<< to prepare a USB Flash Drive for a safe BIOS-Flash in a pure DOS Environment. The tool itself will not perform the actual flashing operation.  It will "only" help you to get your USB Stick set up for an automated DOS flashing procedure which requires final confirmation.  (If you should run into any problems before you are prompted for final confirmation in DOS, no attempt to flash has been made yet and there is no danger of a bad flash.)
    NOTE: If you are having problems getting your USB device to boot correctly, you may need to format it correctly as the geometry data may be incorrect. You can do that by pickup option "Fix My USB key" from the Tool or by using >>> THIS <<< tool here! For future usage you can skip this step, it need to be done only once if your stick need adjustment.
    Symptoms that your USB key need a fix after booting from the USB key:
    * Error: "No bootable partition in table"
    * Blinking cursor in a top left corner and nothing happens
    * "RIVER2 MSI"
    * "Error loading operating system"
    * "Missing operating system"
    * "Disk in drive is not a bootable"
    * Booting from selected USB key is IGNORED, the other/typical OS continue to load as usual
    If still no change after using "Fix My USB key" Tool's option or HP Formatter Tool as alternative.
    Then try with different USB key, the issue is there.
    Note: Those USB keys who support "U3 Smart", this "feature" must be removed before proceed.
    Refer to followed link: http://u3.sandisk.com/launchpadremoval.htm
    Read the three notes that follow first before you move on:
    1. Note: Before you even think about flashing a different BIOS, be sure that your system is stable. If it is not stable, make it stable first. (Read >>here<<.)
    2. Note: Make sure your system meets the preconditions and system requirements mentioned below before you attempt to use the tool.
    3. Note: Do know that flashing your BIOS, be it with the help of the tool or otherwise, is done at your own risk.
    Contents of the Guide:
    0. Preconditions & System Requirements
    1. Basic Description of Functionality
    2. Installing/Starting the tool.
    3. Choosing a Preparation Method
      3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
      3.2. Method 2: Processing a BIOS File Directly
      3.3. Method 3: SureHands Live Update
      3.4. Method 4: Geometry Change
    4. Selecting the USB Flash Drive for preparation
    5. BIOS Settings, Booting & Flashing
      5.1. BIOS Settings to Check
      5.2. Booting from USB Flash Drive
      5.3. Flashing Procedure/Running MemTest86+ & CMOS-Clear
    6. FAQ: Common Problems & Solutions
    7. Version History
    0. Preconditions & System Requirements
    The main precondition for using the tool is a working & healthy Windows installation on the system that needs the BIOS flash.  The Tool is designed to work with MSI Retail Boards & Laptops only.
    Please note mainboards of other brands and OEM boards that are manufactured by MSI but sold by Medion, HP, NEC and others are not supported. If you have an OEM board that needs a BIOS update read this topic: >>OEM boards manufactured by MSI<<
    Supported Operating Systems: All current Windows Versions (32bit & 64bit, any service pack (SP)): Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, and Windows 7.
    The second requirement is that you have a fully functional USB Flash Drive that uses the FAT file system (FAT/FAT32).  NTFS is not supported. If your USB Flash Drive is using the NTFS File System, reformat it to FAT or FAT32.
    As the tool also provides a Live Update Option ("SureHands"), you'll need a working internet connection if you want to choose this method. Not all boards are supported at this point.*
    * Check section 3.3 of this guide to see if your board is currently supported by the SureHands feature.
    1. Basic Description of Functionality
    The MSI Forum HQ USB Flashing Tool will help you to easily prepare an USB flash drive for an automated BIOS flash in a pure DOS environment, which is the safest way to perform such a procedure. The tool will also allow you to run MemTest86+ in a pure DOS environment. However, the preparation of your USB Stick is done in Windows and basically includes two steps:
    (1) The device will be made bootable.
    (2) All necessary files (incl. BIOS file, actual flasher and MemTest86+ executable) and all DOS commands that are needed to flash/test memory will automatically be implemented.
    Because the tool does not reformat your USB Flash Drive*, no files that may currently be on the stick will be lost during the procedure.  Just make sure that there is still some free drive space, otherwise there will not be enough room for the files that are needed for BIOS Flashing.
    * Excluding the Geometry Change method which will destroy all data on the USB storage device.
    2. Installing/Starting the tool
    Treat the forum's USB Flashing Tool like a regular application.  Download it to and run it from your hard drive, there is no need to copy & start it from the USB Flash Drive that you want to use for flashing.  Both, the installer version and the stand-alone version, do precisely the same job.  Which of the two versions you use, is solely up to you and your preferences.  The stand-alone version can be started directly by clicking on the executable file.  The installer version will perform an installation and provide you with an entry in your start menu and a desktop shortcut to start the tool.
    When you start the tool a DOS box should open up to provide you with status messages and prompts.  Do not close that box unless you want to abort the preparation procedure!
    Please ensure that you connect the USB flash drive you wish to use before starting the Tool!
    NOTE: If you do not connect your USB storage device before starting the tool, or the tool doesn't detect it. You can still insert the drive letter, as the tool will continue as normal.
    The tool will first check, if an MSI mainboard is installed in your system and show you its model name and PCB Version in a message box. Click >OK< to continue to choose the tool's preparation method that you want to use to prepare your USB Flash Drive.
    3. Choosing a Preparation Method
    If your MSI Retail Board is properly detected and you have pressed the >OK< button in the message box, an option box will pop up that allows you to choose between three different operating modes.  The options you can choose from are more or less self-explanatory, however, read the detailed description if you are unsure how to proceed at this point:
    3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
    Official MSI BIOS-Updates that can be downloaded from the product site of your board model do usually come as .ZIP or .RAR archives that contain the actual BIOS File and the corresponding AWARD or AMI flashing utility (depending on the BIOS Type of your board).  If you have downloaded such an archive, you should choose the first method from the option box. 
    You do not need to extract the files from the BIOS archive.  The tool will ask you to point it to the archive you downloaded and automatically extract the BIOS File and the AMI or AWARD flashing utility and put it them on your USB Flash Drive.  You don't have to worry about anything else.  All you have to do is to remember where you saved the ZIP or RAR file you downloaded:
    3.2. Method 2: Processing a BIOS File Directly
    If you do not have a ZIP or RAR archive that already contains a BIOS File and the proper flashing utitility, but only the plain unpacked BIOS File, choose the second Method from the option box.  In most cases BETA BIOS Files supplied by MSI Support or shared here in the Forum do not come with the proper flashing utility.  If the MSI Forum HQ USB Flashing Tool is told to process a plain BIOS File, it will automatically check the type of BIOS File (AMI or AWARD) and then select the proper flashing utility that needs to be used.  All you need to do is point the tool to the BIOS-File that is supposed to be flashed:
    3.3. Method 3: SureHands Live Update
    "SureHands Live Update" is the third operation method you can choose from the option box.  It provides a much safer and more reliable alternative to MSI Live Update as the actual BIOS Flash is performed in a pure DOS environment as well.  If you decide to use this option, you do not to supply the tool with a BIOS-Archive or a BIOS-File.
    Not all MSI Retail Boards are currently supported.  With every update of the USB Flashing Tool more boards will be added.  At present, you can use the "SureHands" Live Update method with the following boards only (the list will be updated regularly):
    AMD based boards:
    K8N Neo4-F (MS-7125, PCB 3.0)
    K8NGM2-FID (MS-7207, PCB 2.0)
    K8N Diamond Plus (MS-7220, PCB 1.0)
    K8N Neo3 (MS-7135, PCB 1.0 & 2.0)
    K9A Platinum (MS-7280, PCB 1.0)
    K9A2 Platinum (MS-7376, PCB 1.0)
    K9A2 CF-F (MS-7388, PCB 1.0)
    K9N Neo-F (MS-7260, PCB 1.0 & 2.0)
    K9VGM-V (MS-7253, PCB1.0)
    K9N2GM-F V2 (MS-7509, PCB 1.0)
    K9N Neo V2 / V3 (MS-7369, PCB 1.1)
    K9N Platinum & K9N SLI Platinum (MS-7250, PCB1.0)
    K9N2 Diamond (MS-7375, PCB 1.1)
    K9N2 SLI Platinum (MS-7374, PCB 1.1)
    K9N2 Zilent (MS-7374, PCB 1.1)
    K9N2 Neo-F (MS-7511, PCB 1.1)
    DKA790GX Platinum (MS-7550, PCB 1.1)
    790FX-GD70 (MS-7577, PCB 1.0)
    790GX-G65 (MS-7576, PCB 1.0)
    Intel based boards
    HydroGenX48C & X48C Platinum (MS-7353, PCB 3.0)
    X48 Platinum (MS-7353, PCB 1.0)
    X38 Diamond Plus
    X38 Diamond (MS-7353, PCB 1.0)
    X38 Platinum (MS-7353, PCB 1.0)
    EFINITY-FP (MS-7395(E), PCB 1.0)
    P35 Neo Combo-F (MS-7365, PCB 1.0)
    P35 Neo2 Series (MS-7345, PCB 1.1)
    P35 Platinum (MS-7345, PCB 1.1)
    P35 Neo-F (MS-7360, PCB 1.0)
    G33 Platinum (MS-7345, PCB 1.1 & PCB 1.2)
    P965 Platinum (MS-7238, PCB 1.1)
    975X Platinum PowerUp Edition (MS-7246, PCB 2.1)
    865PE Neo2-P Platinum Edition (MS-6728, PCB 2.0C)
    P7N SLI Platinum (MS-7380, PCB 1.0)
    P7N2 Diamond (MS-7523 PCB 1.0)
    P7N Diamond (MS-7510, PCB 1.0)
    P7N SLI Platinum (MS-7380, PCB 1.0)
    P6N Diamond (MS-7320, PCB 1.0)
    P6N SLI Platinum (MS-7350, PCB 1.0)
    P6N SLI-FI (MS-7350 PCB 2.0)
    P6N SLI V2 (MS-7346 PCB 1.0)
    ECLIPSE SLI (MS-7520, PCB 1.0)
    ECLIPSE Plus (MS-7566, PCB 1.0)
    P35 Neo3-F (MS-7395, PCB 1.0)
    After selecting "SureHands" from the option box, the tool will automatically check for all available official BIOS-Versions for your mainboard.  It will also look for the latest available BETA BIOS Version for you board and save that information in a TXT-File on your Desktop:
    Note: The SureHands option will not provide you with the latest BETA BIOS, it will only provide the information.
    When the tool is done scanning for official BIOS releases for your board, it will give you the possibility to manually choose the BIOS Version you want to flash.  SureHands Live Update will not automatically select the latest version and use it for flashing, it will give you the chance of choosing between all available official BIOS releases that are available:
    Note that the "May not exist" comment that appears behind some versions does not mean that the BIOS does not exist.  If you know the latest BIOS for your board is e.g. v1.8, SureHands will retrieve it even though there may be such a comment.  That message is part of a prediction feature that tries to determine future BIOS Releases.  If a BIOS version that was predicted by the SureHands feature is not available yet, the tool will tell you if it cannot retrieve the files and ask you to select an earlier version.
    3.4 Geometry Change
    If the tool fails to make your USB storage device bootable then you will need to use this mode. It will make your drive bootable, select it:
    Select your drive then let the tool do it's business.
    Once the process is complete, run the tool again via method 1, 2 or 3, restart your computer and try booting from the USB storage device again.
    NOTE: This method will destroy ALL data on the USB storage device!
    NOTE: This method is available in v1.17 and beyond.
    4. Selecting the USB Flash Drive for preparation
    When you have chosen one of the three methods from the option list and pointed the tool at the corresponding archive, BIOS File or selected the desired BIOS Version from the list in case you chose to use SureHands Live Update, the MSI Forum HQ USB Flashing Tool will prompt you to enter the drive letter of the USB Flash Drive you want to use for flashing:
    Note that certain drive letters are reserved and will therefore not be accepted by the tool (currently A:, B: and C:). If you are sure you have connected an USB Flash Drive to the system that works properly but it does not appear in the table that appears in the DOS box, enter the corresponding drive letter anyway and see if the tool accepts it.  This can happen in rare cases, but it is usually no problem.
    The tool will check the selected drive and will provide you with status messages.  If everything is okay, the message should look like this:
    The tool will attempt to make the device bootable and automatically write all files that are needed for flashing to the drive to prepare it for flashing.  If the procedure was successful, you will get the following message in the DOS box:
    5. BIOS-Settings, Booting & Flashing
    If the Tool has prepared your drive for booting & flashing, no BIOS flash attempt has been made yet. Only the preparation process. In order to initiate the flashing procedure, you have to restart your system and make it boot from the USB Flash drive. Before you move on to do that, enter the BIOS Setup and check a few options:
    5.1. BIOS Settings to Check
    Check USB-related Options in BIOS:
    - USB Controller
    - USB 2.0 Controller
    - USB Legacy Support
    - USB Storage Support
    - Boot from other devices
    - etc.
    Not all of these options may be found in BIOS and the precise name may vary as well.  Just make sure you checked for such options and that they are enabled (if present).
    Another option you should check for is "Boot Sector Protection".  If such an option is present in your BIOS, make sure it is disabled because it may make a BIOS Flash impossible.
    @all Overclockers: In case your system is currently overclocked, make sure you roll back to default clock and voltage settings before you attempt to start the flashing procedure. Otherwise you increase the risk of an unsuccesful flash, and you most probably don't want something like that to happen.
    5.2. Booting from USB Flash Drive
    To boot from your USB drive you can either change the boot sequence in BIOS accordingly or just press F11 during POST* to get access to the BIOS Boot Menu.  From here, you can select you drive directly without having to adjust the boot sequence in BIOS.  Note that your USB Flash Drive may be listed as a hard drive (if you choose that entry you will get another list to choose from).
    * Not all mainboards use F11, for the boot menu. If F11 fails for you, please consult your manual for the correct key.
    Note: If you have problems booting from your drive, look at the FAQ-Section of this guide and see if any of the tips resolve the issue.
    5.3. Flashing Procedure/Running MemTest86+
    As soon as the system boots from the drive, DOS will be loaded and you will be displayed with two options. One option will start MemTest86+, the other will begin the flashing procedure. If no choice is made, MemTest86+ will automatically start.
    The flashing procedure will automatically be initiated from there.  You will see status messages on the screen that will supply you with information and also prompt you for final confirmation for the actual BIOS-Flash.  A backup of you current BIOS will automatically be saved to a file on the drive (backup.bin) before the flashing actually starts.  You do not need to enter any commands in DOS.  All you have to do is acknowledge the information on the screen by pressing a key.
    The flash itself will only take a couple of seconds (20-30s at the most).  If the flashing is successfully completed, shutdown the system and clear CMOS with main A/C power cable removed from PSU.  Read the >>Clear CMOS Guide<< for further information. 
    After clearing CMOS you have completed the BIOS-Flash. 
    Guide created by Jack The Newbie and the forum team

    Version updated to 1.18x:
    * Mode 3 Sure Hands, Live Update:
    - Removed beta BIOS query check[global]
    - Fixed issue K9N2 Diamond unable to be detected as supported unit if onboard is installed BIOS version 2.4,
     add dynamic detection for future versions.
    - Fixed issue 790FX-GD70 unable to be detected as supported unit and add dynamic detection for future versions.
    - Fixed issue 790GX-G65 unable to be detected as supported unit and add dynamic detection for future versions.
    - Add support for 785G-E65, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
    - Add support for 785G-E53, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
    - Add support for 790GX-G65 Winki ED, prediction BIOS range 2.1 - 2.A
    - Fixed issue P7N Diamond unable to be detected as supported unit if onboard BIOS installed is 1.3 and above,
     add dynamic detection for future versions.
    - Add support for K9A2 Neo2, prediction BIOS range 7.4 - 7.D
    - Add support for 790XT-G45, prediction BIOS range 2.2 - 2.B
    - Add support for 770T-C45, prediction BIOS range 8.4 - 8.D
    - Add support for 770T-C35, prediction BIOS range 8.4 - 8.D
    - Fixed issue K9A2 Platinum[V1,V2] unable to be detected as supported unit if onboard BIOS installed is 1.9,
     add dynamic detection for future versions, prediction BIOS range extended to 1.F0
    - 790GX-G65 board prediction BIOS range extended to ver: 1.D0
    - 790GX-G65 board update bios base ver from 1.xx to 4.xx [following new msi rule for this board jumping from 1.xx to 4.xx]
    - Add support for 770-C35|C45 boards [p1] BIOS range 1.40 - 1.D0
    - Add support for 770-G45 board [p2] BIOS range A10 - AA0
    * Add "Exit" option to navigation screen
    * Update version info related to boot part
    * Update boot part to handle newest features
    * Modify Self update sequence of Installer version
    * Update internal version check ID
    * Mode 4 minor update
    * Build and add new Tool's module for newest features
    * W32 Tool's exit time part decreased by 10 seconds
    * On received OS reboot user request, time delay before execution decreased by 15 seconds
    * Update EC decoder
    * Update start-up information screen
    * Auto store start-up detected information to user's desktop ==> [MSIHQ_INFO.TXT]
    Details:
    Easy to show machine information on request, instead write down from the screen manually, now just copy/paste can be used from MSIHQ_INFO.TXT
    User can check and compare information before and after the BIOS update
    Also usefull if didn't remember what was his original BIOS or EC versions before the update, Tool will auto store it there.
    And easy can be checked if needs. E.g Tool's log file of each Tool's execution, each report will include date and time as well.
    F.A.Q example:
    Q: I flashed BIOS on my notebook and now it doesn't work properly.. And i don't remember what was my old BIOS version.. What can i do?
    A: Take a look in MSIHQ_INFO.TXT at your desktop, there is auto recorded your detailed information about your notebook before the BIOS update.
    So you can easy find what was your original BIOS & EC versions.
    Is it OEM one or not, and the exact original BIOS & EC versions.
    So you can roll back easy or if crossflashing were done to reflash to correct versions.
    Example question:[this board now use 4.xx bios, but don't have time to make a new images.]
    It's just example, do not mean that this BIOS used in the example is bad. But generally often can need to roll back to older version.
    Or to use Sure Hands because[The BIOS is N/A for manual download, By SureHands no need to browse/search/download and point to the BIOS version, also eliminate any chances to pickup the wrong BIOS, and not at last its more quickly[save a time]]
    Q: I flashed my BIOS via MSI Live Update, but the new BIOS has an issues.
        How i can roll back to my old BIOS version?
        The MSI LiveUpdate can only update to the latest BIOS version, which is not good for me.
        And i can't download my old BIOS version manually... Because "This BIOS can only update via Live Update function"
        http://eu.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1739
        How i can re-flash to my original BIOS version and from where can i get it?
    A: Run >>Use the MSI HQ Forum USB flasher<<,
    then choose Mode 3 [Live Update{aka SureHands}]:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:09:45,15
    Mainboard:  790GX-G65 (MS-7576)       
    PCB Version:  1.0
    BIOS Version: V1.3
    BIOS Date:  05/08/2009
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:22:38,42
    Mainboard:  790GX-G65 (MS-7576)       
    PCB Version:  1.0
    BIOS Version: V1.6
    BIOS Date:  11/30/2009
    Then choose your old BIOS version from the list:
    The followed image used below is a sample from Eclipse board,[no time to make accurate image] but will look similar for others boards too:
    In a list will be noticed that there is a future BIOS versions.
    Some of them will be not released yet. If you pick some of those the Tool will note you:
    It's a part of Tool's BIOS prediction system called "Crystal Ball", when MSI release a future BIOSes for your board,
    Tool can find them immediately. By that way the Tool no need to be updated to be actual in each moment
    * Add new feature "True BIOS Version Ready"
    - Updated Mode 1
    - Updated Mode 2
    - Updated Mode 3
    Details:
    Q: What "True BIOS Version Ready" means? Does the Tool show the wrong BIOS version until now? 
    A: Of course not, the Tool always show accurate info.
    The same as CPU-Z/Everest of whatever other Tool.
    However Tool also detect EC-FW versions for notebooks:
    The "True BIOS Version Ready" Tool's feature is aimed to eliminate user's mass confusion about MSI BIOS versions.
    And not only users are confused, but MSI's Live Update is confused too... which confuse users even more..
    Few typical real examples of confusion:
    "K9A2 CF wont flash to Bios v. 1.A !!!" 
    Quote from: Fingon on 25-October-09, 16:53:15
    Hi MSI,
    I have a problem. I have bought a new processor: AMD Phenom II x545. I looked on the support page of my MB (MSI K9A2 CF) and there the CPU is supported from the bios version 1.A. So I wanted to flash the Bios the the newest version (1.A). I used the MSI live update 4 program to flash it via windows mode. But everytime it boots it writes "CMOS checksum BAD", then I hit F1 to Bios and I see the version of my BIOS fell to the oldest version 1.1. Then I tried to flash it thru Flash disc (with boot files) and dos mod. The result is the same. I can flash my MB to version 1.8 but when I try the 1.A it wont flash it and my Bios fell to the oldest version (1.1). I realised that the exe files in version 1.1-1.8 are the same (afud412.exe) but the exe file in 1.A is different (afud4310.exe).
    My questions are:
    1) How to flash my MB to the version 1.A ?
    2) Is version 1.A really needed for AMD Phenom II x545? I guess yes, because CPU was avaible in July 2009 and the bios 1.A went out in June 2009. I am able to flash it only to version 1.8 (december 2008).
    Thank you for any help!!
    EDIT: After reading this topic: https://forum-en.msi.com/index.php?topic=129204.0 I realised I have the VERSION 1 of this board (I purchased it right after the launch of the MB (November 2007). It means it doesnt support CPU over 95W, but my Phenpom II x545 has only 80W. I still cant update Bios to the 1.A version.
    So my third question is:
    3) Is the Bios update 1.A only for version 2 of this MB?
    Thx for replies!
    Quote from: Jack t.N. on 25-October-09, 17:16:16
    A CMOS Checksum error is normal and expected after a BIOS Flash and/or a CMOS Clear.  The fact that this message appears, shows, that there was actually something programmed to the chip.
    If you haven't done that yet, please clear CMOS with the main A/C power cable removed from your PSU and load "Optimized Defaults" in BIOS Setup.
    The BIOS Version should be shown on the POST Status Screen and there should be a date behind it.  Please check the BIOS Date and write it down:
    Are you absolutely and entirely sure that what you see is "1.1" and not "1.10"?  Because v1.A0 is actually just the hexadecimal notation for v1."10" (one dot ten).  The hexadecimal notation is only used in the BIOS File Ending.  Once flashed, the BIOS will not identify itself in hexadecimal notation but in decimal code (which means you will never see "v1.A0" after the flash but "v1.10" instead.
    Here is a piece of well-meant advice for now and the future:  MSI Live Update should be avoided under all circumstances when it comes to BIOS Updates and/or information retrieval regarding your current BIOS Version.  Why?  Because this tool is stupid and one of there most risky applications for performing a BIOS Flash.  Please uninstall it completely.
    Why do I call it stupid?  I call it stupid because it does not differentiate between hexadecimal notation and decimal notation.  It will show you that "v1.A0" is available.  The it will flash it, if you allow it to do so.  Of course, a v1.A0 Version will always come out as "v1.10" (one dot ten).  When you re-run MSI Live Update it will not recognize that v1.A0=v1.10 and tell you again that there is a newer version available (1.A0, which, again, is the same as v1.10, which was just properly flashed).
    I believe that the update went just fine, that you are currently using v1.A0=v1.10 and that MSI Live Update is actually just creating a pseudo-problem which is currently confusing you.  The pseudo-problem will immediately be out of the world, if you uninstall MSI Live Update and rely on the BIOS ID String as it appears on the POST Status Screen (this includes the date shown there).
    If a BIOS Update should ever be necessary again, please make sure that you won't use MSI Live Update but >>Use the MSI HQ Forum USB flasher<< instead.
    Quote from: Fingon on 25-October-09, 18:03:44
    Thank you for the quick reply!!
    Thats exactly what I have JUST found in this post by Svet: https://forum-en.msi.com/index.php?topic=127672.msg974800#msg974800
    Yes it is 1.10 of course!! I didnt know that 1.10 = 1.A0 ! Thank you for the reply. Then the MSI live update 4 program is dump that he wanted from me another update of Bios.
    So thank you! Problem is solved. 
    Edit: Yes, because of MSI live update I learned how to flash bios via flash disc. :-) But I was still confused by that 1.10 and of course by program saying me I should update again.. :-P
    Quote from: Lostsoul777 on 14-August-09, 05:46:25
    I had the same problem with 1.90 bios, so i updated to 1A, i just want to know why Bios Version says: v.1.10 instead v.1A?
    Quote from: LinuxGuy on 29-December-09, 01:17:45
    My computer does not have a floppy drive.  How do I update the BIOS?  (I tried the online utility 3 times.  It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.  So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).  So either the BIOS is getting updated, but the online tool is not recognizing this or it's not getting updated.  Either way, I would like to manually flash it in DOS.  Is it safe to burn the setup files to CD and boot from CD into DOS?
    That's the same BIOS version... Just the "MSI Live Updater" is not very smart...
    H.A=H.10=17.A=17.10 [A=10, H=17], the last "0" suffix in H.A0 means its official version.
    Quote
    I tried the online utility 3 times.  It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.
    So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).
    So ignore this MSI Live Updater's no sense, and stop flashing your BIOS. You already have the latest version installed.
    The Tool now will detect and shows BIOS versions alias when the MSI BIOS version is known with more than one name.
    So no more flashing and flashing and flashing to the same version because of MSI LiveUpdate suggest again BIOS update...
    Also no more confusion:
    "What's my BIOS version?" -> I flashed my BIOS to 1.A0 [A7520IMS.1A0], but BIOS says its 1.10
    And MSI Live Update also says that i have 1.10 and 1.A0 is available and i should update it. I flashed it again, but its still 1.10?
    What's going on?
    Just run the MSIHQ USB Flash Tool and will show you all that you need to know
    Examples[with real/accurate info]:
    MSI Eclipse:
    BIOS version 1.9:
    BIOS version 1.10:[Tool now shows both BIOS versions alias]
    Report stored respective in MSIHQ_INFO.TXT at user's desktop:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:30:55,34
    Mainboard:  Eclipse SLI (MS-7520)
    PCB Version:  1.0
    BIOS Version: V1.9
    BIOS Date:  09/22/2009
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:37:25,66
    Mainboard:  Eclipse SLI (MS-7520)
    PCB Version:  1.0
    BIOS Version: V1.A (aka Version: V1.10)
    BIOS Date:  10/27/2009
    More examples =>K9N6SGM-V / K9N6PGM-FI / K9N6PGM-F :
    More examples =>945GCM5-F V2 (FSB 1333) :
    Report stored respective in MSIHQ_INFO.TXT at user's desktop:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:47:34,35
    Mainboard:  MS-7267
    PCB Version:  4.0
    BIOS Version: VH.9 (aka Version: V17.9)
    BIOS Date:  11/20/2008
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:52:46,26
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VH.A (aka Version: V17.10)
    BIOS Date:  06/02/2009
    More examples =>780GT-E63 [N/A at MSI web yet] :
    For MSI Notebooks such decoding isn't need, examples:
    * Add new feature "Triple BIOS flash Recovery Ready"
    - Updated Mode 1
    - Updated Mode 2
    - Updated Mode 3
    Details:
    The feature include 3 auto prepared BIOS backups for followed purpose:
    * Internal BIOS recovery:
     - In a failure case Tool perform auto flash recovery [3 attempts, check for success after each and stop flashing if successful] before give control to BK_IO2, notice users about results and give control for manual attempts[if need]. [This a case if system isn't lockup/reboot, if bad flash occur]
     - This mode also have own store up to 5 backups[+1, the last saved copy is always backup.bin, if there was older one they become backup1.bin .. till 5]
    * BIOS backup stored as AMIBOOT.ROM [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
    * BIOS backup detected and stored for M-Flash style boot/recovery [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
    Performing test simulations with random generated BIOS versions[including betas] for M-Flash boot/recovery style, some examples:
    Copy/paste Tool log file:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:00:53,46
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VD.XB2 (aka Version: V13.33B2)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created  ==> A7267IMS.DX2 
    Where:
    * V13.33B2 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VD.XB2 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.DX2 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:12:23,95
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VK.VB7 (aka Version: V20.31B7)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.KV7 
    Where:
    * V20.31B7 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VK.VB7 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.KV7 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:18:34,46
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V3.9
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.390 
    Where:
    * V3.9 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
    * A7267IMS.390 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:22:24,04
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V8.1B9
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.819 
    Where:
    * V8.1B9==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
    * A7267IMS.819  ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:25:38,51
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V4.E (aka Version: V4.14)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.4E0 
    Where:
    * V4.14 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * V4.E ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.4E0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:28:16,62
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V1.BB1 (aka Version: V1.11B1)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.1B1 
    Where:
    * V1.11B1 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * V1.BB1 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.1B1 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:31:57,78
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VI.FB5 (aka Version: V18.15B5)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.IF5 
    Where:
    * V18.15B5 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VI.FB5 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.IF5 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:36:02,40
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V7.O (aka Version: V7.24)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.7O0 
    Where:
    * V7.24 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * V7.O ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.7O0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:39:11,84
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VC.8B6 (aka Version: V12.8B6)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.C86 
    Where:
    * V12.8B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VC.8B6 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.C86 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:49:38,46
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VG.PB6 (aka Version: V16.25B6)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.GP6 
    Where:
    * V16.25B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VG.PB6 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.GP6 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:53:17,26
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VU.H (aka Version: V30.17)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.UH0 
    Where:
    * V30.17 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VU.H ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.UH0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]

  • Might be a dumb question...bios flashing...

    I created the DOS boot disk, rebooted, but I can't get to C drive...only A
    I went through first 6 letters and none were correct.
    I followed these directions;
    When you get the A:\ prompt, type the following sequence:
    C: <enter> (I get an unspecified drive notice)
    cd\test <enter>
    C:\test> awdfl783m BIOS file

    Get the win98 bootdisk from www.bootdisk.com , and follow the instructions for bios flashing with a ntfs-formatted system :
    (the RAM-drive is important) (all out of the official MSI-document from the zipped bios-file)
    (I tried it with an official 98bootdisk first but had no ram-drive, the 1 from bootdisk.com has  :D )
    Flashing the BIOS for Non-FAT file system (Thanks to Forum Moderator Assaf for his valuable contribution)
    1.Check your BIOS for BIOS FLASH DISABLED and ENABLE it, some boards have this function.For Example:
    K7T266 Pro (MS-6380) -BIOS setup/chipset setup/BIOS protection/disabled
    2.Know Your model number
    a. Open your case and look for the MS-XXXX number on the motherboard between the PCI slots, also check the version number that is written there as well. (some motherboards are named like K7T Turbo, make sure you have the right version number)
    b. Boot up your system & take a look at the top left screen during POST, you should see something like "A6380MS v1.7 122101" This means the board is MS-6380 with BIOS version 1.7
    Hint: Many systems are clearing this message very fast, the bios version is then unreadable, you can either press “PAUSE” or disable the “Quick Boot” in the BIOS setup.
    3.Download the BIOS that matches your motherboard AND version number (some motherboards are named like K7T Turbo, make sure you have the right version number). BIOS can be found according to the CPU type of your board like if your CPU is Intel P4 478 type then look here
    <http://www.msi.com.tw/support/bios/socket_478.php>
    if you cannot find the BIOS that matches your board, try here <http://www.msi.com.tw/support/bios/more.php>
    4.Extract the file you have downloaded to a floppy (not the win ME/98 startup floppy) by double clocking the file in windows mode and supplying the path a:\
    5.Boot the computer using a windows ME or windows 98 startup disk. It must be one of these! A plain boot disk will not be good enogh.
    If you do not have Windows ME or 98 to create the floppy you can make one on a friend's computer.
    6.When boot is done there will be a message on the screen showing :"Diagnostic tools were successfully loaded to drive" followed by a single letter.
    This letter is the leter assigned to the RAMDRIVE. This RAMDRIVE is a virtual drive in the system memory and can be accessed and controlled like any other drive with DOS commands such as:
    MD - Make Directory
    Copy - copy a file
    Deleate - Deleate a file
    There is one important difference which is that being in the system memory this drive is wiped once the computer is restarted or shut down.
    7.Replace the startup floppy with the one containing the flash utility and bios ROM files previously extracted in windows.
    8.Copy the 2 files to the RAMDRIVE by using the DOS command copy.
    Here is an example, in this example the flash utility is AWFL814B.EXE ,the ROM file is  w6373nms.220  and the RAMDRIVE letter assignment is D
    copy awfl814b.exe d:\
    copy w6337nms.220 d:\
    9.Change the current working directory to the RAMDRIVE root directory, with the example case of the RAMDRIVE being drive D this is done by simply done with the command d:
    10.Execute the flash utility with the ROM file as a command line argument, with this example:
    awfl814b w6373nms.220
    If you wish to save the current bios you must specify the full path a:\filename. Specifying only a file name will save the bios to the RAMDRIVE which will be wiped after restarting the computer and the file will not be saved.
    a:\bios.old is an example of the correct way to save the bios.
    11.Reboot your system when prompted
    12. If your system doesn't boot after you flashed, please refer to the BIOS recovery method as described

  • MSI Gaming 5 Z97 00 Error Code after Bios Flash

    Was using a USB for bios flash through the uefi bios. I chose ME flash, and it flashed ME then rebooted and then flashed the bios and then it finally rebooted but to a black screen. After a few minutes, I restart the computer and it has an 00 error code now. I removed the graphics card and cleared the CMOS.

    Quote from: HighMans on 05-October-14, 04:04:37
    I flipped the PSU off, I always do that.
    remove the power cord itself from the electrical outlet
    after that proceed with >>Clear CMOS Guide<<
    Quote
    PSU:   
    12v rail Rating of listed PSU: 384W
    CPU: G3258
    Memory: Corsair 8GB XMS
    SSD/ HDD: Seagate 1TB and a PNY SSD
    CPU COOLER: Coolermaster Hyper Plus 212
    Raid Card: N/A
    Sound Card: N/A
    Any Additional hardware plugged into your system: N/A
    OC: (Yes / No) Yes
    Operating System: Windows 8.1
    Quote
    PSU:   
    12v rail Rating of listed PSU: 384W
    PSU brand and exact model?
    Quote
    Memory: Corsair 8GB XMS
    how many memory sticks?
    exact models?
    Quote
    SSD/ HDD: Seagate 1TB and a PNY SSD
    have you tried to disconnect them both?
    Quote
    OC: (Yes / No) Yes
    that's not good idea to flash your BIOS when the system is OCed

  • Re: Bios Flash Upgrade For NB200 and NB205 Series Posted For Download

    For those of you who are interested, the bios flash can be downloaded and installed. Download, extract the files, and read the readme file to learn how to install the flash update.
    Here is the link: http://www.csd.toshiba.com/cgi-bin/tais/support/jsp/home.jsp?nav=Download
    Message was edited by: Edmund Dorf

    > {quote:title=jnjroach wrote:}{quote}
    > Used this utility...
    >
    > http://www.lowfps.com/creating-a-bootable-usb-thumb-drive
    >
    > Then copied the bootable files from the floppy install of BIOS to the thumb drive and then rebooted...
    >
    > Jeff
    Thanks for the info Jeff, it led me in the right direction.
    Quick summary: Linux users will need to get the DOS boot floppy image from Toshiba's US website.
    Details:
    It turns out that there is no floppy install in the BIOS update file that is provided by Toshiba Europe (I have an NB-200 PLL20E bought in the UK), which means no DOS-based flash utility.
    This is the update file from Toshiba Europe:
    http://support1.toshiba-tro.de/tedd-files2/0/bios-20090925081640.zip
    Unzip it to get BIOS_V160_Win.exe with the following md5:
    de1cc03a0c732c61638697c8df72d582 BIOS_V160_Win.exe
    The .exe file is actually a 7zip self-extract archive:
    % 7z x BIOS_V160_Win.exe
    Extracting go.bat
    Extracting avaa160a.rom
    Extracting setup.exe
    The BIOS is in avaa160a.rom. The setup.exe file is another self-extracting installer thing that contains winphlash.
    Now, the US website has an even larger number of models for the NB200. I tried a bunch of them and they all point to the same file for the 1.60 BIOS:
    http://cdgenp01.csd.toshiba.com/content/support/downloads/ll20v160.exe
    This file is a self-extracting ZIP, and it contains _the exact same_ .exe that is found in the EU version, but under a different name:
    de1cc03a0c732c61638697c8df72d582 buffalo10a_10b_10c_bios_v160_win.exe
    Fortunately, it also contains a bootable CD image (ll20v160.iso) and a floppy image. The latter is named 2355d160.ima and can be found in the root directory of the CD image, as well as inside the 2355d160.exe self-extracting ZIP file.
    In addition, the US update file comes with a nice readme and changelog. I suppose EU users are all assumed to use Windows and not be overly inquisitive about BIOS revision history.
    A peek inside the floppy image shows the usual files you'd expect to find on a boot floppy, plus the DOS flasher (phlash16.exe) and BIOS image (avaa160a.rom). The latter is of course identical to the one found in the EU version. However, even if it weren't, one would simply loop-mount the floppy image R/W and copy the correct .rom to it. A bootable ISO is easily created from a boot floppy.
    Either of the two images can be booted off a USB flash drive (this is left as an exercise for the reader :-) ). I made a bootloader (grub2) entry for the floppy image as I had an existing setup for this.
    Finally, to summmarise the whole process for Unix users:
    wget http://cdgenp01.csd.toshiba.com/content/support/downloads/ll20v160.exe
    unzip ll20v160.exe 2355d160.exe
    unzip 2355d160.exe
    <boot floppy image 2355d160.ima however you like>
    /-sb.

  • Web link for id plate for flash web galleries

    I've created a number of html galleries, where you have the ability to make your id plate a link- very useful as this can link back to a main page with links to other galleries. This is pretty straightforward for HTML:
    My problem, however, is that the flash galleries do not have this option for some reason! I don't see a way to make the id plate into a link for flash galleries under the web export...
    I don't even mind going back after exporting to my local computer and adding in a link... but I am not proficent with flash, and don't know where to add it.... the index.html that is created as the home page of the web gallery didn't include anything I could edit... I guess flash buries things a bit and its harder to edit it manually....
    Any help in allowing a link to be made from the id plate for flash galleries would be greatly appreciated...
    thanks,
    Erik

    Erik,
    I have the same question/problem. I do need the second link or ability to enlarge one of the posed image. Have you found the answer?
    Leo
    [email protected]

  • DOS BIOS flash for MP Miini 1000, Vivienne Tam (HP Mini 1020TU) ?

    Hi,
    I have a gorgeous Vivienne Tam HP Mini 1000 (Mini 1020TU) that will not boot windows. I can access the BIOS settings and I can boot to a DOS USB stick.
    So the normal BIOS flash is out of my reach. I need to do it from DOS. Yet though HP gives the instructions on how to do this, it doesn't seem to offer the actual ROM file or its loader.
    Is there any way out of this dilemma?
    Thanks,
    Paul

    Hello @paul1149,
    I have read your post on how you are looking to flash the BIOS on your notebook computer, and I would be happy to assist you in this matter!
    Based on the information you have provided in your post, I recommend contacting our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region.
    http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
    I hope this helps!
    Regards  
    MechPilot
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

Maybe you are looking for

  • I can no longer print photos from iPhoto.

    When I try to print photos from iPhoto, I get the error message:  There were no themes located. Until at least one theme has been installed, this feature will be unavailable. The solution offered by iPhoto help is ridiculous as it assumes that you ca

  • BC data form wizard error

    The wizard generated for QueryInfo "OBJECT_NO as \"Project\"," + for the DetailIter But project is the 1st column of the primary key and object_no is the third. Project was not one of the columns being displayed. Object_no is the first column display

  • HT1338 How can I formate  my MacBook Pro??

    How to reformat MacBook Pro?

  • XML-24521 Element not completed in oracle bpel - BPEL Test Case

    Hi All I created a baseline test for my bpel process which reads an image from one server and does ftp to another server. But this baseline test invalidates and giving following 2 errors Error(40,35): <Line 40, Column 35>: XML-24521: (Error) Element

  • Naming new layer in Illustrator CS4 js

    Hi, I have this piece of code and it works, but it doesn't assign the name to the layer (green text). Could you please see what I am doing wrong: var myLayer = app.activeDocument.layers.add("Guides"); var myLeftGuide = myLayer.pathItems.add(); myLeft