David's profileDavid Moisan's ITPhotosBlogLists Tools Help
    December 09

    Vista tip: Using the DiskPart Command to Create a Bootable USB Flash Drive

    Hat tip to Philip E. for this one!

    One often needs to flash a BIOS with a boot disk.  Back in the day, this was done with floppy disks, but there are more and more problems in doing this.

    For one, many BIOS images will not fit on a 1.44M floppy;  at best, you need two floppies, one to boot and one to hold the image.  (Similar to the old Linux boot/root floppy pair.)  Secondly and most importantly, the floppies are slow and none too reliable.  I have never bricked a computer from a bad BIOS flash and I would not miss it if I were to never experience this!

    HP had a utility that would let you make a USB disk bootable if you provided a boot floppy (such as one made in XP), but it seems to have disappeared from their site.  The utility can be found here:  http://www.bay-wolf.com/usbmemstick.htm.

    But Vista has an easier way.  The diskpart utility now supports flash drives!  From a command prompt do:

      • On a Vista system plug in the USB flash drive to an available USB port (ReadyBoost compatible is best)
      • Start-->diskpart [Enter] (UAC Prompt)
      • list disk (USB flash drive will show in the list - Disk 1 for this example)
      • sel disk 1
      • clean
      • create par primary
      • sel par 1
      • act
      • format fs=fat32 (note that USB HDD's will need to be NTFS)
      • exit

    You'll then have to copy system files from the floppy (MSDOS.SYS and COMMAND.COM), plus any files you need to flash.  I have one USB stick that I keep a boot sector on to use for flashing machines.  (I don't routinely reformat any of my USB sticks.)

    Original:  MPECS Inc. Blog: Windows Vista - Using the DiskPart Command to Create a Bootable USB Flash Drive

    Comments (1)

    Please wait...
    Sorry, the comment you entered is too long. Please shorten it.
    You didn't enter anything. Please try again.
    Sorry, we can't add your comment right now. Please try again later.
    To add a comment, you need permission from your parent. Ask for permission
    Your parent has turned off comments.
    Sorry, we can't delete your comment right now. Please try again later.
    You've exceeded the maximum number of comments that can be left in one day. Please try again in 24 hours.
    Your account has had the ability to leave comments disabled because our systems indicate that you may be spamming other users. If you believe that your account has been disabled in error please contact Windows Live support.
    Complete the security check below to finish leaving your comment.
    The characters you type in the security check must match the characters in the picture or audio.

    To add a comment, sign in with your Windows Live ID (if you use Hotmail, Messenger, or Xbox LIVE, you have a Windows Live ID). Sign in


    Don't have a Windows Live ID? Sign up

    xanadu.dmwrote:
    thanks for the suggestion.

    We had this problem on ISA Server 2006.
    The suggested workaround didn't work however with the ISA monitoring tool I figured out it was a rule who blocked the execution of WMI scripts.
    To solve this problem:

    Right-click the rule which caused the problem, in our case this was 'Allow all access to ISA except browsing'
    Chose 'Configure RPC protocol' and uncheck ' Enforce strict RPC compliance'.
    19 Dec.

    Trackbacks

    The trackback URL for this entry is:
    http://dmoisan.spaces.live.com/blog/cns!95CB015E3E4A702A!281.trak
    Weblogs that reference this entry
    • None