Help in designing a flash tool to compare before and after photos

Hello,
I would like to create a photo comparison tool similar to the tool in this web site:  http://www.restylaneusa.com/before-after.html  Our company is in the aesthetics market and I have been tasked on creating a tool that would allow us to "morph" from the before picture to the after treatment picture in attempt to show change in facial features.
Thanks,
Trackside2

you could use the bitmapdata class to do image morphing.  because there are many ways to morph one image into another, you'll need to know all the expectations of the client.

Similar Messages

  • Comparing Before And After

    I'd like to look at a before and after version of a picture once I've made an adjustment, but haven't been able to figure out how it's done.
    Thanks.

    If you want to compare different stages in a series
    of adjustments, you have to remember to make a new
    copy of the current version before doing the next
    step in the series. (In that way it's just like a
    word-processing program.) But the versions don't cost
    you anything, to speak of, in the way of disk space.
    The more info the better. Thanks very much.

  • Compare BEFORE and AFTER image in replicat

    Do any of You experts know how to make the following code smaller?
    ...,p_kolonner=@STRCAT("ID='",@IF(@COLTEST(BEFORE.ID,PRESENT),BEFORE.ID,""),"'>'",@IF(@COLTEST(ID,PRESENT),ID,""),"'¤",
    "OBSOLETED_ON='",@IF(@COLTEST(BEFORE.OBSOLETED_ON,PRESENT),BEFORE.OBSOLETED_ON,""),"'>'",@IF(@COLTEST(OBSOLETED_ON,PRESENT),OBSOLETED_ON,""),"'¤",
    "SMRT_ID='",@IF(@COLTEST(BEFORE...The actual parameter would look like:
    P_KOLONNER:  ID=''>'11531'¤OBSOLETED_ON=''>''¤SMRT_ID=''>'1'¤SM_SMID=''>'2011X0074-00'¤SMT_ID=''>''...
    This code is part of the params section of a sqlexec in a replicat file where I want to concatenate before and after images of a table into one parameter. I have to replace all NULLs with '' or the whole string evaluates to NULL when one of the columns are NULL. I have a procedure receiving the parameter.
    How do I write this code shorter? I have to use less code to accomplish the same thing.

    Hi Yosemite:
      You're right, the correct term is "Key Fields", in the previous post I made a mistake when referring to it as "Key Part", I'm sorry for the confusion.
    Anyway, it is not clear to me if you managed to solve the problem or if you're still struggling with your data loads, if this is the case, Could you please elaborate?
    -Which is the data source you are working with?
    -Did you map the ROCANCEL field both to the 0STORNO and 0RECORDMODE InfoObjects?
    -Are you using Addition or Overwrite on the Update Rules/Transformation Rules to the DSO?
    -Have you applied any relevant SAP Note to fix this issue?
    In case you have not read the blog by Swapna Gollakota, take a look at it, you might find it useful.
    How does a datasource communicates "DELTA" with BW?
    /people/swapna.gollakota/blog/2007/12/27/how-does-a-datasource-communicates-delta-with-bw
    Regards,
    Francisco Milán.
    Edited by: Francisco Milan on Oct 29, 2010 12:31 PM

  • Flashing Tool Use with Linux and DOS

    OK, I am convinced that I should use the MSI Forum HQ USB Flashing Tool on my recently-RMA'd FM2-A75MA-E35.  After reading the documentation repeatedly, I still have questions. 
    I agree that the way to go is to flash from DOS, and I do in fact boot and run FreeDOS from a USB flash drive for video BIOS updates.  But my new msi board runs Linux, not Windows, so I cannot execute and install the Flashing Tool the expected way. 
    1.  So I installed the Flashing Tool on my Win7 system, which runs on a Biostar board.  Can that cause problems?
    2.  Can I put the resulting flashing system on my existing FreeDOS boot USB? 
    3.  As I understand it, the Tool will first read and save the existing BIOS code.  Is there an easy way to archive all of those saves and not overwrite earlier versions?  Is there a way to easily change the filenames in the Tool? 
    4.  On this new board I have on-chip video.  Is the video BIOS automatically updated when burning the MB BIOS?  Is it updated separately? 
    Thanks for your help!

    The forum flash tool can be run from any computer.
    What it does is prepare a bootable use stick. It also places the required flash exectable etc onto the drive and bios. So all you need to do is download whatever bios you wish from msi:
    >>MSI Downloads<<
    Place it on the desktop of the biostar computer, run the flash tool, point it at the bios then to your flash drive. Then put the flash drive in the other computer, hit f11 at boot and boot to the prepared usb stick.
    Then follow the directions.

  • Help.  ipad air flashes between white apple logo and unlock screen?

    help.  ipad air flashes between white apple logo and unlock screen?  how do i fix this ?

    You can try resetting your iPad by simultaneously pressing and holding the Home and Sleep/Wake buttons until you see the Apple Logo. This can take up to 15 seconds so be patient and don't release the buttons until the logo appears.
    Try again to see if the problem persists.

  • My husband uses adobe cs5. The clone tool isn't working and after resetting the tools adobe bridge now goes to picasa. How can we make the clone tool work and have bridge go to cs5 not picasa?

    My husband uses adobe cs5. The clone tool isn't working and after resetting the tools adobe bridge now goes to picasa. How can we make the clone tool work and have bridge go to cs5 not picasa?

    A lot more information about your hardware and software is needed.
    BOILERPLATE TEXT:
    If you give complete and detailed information about your setup and the issue at hand,
    such as your platform (Mac or Win),
    exact versions of your OS, of Photoshop (not just "CC", but something like CC2014.v.2.2) and of Bridge,
    your settings in Photoshop > Preference > Performance
    the type of file you were working on,
    machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
    what troubleshooting steps you have taken so far,
    what error message(s) you receive,
    if having issues opening raw files also the exact camera make and model that generated them,
    if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
    a screen shot of your settings or of the image could be very helpful too,
    etc.,
    someone may be able to help you (not necessarily this poster, who is not a Windows user).
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
    http://forums.adobe.com/thread/419981?tstart=0
    Thanks!

  • How to compare value before and after

    hi,
    one of the queried Values ​​is the number of defective frames.Here, this value is compared with a previously sampled value
    If now (after 10 s) this value is bigger than previous one ,then It saves new value otherwise loop will be continue.If again after (10s) the new value is bigger than  previous  new value then again saves this new point.how can i comapre value before and after?thanks.
    Tadhika

    Do you know what a shift register is? It preserves a value from one loop iteration to the next. Please read the LabVIEW Help on shift registers. There's is also a simple example that ships with LabVIEW that will give you the basic idea (Help -> Find Examples).
    You can also use a Feedback Node in lieu of a shift register. Same concept, different implementation.

  • Comparing pictures before and after adjustments

    Dear all,
    I'm about to switch from the Canon software DPP to Camera RAW.
    In DPP it's possible to split the view in order to compare the same RAW picture with different adjustements. This possibility is very valuable to me.
    Is it possible to split the view in Camera RAW ?
    If not, how do you manage to compare the original picture to the one you obtain after having made your adjustments ?
    Thank you for your answers,
    Cédric

    Each adjusment panel in ACR has a Preview box you can check or uncheck to view the adjustments you have made in that panel.
    Alternatively, you can simply toggle the "p" key to see the difference in your image before and after the adjustments. But in either case, this before/after comparison is limired to the adjustments made only in the panel you are currently working in.
    However, if you switch to the Presets panel and toggle the "p" key, this will show you the difference between the image as it was initially opened in ACR and after all adjustments made in all panels.

  • Need help finding a BIOS flash tool and BIOS updates for HP Compaq nc8230 running Windows 7

    I put together this laptop. It didnt come with a hardrive, and basically I installed everything from the ground up.
    It is an HP Compaq nc8230, IDE Hard drive, Windows 7 32 bit. The BIOS on it is the original one. I've searched far and wide, but to no avail, it seems there's zero support for this model anymore.
          Basically it was never intended to go beyond Vista, back in 2004 when this model was introduced.
       The reason I am searching for some kind of BIOS update, whether it is BIOS or SMBios is to get the ACPI driver to recognize the primary laptop battery. This is crucial: it only sees both as the travel battery. Other than that, all else is fine.

    Hi:
    Here is the latest BIOS update for your notebook.
    http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=32...
    You cannot use the windows based flash because you installed windows 7, so I provided the link to the DOS based flash.
    You need to use a USB floppy drive for this update.
    Oh, and the card reader won't work unless you install this updated driver which is not on your PC's support and driver page.
    http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=32...
    Also, here is the link to your PC's support and driver page...
    http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?lang=en&cc=us&prodTypeId=321957&prodSeries...

  • Someone please help me with my flash player problems, i install and then told its not installed

    i have windows 7 only on my laptop now, but it seems that i have all the necessary products needed to play games etc.  I have all my programs that need updates marked to do so as available. I have noticed when i go to particular sites now , like games in FB or games thru my AOL they tell me i need to install the newest version of the flash player. so i do that, go back to that site, same notification appears to install. i dont know ALOT about my laptop but have learned enough to know that i should very well it should be there if i have installed it time and time again  correct? i dont understand the whole basis of what i might need for different sites/games. I have been playing the Big Fish game site since Dec. 2012 and it seems ever since i have been on a daily visit to that site SOMEHOW i cant play any other sites games now. so i read , do this, than this, if this or that is needed..........well it becomes a miss in my brain as to what they are telling/suggesting could be the problem. I truly need someone that has this knowledge to help me learn. i use to play on the webkinz world site for over a year, so last night i thought i would go back in there and again the flash player notice. so something has changed that i am unaware of it and how to solve it. i totally appreciate any help and time someone could give me. thank you,

    In any case, the Flash Player forum is here:
    http://forums.adobe.com/community/flashplayer
    This is the Reader one.

  • Bug exposed when comparing Jpeg and RAW Photos taken with Canon 20D?

    I'm using iPhoto 7.1 to manage my photos. My Digital SLR, the Canon 20D, can be set to save photos as both RAW (CR2 files) and Jpeg (JPG files). Both of these files can be imported into iPhoto with no problem.
    The problem that I have is that these photos that should be identical, have two major discrepancies.
    1. Their resolution are NOT the same. (3504x2332 for CR2, 3504x2336 for JPG)
    2. The colors appear different (CR2 appears reddish, JPG appears normal)
    Interesting to note: if I export the same CR2 file out of the iPhoto library (export it as Kind='original'), and open it with IrfanView running on Windows 2000, the photo is viewed with the expected resolution of 3504x2336 and the color appears normal (i.e. not reddish).
    I'm a new Mac user, and relatively new to digital photography, so any advice or suggestions would be appreciated! I've heard of color profiles and adjustments, but I'm not sure how that works. Perhaps I could be pointed to a HOWTO type document?
    Cheers

    OK, next RAW files again.
    These hold the data the sensor 'saw' when you took the shot together with 'metadata' such as aperture, shutter speed, white balance settings, ISO setting etc - lots of data in fact.
    Most programs do not alter RAW files at all - they are the digital negative and should not be altered.
    The latest iPhoto treats all newly imported photos in this manner - RAW/JPG or other format. It keeps a copy of the original in a folder called originals, and any edits/crops you make are applied and saved either as a modified JPG or TIFF. This non-destructive editing is a great feature that many RAW editors allow so you can go back to the original image if you mess things up. Applying the principle to JPGs etc is equally as important.
    Canon's Digital Photo Professional is a free RAW processor program you can download from their site - certainly worth a look, but you may well find iPhoto simpler if not as flexible. On Windows, not sure about Mac OS, DPP does actually alter (or add) some metadata to RAW files - it doesn't alter the 'sensor data' but somehow embeds edited values to the RAW file so they display as edited next time - you can go back to original but I doubt other software will understand these tweaks.
    Digital cameras are getting better and better at getting white balance etc correct, however RAW files are great mainly for two things.
    Firstly - in camera white balance settings are simply those applied to JPGs the camera produces. Set it to fluorescent and take a shot of a cloudy scene and the JPG may look awful. With the RAW you can change the white balance after the event and is a real image saver. I particularly like software that lets you use a 'dropper' to choose a neutral grey shade on the image to set the white balance.
    Secondly - over/under exposure. As RAW files hold more light intensity detail you can often bring out shadow detail from underexposed images or recover blown highlights from images that are unusable as JPGs. There are limits to this latitude of course.
    In camera JPGs are often all you need - the RAWs just give added flexibility.
    Next thing I'd say is not to get too hung up about profiles at this stage.
    Yes, you can pay for generic profiles or even expensive personalised profiles for the 20D - there are some gains in compatible software (sometimes the profiles are designed to work with particular software!). Not necesarily huge gains though, so I'd say keep it simple to start with.
    If there's one thing it's worth profiling, then it's your monitor.
    I often use the analogy of a TV with a video still image from DVD or VCR.
    Say you adjust the brightness/contrast/colour/sharpness of the TV then the image can be made to look wildly different on different settings.
    However the actual image being displayed is not itself altered at all by the DVD player or VCR on pause. Turn the TV off it goes black, but the DVD/VCR still outputs that same image. It's just displayed differently or not at all!
    Translate this to editing photos.
    The RAW or JPG will be processed by iPhoto according to a particular colour space, say sRGB or AdobeRGB - now how on earth do you know that the monitor's brightness/contrast/saturation are at the correct level to display the image correctly? Is it brightnes 50%/75%/20%?
    The answer is the monitor profile which tweaks the output of the monitor towards a preset calibration - this is for a given brightness/contrast/colour setting (not all monitors have exhaustive adjustments but some do). Generic profiles which come with Macs are better than nothing, and indeed often quite close to an individually calibrated monitor profile.
    You can however calibrate your monitor either by eye or using a hardware accessory.
    Open your System Preferences folder and choose Displays.
    Click the colour tab and remember the profile name highlighted!
    Click on any others to see how different profiles affect the display - the other profiles will invariably be wrong for the monitor but they show the effect.
    These other profiles DO NOT make you system display an image say as sRGB or AdobeRGB - what they imply is that the monitor can display the range of sRGB or AdobeRGB - it can't! It can display what IT is capable of displaying.
    It is the image profile that makes software display it in the sRGB or AdobeRGB or other colour space. The monitor profile allows the image to be displayed more accurately by mapping available colours it can display or close fits to the one's the image contains.
    There is a Calibrate button in this tab which should help you Calibrate your monitor by eye (I think I've not used it).
    You can also buy hardware accessories to accurately calibrate your monitor (I use an EyeOne Display by Gretag Macbeth - older version - there are far more expensive and also reasonable cheaper options out there). The hardware devices basically cycle through a display of 'known colours'. The device's software knows what colour it's trying to display, the device usually hangs over the display and measures what's actually displayed, then reprograms the way the graphic card displays colours and also creates a custom monitor profile - this process of calibration optimises your monitor's display.
    You can also calibrate or get custom printer profiles made to optimise printer output, but you won't be doing that. Some online photo sites do however supply profiles which match their photo printers so you can tweak your images to match output on their hardware.
    Most photo sites that the public use however will assume that the images are sRGB. If you send an AdobeRGB image for printing it may be treated as sRGB and printed incorrectly if that photo printer's software doesn't take account of embedded profiles.
    I said it was complex and confusing!
    Continued again!
    AC

  • Help with the complexities of a mix of managed and referenced photos

    When I first started using Aperture instead of iPhoto, I elected to keep my iPhoto photos in their existing location (as referenced files) and all subsequent photos that were imported into Aperture were (obviously) managed by Aperture.
    I am hoping to start freeing up some hard drive space by deleting some photos.
    [1] If I delete a referenced photo in Aperture, does the photo also get deleted in iPhoto, or does the reference to it merely get deleted from Aperture?  I'm assuming the latter is true. If I delete the photo in iPhoto, I'm guess in a preview thumbnail remains in Aperture. 
    So, what's the best way to accomplish this?
    [2] I'm ultimately hoping to get a new MacBook Pro and am thinking since I'm now an Aperture afficianado, I'd like to move all my photos to aperture as managed files since I might ultimately put my burgeoning photo collection on an external drive. 
    Is there a way to change the referenced iphoto files to managed Aperture files (thereby completely bypassing iPhoto altogether)?
    Thanks for your help!

    Thanks. That is pretty straightforward.  One follow-up question:
    Do I then select all the photos in Aperture and do Colsolidate Masters (assuming Aperture will skip over those pictures that are already Managed), or do I have to select only my iPhoto referenced files?

  • IPad 2 cannot connect to Wifi before and after updating  PLEASE HELP

    i have been using iOS 5.1.1 till today.. the connection to wifi stopped working.. it slowly faded away and today i woke up and could not connect to My wifi at all, i have decided to update my iPad to iOS 7.0.4 but the problem is there
    what should i doo ??

    It could be a problem with your WiFi router or your iPad.
    If you are having WiFi problems it is necessary to isolate whether the problem is with your network or your iPad. Note: Do NOT consider your network to be blameless if some other devices can connect to it.
    First, test your iPad on some other WiFi networks: a friends, Starbucks, Barnes & Noble, etc.
    If it works well there then the problem is probably with your network. Try restarting your WiFi router by removing power for 30 seconds. If that does not help check for a firmware update for your router. If none exists which corrects the problem consider replacing the router.
    If your iPad does not function well on other networks it possibly has a hardware problem. You could try Settings > General > Reset > Reset Network Settings to see if that corrects the problem. If not, contact Apple Support or visit an Apple store for evaluation. They can provide a replacement if your iPad is bad.
    If you need more help please give the make, model, and version of your WiFi router and how you have it configured.
    See also here: http://www.apple.com/support/ipad/wifi/

  • 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]

  • MSI Forum HQ USB flashing tool!!!

    Hi guys,
    We the forum team have developed  a new way of flashing.
    You no longer need a floppy or anything, just an USB-stick.
    The tool has been tested together with MSI and as far as we have done our testing, there are no problems at all.
    As long as the USB-stick is FAT or FAT32 formatted!
    However, flashing is allways risky, so if it goes bad it's your own fault, but that goes for all flashing you do.
    This tool is intended to flash MSI retail motherboards and laptops,
    but if needs you can use any other machine to prepare the necessary stuffs and the USB stick there,
    before move the USB stick to the msi product that you want to flash.
    The way it works is simple: Download the package and download the BIOS from the MSI website that you want to flash.
    The rest is straight forward.
    Make sure that your board is set to be able to boot from USB.
    So turn on USB Legacy Support in the BIOS.
    Boot and press F11 to get the boot-popup and select your USB-device to boot.
    (some boards have a different key, like K8N Master uses ESC for the boot-menu)
    What ever you do, make sure you read all warnings!
    The forum nor MSI is responsible if it fails for you.
    Nor is this software supported by MSI technical support!
    Please report problems/buggs if you find them.
    currently supported OS ( both 32 & 64 bit):
    Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, Windows 7 (also Windows in Virtualbox under Linux!)
    (all kind of versions)
    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.
    This topic is for discussion of and help with the USB flash tool only. If you have a problem with your PC and need help then do not hijack this topic, please start your own new topic in the correct area of this forum!
    NEW! >>> Read the comprehensive user guide here! <<<
    The download links are listed below:
    https://www.dropbox.com/s/yu8imcr1tsopm24/MSIHQ%20Tool%201.26h%20Installer.rar?dl=0

    Quote from: max-sever on 25-May-07, 01:29:21
    Hi!
    I'm have problem with antivirus program too.
    Dr.Web
    C:\Temp\x863\bossmsi.exe - &#1080;&#1085;&#1092;&#1080;&#1094;&#1080;&#1088;&#1086;&#1074;&#1072;&#1085; Trojan.Blakhal
    Kaspersky Anti-Virus
    bossmsi.exe - &#1080;&#1085;&#1092;&#1080;&#1094;&#1080;&#1088;&#1086;&#1074;&#1072;&#1085; Backdoor.Win32.Iroffer.af
    This file is a antivirus testing program?
    Hi Max,
    "This file is a antivirus testing program? "
    yes, the latest version accidentally really become a test for any AV....
    in latest 1.13b Avast! no more report false positive,
    but all others AV software starting reporting a different false positive results:(all AV listed didn't report false positive problem in a provisional version) Avast! was fixed and no more report the false passivity and passed, but all other AV software started to be a lot confused...
    Kaspersky Anti-Virus - Proactive Defense Warning: Riskware detected.
    Kaspersky Anti-Virus 2nd ID - Backdoor.Win32.Iroffer.af
    Dr Solomon's:  probably found Zafi.D.Virus
    Symantec: Bloodhound.Overpacked / * Overpacked when a potentially unknown virus is found using Symantec Bloodhound technology */
    Panda: Win32:Trojan-gen.(Mytob.U.Mod)
    Mcafe: Worm.W32/Bakain
    Dr.Web: Trojan.Blakhal
    Bit.Defender: Trojan.JS.Obsq.Gen
    Just to clarify one more time, all things listed are false alert coused and exist in latest version only due Avast! fix.(1.13b)
    didn't continue to test with rest of AV...
    only Avast! and NOD32 report no problem detected.
    in 1.13a all false positive listed above doesn't exist, but only Avast! report false positive.
    Hoverer, the wave of false positive mess has been resolved along with Avast! false positive as well.
    New version is ready, 1.13c:
    - fixed false positive wave which confusing most of AV software. (all AV do not report any problems anymore)
    - fixed 3 minor bugs:
           * after finished work the tool do not quit normal as expected and hang instead, that happend in x32bit OS only when used has been asked for reboot and answered with "No". e.g. in described specified case.
           * 4th mainboard filter report positive results in some Biostart mainboard and this cause tool to false ID some Biostar board as MSI one.
           * added missing drive letter as USB key choice ("I")
    Download location in a the 1st post of this topic.

Maybe you are looking for