POMAH-PRESS

So when is version 3 coming out?.. Gonna be doing some lite'ing soon...

Updated the package today. Changes in changelog.txt.

Any feedback? Requests?

Sooooo... Have you figured that out or what???

Well, it's like it is written in the guide 1. You don't start run.cmd, in fact there is no run.cmd, not until you start USBMultiWimSetup.cmd. That's what you should be doing. To do that you boot into PE - the boot.wim from your installation media (you must put it on your USB drive as described in the guide). When PE boots and the welcome screen is shown you press Shift+F10 to start cmd window. Then you go to the root of the drive where your wims and xmls are and where your USBMultiWimSetup.cmd should be. If you're not used to cmd interface you can just type notepad there, then in notepad window press Ctrl+O to go to open file dialog - that will present you with an explorer-like window and you will be able to browse your disks just like you would in normal windows. And don't forget to enter "*.*" into filename field to be able to see all the files and not only the .txt ones. So you go to the right directory and right-click the USBMultiWimSetup.cmd and click run as administrator (or whatever, I don't remember atm) so it starts executing and not opens in notepad. And you're done. Or you can avoid all this procedure by integrating files from the archive into your boot.wim like described in the guide - Step 1.a. That way you will see the scripts menu immediately after PE boot. You will just have to Alt+Tab to it. It's all there in the guide, really. I thought I've put all the necessary info there, but I might be wrong... 2. All the files in the sources folder are used only when you start installation from Windows (like upgrading from XP or Vista or 7...). When you start installation booting from DVD (or USB in our case) PE boots and all the same files located inside the PE image are used. That's it. 3. You put your PE wims on the boot disk, USB in your case. You can put them in any folder you like just change the BCD store accordingly. In my guide I use sources folder because it's the standard folder so you don't have to change anything in the BCD. You could put them in, say, "PE" folder and name the wims "pex86.wim" and "pex64.wim" and change the BCD to reflect that. If you don't want to mess with BCD just take the pe wim you need and put it in sources folder, like described in the guide. It's all really simple, you just have to do it right once and you will see that. If the above doesn't answer your questions ask more. We will sort this out, I assure you.

Yeap, that's the way to go I think... 7 and Vista should be deployed separately using this method. I didn't think about Vista when developing this anyway.

That would be great and appreciated. Didn't get that.

Well, I don't see why it shouldn't. I don't have any Vista's to test though.

mb stick this for a while?

I've put together techniques from different guides and made a script that allows one to place several WIM's and XML answer files in some directories on one disk (USB, HDD, CD/DVD,...) and have them listed in script's menu after the installation media's PE boot. You can select an image and an answer file to use and start the installation. How it works. PE boots. If you've injected the autostart script into it - disks are scanned and when found USBMultiWIMSetup.cmd is started (if you haven't injected the autostart script you have to manually start the USBMultiWIMSetup.cmd from command prompt). It scans the disk it is on (two dirs, according to path's inside it) for WIM's and XML's. It generates lists/menus including every item it finds. All this is then output to another script which is presented to the end user. This script currently contains 4 pages/dialogs: 1. IMAGES. Here you can see all the images found and must select one to continue. 2. ANSWER FILES. Same here, only here you select an answer file. If you don't have or don't want to use any - select "[0] - none" or skip to another page/dialog. 3. START SETUP. If you're done you can start setup from here. 0. RESTART WIZARD. This is the page where you can restart the script. It doesn't make much sense now, but I have some future plans for extension of this script, that's where it will be used. A simple(st) example: 1. You need some files from an NT6.x installation media: \boot folder with all it's contents \sources folder with a boot.wim file in it, just this one file, nothing else \bootmgr file all this goes to the root of your boot device, whichever you are using. From now on it will be referred to as [boot disk]. 1a. This step is required to have the script loaded automatically on PE boot. You have to inject the StartSetup.cmd and winpeshl.ini files from downloaded archive to boot.wim's second image. The path is: Windows\System32\ 2. You can now put your WIM's and XML's to some folders on some disk. From now on that disk will be referred to as [source disk]. Next thing to do is to edit the USBMultiWIMSetup.cmd and enter the path's to WIM's and XML's you are using at the top of the file. In this example we are using: \IMG for WIM's and \XML for XML's so it looks like this in the .cmd: set wimpth=IMG set xmlpth=XML 3. You need to put the modified USBMultiWIMSetup.cmd file to the root of your [source disk]. Now, the [boot disk] and the [source disk] can be two different devices/disks or it can be one disk. In this example it is one disk. So the next picture shows the end file/folder structure one should get after peforming all the above steps. It also shows what files/folders should go to the [boot disk] / [source disk] if they were two different disks (according to the color). The run.cmd file included in download is the end user generated script for our example. The following pictures show what it looks like. Download:USBMultiWIMSetup v0.9.1 RC.zip Known issues: Current version doesn't allow to use spaces inside commandline's arguments. Example: this works X:\sources\setup.exe /installfrom:H:\IMG\WIM\ENTx64.wim /unattend:%answ_path% and this doesn't work. X:\sources\setup.exe /installfrom:H:\MY IMG\WIM\ENT x64.wim /unattend:%answ_path% Quotes seem to break the command line as well. This needs further testing. My original thread at boot-land.net (reboot.pro)

And those of us that have Win7 installed in drives/partitions other than C:\> are ready to test things when the updates/changes are made. +1

Hey everyone)... Cool down, LOL)... I'm just saying I'll stick to vLite, for now... And then, well... We'll see)... And yes, having Nuhi back here would be really fantastic...

Well, what Nuhi did several years before for Vista fully suits my needs today with my W7... And it is far more stable for me then this tool specifically designed for W7... vLite is a quality product, proven with time.

Hahaha)))... What a nice progie))))... Good luck to you, Dev's... With that kind of attitude and... "quality")))... ChiefZeke: Thnx for clearing this up... P.S. : vLite and DISM rule!) P.P.S. : Nuhi is da BEST!)))

Yes... Why? Is there a difference? Should I use x86 one? I'm on Winx64. Update: Tried x86 version 1.4.0 on W7 x86, same story, but I figured out a way to lunch the app by first pressing "quit" in an error window, and then pressing "Continue" in a second identical window. However, when I'm trying to do something I get the same error repeatedly... So no-go ( ...