click-click

When booting my 7pe, I use a different background image, but before it displays, I briefly see a different background and I haven't been able to find where this resource is located so I can change it to match my background. The image I am seeing is below. On a normal Win7 system it is located in oobe as background.bmp, but in the Make_PE3 image, this dir is not present. Anyone know how this can be changed?

Oh, okay. I misunderstood and thought Bootice would no longer be available from the GUI. I'm glad it can still be selected if found in the tools dir. Sorry for the misunderstanding. I did not report bootsect not working when installing XP from Win7 because I thought the error was caused by doing the XP install from an active Win7 system. The previous versions of WinNTSetup included bootsect.dat in \$WIN_NT$.~BT\. If it ended up wrong, I just replaced it with my own bootsect.dat that used NTLDR. There is no longer a bootsect.dat included in \$WIN_NT$.~BT\ and my alternative was to use Bootice from the GUI.

I'm talking about using the WinNTSetup GUI when preping for an XP install selecting either bootice or bootsect to update the PBR . I'm not saying running from a cmd line does not work.

Why did you decide to do this? Bootice is what I use when the PBR for XP is incorrect. I have a multiboot system that uses BootitNG as the boot manager. When I prep XP with WinNTSetup from W7, I select bootice if the PBR for XP (on F:) is not correct (PBR sometimes has bootmgr). If I use bootsect, it doesn't change the PBR to NTLDR and also disables BootitNG.

Installed XP with 3.1.0 and noticed that the RegTweak directory in \$WIN_NT$.~LS\$OEM$\ is being populated with a bunch of directories numbered 5-22 and also with a file called RegTweals.cab. I have my own tweaks that I copy to RegTweak and I did not select anything from the tweaks menu. Previously, if no tweaks were selected, the RegTweak dir remained empty. Now I'm not sure if my reg files will be applied after copying them to RegTweak since it looks like the tweaks process has changed. Can I just delete the dirs and cab file? The RegTweak.cmd doesn't even access these dirs.

I just noticed that -cfg: only accepts a full path for the file. I kept wondering why my settings never showed in the GUI. I use a shortcut for the GUI and my ini file is included in the target directory. If I only specify the filename in the shortcut parameters, WinNTSetup ignores the ini, so I had to specify the full path. V2 previously allowed only the filename. Just a heads up in case someone is having the same problem.

Thanks, I must have missed that parameter change. Any others besides-nt5/-nt6 -> nt5/nt6 and -configfile -> -cfg ?

I noticed in the last few versions of WinNTsetup that it no longer accepts an ini file using a name other than WinNTSetup.ini. For example, the following shortcut is ignored C:\Toolbx\WinNTSetup\WinNTSetup_x86.exe nt5 -configfile:XP_WinNTSetup.iniI have various ini files that I use depending on which system I'm building. WinNTSetup only uses WinNTSetup.ini if present, otherwise it uses a default and ignores anything else.

Sorry for not getting back to your question. Looks like you already made your decision with 3.05 so thanks for that. Either way would have been fine.

The following regtweak is no longer present for Win7 using 3.0: TakeOwnContextMenu=1 Some tweaks do not always apply to a specific system, so is there any way to only show the applicable tweaks for a given system? i.e. Boot to Desktop, etc. don't apply to Win7, but you can still select them.

I see there's a v4.7 of Make_PE3. Are there any notable changes since your last 4.5 announcement?

KMS activated systems = no free update from the store. http://windows.microsoft.com/en-us/windows-8/why-can-t-find-update-store

I also have 3 other OSes to choose from, but I just happened to be using XP at the time. I was just curious about what would be reported

Crashes if it can't find the MSDM table. Doesn't seem to check on what type of system it is running on.

Now that you mention it, yes 8.1 lets you do this via settings. I assumed this was a reg tweak that applied to 8 also.

Please keep XP in there - at least until it goes out of support in April. I still use WinNTSetup to build a new XP every patch-tuesday. For those of us that have multi-boot systems, it would be nice if the XP code were left in there. On another note, I recently did a new Win8 install and thought I would try the Boot to Desktop Option. I was a bit disappointed because after booting, the desktop only showed up briefly before the metro start screen took over again. Is there any way to make it stay with the desktop?

From my trials, activating default file associations on an online system has to be done via the Control Panel or with a customized OEMDefaultsAssociation.xml that is applied during the first boot after installing win8. Doing this via the registry is problematic as mentioned by the OP.

Has anyone successfully managed to import and activate program/file associations using dism? I ran a small test with the following xml on an online system, but when I select a .bmp file, Win8 still wants to start the metro app instead of the desktop app. dism /Online /Import-DefaultAppAssociations:Z:\$W8i\$W8-Deploy\test.xml <?xml version="1.0" encoding="UTF-8"?><DefaultAssociations> <Association Identifier=".bmp" ProgId="Paint.Picture" ApplicationName="Windows Photo Viewer" /> <Association Identifier=".eml" ProgId="ThunderbirdEML" ApplicationName="Thunderbird" /> <Association Identifier=".wdseml" ProgId="ThunderbirdEML" ApplicationName="Thunderbird" /> <Association Identifier="mailto" ProgId="Thunderbird.Url.mailto" ApplicationName="Thunderbird" /></DefaultAssociations>If I check the associations via the Default Programs in Control Panel, .bmp is still associated with Fotos instead of Windows Photo Viewer. I also tried enabling the appropriate GPO entry and placing the test.xml in c:\windows\system32 but that doesn't seem to apply to local hosts. I would like to automate setting the program/file associations during the system build process possibly at the OOBE stage. Anyone know how?

I only use SetupComplete to add things such as dotNET, VCRedists, Tweaks,, Fixits, etc.. All integratable fixes go into the wim which I update each month using Komm's repository. Integrating the latest fixes into the wim each month is a no brainer. I've been doing this for over a year now and this was the first time I ran into the problem where a fix was unremovable from my offline image.

Well, after checking, I actually did try to remove 2703811 before adding 2844009. I still had the problem removing it even with 2844009 not integrated at the time.. I did not want to waste moe time on it and I redid the integration up to June stariing with the W7 SP1 install wim. I always make it a point to remove superseded updates from the offline image before adding any replacements. I have no idea what happened.

bootmnt.exe is a small tool I wrote to mount all hidden boot partitions. It's integrated in WinNTSetup and extracted every start to temp folder. Normally an XP/2003 install deletes that folder in the last setup phase, but it doesn't work always. Especially on newer systems, that folder and the file $LDR$ remain after setup. I Never saw this on previous Win7 installs, but I guess I can just delete it without anything getting broken. I will keep an eye on this to see if iit's a random thing the next time I install.

I noticed that $WINDOWS.~BT was still present on C:\ the last time I did a Win7 install with WinNTSetup. Is this normal and can it be safely deleted? Al

Okay, I understand. I could not find this file after winntsetup finished - only in the temp directory when it was running. Where is this file from?

When running WinNTSetup, I noticed it creates some temp files, one of which is bootmnt.exe and HitmanPro is flagging this as a Trojan. Virustotal shows 5 of 47 on this file. I assume this is a false positive. C:\Documents and Settings\xxxxx\Local Settings\Temp\WinNTSetup000\Tools\x86\bootmnt.exe Size . . . . . . . : 14,336 bytes Age . . . . . . . : 0.0 days (2013-07-13 07:54:35) Entropy . . . . . : 5.5 SHA-256 . . . . . : E63FECABFAB2E48953E28347D5BBCEFB637F05C0D956D52211A516CE41CCFD90 Ikarus . . . . . . : Trojan-Spy.Agent!IK Fuzzy . . . . . . : 108.0