[WinNTSetup v5.4.1]

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.

[WinNTSetup v5.4.1]

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.

[WinNTSetup v5.4.1]

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 ...

[WinNTSetup v5.4.1]

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:

[WinNTSetup v5.4.1]

I think you need to tell it where the setup answer file (winnt.sif) is located.

H:\i386\winnt32 /syspart:c: /tempdrive:c: /makelocalsource /copysource:lang /unattend:"D:\winnt.sif"

will release next version in a few days, that will copy lang folder if necessary.

[WinNTSetup v5.4.1]

Sure because maintaining one version is not enough work

[WinNTSetup v5.4.1]

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

[Any programmer think to make a winpe builder?]

... but the biggest problem is keeping developers improving the existent projects ...

hmm funny, the guy who kicked the best developers out of the boot-land forum, calls himself also Nuno Brito.

My focus on this moment is to ensure the independence from Windows API to natively construct registry hives and WIM files without resort to MS code, in the process this allows removing the need for administrative permissions or installation of drivers to run the builder.

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.

[How to set no password expiry]

Im using this in my unattend.xml files:

      <FirstLogonCommands>
        <SynchronousCommand wcm:action="add">
          <CommandLine>net accounts /maxpwage:unlimited</CommandLine>
          <Order>1</Order>
        </SynchronousCommand>
      </FirstLogonCommands>

[WinNTSetup v5.4.1]

Hi Drake,

a direct use of an ISO would not be possible, but you could mount it with imdisk. That's the way I do it.

create a sub folder ISO and put imdiskinst.exe and your ISO inside.

create a batch file next to winntsetup similar like this:

@echo off

set ISO="ISO\de_windows_7_ultimate_with_sp1_x64_dvd_u_677306.iso"

ISO\imdiskinst -y
imdisk -a

for /f "TOKENS=3,4 SKIP=1 DELIMS=: " %%i in ('imdisk -a -m #: -f %ISO%') do (
	set Imdisk_device=%%i
	set Imdisk_letter=%%j
)

echo Imdisk Device Number: %Imdisk_device%
echo Imdisk Device Drive : %Imdisk_letter%:

WinNTSetup2_x64.exe -NT6 -Source:%Imdisk_letter%:\sources\install.wim


rem optional unmount and imdisk uninstall

rem imdisk -D -u %Imdisk_device%
rem rundll32.exe setupapi.dll,InstallHinfSection DefaultUninstall 132 %windir%\INF\imdisk.inf

@Killerdog

sorry for keeping your waiting so long, next version will completely solve that issue with XP Based PE.

[Installing Devices at first boot takes 3 hours]

what about the 2 log files in \Windows\inf folder

setupapi.app.log

setupapi.dev.log

They may show which driver installation hangs so long.

[WinNTSetup v5.4.1]

hi,

I have problem to reproduce this error, so far with the new GENA release i tested a lot combination and all work well

The link you gave, describe overwriting bootstr.dll.mui with one of the Win7 beta files. I can figure that it will be a solution nor that it would be good since you use Vista.

the good thing so far: the error message(s) are not critical and should not cause a problem for booting the new Windows installation.

Have not much time currently, but will continue trying to find a solution.

Maybe you can try to describe how you create/boot your GENA. Made special GENA support topic --> WinNTSetup2 script

[WinNTSetup v5.4.1]

Hi Killerdog,

is your Windows Vista a original or modified Windows source (maybe a integrated lanaguage pack)?

The bootstr.dll.mui file is a resource only file, so there should not be a problem, installing Vista x64 from a x86 Winpe.

Maybe the file C:\Windows\System32\fr-FR\bootstr.dll.mui got corrupted during copy.

[netsh wlan issues]

System Error Codes

ERROR_MUI_FILE_NOT_LOADED

15105 (0x3B01)

Do have added the respected .mui files for these dll's you added?

ex.

\Windows\system32\wlancfg.dll

does require

\Windows\system32\en-US\wlancfg.dll.mui

[WinNTSetup v5.4.1]

I use it to install windows 7 from pe(XP based) and select both the boot drive and installation drive as C(first and primary partition of hdd)

Then after installation finished,I go to "my computer" and I found my OS partition becomes the letter D ..... and it's unchangeable ...

Thought about it, one reason that it use D: instead of the selected C: could be when the the installation drive is a removable drive.

Currently drive letter assignment only works for fixed disks.

Don't think this will be fixed soon, so If a direct installation of windows to usb is need it's better to use Fujianabc's NT6 Fast Installer.

[AutoIt and nVidia GeForce 270.61?]

First unpack, than try /passive /noreboot switch

[WinNTSetup v5.4.1]

Update: Version 2.0.4.71

- accept nativeVHD Boot for Embedded editions

- fixed wrong reported partition as active primary

- suppress boot configuration error on mounted Vmware/imdisk disk

- added Option to automatically reboot after setup finished

- added Command line switches

- /nt6, /nt5 or /vhd have to be the first parameter all other don't require any order

- does not matters if -paramter or /Parameter

- give paths can be relative (to WinNTSetup_x??.exe)

- if a path includes spaces enclose it with " "

- /nt6 or /nt5 - will let winntsetup know which os to install (nt6: for vista and later, nt5 for XP/2003)

- /source:(path) - defines the installation sources (for nt5 the root of the windows CD, for nt6 the install.wim file)

- /syspart:(driveletter:) - defines the driveletter you want as boot drive

- /tempdrive:(driveletter:) - defines the driveletter you want as installation drive

- /unattend:(file) - defines the path of the unattend file (winnt.sif or unattend.xml)

- /drivers:(path) - defines the path to a drivers folder you want to use

- /wimindex:n - defines the edition inside install.wim which should be installed beginning with 1 (like in the combo box Edition)

- /setupwait - will push the setup button and show you the proceed page

- /setup - will start the setup

- /reboot - will automaticly reboot 30 seconds after setup finished

- /forceunsigned - (only for installing Windows 7) will let the driver integration accept unsigned drives

- /testsigning - will set testsigning flag for the new Windows installation

- /disableuac - will disable User Account Control

- /Sysletter:{Letter} - will define the systemdrive letter the new windows installation will have

- /SaveDriveLetters - will save the current driveletter assaignment for the new windows installation

- /Uxtheme - will patch the uxtheme related dll's to enable the use of custom msstyles files

- /nobootsect - will not update BootSector and Master Boot Record

- /RunAfter:{command} - will run a command before reboot

- /cfg:{inifile} - load settings from ini file

- /HiveFix:{inffile] - use a special inf, to customize setup

- /vhd

- /create

- /VHDFile:{path} - defines the full path for the new VHD file

- /VHDSize:{size} - defines the size in MB or GB (ex. 25600MB or 25GB)

- /VHDType:{type} - defines the type of VHD: fixed, expandable or fixedfast

---- optional ----

- /VHDLabel:{Label} - label for the vhd partition

- /VHDAlig:{Alig} - Allignment (32|64|128|256|512|1024|2048) of the partition

- /VHDAllo:{Allo} - Allocation unit (512|1024|2048|4096|8192|16K|32K|64K) of the partition

- /mount - attach a VHD to system

/VHDFile:{path}

- /unmount - detach a VHD from system

/VHDFile:{path}

examples:

- Install Windows7 Ultimate (usually Wimindex 5) to drive C:, using unattend.xml file and define driver to integrate.

Use C: as driveletter for the new Win installation, run set_7_usb_boot.cmd before rebooting

WinNTSetup2_x86.exe -NT6 -source:G:\sources\install.wim -WimIndex:5 -syspart:C: -tempdrive:C: -unattend:"unattend\Win7x86_Ultimate_en.xml"
-ForceUnsigned -drivers:"D:\driver_Win7x86" -Sysletter:C -RunAfter:"set_7_usb_boot.cmd C:\windows" -setup -reboot

- Install Windows XP to drive D:, where boot drive is C:, using unattend file [app dir]\unattend\winnt.sif,

integrate drivers [app dir]\XP_drivers, finsih install and reboot. But does not change MBR and BPR

WinNTSetup2_x86.exe -NT5 -source:E:\XPCD -syspart:C: -tempdrive:D: -unattend:"unattend\winnt.sif" -drivers:"XP_drivers" -setup -reboot -nobootsect

- creating a 25GB fixed VHD file

WinNTSetup2_x86.exe -VHD -create -VHDFile:"C:\my.vhd" -VHDSize:25GB -VHDType:fixed

-attach vdisk "C:\my.vhd"

WinNTSetup2_x86.exe -VHD -unmount -VHDFile:"C:\my.vhd"

-detach vdisk "C:\my.vhd"

WinNTSetup2_x86.exe -VHD -mount -VHDFile:"C:\my.vhd"

feel free to ask or comment about commandline

[WinNTSetup v5.4.1]

Well no problem.

this Win$Man is zhhsh new version, looks very good

I guess the main difference is that this app and Fujianabc's NT6 Fast Installer read the MountedDevices of the current running system and I calculate them.

But this should be a more accurate solution, especially in WinPE 1.x, where MountedDevices is not very reliable.

Anyways, good there are alternatives that works

[WinNTSetup v5.4.1]

hi zomk777,

that interesting, someone else already report me that the "drive letter preassignment" option can assign 2 letter for a partition.

I could never reproduce this, but mountvol.exe should be able to removed the wrong drive letters.

The assignment of the system drive letter always works well for me.

One think that maybe help finding the problem:

- after winntsetup finished load the the offline system hive and save the MountedDevices key:

reg load HKLM\SYS C:\Windows\system32\config 
reg export HKLM\SYS\MountedDevices C:\MountedDevices_before_Reboot.reg
reg unload HKLM\SYS

reboot and let installation continue, after new windows has booted to desktop

export the new MountedDevices key

reg export HKLM\System\MountedDevices C:\MountedDevices_after_Setup.reg

please send me both reg files

[WinNTSetup v5.4.1]

he he nobody really understands setacl's command line, it's more confusing that the one of most linux/unix apps ,

just found there is an easy solution to save and restore security informations http://www.coderforlife.com/projects/utilities/#security

[WinNTSetup v5.4.1]

@ilko_t & BlueLife,

happy you like it

@ click-click

with windows vista and later most system files belong the "Trusted Installer", no sure why this is so.

At least this is no real security feature, since every elevated process can simply change the ownership.

Windows 7 have takeown.exe and icacls.exe to change the rights, but if you also need to do this under Windows XP, SetACL is a better option.

Here a batch file example to change the permission of 3 files, so everyone with admin rights can use them, as he like.

@echo off
for %%c in	("D:\Windows\System32\eventvwr.msc"
		 "D:\Windows\System32\compmgmt.msc"
		 "D:\Windows\System32\gpedit.msc"
	 ) do (

	SetACL.exe -ot file -on "%%c" -actn setowner -ownr "n:S-1-5-32-544;s:y"
	SetACL.exe -ot file -on "%%c" -actn ace -ace "n:S-1-5-32-544;p:full;s:y"
)

Not sure what the problem with power schemes and the reg file is, can you give more details?

Also there is powercfg.exe that can export and import power settings.

[Anyone successfully get sound in PE 3.0?]

Why not simply use MakePE3? It have working sound.

[WinNTSetup v5.4.1]

oh, sorry to hear you had problem with vboot driver.

If you find any way to get this work with vmware, let me know. I have mostly given up Vmware since i switched to windows 7.

[WinNTSetup v5.4.1]

Update: Version 2.0.4.41

- automatic decompression of ntldr/setupldr/bootmgr on NTFS compressed drives

- drive selection will not accept read only drives for boot- and installation drive

- improved VHD creation and installation*

- added option for instant creation of fixed VHD's

- added support for FAT16 and exFat boot drives

*VHD creation now uses diskpart script like this

create vdisk file="C:\Windows7.vhd" maximum=25600 type=(fixed|expandable)
select vdisk file="C:\Windows7.vhd"
attach vdisk
create partition primary align=(32|64|128|256|512|1024|2048)
active
format quick fs=ntfs label="Win7 VHD" uint=(512|1024|2048|4096|8192|16K|32K|64K)
assign letter=X:

In rare cases without setting fs=ntfs, diskpart will format the partition with FAT32.

Partition now active and the installation to a VHD will now create boot files inside the Vdisk too. (So you can boot this VHD also in VirtualBox)

Further due to the long time required by creating big fixed VHD's, there a new option: instant creation of fixed VHD's

Also added Alignment and Allocation option to GUI.

[WinNTSetup v5.4.1]

I'm sorry, but i can not add support for vmware mounted disk.

Even after updating the PBR and create a correct BCD store, bootmgr will at least try to boot the OS, but fail in a black screen.

There is a good reason why the checkbox for read-only mounting is always set, the driver corrupts data.

VMware is very immune against bug reports, so i don't think this will be fixed anytime.

There maybe is a solution, the vmlite guy's have written their own driver which can mount vdi/vhd and vmdk images.

It's in the current version of VBoot

works very good so far:

vbootctl.exe mount "VMware.vmdk"
vbootctl.exe umount Z: