Windows to USB - Windows to Go

This topic has kinda merged with another topic referring to another program already available and supported here..

http://theoven.org/index.php?topic=1236.msg14538;topicseen#msg14538

Although that topic has gone more by way of multi-boot VHD's which is not supported prior to win 7

The possibility is there (if you care to test for yourself ) to create a bootable usb drive with XP and Vista by Appling the install.wim to the usb and making the usb drive bootable...
As noted above by the wintousb website link there may be and are known issues with drivers and such..

Using the WinNTsetup program (utilities plugin) we have been able to create a bootable full windows environment on a portable usb drive..

Some of us may have more time to spend on testing and some have very little time - but we seem to enjoy working with what time we have...

This differs from the builder project(s) for which this forum is about..
And I thank those who have allowed me to continue with this topic and also for providing support to this topic...

Kyhi

This differs from the builder project(s) for which this forum is about..

not much 
 in the end you create a final product in a project way...

Lets differ projects with applications,
Windows to Go  , WinNTsetup  are applications having human readable gui and automatic ways, one do something other do other things, like all applications of same goals,
 projects also gives options easly to be accessed via human readable gui,
  and more important, they are verrrry expandable + contributable, and you can control each step, and you can learn how stuff works 
    on the other hand applications have full control of author, which author more easly decides and stricks how things should work..

Well both ways have advantages disadvantages 
 maybe later with another builder...... 

This differs from the builder project(s) for which this forum is about..

No, the forum is not only for the builder project(s)
Windows to USB, Win To-Go, WinNTsetup are really interresting subjects and are of course welcome 
The use of WinPE, Win to USB, Win To-Go is different with advantages and disadvantage. I have not tested, WinXpese, Gena in vhd is perhaps interresting, also.
So far, I have not participated, free time is not expandable but I support 

Some of us may have more time to spend on testing and some have very little time - but we seem to enjoy working with what time we have...

when combined you can get both the best of both worlds.. WinPE with lightweight unrestricted disk access..

Just have to add entry for WinRE boot.wim (ram-disk) to Win-USB bootmgr

Can also capture attached VHD dir to wim (smaller file) and use as backup or VHD recovery image

I pre-prep my windows 8 wim files (same as using MS SIM) I import drivers and key so as to have just a clean activated install.wim

I can then apply that install.wim to system drive or vhd..

Off Topic...

Most touch tablets require drivers to be pre-installed just to use the device before you can even consider running windows setup..
So I also import the drivers into the boot.wim - which is actually the winre.wim found in windows - I do not run windows setup anymore with win8

I boot a custom windows 8 recovery environment usb

7MB worth of boot files and a prepared boot.wim and install.wim (I edit resetconfig.xml and resetpartitions.txt to tell it, what, where and how to..
 

The imageprep script I use was included in a download link I provided prior in this thread - but was edited to bypass certain features not supported prior to win 8..

This method of setup is known as > Bare Metal Reset < https://technet.microsoft.com/en-us/library/hh824896.aspx

when combined you can get both the best of both worlds..

Which already is :)

WinPE with lightweight unrestricted disk access..

a project do not have to be a PE 

+
my recent (today) experience with pre integrating all drivers from dps http://driverpacks.net result a lot o time loss..
so target specific integration maybe better :)
or installing drivers after boot 

I haven't play with tablets yet, only using them 

+
as Chris underlined,
forum is not only for PE or builder projects,
 there are lots of tools also inside projects, some have topics,
  Do you need some nice android/ios application http://theoven.org/index.php?board=28.0
   etc.
besides focus remains on improving current projects 

shortly we had bad experiences on public forums, we created this one to spend and share with our available free time (at first forum created to develop project),
 with passing time we organised forum so that anyone can share the way one likes on a forum, without annoyance.

when combined you can get both the best of both worlds.......

Others, prefer boot.wim and have an image that does not change for rescue, recovery.

I would look when I have a little more spare time.
you seem to have a bit more time than me and more Advanced.
If you have an idea on how to add vhd option on project with a plugin, I would be happy to add, then 
I have not yet done, I must look at your imageprep plugin whenever I can 

Chris, I seen somewhere a multi-boot plugin that had like adding 4 or 5 ISO's >  VHD ?? (I thought) in Finals, writemedia or utilities

and adding the boot.wim to win-usb would not change the boot.wim as it is in ram . constant recovery image, run recovery apps..

How that would effect a case of having an X and Y drive for recovery > something tells me it would not be an issue either..
As your VHD's would be on Y - same as recovery apps in "program files" folder
When USB has booted boot.wim to X the program folder would be there (same as Project)

Only difference in USB would be when booting usb you would then have to select between recovery (boot.wim) or Full system VHD ( USB Size limitation)

Imageprep is not a plugin, but a .cmd batch (you can make plugin)
after PROCESSING THE FINAL STEPS FOR THE INSTALL.WIM remove remark and remark other

Note: you need to use an install.wim to prep your images ( as you can not "mount" an install.esd )
Createwimiso creates the install.wim by using the downloaded MS Payload (which MS uses to create it's setup media, but MS makes an install.esd) for which does not help us if we want to prep the install image

I do not code - I can follow code.. Although can now dabble a little bit more in this project - but still use a lot of C/P.. I know what I want it to do, just getting the proper coding to do it, is my slowly issue..
I mostly help with setup and recovery issues > via command line options.. And up until this projects GUI (January) did everything from a blank screen and black window..

Actually I have several batch files I would like to create a program.exe with a GUI to be able to change certain variables (disk #, partition size, partition layout.. WinNTsetup does the setup and apply part - if one could add the disk partitioning and layout options - that would be super..

Success was able to Combine both Win-Usb and Win81SE on the same USB - usb now offers to boot SE Project Recovery (boot.wim) and windows 7 / 8 /8.1 full system vhd's > both legacy x86 x64 and UEFI x64

Created a Win81SE os-to-ram project to the win-usb, copied WinNTsetup VHD's to win-usb,
mounted x86 VHD and used cmd > bcdboot VHD:\Windows /s USB: /f BIOS
mounted x64 VHD and used cmd > bcdboot VHD:\Windows /s USB: /f ALL
Booted PC both efi and legacy > both booted VHD - due to No display boot menu option in Win81se bcd
Add displaybootmenu option to both bootmgr and bootmgr.efi > bootice = working Win-Usb w/winse
Edit this under SE winloader from > bootmenupolicy          Legacy (to Standard)
Success - Booting Win81SE boot.wim into legacy and UEFI

  

  http://theoven.org/index.php?topic=1236.msg14618#msg14618

Enjoy!!
Kyhi

Code: [Select]

//-- Post Config edit
//-- x86
ShellExecute,Hide,%BcdEditExe%,"/store #$q%TargetDir%\Boot\bcd#$q /set {bootmgr} DisplayBootMenu 1",%Tools%\%OSArch%\
ShellExecute,Hide,%BcdEditExe%,"/store #$q%TargetDir%\Boot\bcd#$q /set {default} bootmenupolicy Standard",%Tools%\%OSArch%\
//-- x64
ShellExecute,Hide,%BcdEditExe%,"/store #$q%TargetDir%\efi\microsoft\Boot\bcd#$q /set {bootmgr} DisplayBootMenu 1",%Tools%\%OSArch%\
ShellExecute,Hide,%BcdEditExe%,"/store #$q%TargetDir%\efi\microsoft\boot\bcd#$q /set {default} bootmenupolicy Standard",%Tools%\%OSArch%\

One Note: After you get your Win-Usb the way you want it - by adding VHD's and editing BCD's

BACKUP THE WINSE-WIN-USB BOOT FILES and keep a Backup of your VHD's



Had to Rename the Mission: WINSE-WIN-USB

If you have an idea on how to add vhd option on project with a plugin, I would be happy to add, then 

the plugin is rather simple steps
My process was to write project to usb then copy to and register vhd's

lance posted a batch file to locate the vhd - which could be helpful to create bcd registration before writing project usb
And copy over all at once - would have to find usb free space to insure project and vhd fit..

[Main]
Project=source wim
MainConfig=WinPE,OSRam,OSVHD
If,osvhd,create,attach,targetvhd
set,targetdir,targetvhd
Images Config=apply,project,targetvhd

[Build]
retrieve tool
retrieve localized info
Macro library
//- all others present in project

[Shell]
Classic Shell,targetvhd

[Components]
remove,component,targetvhd
remove,component,targetvhd
make smaller,targetvhd

[Tweaks]
WinNTsetup,tweaks,targetvhd
Classic Shell,tweaks,targetvhd

[apps]
apps,targetvhd

[Drivers]
Accesgain,targetvhd
Driver integration,targetvhd

[Finals]
Optimize,compact,targetvhd
Pins,targetvhd
MakeShortcuts,targetvhd
Detach,targetvhd
PostConfig,Write,targetvhd,bcd

[VirualTest]
VMPlayer,targetvhd

[WriteMedia]
Copy to USB, BCD Bootmgr

Good luck on your project, have fun 

When you decide a project name (folder), ex: WinVHD

Using
Gena\Share Plugins -->  Enable "Custom" Checkbox --> fill empty box wih: WinVHD --> click 'Share Plugins With'

and you can continue creation of new project 

edit:
take script.project from Win81SE, demo one above is very old 

There is something wrong with the v2 plugin... When the program launched from script - it does not proceed without errors and/or stops responding. although did recover and finish.. But, Windows Disk Management also fails to populate and thus can not detach VHD..

hmm, interesting ... I feel you find another winbuilder bug 
here is an update candidate
https://www.dropbox.com/s/bekhp995mijpdri/WinToUSB_M_201503151507.7z?dl=0

btw, better update first post of current topic and gather things nicely 

See You