Stupid Move on Promise Bios Flash
I foolishly tried to get the last bit of performance out of my Promise controller by obtaining a bios flash from the Promise website. I am flashed to a bios that probably doesn't go with this board, and although it works, its not smoking like it used to (that was a good thing). Anyone help me get my Promise bios back to what it was or back to spec if I promise (no pun intended) not to do it again.
My bios rev overall is 1.2 and a full mobo bios flash doesn't change anything.
The Promise bios is 1.0.1.34.
tia,
Bill
Ok, are you sure you really want to go from a working bios, to the unknown? If so, copy the two files you outlined to the "ramdrive", copy a:file to be copied c:,assuming the ramdrive letter it gave you is c. Change to drive c, c:\, now you have a c prompt. type in "adsfi707 a6758ims.132", this is the exact command line you need, and you need to do it from the c prompt of the ramdrive after copying the two files to it. My current experience tells me to pass along this, DONT FLASH YOUR BIOS IF IT WORKS FINE FOR THE MOMENT!!!! I'm just talking about normal stability. Overclocking right now is too wierd for this board, till MSI pulls their collective heads out, and fixes this bios issue once and for all.
Similar Messages
-
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 teamVersion 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] -
Can't Enable XMP after BIOS flash to V1.4 on P55-GD85
I didn't put this in the BIOS section because while the BIOS is involved, I don't think it's necessarily a BIOS issue. However, if it should go there please move it.
While not new to computers by any stretch I committed the cardinal sin of updating my BIOS when I didn't absolutely have to. While their were some issues I'd hoped would be fixed with a new BIOS revision, they weren't critical.
I have a i7 860 Lynnfield system running Win 7 Home Premium 64 with a MSI P55-GD85 mobo which has been running fine since being built in March of this year. This was the first BIOS flash since I've built the system. The system came with either V1.0 or V1.1 (I think it was V1.1). I checked using Live Update (yes, I now know this is bad) and found there had been several udpates since my current version. I went ahead and used Live Update to flash the BIOS (yes, I know...not a good idea). Contrary to the horror stories the flash itself went fine. I watched it flash the BIOS and everything verified fine. Of course after the update I had to reset my BIOS settings to get the system to run which went fine. The problem is that the one thing I can't do is enable the XMP option for the memory without the system crashing. If I enable this option the system will POST and then do a memory dump before ever getting to the desktop. Without turning this option on I can't take full advantage of my RAM. I am running G.SKILL Trident 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 2000 (PC3 16000) which are XMP compliant and ran without issue up until the BIOS update. It is possible that there is some other setting that I didn't reset after the BIOS change to allow this to work that I am missing. I know I did a bunch of tweaking and changing of settings trying to get things to run correctly when I first built the system. I've gone over and over the BIOS and can't find anything else to try to get me to allow to enable the XMP option without crashing. By simply enabling that option my system would normally run stable at about 3.6-3.7GHz.
Does anyone have any ideas as to why this might be happening or what I can do about it? About the only other thing I can think of is to reflash the BIOS back to a previous version to see if that helps. I am sure there is something I am missing as there is no reason the BIOS shouldn't allow the XMP feature to be enabled without crashing. Any help would be most appreciated. Thanks.Have you try to increase your RAM voltage to 1.55v ~1.6v?
-
Controlling Captivate movies from a parent Flash movie
Hello, i am in the works of onverting my old AS2 code, for controlling Captivate movies lodaded into a Flash container, over to AS3 becasue of the transition to Captivate 5. There were some weird issues in AS2 and Captivate 3 which i fortunately vere able to solve when i first made this container. Now i am getting weird and unpredictable results when trying to set the appropriate variables in the Captivate move. The main culprit is: rdcmndRewindAndStop, it does indeed rewind the movie, but... it starts playing again... Could anyone be so kind to give me the reason why or better even provide me with a solution to this unneeded change, its quite annoying, and no rdcmndPause does not help, not before rdcmndRewindAndStop or after, the movie is happily trottling along...
sincerely
Frustrated developer with a bloody short deadlineHello and thanks for replying, yes it worked! But... we have to manually edit 40+ files to make this stupid thing to work... Do you know if there is any way i can put those scripts in a flash object, or better even modify the movie from the parent container? This is making our production process way longer than is affordable tbh, a single project consists usually of over 100 captivate movies, and we simply can't manually edit each and every one of them.
I wish i could get my hands on a Captivate developer ;p -
Hi,
During the bios update on my G60 with Windows 7 system freeze, so after 10 minutes of waiting I had to restart notebook. Now when I power on only black screen is pressent (power button and wifi lights are on). I need help to recover bios from (USB/CD). Can you provide me with bios file that I can copy to USB or CD to recover my bios.
I've extracted the file 360BF65.FD from the BIOS update SPxxx.exe on the HP support site, tryed to copy this file to USB but no luck.
Model: HP G60-443CL
Product number: nw148ua#aba
Best regards,
SinisaAll the chips look soldered in, I believe its stored on the one labled via something on it correct? There are 2 chips labeled via, one promise (which I believe controls hardrives etc). One of the chips labeled via is def soldered in, and the other I cant really tell. The black top ofthechip is a little higher than the green board below it, and then a little below that is the normal red board. Does it cost anything to be reflashed? And where would Ihave to ship it to, and how long will it take total?Idont want to be without my computer for too long. My board is the msi k8t based on the via chipset.
What happened: I was using the live update utility, clicked live bios. Said there was anewer one,had some fixes and I thought that I might upgrade eventualy to the x800 pro so I might as well get it. It went throughthe normal process,said turn this program off, I turned off mozilla,and nothing else was running.I created the rescue disk,then clicked next next and it started the bios flashing through windows.When the bars were about halfway, the screen just went blank..... very strange. It was not a power outage,and I have an surge protector with a big battery too incase that happened. Maybe I am not using the rescue disk correctlys?I insert into the drive,turn the computer on, and hold ctrl and home...... what exactly am I supposed to do? I also thought that maybe the rescue diskwasnot created sucessfuly,so could you give me alink to a complete bios rescue disk that I could download and put onto a floppy to try again? Thanx for the answers, I was worried I woudl haveto buy a new motherboard! Im still not exactly sure which one is the bios chip and how to tell if its not soldered in...what wouldit look like? -
BIOS FLASHING
We do not recommend using the MSI LiveUpdate tool to update your BIOS! It may be okay for updating your drivers, but please do not use it to flash the BIOS in Windows!
Windows-based flashing - If you REALLY insist on flashing the BIOS under Windows, if you encounter any error during flashing, whatever you do, DON'T restart your PC! Try again until the flash is successful, otherwise your board will not start! Disable any anti-virus program (along with any other programs) prior to flashing.
Boards with built-in M-Flash function - While M-Flash work's properly most of the time, it has still proved to be less reliable than the forum tool / manual flash.
Before flashing your BIOS, you must ensure your system is fully stable! Any instabilities can cause a bad flash and create an expensive paper weight. Included with the forum flash tool is MEMTEST, we recommend running this for 2 or more passes prior to a flash.
If you do not understand what your BIOS is, or what it does, please read: >> BIOS. What it is, and all you need to know <<
Our first choice we recommend you use is our own USB flashing tool, developed by Svet.
It is important to note, that the only way to flash the ME extension of the BIOS of modern Intel boards is through the use special processes. The bios versions posted by moderators here: >>BIOSes<< include the additional files to accomplish this. These bios are all official and are directly from MSI.
>>>MSI Forum HQ USB Flashing Tool<<<
If you are unable to use the MSI HQ USB BIOS Flashing Tool
>>How to create a dos bootable USB stick>>
It is important to note that if any BIOS, EC FIRMWARE or any other type of FIRMWARE downloaded from MSI for a manual flash contains an BAT file it must be used. Not doing so will cause the flash to fail and require RMA.
For Intel Users, flash via FPT
Socket LGA 1150 : >>ME 9 FPT files & Instruction>>
Many of the bios versions posted here: >>BIOSes<< Contain a .bat file. All you need to do is extract all of the contents of the archive into the root directory of a DOS bootable USB stick and run the bat file from pure DOS.
Socket LGA 1155 & 2011: >>ME 7&8 FPT Files and instruction<<
Linux users
See this topic: >>Flash your BIOS, the Linux way! [beware the dangers!!]<<
Modified and BETA BIOSes
Use only at your own risk! All BETA BIOS versions posted by the moderators of this forum are directly from MSI and will not effect your warranty.The use of user modified BIOS versions may damage the board and may void your warranty. Exercise extreme caution in regards to user posted BIOS versions. Please also be aware that MSI and this forum can not be held responsible if you trash your mobo by using a modded, beta or otherwise incorrect BIOS.
WHEN IT ALL GOES WRONG...
BIOS RECOVERY
In many cases, provided the 'bootblock' of your BIOS is not corrupted during a bad flash, the BIOS can often be recovered by following the recovery procedures detailed below. NOTE: this recovery method should not be followed for normal practice of updating your BIOS!
For Modern MSI Systems, refer to:
<<Multi-Bios Equipped Mainboards>>
<<Single-Bios Equipped Mainboards>>
Legacy Systems:
For Award BIOS
Make a bootable floppy disk*
Copy the Award flash utility & BIOS file to the said floppy disk
Create an autoexec.bat with "Award_Flash_Utility BiosFilename" in the content (e.g. awdfl823K w6378vms.130)
Sample on how to create an autoexec:
a. On Windows, open the notepad
b. On the notepad, write "awdfl823K w6378vms.130" (without the " ")**
c. Save the file as autoexec.bat
Boot up system with the said floppy (it will take less than 2 minutes before screen comes out)
Re-flash the BIOS & reboot.
*Need a bootable floppy disk? Look here: http://www.bootdisk.com
**Make sure you enter the correct filenames for your flasher program and BIOS ROM file!
For AMI BIOS
Rename the desired AMI BIOS file to AMIBOOT.ROM and save it on a floppy disk. e.g. Rename A569MS23.ROM to AMIBOOT.ROM
Insert this floppy disk in the floppy drive. Turn On the system and press and hold Ctrl-Home to force update. It will read the AMIBOOT.ROM file and recover the BIOS from the A drive.
When 4 beeps are heard you may remove the floppy disk and restart the computer.
For new boards with AMI BIOS core 8 (4MB)
Discovered by Jack The Newbie:
Of course, the steps are similar to the standard AMI BIOS Recovery Procedure for internal floppy drives (rename corresponding BIOS File to AMIBOOT.ROM, hit CTRL + HOME after starting the system).
What has to be done (tested on P45 Platinum):
1. An optical SATA Drive needs to be connected to one of the Intel ICH10R SATA ports. {After a lot of testing, I found that it does not work with the same optical drive connected to the SATA Ports hosted by the secondary JMicron Controller. Also, using an optical drive on the JMicron IDE/PATA port does not help either.}
2. A proper BIOS File has to be renamed to AMIBOOT.ROM and burned on an empty CD.
3. CMOS-Clear with main A/C power cable removed from PSU has to be performed. {If this step is not done, the system will reboot after pressing CTRL + Home and will not proceed with recovery procedure.}
4. Press CTRL + Home to trigger BIOS Recovery. -> The system should enter BIOS Recovery Routine. {Will basically work with both USB & PS/2 keyboard. However, a PS/2 Keyboard is recommended as the system will respond earlier to PS/2 Keyboard than to USB Devices.}
What should happen now:
1. After pressing CTRL + HOME the LED Status should change to "Intializing Hard Disk Controller" and there should be access to the optical drive connected to the Intel ICH10R SATA ports.
2. It can take up to 30+ seconds until the BIOS File that was renamed to AMIBOOT.ROM is found. {Drive Bay can be opened to try a different CD without turning off or restarting the system.}
3. When the system finds the BIOS File, LED Status will change to "Testing RTC" and there should be a message on the screen indicating that the Flash Recovery Procedure has started.
4. Since the BIOS File is 4MB in size, it will take a while until the BIOS is actually reflashed.
Its also possible that BIOS recovery on boards with AMIBIOS8 can be done using a FAT-formatted USB stick, containing the renamed BIOS file. Be warned, in some circumstances it may take several moments before recovery procedure actually begins. See Bas' reply below for further information.
BIOS recovery on Wind netbooks
See this post here:
https://forum-en.msi.com/index.php?topic=130509.msg982711#msg982711
BIOS recovery on non-UEFI notebooks
In order to recovery this type of system you will need an FAT32 formatted USB stick.
Download the applicable bios from MSI's website and rename this bios.
It must be re-named to either AMIBOOT.ROM or xxxxIMS.ROM / xxxxAMS.ROM You may need to try each way to determine which one is necessary.
Then place the renamed bios onto the root directory of the FAT32 formatted USB stick.
Now you are ready to cover the Notebook.
To do this, remove the AC power cord and battery. Once that has been completed, install the USB stick you prepared earlier.
Now, apply AC power (leaving the battery disconnected) and turn on the notebook. Recovery should begin after 5 minutes.
IF ALL ELSE FAILS...
Locate the BIOS chip on your mainboard. If it is soldered directly to the PCB like...
...then you have no choice but to return the board to your supplier, or to MSI, for replacement.
To request an RMA from MSI, open a support ticket at https://register.msi.com/ocss/
If your BIOS chip is in a socket, like...
...then you may be able to source a replacement BIOS chip, either from MSI, or from a website such as www.badflash.com
Updated 11/21/2013, original post by StuA.) Download >>this<< bios archive and place it on your desktop. Do not decompress.
B.) Download and install the >>MSI HQ Forum USB flasher<< .
C.) Insert your FAT32 formatted usb stick.
D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
F.) Boot to the USB from working bios B.
G.) Once it booted successfully switch to bios A without powering down or rebooting
H.) Now follow the directions and let the tool flash bios A with desired version -
I recently had an apparently unrecoverable BIOS flash failure which I RMA'd (although I have since found http://service.msicomputer.com/msi_user/TechFAQdetail.aspx?formid=3046). Since I now flash successfully in that same way, my best guess is that the original board really was defective. The advice on this forum generally is to use the MSI Forum HQ USB Flashing Tool, which obviously has had a great deal of development effort. I did try that Flashing Tool, but found it more confusing than I had hoped, and the flashing did not complete for me. Given my previous msi BIOS flashing experience, that was scary. Then I used the msi on-board flashing (as I did originally) with a downloaded file in the root of a USB flash drive. Inside the BIOS, Utilities > M-Flash > Select one file to update BIOS, started flashing and did work, and has since worked several times.
The advice to use the Flashing Tool apparently relates to the Tool working "better" (perhaps with lower chance of failure) than the on-board BIOS flasher. And it may BE better, but flashing should not be error-prone anyway, nowadays! USB flash drives have been around for many years, we use them all the time, and they do not need a special flashing tool. Frankly, I feel that if the on-board flasher does not work, the board is just defective, end of story.
Since I would have been better off with some idea about what to expect, here it is: On my system, BIOS flashing takes MUCH LONGER than one might expect. Overall, it takes about 4min 30sec (for only 8MB), which appears to be only about 30kB per second. The display shows flashing to be about 50percent done in about 3min, then it runs up to 90percent in about 10sec more. At about 95percent done (about 3min 30sec), the screen blanks and the system starts to auto-reset, which appears to happen slowly, and twice, before coming up at about 4min 30sec.
Hope this helps!This board in particular can be flashed properly with the MSI BIOS flasher ,M-Flasher .It s practically as safe as the Gigabyte one.
I have flashed the BIOS with the M-Flash from 1.2 to 1.5 with no problems on this board.
Use a USB stick formated to FAT and you are good to go as long as you already done some stability teats for the machine.
Yes after the Flash the screen may remain black ,but that is why you have on the board a Clear CMOS jumper ,in the lower left side.
Maybe some users should let the flashing process to people that know how to do it and stores can do this procedure for you. -
currently trying to flash my bios upto the current release to attempt to fix a problem that seems i am not the only one to have and have tried every other solution provided.
Now i have flashed many a bios before but never this one....my current version is 5.1 and i am trying to install 5.7. Here's the problem.....when i load dos from a win98se startup disk i goto the c: drive and then run a "dir" to get the list......however instead i get a "file not found" for the whole drive (i am guessing do to it not being able to read a FAT32 partition/drive). so i am able to copy the bios flash files to a ramdrive that the startup disk creates on boot but i am reluctant to install from there as i don't want to fuxor something up by doing so. i would just install them from a floppy but the instructions that come with the flash file say specifically not to install from a floppy (though no reason for this is given).
My questions are these:
1. can i copy the files to the ramdrive and install the bios flash from there without having any problems that anybody knows of?
2. why can't i just install the flash from floppy? i've never run into this on any other boards is this an MSI thing
3. is there a place that i can get a bootdisk online that will allow me to read the fat32 disk so that i don't have to worry about any of the above solutions that i have come up with?
any help with this stuff will be greatly appreciated
tia
Aaronnevermind i figured it out thanks anyway
-
K9N Platinum and BIOS flashing
New to MSI and this forum
I have a K9N Platinum which I've had some problems with and also need to flash the BIOS.
Problems are: Leadtek TV tuner card video problem watching TV (image and sound freezing) then my laser printer would not print through the parrallel port (works okay through a USB port).
Have had no real solutions from MSI with those two problems
Just recently I've come into owning a MSI 7950 GX2 video card.
Apparently this card won't work with the K9N unless I flash upgrade the BIOS (using A7250NMS, V1.20)
I know my way around computer hardware but BIOS flashing I've never done.
I'm using a NTFS file system,OS is WINXP SP1, processor AMD64 4800+ and HDD Hitachi 250GB SATA2
I have two choices to use these brand new video card:
1: Try to flash the BIOS (with the obvious risks involved)
2: Replace the K9N board with one that is compatible with the 7950 (bearing in mind the other problems with the K9N)
I've read artcles from this site and MSI about flashing using a NTFS file system and I'm not confident.
I know this post is between BIOS and motherboards so it was hard to decide where to place it.
If anyone has any thoughts on the best solution for this it would be appreciatedFirst of all , make sure you have a "fixedup" motherboard .
( the capacitor fix , see info in the "Post your K9N Ultra/Platinum (non SLI) 'Power Off' Issues Here (NForce 570 MCP)" thread)
https://forum-en.msi.com/index.php?topic=99924.0
Flash bios doesn't need to be done from HD .
You can have both afudos flash util and bios image file on a msdos bootable floppy diskette (verify it from windows with chkdsk A: /R ) -
Hard-Power off caused BIOS to stop working (NOT because of BIOS Flash)
I was trying to boot up a live CD on my Toshiba Satellite P305D-S8900. The F12 key to pull up the boot menu didn't work, and it started to boot to Windows. I let it get past the "Starting Windows" Orab (running Windows 7), and hard-powered it off when it got to "Please Wait..." right before the login screen. After that, when ever I turn it on, the BIOS isn't loading. The Only LED lights going on are the Power button one, and the three that indicates it plugged in, the power is on, and the Battery indicator. The media buttons and the one above the trackpad doesn't work. The track pad one lights up when I hit the power button to turn it off. The fans are working (indicating the power management is working), the CD Drive is reading to see if there is a disc in there, and the screen remains black. There is no hard drive activity whatsoever. And the strangest thing of all...no beep code!!
I have so far tried taking out my MAIN battery for 24 hours (NOT the CMOS battery) and a Pheniox Crisis Disk with these combinations: "Win+B", "Fn+B", and "Fn+F". There is no beep codes when I do it or even any beeping to indicate the BIOS is getting flashed for that matter. Are there any other key combinations I could try? And yes, I from the start took out the battery, plugged in the drive, and pressed and held the key combinations while plugging in the AC, turning it on, and waiting about 30 seconds to release the key combinations. Like I said, this was not during any BIOS flashing, and what went wrong really stumps me.
Is there any other solution I could try? As of right now, sending into repair is not an option. Can anyone help me fix this? Thanks in advanced!I was trying to boot up a live CD on my Toshiba Satellite P305D-S8900. The F12 key to pull up the boot menu didn't work, and it started to boot to Windows. I let it get past the "Starting Windows" Orab (running Windows 7), and hard-powered it off when it got to "Please Wait..." right before the login screen. After that, when ever I turn it on, the BIOS isn't loading. The Only LED lights going on are the Power button one, and the three that indicates it plugged in, the power is on, and the Battery indicator. The media buttons and the one above the trackpad doesn't work. The track pad one lights up when I hit the power button to turn it off. The fans are working (indicating the power management is working), the CD Drive is reading to see if there is a disc in there, and the screen remains black. There is no hard drive activity whatsoever. And the strangest thing of all...no beep code!!
I have so far tried taking out my MAIN battery for 24 hours (NOT the CMOS battery) and a Pheniox Crisis Disk with these combinations: "Win+B", "Fn+B", and "Fn+F". There is no beep codes when I do it or even any beeping to indicate the BIOS is getting flashed for that matter. Are there any other key combinations I could try? And yes, I from the start took out the battery, plugged in the drive, and pressed and held the key combinations while plugging in the AC, turning it on, and waiting about 30 seconds to release the key combinations. Like I said, this was not during any BIOS flashing, and what went wrong really stumps me.
Is there any other solution I could try? As of right now, sending into repair is not an option. Can anyone help me fix this? Thanks in advanced! -
Copy frames from one movie to another in Flash 8
How do you copy frames from one movie to another in Flash 8?
I found this one, but it does not work on Flash 8.
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_12863
I want to copy the contents of a scene from one movie, and
then create a scene in another movie and paste it in there.Adesi wrote:
> How do you copy frames from one movie to another in
Flash 8?
>
> I found this one, but it does not work on Flash 8.
>
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_12863
>
> I want to copy the contents of a scene from one movie,
and then create a scene
> in another movie and paste it in there.
you must be doing something wrong, the above tutorial is
correct and it is the
only way to copy paste frames in flash.
Make sure your layers are not locked. Locked layers cant be
copied.
Best Regards
Urami
<urami>
If you want to mail me - DO NOT LAUGH AT MY ADDRESS
</urami> -
PDF error A script in this movie is causing Adobe Flash Player 10 to run slowly.
When opening a PDF of a website using Acrobat 9.0 Professional, I am recieiving the following notification.
A script in this movie is causing Adobe Flash Player 10 to run slowly. If it continues to run, you computer may become unresponsive. Do you want to abort the script?
The error does not occur when viewing the live website from which the PDF was made.
I recieve the same error when trying to open the PDF on other PCs using Adobe Reader 9.
I have updated the flash player on each of the PCs as well.
I am wondering if anyone has any ideas or insight regarding why I am recieving this notification.
Thank youI'm suddenly getting the same error message, on a variety of web sites. I'm running Windows Vista on a fairly high-end desktop, and I haven't added any new software lately. This just started up out of nowhere. When searching for this error message on the web, people are asking this same question all over the place, and no one has an answer. Does Adobe ever monitor these forums?
-
845 PE-Max "NEW" Bios Flash "does it really fix the temp readings?"
So MSI has been having problems with there Temp readings on there boards. So I was surprised to see that they just released a bios update to correct this issue. Of course I couldn't wait to download and flash the bios and see what effect it had. Everything went well, I popped into windows and (I'm testing Intel's stock HSF currently) and my temps dropped drastically????? Now this can't be correct either...
Motherboard: 32c
CPU: 29c
Case 23c
Now remember this is with the retail P4 2.53 HSF. With the new bios flash it shows a cooler temp than my Spark 7. And the Intel is only running at 2400RPM. Before the bios flash with the Intel HSF:
Motherboard: 33c
CPU: 40c
Case 23cWell ran another test last night. Ran a CPU Burn-In test for 30 Minutes and the temp only hit 45c during the test. Obviously the new BIOS is incorrect. I find it impossible that the retail HSF on my P4 2.53GHz can keep it below 50c under max load. My Tt Spark 7 with Artic Silver II only kept it at 37c idle. I'm reading 28c Idle now using the retail HSF.
MSI - ?????????????????????????? -
Thinkpad R40 type 2682 - 6GU Bios flash problems
Hello all! I made sure to check all of the R40 threads for information on this, and have been unable to find anything, I was hoping you could help me!
I recently purchased a Thinkpad R40 type 2682 - 6GU, and absolutely love it! I maxed out the RAM (1 gig), and it came equipped with Windows XP professional. It has the internal 802.11a/b wireless pci card.
I just purchased the IBM Thinkpad MiniPCI Atheros 802.11g card, and saw that I will need the latest BIOS
Version: 1.27
Release Date: 2006/06/30
1ouj24us.exe
installed for the card to work. I checked, and I currently have 1.14 .
I downloaded the file straight from the Lenova Support & Downloads site. I read the readme file, and followed all of the instructions, and it isn't doing anything. I will give a detailed description of what I am doing, to see if you can pinpoint something I am doing wrong, or a setting somewhere I need to change.
1. saved file as C:\bios\1ouj24us.exe
2. opened start menu --> run
3. typed in c:\bios\1ouj24us.exe --> enter
4. clicked "run"
5. accepted EULA
6. chose "next" through the first 4 messages
7. chose "next" on the next 1 of 4 messages
At this point, the computer restarts, logs into windows (no user accounts or passwords setup yet to avoid the mess of that during BIOS flash), loads like normal, and no further process on the BIOS flash. I have done this at least 20 times on the same machine, and it still has BIOS ver 1.14 .
Can you please help?!?
Thanks in advance,
LeeIf it's a genuine IBM card, there should be a sticker on it saying FRU P/N 39T0081 or something like that, but would include a FRU P/N part regardless of the actual number.
A generic card will throw a "1802 error" in a R40, where the original one won't.
You can't update BIOS on a machine that has a bad battery or charging issues, BTW.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you. -
Flash error in Safari: "A script in this movie is causing Adobe Flash P..."
When using the BBC iPlayer to watch movies in Safari they freeze after 8 seconds (although the sound continues). After a few more seconds an error message pops up that says "A script in this movie is causing Adobe Flash Player 9 to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script? Yes/No". If I click "Yes" the movie will jump frames until it catches up with the sound and then play normally, although a lot of functionality will be lost in the player (pausing, time elapsed etc.). If I click "No" the browser will crash.
I originally had Flash Player 10 running, which gave me the same problem. I uninstalled it, fixed permissions, installed Flash Player 9 and fixed permissions again. There is no difference.
The same problem exists in Firefox, so I believe it to be a Flash problem rather than Safari but the Adobe site is no help and the forums there have a lot of people with the same problem but no solutions. So I'm hoping that someone here might have an idea...Klaus1:
You also asked if I had installed the latest update to iPlayer. I assume that you mean the Desktop iPlayer, but this is a whole different issue! When I first tried to download the movie using Desktop iPlayer I was presented with a button to install it. This surprised me as it was already installed, but maybe it was really just offering an update. As it wasn't optional, I clicked the button. It then tried to install AdobeAIR (which was already installed) and failed as it couldn't get permission to write to the disk.
I thought I'd make things simple and uninstalled AdobeAIR and Desktop iPlayer. I then tried to reinstall. Again it tried to install AdobeAIR and failed. So I tried downloading and installing AdobeAIR direct from Adobe. The installer loads into the dock but that's it. I've spent many hours trying to resolve this without success.
Hence I'm just trying to use the browser version of iPlayer.
I thought I'd get the Flash Player thing resolved first and then start another thread about AdobeAIR! I thought Adobe products were solid but I'm now seeing lot's of differing opinions on that.
Maybe you are looking for
-
How do I "Permanently" uncheck the box "Re open windows when logging back in"?
-
What is advisable? [Jar the property file or not?]
About standalone applications, what is advised? shall the properties file and other configuration files be a part of the jar file or not? One benefit keeping them out is to have a privilege of 'not-building' the entire code just to change the configu
-
How do I Update Twonky on NSS324?
Hi The twonky server on NSS324 has bugs and will need to see if there is a new twonky pkg available for NSS324. If there is one where can I find it and how can I update it? Abhijit
-
Session variables trying to resolve as columns
Hello, I have a simple case statement where I am trying to use the user.id variable. Unfortunately whenever I do this it returns an 'Unresolved Column' error. CASE WHEN "Users"."User Name" = CAST(@{user.id}{'DWBACKUP'} AS VARCHAR(8)) THEN '1. User'
-
My Itune program crashed while listening to music last monday and unable to download program back onto my desktop.