click-click

When I install XP from a source that has an $OEM$ dir with cmdlines.txt and ROE.exe, the files don't get copied to the target drive after running WinNTSetup. Is this correct?

I hope it wasn't too much work. I would have accepted 'no longer supported' too. Thanks ... BTW, does WinNTSetup support upgrading on top of an installed system? For example, upgrading a Win10 build to a newer Win10 build without doing a clean install. All of my WinNTSetup procedures till now have been fmt -> install fresh, so I 'm not sure if upgrading is supported.

Still getting same error using XP with v3.8. Installing Win10 using Win7 doesn't give you that error.

I see someone had this problem before and it was related to XP. BCDBoot XP compatibility was put back in as stated here. Has XP support for this been removed again? I'm using V3.7.9. I know XP is EOL, but I'm using the POSReady 2009 version which doesn't go EOL until 2016

I got this installing win10 Preview I ran the install from XP. This is build 10159. Input was a decrypted esd. When booting, the OS it goes to a recovery screen saying the system needs to be repaired because there is something wrong with the BCD. I looked at the BCD and it doesn't have any entries in it. I had to manually create a BCD so the OS would boot.

I just upgraded to 3.7.2 -> 3.7.7 and noticed a new drop-down that appears next to the use bootsect ... drop-down after starting Setup. Some of the options are ALL, BIOS, UEFI, etc. I must have missed the discussion about this. Can someone explain what those options are for and what changes they make?

I recently installed Win7 with 3.7.2 and after the installation, I notice the following error in setuperr.log 2014-12-24 12:29:36, Error CSI 00000001 (F) E_INVALIDARG #2# from UnloadStore(target = NULL) [gle=0x80004005] Anyone know what might be causing this?

z.I. Download link on first page points to the version in \old (3.6.1).

Okay, thanks - a lot of the information I read (even from MS) indicated that DISM supported Vista. http://technet.microsoft.com/en-us/library/dd744566%28v=ws.10%29.aspx . What did I misunderstand?

Sorry if this is OT, but I need to install Vista x64 with WinNTSetup. and before I use WinNTSetup, I would like to service the install.wim with all of the updates after SP2. I was under the assumption that I could use dism to service the wim. I can do things like dism /Mount-Wim, /Unmount-Wim, /get-wiminfo and imagex.exe /export, but when I try /get-packages or /Add-Package, I get the errors below: C:\>dism /image:r:\Offline /get-packages /format:table /English >R:\$WVista\DrWin\VBSP2_a-r.txtDeployment Image Servicing and Management toolVersion: 6.1.7601.17514Error: 50The command specified is unknown or not supported when running DISM.exe against a Windows Vista with Service Pack 1 or a Windows Server 2008 target image. For more information, see the Help documentation available in the Windows Automated Installation Kit (Windows-AIK) or the Windows OEM Preinstallation Kit (OPK).AlsoC:\>dism /image:r:\Offline /Add-Package /PackagePath:R:\$WVista\DrWin\Repo-Dir\Deployment Image Servicing and Management toolVersion: 6.1.7601.17514Error: 2An error occurred while processing the command.For more information, review the log files.Is adding patches to a Vista install wim (SP2 RTM 6.0.6002.18005) supported? I don't know how to get past these errors to use WinNTSetup. DISM.txt dism.log.pkgmgr.txt

Can anyone tell me how startnet.cmd is auto started during the PE Boot?

I have a Desktop (create shortcut).DeskLink in P:\Make_PE3\PE3_mod\PE3_add\x86\Users\Default\AppData\Roaming\Microsoft\Windows\SendTo, but it does not show up on the context menu, so I can't create shortcuts on the desktop via SendTo. Is this supposed to be supported with PE? All other files I have there show up fine in the context menu. Any idea what might keep the Desktop(shortcuts) from appearing? I saw this, but I don't know if this relates to Make_Pe3 too. Edit: I found it - sendmail.dll is missing in \system32

XP UpdatePack from user_hidden using RVM Integrator has always worked for me using WinNTSetup. If I recall correctly I once used 5eraph's Windows XP x64 post-SP2 Update Pack with RVMi and that too was okay as the source for WinNTSetup.

Thanks, I see the setup.bmp and missed viewing that one on X:. I originally looked in the \PE3_mod and did not find an image that matches the setup.bmp. I still don't know how this file ends up in x.\windows\system32 Do you happen to know?

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?