JFX

@maanu why not let PECmd call a batch file that start both? I found a way to bring up the native format dialog of windows inside default winpe, so next version will have a (F)ormat button. @ghfujianbin that strange, i installed Windows7 several times that way next to Windows XP and never had a problem. If there is an entry in boot menu means, that the update of boot sector did work all right. What exactly is the error message?

Hi maanu, bootice is not included anymore, because of bugs and missing x64 version. an option to format i can properly add. but why not launch Partition Guru before or parallel to Winntsetup and use it to make partitions ready?

Hi zamarac. Thin Client and Embedded versions are not supported, one reason they mssing boot files. Another reason they often gives 0x7b or a blank screen with this direct install method. I never had the time to find out what really happens there. You can run Winntsetup from any OS (Windows XP SP1 up to Windows 8 Pre) It also support running from WinPE and from any read-only device like CD-ROM's Unsingned drivers are only integrated if cmdline option -NT6 -ForceUnsigned -TESTSIGNING is used. A driver that have not a trusted signed cretificated, win7x64 will always need to run in testmode it use bcdboot X:\Windows /s C: /l en-uS there is actually no suppression of error, it would show error message. some people want to create VHD's in their forensic WinPE (no automount, readonly disk access). The 4 NOERR lines are added that this works now. ALIGN and UINT is usually not needed to set by user, Windows 7 default is okay in all cases. Newer harddisk, will often have a recommanded Aligment size, if this case user should select it. higher UINT values can result in slightly better perfomence

You can not! Only Windows 7 and later is supported for direct install to USB device.

... oh should turn off opera turbo ... anyone can delete this double post

No, it's not mandatory. install will overwrite files and abort if there would be a problem. But yes there will be files remaining from old Windows installation. With removing an old installation without formating, i see 2 problems: 1. NTFS security settings - one would need to take ownership & grant access or using a tool like xdel 2. Junctions and Symlink (and this is the thing that scares me ! ) - junctions and symlinks in Win7 are created with full path. think you have an offline win7 that has C: as normal drive letter and is now under your current running windows mounted as D: It's junctions and symlink will still point to C:, but that could be the current running windows Even Mircosofts own tools like robocopy don't handle symlinks right. It might happen that deleting an offline windows switch the drive and start deleting files/folder one the current system drive !

Hi maanu, alright here, hope everything is okay by you too. Sounds interesting, please send me additional "information" about this GHO image via PM.

You can't remove the wimfltr driver if it was started, without a reboot. Why would you need both versions?

How did you integrated IE8? It has no integrate switch, surely for a reason. IE8 or wmp11, can only be installed via svcpack / runonceex method.

Properly UAC prevent creation files in all user start menu. Seems renaming hh.exe does not "unblock" it I just put a shortcut to xchm.exe inside %APPDATA%\Microsoft\Windows\Start Menu\Programs and have expandable arrow now for help files.

hmm , hh.exe is on the exclusion list for start menu http://msdn.microsoft.com/en-us/library/windows/desktop/dd378459(v=VS.85).aspx#exclusion_lists Not sure how the the override this, maybe just make a copy of hh.exe to hh2.exe and change file association Of course there have to be a .lnk file inside start menu that has hh2.exe as targetpath.

Yes that's right, WinNTSetup2_x86.exe is all you need. WinNTSetup2_x64.exe is thought to run under a 64Bit Winpe, which does not support 32 Bit applications. like: - Erd Commander x64 - Recovery Console of Windows 7x64 - Windows 7 x64 Setup DVD

Hi xpclient, not sure I understand you right? WinNTSetup2_x86.exe is a standalone exe, that can install from any 32 bit system (at least XP SP1 and higher) all Windows version from Win2000 up to Windows 8 Pre x64. It support installing 64Bit OS form 32 Bit Windows.

hallo my dear friend, Thanks for that thread. And yes with version 2.1 these both entries are set: [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet???\Control] "BootDriverFlags"=dword:00000006 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet???\Control\PnP] "PollBootPartitionTimeout"=dword:00007530 also if you integrate NEC USB3 driver, they get BootFlags assigned.

assume you mean a xp install? It does actually nothing special, only disable the sr service [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sr] "Start"=dword:00000004 enter this in command prompt: Should active System Restore again.

Hi click-click, WinNTSetup, is written mainly in Autoit3. A few months ago, i noticed that it looks awful on Windows with a higher DPI setting. After searching i found a topic: fontgui-resizing. So I changed every GUI coordinates/width,high using a DPI factor. Very Nice if one already have over 150 GUIelements Also added dpiAware entry to the application mainfest.

Ah, thanks think i understand now. Winntsetup creates following boot order: MBR --> PBR --> NTLDR --> Boot.ini --> BOOTSECT.DAT --> $LDR$ of course BOOTSECT.DAT will give an error on different hardware. What you can do before capture: - delete NTLDR and boot.ini - rename $LDR$ to NTLDR this should hopefully solve your problem.

hmm, i wouldn't call "A" a problem, it's just that I prefer keeping the folder. Deleting it manually should not be that much of a problem I guess B and C are the same problem: Have not used Norton Ghost for ages, maybe it does not cause the problem. anyway if you want to make an image of "Pre" - setup phase, that should run on different hardware make sure you have necessary SATA drivers in setup. Also do NOT use, the 2 options: "Mount installation drive as ..." and "use migrate.inf for drive lettter pre assignment". Both saving disk/partition infos that will cause trouble if use on different hardware.

Hi, sorry for late respond. Yes the Windows 8 Pre-Beta is supported by the current release. Will add ISO file browsing, that's running user defined batch file and scan for new drives ...

Update: Version 2.1.0.0 - Support for Windows 8 Pre Release - GUI upscale on higher Windows DPI settings - Now automatically finds Vista/7 "system reserved" boot partition - filesize and speed improvment - file patching no longer changes NTFS ACL attributes (Thanks Jeff Bush - bcopy tool) - added support for splitted WIM files (.swm) - added support for direct USB install for Windows 7 (Thanks cdob, wimb, maanu) - added more manufactors for XP CD OEM detection - fixed bootstr.dll error message on certain WinPE1.x - fixed small issue with reboot option - fixed small issue with command line - fixed shutdown option not works correclty on certain winpe version - fixed app crash when running under Windows 8 Pre-Release - fixed wrong warning on too low disk space - fixed Service Pack not displayed for Vista sources - fixed copy LANG folder if multiple selections are used for LanguageGroup in winnt.sif - Improved VHD creation: - fixed .vhd file extention was not auto appended for VHD creation - fixed VHD creation output on unicode languages - fixed WIM file discription not displayed correctly on some selfmade install.wim files - fixed VHD creation possible even in forensic WinPE :now use diskpart script like this one: create vdisk file="C:\Windows7.vhd" maximum=25600 type=(fixed|expandable) select vdisk file="C:\Windows7.vhd" attach vdisk online disk noerr attributes disk clear readonly noerr create partition primary align=(32|64|128|256|512|1024|2048) online volume noerr attributes volume clear readonly noerr active format quick fs=ntfs label="Win7 VHD" uint=(512|1024|2048|4096|8192|16K|32K|64K) assign letter=X:

I think you need to tell it where the setup answer file (winnt.sif) is located. will release next version in a few days, that will copy lang folder if necessary.

Sure because maintaining one version is not enough work

Hi dlinh9, Welcome here 1. problem is caused by the IE8 AddOn, nlite Addon Packs are not supported. It would require a complete parsing of dosnet.inf, txtsetup.sif layout.inf, ... , like the original winnt32.exe does. 2. Problem occurs because Winntsetup does not copy the \I386\LANG folder from the Windows source I will adjust next version to copy LANG folder, if LanguageGroup has multiple selections

hmm funny, the guy who kicked the best developers out of the boot-land forum, calls himself also Nuno Brito. Your focus is not what any script developer cares about. I would highly recommend to focus on reliability, speed, simplicity AND a clear script syntax.

Im using this in my unattend.xml files: <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>net accounts /maxpwage:unlimited</CommandLine> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands>