Recompose tool + more....

I have been trying for hours to use the recompose tool on a photo. It is not working. I have read every tutorial that I can find, & watched the video on Adobe muliple times, it does not work. I can use the protect & removal tools... but when I go to use the side arrows... NOTHING deletes! Is there a limit as to how many items you can remove? Any ideas? I am frustrated
Also- I don't think that I am supposed to have a white line running across my top tool bar, the one you use to open, etc. Am I right?
Thank You
alarmrx2

First I clicked on the Recompose tool and used the "delete" brush to mark the objects to be deleted:
Next, I grabbed the right handle and started dragging it to the left:
You've got to squash the picture quite a bit to get rid of all the marked objects.  The thing to keep in mind is that if you want to delete an object 10 pixels wide, you've got to shrink the width of the picture by at least 10 pixels.  Since the cars and boat consume about half of the width of the picture, you've got to squash it by about half to get rid of them.
Here's the result:
There are some artifacts left over from the right edge of the black pickup.  I think that's a bug in Adobe's implementation of the "slicing" algorithm underlying the tool.  But you can use the Clone Stamp tool to do a good job of getting rid of them.

Similar Messages

  • Re: Recompose Tool

    Being new to PS Elements 9, I tried the recompose tool on my own.  It worked well and I achieved the correction in my photo.  I went to save it and noticed that the extension on the file name was changed from a .jpg to .psg  I did not know what to do and tried to change it to a .jpg extension.  When I hit SAVE, I got a strange image on my screen which replaced the amended photo that I'd worked so very hard on.  Have I lost that amended photo?  It shows up in my organizer but doesn't appear as the amended photo.  Can it be retrieved?  And what does this image mean - it looks like a torn photograph. The guide book I had been using did not mention any warnings about saving an amended photo.  I can start from scratch but would rather not. 

    Hi lushkie
    The process I outlined is so that you still have the psd file (with its layers) in case you want to do more work on it.  But you will also end up with a jpeg (also known as jpg) file to send or print etc.  To flatten means to flatten all the layers so that you just end up with one.  It may be that you only have one layer in the first place anyway - you can press f 11 if you want to check this and a box will pop up on the right to show you.  Pressing f 11is a toggle switch so you can hit, to hide, and again, to show.
    Anyway back to flatten.  Go to layers pull down menu and it is the very bottom item.  If you have layers showing then when you flatten you will see them all condense into one. 
    Barbara Brundage's missing manual is great.  Have been dipping into it quite a bit in the last month.  She is very thorough.  I love Scott Kelby's book on PE11 but he does not write much on layers whereas Barbara has heaps about them.
    From what I have seen in written form you have made the right choice with her book so stick with it. 
    Let us know how you get on.  If anything unclear come back with details.
    Good luck !
    Jim

  • Using the recompose tool

    What am I doing wrong? Using the recompose tool I highlight areas in green to keep and highlight areas in red for deletion but when I move the sliders everything is still in the photo. What am I missing?

    If you moving the threshold slider , then I would like to tell you that moving this slider decides how much recompose you want to apply to the photo. For eg 100% value of this slider means 100% recompose while a 0%  is equal to a simple tranform of the image.
    You have to drag the handle on the sides of image to apply recompose or you can also choose a preset from the preset dropdown in the option bar .

  • PSE 8 recompose tool

    I installed PSE 8 three days ago and I used the recompose tool. I am trying to use it now and it will not work. I try to color the items that I want to save with the green color marker and it does not show up. I select the red marker for the remove and it does not show up. I have reset all tools and it still does not work. I was going to try a reinstall but when you put the disc in it will only try to uninstall.Any help will be appreiated.

    I guess that I found the solution. For some reason the Bamboo Fun tablet works for everything except showing the color. I tried my regular mouse and it works fine for the color.

  • PSE8 question: Recompose Tool says "Program Error"

    And does not recompose. I tried this with an exercise photo from the DVD of Digital Classroom and with a photo of my own. What could be happening?

    Select the recompose tool then click the dropdown icon (top left under the blue PSE symbol) and choose reset tool.

  • Recompose tool will not work properly in 8.0

    I have tried using the recompose tool in 8.0 in multiple ways and it continues to distort the people in the photo that I have marked as save.

    Good day!
    If this relates to Photoshop Elements please post over at
    http://forums.adobe.com/community/photoshop_elements
    for example.
    If you are indeed talking about Photoshop CS please elaborate what you mean by "recompose tool" and maybe post a screenshot to illustrate the issue.
    Regards,
    Pfaffenbichler

  • PSE 9.  My crop tool disappeared, replaced by "recompose tool"

    I have tried a few things to get back the usual tool pallette, but all have failed, so far.

    I see that at the bottom right of some tool icon boxes there is a small black triangle, and I see one with the Recompose box.  However, when I clicked on it, an invitation to a tutorial came up, and I saw no way to get to "Tool Options."
    Then, almost haphazardly, I thought to right click on the Recompose tool which allowed me to select Crop Tool.

  • Internal hard drive/repair: SMART status; Disk Utility, Tech Tool & More

    machine: 12" PowerBook 1.5 GHz PowerPC G4 (Aluminium) with 80GB internal HD
    internal hard drive (original): Hitachi Travelstar 5K100 series HTS541080G9AT00
    hard drive firmware: MB4AA5AJ
    ATA version: 6
    ATA standard: ATA/ATAPI-6 T13 1410D revision 3a
    I have monitored the SMART status etc. of my internal drive with smartmontools for some time. Occasionally, I would see an error or a failed self-test but later testing always succeeded and things did not seem to be problematic.
    At the beginning of this week, I started to see a lot of failed self-tests (though some still passed), a rising number of bad ("pending") sectors and reallocation attempts (though no reallocated sectors) and various other errors. The computer seemed to have trouble reading from the disk at times and Carbon Copy Cloner reported two I/O errors when cloning (a later clone succeeded). fsck showed errors although running fsck -fy repeatedly seemed to resolve them.
    The Apple hardware tests initially reported an error (2STF/8/3:ATA-100 ata-6-Master) but I hadn't realised I should disconnect peripherals before running it so I did that and repeated the test which found no issues. I ran the extended test a total of three times with no errors.
    As I continued to have problems, I booted from my clone and had Disk Utility wipe the drive by writing zeros to it. (I thought trying to get it to write everywhere would either finish the drive off or force it to reallocate the bad blocks. As I understand it, in normal use, the drive won't reallocate the blocks unless it can recover the data in the hopes of reading it at a later time.)
    I then continued monitoring the disk using smartmontools. At this point, short self-tests succeed but extended self-tests "disappear". They don't fail, they simply vanish. They begin and smartctl shows the test in progress but then no error or result is logged - it is as if the test was never run. The first time I did this, I got an error saying the SMART attributes could not be read but subsequent tests do not trigger even an error. Short self-tests continue to pass.
    There are now (according to SMART) zero bad ("pending") sectors but zero reallocated sectors, which seems odd. The raw read error rate fluctuates (zero one minute, many thousands a while later) although I am not sure it did not do this before.
    Disk Utility claims the disk does not support SMART status even though smartctl clearly shows it does. Disk Utility claims the volume is "OK".
    I ran Tech Tool Deluxe 3.04 from CD and 3.1.1 from my clone. In both cases, I ran all available tests on the drive. No problems were found.
    I am seeing some problems even while booted from my clone - yesterday, the system froze completely and I had to force a shut-down by switching off the power (fsck then found a minor error but repaired it). Just before this happened, I was unable to mount a disk image and was trying to rectify the situation when the system froze. It is possible that the errors fsck corrected were implicated in the freeze, rather than caused by it, since Disk Utility found and repaired similar errors for the other two clones I have (on different partitions of my external drive - yes, I know this is sub-optimal).
    Here is some current output from smartmontools:
    ---output: smartctl -q noserial -a disk0---
    smartctl version 5.38 [powerpc-apple-darwin8.11.0] Copyright (C) 2002-8 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/
    === START OF INFORMATION SECTION ===
    Model Family: Hitachi Travelstar 5K100 series
    Device Model: Hitachi HTS541080G9AT00
    Firmware Version: MB4AA5AJ
    User Capacity: 80,026,361,856 bytes
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 6
    ATA Standard is: ATA/ATAPI-6 T13 1410D revision 3a
    Local Time is: Sat Jul 3 20:28:52 2010 BST
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 645) seconds.
    Offline data collection
    capabilities: (0x5b) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    No Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 55) minutes.
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 RawRead_ErrorRate 0x000b 100 100 062 Pre-fail Always - 0
    2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
    3 SpinUpTime 0x0007 142 142 033 Pre-fail Always - 2
    4 StartStopCount 0x0012 097 097 000 Old_age Always - 5793
    5 ReallocatedSectorCt 0x0033 100 100 005 Pre-fail Always - 0
    7 SeekErrorRate 0x000b 100 100 067 Pre-fail Always - 0
    8 SeekTimePerformance 0x0005 100 100 040 Pre-fail Offline - 0
    9 PowerOnHours 0x0012 039 039 000 Old_age Always - 26720
    10 SpinRetryCount 0x0013 100 100 060 Pre-fail Always - 0
    12 PowerCycleCount 0x0032 098 098 000 Old_age Always - 4168
    191 G-SenseErrorRate 0x000a 100 100 000 Old_age Always - 0
    192 Power-OffRetractCount 0x0032 100 100 000 Old_age Always - 201877487644
    193 LoadCycleCount 0x0012 001 001 000 Old_age Always - 2209599
    194 Temperature_Celsius 0x0002 141 141 000 Old_age Always - 39 (Lifetime Min/Max 16/46)
    196 ReallocatedEventCount 0x0032 100 100 000 Old_age Always - 194
    197 CurrentPendingSector 0x0022 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
    199 UDMACRC_ErrorCount 0x000a 200 200 000 Old_age Always - 0
    SMART Error Log Version: 1
    ATA Error Count: 2138 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    PoweredUpTime is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    Error 2138 occurred at disk power-on lifetime: 26716 hours (1113 days + 4 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    10 51 00 09 4f c2 a0 Error: IDNF
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
    b0 d6 01 09 4f c2 a0 00 08:30:04.500 SMART WRITE LOG
    b0 d5 01 09 4f c2 a0 00 08:30:04.300 SMART READ LOG
    b0 d1 00 00 4f c2 a0 00 08:30:04.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
    b0 d0 00 00 4f c2 a0 00 08:30:04.000 SMART READ DATA
    b0 da 00 00 4f c2 a0 00 08:30:04.000 SMART RETURN STATUS
    Error 2137 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 28 18 95 98 e4 Error: UNC 40 sectors at LBA = 0x04989518 = 77108504
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
    25 00 80 c0 94 98 e0 00 1d+01:30:37.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:30.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
    25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
    Error 2136 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 21 1f 95 98 e4 Error: UNC 33 sectors at LBA = 0x0498951f = 77108511
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
    25 00 80 c0 94 98 e0 00 1d+01:30:30.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
    25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
    25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
    Error 2135 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 22 1e 95 98 e4 Error: UNC 34 sectors at LBA = 0x0498951e = 77108510
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
    25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
    25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
    25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
    25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
    25 00 80 40 93 98 e0 00 1d+01:30:13.500 READ DMA EXT
    Error 2134 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 28 18 95 98 e4 Error: UNC 40 sectors at LBA = 0x04989518 = 77108504
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
    25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
    25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
    25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
    25 00 80 40 93 98 e0 00 1d+01:30:13.500 READ DMA EXT
    25 00 80 c0 92 98 e0 00 1d+01:30:12.100 READ DMA EXT
    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBAof_firsterror
    # 1 Short offline Completed without error 00% 26717 -
    # 2 Short offline Completed without error 00% 26717 -
    # 3 Short offline Completed without error 00% 26717 -
    # 4 Short offline Completed without error 00% 26717 -
    # 5 Short offline Completed without error 00% 26716 -
    # 6 Short offline Completed without error 00% 26715 -
    # 7 Short offline Completed without error 00% 26714 -
    # 8 Short offline Completed without error 00% 26697 -
    # 9 Extended offline Completed: read failure 10% 26692 75071682
    #10 Short offline Completed without error 00% 26687 -
    #11 Extended offline Completed: read failure 10% 26676 77108511
    #12 Short offline Completed: read failure 40% 26663 296917
    #13 Short offline Completed without error 00% 26657 -
    #14 Short offline Completed: read failure 10% 26646 296918
    #15 Short offline Completed: read failure 70% 26645 296905
    #16 Short offline Completed: read failure 10% 26644 296910
    #17 Short offline Completed: read failure 10% 26644 296910
    #18 Short offline Completed: read failure 40% 26643 296916
    #19 Short offline Completed: read failure 20% 26643 296909
    #20 Extended offline Completed without error 00% 26620 -
    #21 Short offline Completed without error 00% 26618 -
    Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum.
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENTTESTSTATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    ---end output---
    Self-tests 1-8 were all run after I erased the disk. The others were run before I did so. Not listed are the extended self-tests I've started since erasing which, as I say, have simply disappeared.
    The checksum error regarding the log is normal for this disk. At least, I've got that error ever since I started using smartmontools for monitoring so I assume it is normal. (I installed this version of the software in about April 2008 and have used it since.) Also, starting offline testing has never succeeded on this disk (I think I checked into this at the time but can't quite remember - this is not new, anyway).
    Questions
    how should I interpret all this? (Why does Disk Utility say SMART is not supported while smartctl clearly shows it is at the same time? Why do the extended tests simply vanish? Is the drive definitely dying?) I do not want to replace the disk unless I absolutely have to because I understand that replacing disks in 12" PBs is no small matter and cost is an issue. I do not want to replace the machine unless I have to because cost is an issue and, also, I really like this computer and have no idea what I would want in its place, even if expense were no obstacle.
    if it isn't clear whether the drive is dying or not, is there some further strategy I can use to establish this?
    if the drive is dying, is a machine of this age worth repairing and, if it is, under what circumstances is it worth doing so? For example, it might be worth doing if you can do the job yourself, but that might be quite impractical for non-expert (not to mention, inexpert) users.
    if there is a hardware problem (which I obviously think is very, very probable at this point), is it definitely a dying hard drive? (I've seen people write ominous things about disk controllers etc. which I gather are more serious - or less repairable - than a "mere" dying disk.)
    what questions should I be asking you and what are the answers to those questions?!
    Many thanks for your patience in reading this far.
    - cfr

    The 12" PB internals are a bit more complex, for PB's. If you don't want to replace the hard drive yourself or pay someone to install it, you could always get an external firewire hard drive, and use it to boot from and for general usage. Would have to be firewire, since the PB won't book from a USB device. One example of what you could get is a 160GB external hard drive: http://eshop.macsales.com/item/Other%20World%20Computing/MS4U5160GB8/ . All the choices with that case are listed here: http://eshop.macsales.com/shop/firewire/on-the-go
    Have you called any Apple Authorized Service Providers to see what they would charge to install a drive for you? Whether you bought it or they supplied it? You can find a local one in the US at http://www.apple.com/buy/locator/service/

  • PSE9 The crop/recompose tool is stuck on recompose

    I've tried to reinstall Elements 9 but its still stuck.  Its ok in PSE8.  Any idea how to fix it.  I can crop using the Image menu but if there is supposed to be a short cut then I prefer to use it.

    Don't hover. Click. The black triangle means that there is a group of tools in that slot in the toolbox. Many tools have this. You must either click and choose another tool to switch or tap the letter that appears when you hover (in parenthesis at the end of the tool's name) to switch to the other tools. If you do it that way, watch the icon for it to change to the one you want.

  • PS CS 5 Cursor sticking as hand tool-more discussion

    I just purchased a Macbook pro and also have an iMac.  Both are OCX 10.6.6, laptop is a clone of the desktop.  So why would I have the new issue of the cursor sticking as the hand tool only on the laptop?
    Rebooting does not help.  It seems that disconnecting the wacom and totally powering down is the only answer.  Is this an Adobe issue or Mac issue?  It's making me crazy.
    Cindy

    Maybe the thing PECourtejoie links to in the FAQ has some bering on the issue – mind you, that’s a »maybe«!
    http://forums.adobe.com/thread/784569?tstart=0

  • Content aware move tool and recompose do not work.

    Content aware move tool and recompose do not work. Nothing happens...What can I possible do wrong?

    There is not Content Aware Move or Recompose tool in Premiere Elements.
    Have you tried taking this question to the Photoshop Elements forum, Dion?

  • Recompose in PE 12

    I am trying to change a landscape 4x6 photo to a portrait 4x6 using compose in ps element 12 and it doesn't seem to work.

    Are you selecting the 4 x 6 preset to start with?
    Note though that using Recompose to convert 6 x 4 to 4 x 6 will most likely result in severe image distortion. I'd be more inclined to use the crop tool and crop to 4 x 6. You could go bigger if there are elements you want the recompose tool to get rid of during the process, but even then crop to something that is initially more portrait than landscape, before entering Recompose, for best results.
    Cheers,
    Neale
    Insanity is hereditary, you get it from your children
    If this post or another user's post resolves the original issue, please mark the posts as correct and/or helpful accordingly. This helps other users with similar trouble get answers to their questions quicker. Thanks.

  • My photos looks really bad when I try to recompose for a collage?

    why my photos look really bad when I try to use a recompose tool for put in a blank layer?
    Photoshop Elements

    Look under "More like this" on the right of this page, specifically "Re: no photo selected"; the discussion there may be of help.

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

  • Problem with recompose in PSE 11 trial version

    I am trying to determine whether to purchase PSE 11. I currently solely use Lightroom 4. I have attempted to use the recompose tool several times on several different pictures marking different things and generally have failed results. On the odd occasion that part of the photograph is saved, it is the part I have painted red. I am not saying that the problems with recompose is a deal breaker for purchasing the software, but this was one of the tools I really liked (at least the idea). Someone please enlighten me. Oh, and I am using a duplicate background when trying the recompose tool.

    The green areas are protected areas. That's what gets saved if you have protected all the important features.
    Take a look at this video tutorial.
    http://tv.adobe.com/watch/learn-photoshop-elements-9/using-the-recompose-tool/

Maybe you are looking for