Since I deployed my HP Proliant Microserver, I had been running ESX from a USB flash drive. Now that Windows 8 Beta is available, I wanted to test out some of the new Hyper-V features in my home lab. All the talk about Windows To Go had me thinking it would be a good test to run Windows 8 Hyper-V server from a USB flash drive. After all, deploying Microsoft Hyper-V Server 2008 R2 on a USB Flash Drive was already supported.
I found a good tutorial about running Windows 8 Developer Preview from a UFD which outlines the process. If you’ve used WAIK before, then you’re familiar with the process which basically involves creating the partitions on disk, and then applying a WIM file to the partition. This process works great for Consumer edition on many UFD’s, however, Windows To Go is not supported with server edition. That doesn’t mean Windows 8 Server cannot be installed to a UFD though – it just means that the same rules apply as 2008 R2.
Specifically, the UFD needs to have it’s Removable Media Bit set to 0. This is a setting in the UFD’s controller that tells Windows how to treat the device. Typically, when you attach a UFD, Windows classifies the device as a Removable Disk:
There’s a couple of limitations that come with Removable Disks in Windows though. Specifically, you can’t create multiple partitions on them (even if you do via other partitioning methods, Windows will only show you the first partition), and you can’t run Windows directly from them. So, in order to deploy Windows 8 server to a UFD, the RMB needs to be set to 0.
Some UFD manufacturers provide utilities to set this. Lexar has the BootIt utility for instance. This utility may work for UFD’s manufactured by others provided it’s using the same controller. After some searching, I came across and excellent thread that described how to flip the Removable Media Bit for non-Lexar UFD’s. The ChipGenius and USBDeview utilities will give you detailed information about the Controller in the UFD:
This tool provides a few critical pieces of information: The Chip Vendor, Part Number, VID and PID. Using the VID and PID, you can find out if there is a tool available that will allow you to program the UFD controller. Head over to the Russian site flashboot.ru (I recommend using Chrome and you can auto-translate the page) and enter your VID and PID. This will list all known UFD’s matching those ID’s and let you know what utility you can use to program the controller, as well as helpful hints from other users. In my case, the Patriot XT Rage 16GB UFD showed up in the list:
In my case, I needed to use Phison’s MPALL tool (version 3.20) to program the Phison PS2251-38 controller on the Patriot XT Rage 16GB UFD. FlashBoot.ru has a catalog of all utilities for Phison controllers and I was able to easily download the necessary version. Inside the MPALL archive, you’ll find a few utilities. The first is GetInfo which displays current configuration of the controller:
The second tab has partition information:
Notice the Fixed Disk setting of “No” – this is the RMB on Phison controllers. All that’s necessary is for us to update that using the other utilities in the archive. It took some testing/tweaking to figure out how things work with the Phison USB Mass Production Tool, and admittedly I’m a bit fuzzy on the specifics. However, it looks as though there are two controller configuration sections that need updating: F1 and F2 (I haven’t been able to find what these mean, but they seem to be common to all UFD’s). There are two Parameter Editor utilities that generate INI files that can then be used by the flash utility, one for the F1 configuration (writes to a MP.INI file) and one for the F2 configuration (writes to the QC.INI file). In here, we can set the UFD to be a Fixed Disk:
You will find all of the necessary information from the GetInfo screen for the Controller, FC1-FC2 settings, the VID and PID’s, etc. Once you have your settings in place, hit save to write them to the MP.ini file. From there, you can use the MPALL F1 utility to write the configuration to the UFD. When performing this procedure, ensure that ONLY the UFD you want to program is connected. Insert the USB flash drive, click the Update button which will populate the various boxes with ANY UFD found that has a Phison controller. Once it’s detected, click Start to program.
Once F1 is done, you’ll need to do the same for F2. I was unable to get it to successfully update the F2 settings using any of the versions, however, even though the MPALL F2 utility reported an error, GetInfo did show that both F1 + F2 where set on the controller after the update. A few notes that may save you some time:
- I’m not sure where the “MAPPING” setting comes from, but when I created my MP.INI and QC.INI files using the ParamEditor utilities, the MPALL utilities would not find my UFD. I had to add MAPPING=0 to the Configuration section of both files.
- The Inquiry Version of my UFD was PMAP to start and though I had it set in MP.INI, the MPALL F1 utility changed to to DL07. Because of this, my QC.ini had to have Inquiry Version set to DL07 in to avoid a Incorrect Inquiry Version error message.
Once this is done properly, the partition will show as a fixed disk:
Now that we have a UFD with the RMB set to 0, we can proceed with deploying Windows 8 to it. Obviously, the FAT32 partition the pre-format created won’t work for Windows 8, so we’ll need to clean out that information. We’ll use diskpart for this – run the following commands from a command prompt:
select disk X
create partition primary
format FS=NTFS quick
This will delete the existing partition table, create a new primary partition and mark it as active and then format it as NTFS. Now, we can use the imagex utility (available as part of the WAIK) to apply the install.wim file to the UFD. Either mount the ISO or insert the DVD and apply the image to the UFD:
imagex /apply F:\sources\install.wim 4 G:\
The number 4 is the index of the image in the WIM file to be applied. The Windows 8 beta media has multiple available (Standard Core, Standard w/ GUI, Datacenter Core, and Datacenter w/ GUI) so I’m applying Datacenter w/ GUI by selecting index 4. You can read the available options by using the imagex /info F:\sources\install.wim command. Once the image has been applied, we need to write a boot record using bcdboot:
bcdboot G:\windows /s G:\
If you’ve done everything correctly, you should now have a bootable UFD with a base install of Windows 8 Server that is recognized as a non-removable hard disk:
this helped me out a lot since i got a new usb flash drive only to find out that it is “not compatible” with portable workspaces. unfortunately my flash drive has a phison 2551-67, which isnt supported by any verseion of MPALL i can find.
2251-67 needs version 3.6 of MPAll
Do you how to format back to Removable Disk?
after I did the Fixed Disk format, I use back the MPAll tools, it not able to detect my driver ><
To set it back, you should just need to update your INI file for the F2 configuration and select “Removable Disk” instead of fixed disk.
This page has helped me in the past, but now I have a new USB drive with Phison 2251-67 Controller, which I can not find. Any have ideas?
You need version 3.6 of MPAll to work with the 2251-67 controller.
Pingback: Corona v2 4GB al "microscopio" - Pagina 3
I have a Phison IC 2251-03 in a patriot Supersonic XT Rage 32GB USB 3.0 drive that I’d like to set Fixed. Any ideas on the MPALL version? I couldn’t find one that had that particular type.
I’m not certain the specific version, but you can try using the latest available – they should be backwards compat.
You’ll need at least Phison MPALL v3.62.00.
If there’s something like a “IDBLK file Version check error”, try to add the dll’s version number to the settings.
I’ve tried MPALL v3.63,It’s not working , I get 0 passes everytime in the testing counter
Thanks for this tutorial.
I have a Toshiba Suzaku pendrive with Phison 2251-03 controller that stopped working.
MPAII couldn’t find my device until I read this”I had to add MAPPING=0 to the Configuration section of both files.”.
Toshiba totally screwed it up. It’s unacceptable to lose access to pendrive’s data because of some programming error in firmware.
I have a patriot Supersonic 128GB and your guide has allowed me to make the drive useful. Thank you so much
in case anyone else has on I used the Phison_MPALL_v3.63.0C-DL17 and only had to flash the F1
This just killed my good old 8GB Patriot!
Same controller as in example.But using these tools ist just not as easy as this page makes it look!
there’s a hugelack on information for hundreds ofparameters,, and the tools themselves are more than obscure to use!
I tried following the information as close as possible, but it didn’t help. Yo need five times more information than the GetIngo tools deliversand this manual doesn’t give this information, too.
My stick is still recognized as USB device, but neither the get info, nor the flashing tools will find it anymore when inserted!