atolica

Has anyone noticed that you can't set the powerplan (high performance or other) by WSIM(WAIK) in Windows 7? I'm using the latest WAIK. Whatever I tried, the default powerplan is always set.

Hi all I've been tweaking an unattend.xml file that I have created using WSIM and noticed that the powerplan settings are not getting implemented in the final installation. I know about setupcomplete.cmd, but I'd like to use the runsynchronous commands in oobe. What is the proper way of doing that? I know that it should start with "cmd /c ....", but what about the path? I don't have a network share I could use. Environment variables maybe? I don't want the batch files to be copied on the computer I'm installing, I'd rather run them directly from the dvd. Is that possible??? Thank you.

I still don't understand what you're trying to do. Be specific!

Hi guys I am trying to build an unattended windows 7 installation starting from Firegeir vista guide with windows 7 OPK(WAIK), but for some reason it hangs. I narrowed it down to autologon thing, as the Administrator account is disabled by default in win7, not enabled like in win7. But even if I create it and set it to autologon, it doesn't work, it doesn't log on. The biggest problem is that the auditsystem pass doesn't start at all, and so the runsynchronous commands don't run. I didn't get any error messages, it just skips to oobe pass. What the heck is going on? Here are the two autounattend.xml I tried. Autounattend.xml Autounattend2.xml Thanks

do you want to have a multiboot dvd? different install.wim? no way this is the only way.

SEE HERE !!! Suppose you'd like to have a dvd with Vista/Win7 setup files(installation disk) PLUS ERD Commander, Active Boot Disk, ESET SysRescue or any other custom made WinPE that you built, on a multiboot CD/DVD, so you could chose which one you'd like to boot. How do you do it? Answer: very easy if you know where to look complete procedure... use the default WinVista, WIN 7 or any WinPE dvd or any bootable wim. copy the contents to the HDD the structure would be dvd1 | - Project Root | - BOOT (CONTAINS THE BCD FILE TO BE EDITED) | - EFI | - SOURCES (CONTAINS THE PE .WIM FILES) | - OTHER FILES In the boot folder we need to run the command bcdedit /store bcd /ENUM This will give you the details of old entry in the boot loader. You need to note the guid. In every case the default guid is {7619dcc8-fafe-11d9-b411-000476eba25f} bcdedit /store bcd /enum Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes First you'd like to see the existing boot entries in the BCD store. bcdedit /store bcd /ENUM *** note the old guid Then you copy the default boot entry to a new entry in the bcd store, that has to be updated. bcdedit /store bcd /copy {default} /d "Active Boot Disk" *** new guid is given at this stage Active Boot Disk is the description I'd like to use for my Active Boot Disk WinPE. operation completed successfully. {613fe2f0-2356-11de-bf6a-001e4cdc40b1} ***{613fe2f0-2356-11de-bf6a-001e4cdc40b1}=new guid It can be different for you. therefore my new guid is {613fe2f0-2356-11de-bf6a-001e4cdc40b1} now bcdedit /store bcd /set {newguid} DEVICE ramdisk=[boot]\sources\boot32.wim,{oldguid} boot32.wim being the name I chose for the Active Boot wim file. You can rename it as you like, but you can not use spaces. operation completed successfully. next bcdedit /store bcd /set {newguid} OSDEVICE ramdisk=[boot]\sources\boot32.wim,{oldguid} *** boot32.wim is the file copied from the active boot disk (boot.wim renamed) *** to check whether the bcd store has 2 ramdisks bcdedit /store bcd /ENUM Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} {613fe2f0-2356-11de-bf6a-001e4cdc40b1} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes Windows Boot Loader ------------------- identifier {613fe2f0-2356-11de-bf6a-001e4cdc40b1} device ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Active Boot Disk locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes like this you may add n number of vista pes... (i have tested 3 PEs + Windows Vista Setup) to the BCD Store. Just you have to keep the oldguid to same as {7619dcc8-fafe-11d9-b411-000476eba25f} {7619dcc8-fafe-11d9-b411-000476eba25f} will never change... that's the rule. copy the boot.wim file in sources folder of active boot disk/ ghost pe/ erdcommander 6.0 to the sources folder in disk1 in the project. and rename it to desired. i renamed it to boot32.wim you may use any... {default} is not a variable and need not be changed. Next This is a script that automates the above process: Rem BCD (boot configuration data) editor for multiple vista pe REM THIS IS THE ORIGINAL BCD FILE EXTRACTED FROM ANY VISTA WINPE / VISTA DVD (I USED VISTA INSTALLATION) set BCD-File="c:\bcd 1\BCD" REM SET THE NAME FOR THE VISTA PE HERE set pename="Your PE Name" REM SET THE NAME FOR THE WIM.FILE HERE WITH PATH set filena=[boot]\sources\yourwimfile.wim for /f "eol=r tokens=1-2" %%a in ('bcdedit /store %BCD-File% /ENUM all') do set rdo=%%b for /f "tokens=1-7" %%a in ('Bcdedit /store %BCD-File% /copy {default} /d %pename%') do set guid1=%%g bcdedit /store %BCD-File% /set %guid1:~0,38% DEVICE ramdisk=%filena%,%rdo% bcdedit /store %BCD-File% /set %guid1:~0,38% OSDEVICE ramdisk=%filena%,%rdo% bcdedit /store %BCD-File% /ENUM Run it as many times as you like to add multiple pes after changing the variables - bcd-file, pename, filena remember not to use any spaces in filena variable.

Hi Firegeier I have the same problem as Amit when running a windows 7 unattended installation. I built my Autounattend.xml using the latest WAIK (WSIM). For some reason the audituser pass runsynchronous commands for installing applications don't start at all. The setup just skips that audituser step and passes to "oobeSystem". this is what I have in specialize pass: cmd /c "FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\AppsRoot.txt SETX AppsRoot %i: -m" The latest WAIK and Windows 7 introduced some changes. For start, the builtin Administrator account is disabled by default, not like in vista, where it was enabled. So I deleted the Administrator autlogon pass from "auditSystem" , and I added the "Reseal" command instead of "sysprep /audit /quiet" which hangs. The help file says the Reseal with audit option does the same thing, and this is the new way of sysprepping the system and entering the audit mode. it doesn't work. I tried letting the Administrator account and still doesn't work. Anyways, the RunSynchronous commands don't start at all in "audituser" pass. The system just logs on using the user I created afterwards. I'm going to attach two versions of my Autounattend.xml, one without the Administrator autologon account. I think that the runsynchronous commands don't start because there is no Administrator account logged on. I created one and testing it next. Let's see how it goes. edit: didn't work. It doesn't autologon to the Administrator account. It didn't even create it. edit2: i uploaded the original autounattend.xml, the one with the administrator account autologon. i made it starting from Firegeier's vista guide. As I already said, the administrator account is disabled by default. I cant install te applications in audit mode and sysprep. All I can do is install the apps in oobe phase, logged as a normal user. then I can't sysprep generalize no more. I've read here on this forum that this can be done with the help of another xml file, unattend.xml used togheter with Autounattend.xml. Can't find the post. Do you know how that is done? Greets Autounattend.xml Autounattend2.xml

What's vista?

I don't get it. What is the purpose of your thread? Do you feel alone?

Thank you.

You're welcome. iamtheky's right, by the way.

Yes. Select nv4_disp.inf and all the other files will be integrated by nlite.

1. Inside Windows Windows XP+SP3 CD there is a directory "i386" inside which there is a file called IMS.CAB. With WinRar (or something similar) unpack the content to a temporary folder (you will need them at the end of the installation) 2. Search and find the file on the local computer: c:\WINDOWS\INF\SYSOC.INF 3. In the section [COMPONENTS] you will find this line: iis=iis.dll,OcEntry,iis.inf,hide,7 4. Change it to this: iis=iis2.dll,OcEntry,iis2.inf,,7 (remember to change the name in iis2.dll and iis2.inf and to eliminate the word hide. In this way you bypass the protection of XP Pro) 5. From the Windows XP + SP3 CD (Pro) take the files: iis.dl_ and iis.in_ that are in the i386 folder and copy them on your desktop, open a dos windows and with the prompt pointing at your desktop edit the following commands: EXPAND IIS.DL_ IIS2.DLL EXPAND IIS.IN_ IIS2.INF this will generate two new files named iis2.dll and iis2.inf copy and paste IIS2.DLL to c:\WINDOWS\SYSTEM32\SETUP\ and IIS2.INF to c:\WINDOWS\INF\ 6. Go to control panel/application/windows components and start windows installer. You will see "Internet Information server" is now available as a checkable option. 7. Select it. 8. It will need about 10/15 minutes and during that time the system is going to ask you for a lot of files: some are in XP PRO CD. At a certain point the system will ask you for the EXCH_adsiisex.dll file: it is the file you have extracted at the point 1 of this guide, select it and you should go on without trouble. 9. At the end restart you computer. 10. Test if it is working: open Explorer and type in the address line: http://localhost 11. If it will not work, try the following: open a DOS window and type: iisreset /RESTART edit: Enough editing. Now it should be ok.

lol. Cylinders as I know, are only used in harddisks. You can't do much. Optimize the Iso maybe. See Ultraiso optimization!

You were right. Windows 7 betas BCDEDIT it is still being developed that's why it didn't work. But using the one inside vista sp1 solved the problem. It seems MS is not releasing fully working utilities with the betas. The vista+sp1 bcdedit size is 326 KB (334,336 bytes) when Windows 7 build 7057 bcdedit is 287 KB (293,888 bytes). This might explain that behavior.

I think is due to the fact that Win 7 hasn't got all the "goodies" put inside. I get some strange bugs, features of bcdedit not working. It might be due to the fact I run on build 7057. The boot menu not showing is very weird. In virtualBox everything is working flawlessly, iso and burnt DVD. I'll install build 7077 Sunday night, and get back to you on that. edit: You said something about optimization. You mean ultraiso optimization? It might be the culprit. What about creating the iso with oscdimage? Or cdimage. MS does it that way.

@varun037 I just burnt a DVD with Win7 and several other winpe to see if it works. I tested it first in virtualbox , boot menu shows up normal and where besides one winpe not starting, the other 4 ran smooth. But, booting on the real machine, the boot menu is GONE. Nothing shows up. Black screen. I'm trying to see what's causing this, but can't think of anything right now. Still searching.

varun037 You're amazing man! Thank you. I will alway be in your debt. Muchos gracias!

Can someone with good scripting skills help me create a batch that will automate varun037's method? Probably you Nois3. For some reason your script doesn't work for me. It stops working at Bcdedit /store "%BCDFILE%" /set %guid1% systemroot \Windows Thank You!

http://www.msfn.org/board/index.php?showtopic=131887 See this!

Hi guys Suppose you'd like to have a dvd with Vista/Win7 setup files(installation disk), ERD Commander, Active Boot Disk, ESET SysRescue or any other custom made WinPE that you built, on a multiboot cd/dvd, so you could chose which one you'd like to boot. How do you do it? I had the same problem until a guy from Ultraiso forum -varun037- gave me the perfect solution. Here it is, I'll spare you the details. Thank you varun037! I hope someone will have use of this how-to. Greets, Atolica

Regarding the help you gave me Nois3 and everything else, I will always be in your debt. It was a learning curve for me, a starting point. Although I had a lot to learn from you, I couldn't make it work so I asked for help in some other place. And it paid off. A guy from Ultraiso forum had the same problem as I, and found a way to successfully built an iso with two WinPE distributions on it. One can put as many WinPE as he likes, I don't think there's a limit. To spare you guys the long talk, here's the original post, with thanks going to the original poster varun037.

Hi guys I opened a thread over in multiboot thread. Can you take a look and share your opinions please! Thank you! http://www.msfn.org/board/index.php?showtopic=131887

http://www.msfn.org/board/index.php?showtopic=131887

I know what I did wrong. I was trying to do this running on Windows 7 and just running WAIK from an administrative install point. I guess I have to install it. Let's see how it goes from here. You've been of much help. Although technet and some part of the documentation covers what you've helped me with here, I didn't know where to start. I was kind of lost. I also searched for your posts here on msfn and I've found some related ones. Thank you again. I hope I'll have a dual boot WinPE in no time. Regards, Atolica