WinPE + DD11 + TIH2010 created but DD11 fails to start - localhost problem (SOLVED)
I finally managed to create my WinPE ISO with DD11 & TIH2010 along with a few other tools I needed. BUT, DD11 fails to start with "cannot connect to localhost". Any ideas?
I know it can work because I used DD11's boot media creator to "automatically" create an ISO with only DD11 and that worked.
The approach I took was to start with a stock boot.wim file and let TIH2010's WinPE ISO builder add TIH to that .wim file. Then I moved that file back into ISO\Sources to become the new stock boot.wim file. Next I used DD's Bootable Media Builder to add DD11 and create yet another .wim file. Then I moved that file back into ISO\Sources and ran the WAIK tool to create the ISO.
The resulting disk boots and everything works except for DD11. I'm almost there!
The localhost sounds like a config problem but I'm not sure where to look. I added DD after TIH so if any conflicts were to occur, I would have expected TIH not to run - but it works fine.

- Log in to post comments

I am making a special WIM.
DD11's media builder doesn't provide any options for what to put in the image. If you have TIH it reports that it will be included but that's not the case. Using my method above I got them both in the image.
I'm currently comparing the standard DD11 image that works to my custom version.
- Log in to post comments

The working DD11-only image contained some updated snapman.sys and snapapi.dll files that were newer than those in my non-working image. It also contained shfolder.dll. After mounting my custom .WIM file and placing the newer files in their proper locations I now have a custom WinPE with TIH 2010 & DD11.
In creating the custom image I started with TIH and then added DD11. But for some reason the new and updated files above did not get added when I ran DD11's media builder. I didn't write all this down originally so I could have done it in reverse. Even if that were the case, my custom .WIM never had shfolder.dll so DD11's media builder should have added that.
It would be nice if Acronis could just fix DD11's media builder to actually add TIH to the .WIM - which I could then mount and customize - saving me grief when the next update comes along and I want to update my WinPE.
- Log in to post comments

It's a shame if the WinPE media builder for DD11 doesn't allow making a .WIM file like the TI WinPE builder. I manually put DD10 into a TI2010 build .WIM. At this point, I have no desire for DD11, since what I want most from DD10 (disk editor, partition hiding) won't appear for a while, so DD10 and TI2010 on a WinPE ISO meets my needs well.
- Log in to post comments

Gary Darsey wrote:At this point, I have no desire for DD11, since what I want most from DD10 (disk editor, partition hiding) won't appear for a while, so DD10 and TI2010 on a WinPE ISO meets my needs well.
Have you heard?
# Added in Update 1: Acronis Disk Editor.
# Added in Update 1: Change file system: FAT16 to FAT32 and back, Ext2 to Ext3 and back.
# Added in Update 1: Hide/Unhide volume.
# Added in Update 1: Change cluster size.
# Added in Update 1: Split dynamic volumes
# Added in Update 1: Change space per i-node
# Added in Update 1: Clear disk
# Added in Update 1: Ability to install and activate OSS from bootable media
Time to update my bootable recovery media. I wonder if the WinPE media builder will now be able to add both TIH and DD.
- Log in to post comments

rkh wrote:Time to update my bootable recovery media. I wonder if the WinPE media builder will now be able to add both TIH and DD.
NOT. Had to do it the hard way again. First I had to buy the 2011 Plus Pack, DD11's media builder still lies - telling you TIH will be included in the image but it's not. Then I used a standard .wim image as the source and used TIH 2011 Plus Pack media builder to add TIH 2011 to it. I did this first because DD11 has some newer drivers that both programs use - snapman.sys and snapapi.dll.
Next, using the newly created .wim above as the source, I used DD11's media builder to add DD11 to it. Then I had to mount the .wim and add the shfolder.dll to windows\system32 - otherwise DD will not run. Then I close the .wim and commit the changes. Finally I create the ISO and boot it.
- Log in to post comments

The easiest way I've found is to do it the other way round! This way avoids doing any manual messing around with WIMs.
I have managed to build a combined WinPE 3.0 ISO with both DD 11 (Build 2121) & TI 2011 with Plus Pack, as follows:
(1) Install WAIK but don't bother to run _anything_ on it - no need to do any "copype" business or anything after installing it.
(2) Install DD 11, TI 2011, & then TI 2011 Plus Pack (obviously!).
[I did 1 & 2 with a Win7 virtual machine, but I think WAIK doesn't cause much mess, so it probably wouldn't hurt to do it on a standard installation.]
(3) Run the DD "Run Bootable Media Builder". As long as WAIK is installed, you can then choose "Bootable media type" as "Windows PE"; leave is set to "Create Windows PE2.x or 3.0 automatically"; "Next"...
(4) Wait as a command window opens and builds a WIM image. You then get to a dialog where you can add drivers. I haven't tried using this. Next .. & then choose "ISO image". Choose a name, => "Next" => "Proceed", & then have a long wait.
As before, just before "Proceed", the DD builder says it will add TI as well - but it doesn't. So we add it next:
(5) Extract all the files from the ISO into a new folder. (As I was using a virtual machine, I just copied the ISO file to the main machine, then mounted it in the virtual machine & copied out the files.) Don't worry about losing "bootability" - the next stage puts this back.
(6) Start the TI 2011 Plus Pack "Acronis WinPE ISO Builder". You then need to "Specify a path to the folder with the WinPE files" ... obviously you just specify the folder where you extracted the ISO files in (5).
(7) "Next" - leave it at "Add components and build an ISO" - then "Next", choose a name for your final ISO, "Next" => "Proceed" .. & hopefully there you are.
When you start a machine with the resulting ISO (& press a key when prompted), it should then (eventually) start a command window, then open DD & TI in turn. (You don't get a neat menu for them, as with the Linux versions.) But you can minimise or close either the DD or TI windows, & use the command window as needed, including to restart DD or TI if you need to.
I've no idea which snapman.sys, snapapi.dll & shfolder.dll versions I end up with - all I can say is that the ISO seems to work in a variety of laptops & desktops without apparent problems.
- Log in to post comments

I found the solution to my shfolder.dll issue described above. When using DD11's Bootable Media Builder I chose the create automatically option - see attachment. I had previously chosen the other option which was to add to the stock .wim that came with the AIK.
I then placed the .wim that was created into the proper folder. Next I used the TIH Plus Pack WinPE builder to add TIH to the .wim created above.
Took some reading initially to understand the .WIM process and I created notes to help me remember the steps. But I needed this because...
1. I did not want the Acronis programs to start when I boot from the media.
2. I wanted to add several utilities to my bootable media. File manager, editor, and most useful of all, a utility to set the screen resolution.
So, when I boot up I pick the resolution I desire depending on what system I'm on, then I choose which program to run.
Attachment | Size |
---|---|
59399-94396.png | 38.21 KB |
- Log in to post comments