joakim Posted November 4, 2010 Share Posted November 4, 2010 For those interested in the details, it can be found here; http://forum.sanbarrow.com/viewtopic.php?f=85&t=15The point is to modify bootmgr so that the wim header gets patched in memory after it is read by bootmgr. It is a proof of concept, and not very elegant. It is required to know your target wim and the images inside it. When you know that, you can put the magic bytes inside menu.lst and map bootmgr to the rd device and patch it there. Well, read the thread and get the details. The point is it is possible to boot off any image inside your wim. It does not have to be specified as the boot image in the wim header. Joakim Link to comment Share on other sites More sharing options...
jaclaz Posted November 5, 2010 Share Posted November 5, 2010 (edited) The point is to modify bootmgr so that the wim header gets patched in memory after it is read by bootmgr. It is a proof of concept, and not very elegant. It is required to know your target wim and the images inside it. When you know that, you can put the magic bytes inside menu.lst and map bootmgr to the rd device and patch it there. Well, read the thread and get the details. VERY nice. Some details about the uncompressed BOOTMGR and if a given version is needed may be of help so that other people can experiment with your findings..... Just for the record, your post is on sanbarrow's "new" boardhttp://forum.sanbarrow.com/index.phpbut previous posts/topics are on the "old" board here :http://sanbarrow.com/phpBB2/index.phpjaclaz Edited November 5, 2010 by jaclaz Link to comment Share on other sites More sharing options...
joakim Posted November 5, 2010 Author Share Posted November 5, 2010 Here's the link to the thread where information can be found on how to get uncompressed bootmgr; http://sanbarrow.com/phpBB2/viewtopic.php?t=1696 If you for some reason want to experiment with decompressing/recompressing the original, you will also find a post there with a link to a tool that can do so. Basically you just grab bootmgr.exe (otherwise known as pxe version) remove some unneded bytes to reduce its size and attach an older vista sp0 stub. Oh and you will need to patch some integrity checks as well so that the modified bootmgr will load without complaints. That is 1 checksum check in the stub as well as the selfintegrity check in bootmgr (validating the digital certificate). There's many ways to solve this, but the one I'm currently using is by patching in two nops (9090) at VA 421EC5.Joakim Link to comment Share on other sites More sharing options...
joakim Posted November 6, 2010 Author Share Posted November 6, 2010 The referenced thread (first post) now contains complete descriptions with lots of details, as well as my sample menu.lst covering 4 different images. I would say it's now a fully working solution.Joakim Link to comment Share on other sites More sharing options...
jaclaz Posted November 6, 2010 Share Posted November 6, 2010 The referenced thread (first post) now contains complete descriptions with lots of details, as well as my sample menu.lst covering 4 different images. I would say it's now a fully working solution. jaclaz Link to comment Share on other sites More sharing options...
joakim Posted November 7, 2010 Author Share Posted November 7, 2010 JFX has provided an excellent tool to generate your menu.lst based on a target wim.Joakim Link to comment Share on other sites More sharing options...
jaclaz Posted November 12, 2010 Share Posted November 12, 2010 (edited) Just to keep things as together as possible :http://www.boot-land.net/forums/index.php?showtopic=8043&st=131http://sites.google.com/site/rmprepusb/tutorials/multi_boot-wimIt is possible to have 4 different boot.wim files (say Vista x86, Vista amd64, Win 7 x86 and Win 7 amd64) all on the same USB drive and a grub4dos menu.lst menu file that will allow you to boot to any one of them (see tutorial #2). However, wouldn't it be nice if you could combine these four boot.wim files into one single boot.wim that contains four images? Well some very clever people have now made this possible. This tutorial assumes you know how to use ImageX and have a number of boot.wim files that you want to combine into one boot.wim file. It is taken from this post by joakim and uses a great tool made by JFX - all credit to these guys! jaclaz Edited November 12, 2010 by jaclaz Link to comment Share on other sites More sharing options...
joakim Posted November 12, 2010 Author Share Posted November 12, 2010 And if you're looking for updates on the topic (or details), then follow the main thread; http://forum.sanbarrow.com/viewtopic.php?f=85&t=15 Joakim Link to comment Share on other sites More sharing options...
CtrlSoft Posted January 25, 2011 Share Posted January 25, 2011 can you write a step-by-step guide?thx Link to comment Share on other sites More sharing options...
jaclaz Posted January 25, 2011 Share Posted January 25, 2011 can you write a step-by-step guide?thxWhat do you think this is? http://sites.google.com/site/rmprepusb/tutorials/multi_boot-wimjaclaz Link to comment Share on other sites More sharing options...
CtrlSoft Posted January 25, 2011 Share Posted January 25, 2011 (edited) can you write a step-by-step guide?thxWhat do you think this is? http://sites.google.com/site/rmprepusb/tutorials/multi_boot-wimjaclazI did not getI'm trying to make a bootable ISO.Resolved! thank you for tutorial! Edited January 25, 2011 by CtrlSoft Link to comment Share on other sites More sharing options...
CtrlSoft Posted January 26, 2011 Share Posted January 26, 2011 (edited) hellotell me please, how i can modify wimpatched to use multiple bcd (as here http://sites.google.com/site/rmprepusb/tutorials/how-to-create-a-usb-drive-that-will-install-vista-win7-and-server-2008 )it does not work with Windows 7 (SP0/SP1) ((zbootmgr http://img209.imageshack.us/img209/419/screenshot20110125001.pngoriginal bootmgr also not supportedI want to do this:grub -> menu.lst -> wimpatched1 -> \boot\bc1 ...grub -> menu.lst -> wimpatched2 -> \boot\bc2 ... Edited January 26, 2011 by CtrlSoft Link to comment Share on other sites More sharing options...
joakim Posted January 26, 2011 Author Share Posted January 26, 2011 It should be even easier with my custom version as it is not compressed, unlike the original bootmgr. The tools you refer to in that referenced thread will thus not work on my version as the offsets are hardcode in the program. Since I don't have the file at hand at the moment, I can't really say at which offset you must modify. But I will get back to it. Otherwise, just open the file in a hexeditor and search for the string boot\bcd for which you can modify to your likes. I've tried paths like 1\a\2\b with success in the past, which means you are not restricted to the boot folder. Joakim Link to comment Share on other sites More sharing options...
JFX Posted January 27, 2011 Share Posted January 27, 2011 it does not work with Windows 7 (SP0/SP1) ((zbootmgr http://img209.imageshack.us/img209/419/screenshot20110125001.pngoriginal bootmgr also not supportedWell that bootmgr BCD changer ONLY support original bootmgr files.CRC of bootmgr from Windows 7 SP0 is: EE471B58, if your's if different from this, it's not original or not a RTM version.SP1, hmm it's not released and therefore not supported.As joakim said just search the string in the modify wimpatched one and adjust it to your like. Link to comment Share on other sites More sharing options...
CtrlSoft Posted February 1, 2011 Share Posted February 1, 2011 (edited) please tell me how to add sata drives support to my menu?I tried the following but not working:i cdrom --add-io-ports=0xE800EA00cdrom --initcdrom --add-io-ports=0xEA00E800cdrom --initmenu.lst: timeout 20default 0gfxmenu /boot/splash.gzcolor light-gray/black yellow/green light-cyan/black light-green/blacktitle [1] Boot from HDDfind --set-root --ignore-floppies --ignore-cd /bootmgrmap () (hd0)map (hd0) ()map --rehookfind --set-root --ignore-floppies --ignore-cd /bootmgrchainloader /bootmgrtitle [2] Microsoft Windows 7 Ultimate x86 >>root (cd) configfile /boot/x86.lsttitle [3] Microsoft Windows 7 Ultimate x64 >>root (cd) configfile /boot/x64.lsttitle [4] Microsoft Windows Recovery Environment x86map --mem /boot/wim86 (rd)write --offset=0x654C4 (rd)+1 \x14\xAF\x0D\x00write --offset=0x654CC (rd)+1 \x6E\x9F\x14\x0Bwrite --offset=0x654D4 (rd)+1 \xA8\x1B\x44\x00write --offset=0x654DC (rd)+1 \x06\x00\x00\x00chainloader (rd)+1root ()title [5] Microsoft Windows Recovery Environment x64map --mem /boot/wim64 (rd)map --hookwrite --offset=0x654C4 (rd)+1 \xD6\xE0\x0D\x00write --offset=0x654CC (rd)+1 \xD5\x21\x7F\x0Cwrite --offset=0x654D4 (rd)+1 \x08\xDF\x45\x00write --offset=0x654DC (rd)+1 \x06\x00\x00\x00chainloader (rd)+1root ()title [6] Acronis Disk Director Homefind --set-root /boot/ADDH.iso map --mem /boot/ADDH.iso (hd32) map --hook chainloader (hd32)boottitle [7] Acronis True Image Homefind --set-root /boot/ATIH.iso map --mem /boot/ATIH.iso (hd32) map --hook chainloader (hd32)bootthx Edited February 1, 2011 by CtrlSoft Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now