Innocent Devil

to further for a BIOS based PC only two folders required boot and sources (with right content) efi, upgrade etc can be deleted also from boot directory etfsboot.com,memtest.exe,bootfix.bin and fonts folder can be removed i m not sure abt the en-us folder, probably it can also be removed

Sources Directory need only the two files boot.wim and install.wim it works fine on dvd boot UA BTW does anyone know how to change the path and name of install.wim ie "\Sources\install.wim" of default to somthin like "abcd\def.wim"

that might be dvd region problem ,i think u r drive may have region locked and the dvd is not in ur region try changing dvd drive firmware to region free

F10 is available for Vista and higher OSes only it is for editiong the boot options like NoExecute or DDISABLE_INTEGRITY_CHECKS or any other documented boot options it is an extesions to the "loadoptions" bcd setting, that allows dynamically adding boot options (like the linux loaders can do) for older oses, it is not possible as bootmgr loads the ntldr only(then ntldr scans the boot.ini for boot options), adding any boot options by bootmge willbe ignored by ntldr as it only searhes boot.ini

to be on safe always keep mirror ISO and Joliet structures along with UDF (ie select ISO/UDF type in Nero) unless u r having verry big files >2GB Also check the UDF fs version some new UDF versions cannot be read by OLD Oses. i dunno abt mac OS support or not the UDF 2.5 but sure it cant be read in XP

the sfc problem persist in 2k3 sp2 too, besides XP this probly due to improper setting of HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SfcDisable to 0 It should be 0xffffff9d manually making the change doesnt persist over a reboot. EDIT: Thanks Mauri , for pointing out th err , it was a typo

why use litestep ? why cant the "shell" be directly c:\windows\ehome\eshell.exe ???

So does this solve the problem ?? dexter.inside, plz update "The Art of OEM" with this

thanx i managed to create a new scsi hd attached to ame machine and imaged ide drive from winpe to the scsi disk then i mounted the scsi disk using vmount2 and copied the install.wim isn't weired ??

bocoz the install.wim is now in \Vista\sources dir which is supposed to be in \sources dir i dunno how to change the path of install.wim in the setup.

just For the Info : Probably this issue can be solved by looking at u r setuplog.txt This logs vary neat scktch of how the setup is performing. btw by some change u can increase the verbosity of the setup logging (i dont know which is , plz let me know) The setup is done by setupapi.dll.(All setup routines call setupapi procedures) This dll seeks the help of dosnt.inf,txtsetup.sif and layout.sif to accomplish the task. It has only directives like processing sif or inf files to get sections,parameters and values (say winnt.sif ,[unattended] ,Unattended = 1) "find filenames from dosnet.inf or txtsetup.sif and paths from txtsetup.sif or layout.inf and copy/install it" By that time we have cd in cd drive and all file paths can be correctly mapped Now the files are copied to the locations specified in txtsetup.sif Then builds the bare registry using hive*.inf files Sets up bootloader,boot.ini Thus Textmode is over and it reboots... The setuplog.txt and setupapi.log begins here The next steps prepare the system to continue install these steps are similar to "ComplianceCheck" in Vista After processing paramters from SIF and so and so... it comes to "BEGIN_SECTION,Initializing regional settings" here it processes intl.inf, the Language Settings At this stage the problematic files are being copied. These goes to nonstandard (not in %path% variable )locations like windows\fonts\,WINDOWS\msagent\intl\,WINDOWS\help\ This is normal scenario wen installing from cd , completes without err as the files are readily availabe from <CDROM>:\I386 ########################################################## The problem : Sysprep -reseal -mini-setup Scenario: reads the c:\sysprep.inf file and process the language settings Now it searches for those files in path specifiedby "InstallFilesPath" of Sysprep.inf From ref.chm of deploy.cab Suggestion: Read documentation CAREFULLY before you do. B) Doesn't the OEMs ship their image with C:\sysprep\i386 ? as, that after running sysprep, the folder get automatically deleted and no space wasted on end user's system. To Nuhi: There is nothing wrong with nLite on this issue AFAIK. Good is that u addded a sysprep compatibility that saved OOBE, which otherwise will result some weired error i got with some old builds trying to do the same.

WinFPLs PE is NT 5.2.3790 (Workstation built of 2k3 ) how can a BartPE built from srv03 sp2 std edition support Panther ? even after satisfying the dependancies the pather setup stays at "Starting Setup ,Please wait...." not at all progessing... is there any workaround for 2k3 sp2 BartPE ?? XP PE is not supported at all (setup complaints requirement of a .NET capable PE) Another weired prob: the vmware cmount2 deosnt recognizing my virtual disk partition (which created using XP in the Virtual machine) in virtual IDE disk Virtual disk partitions created by Panther or vista RTM PE are recognized (both IDE and SCSI on a new virtual disk disk) just only one virtual disk (on which i installed XP), all others are detected by vmount2

to aviv00 just make independant wims of ur choice like u said 1. a fully edition --full.wim 2. full edition without langs and drivers --- nolangdrv.wim 3. like 2 and few more stuff that removed --2removd.wim 4. ripped off everything ---allremvd.wim now do "imagex /append " to append all these imagex to singe wim now select requied wim the Answerfile

easy way : just put sources folder to WinFLPs disc delete Setup directory add setup.exe to run from winpeeshl.ini load setupreg.hiv from I386\system32 and change value of SETUP\CmdLine from "\Setup\SetupLauncher.exe" to "winpeshl.exe" it worked like a charm..

u have to create the boot configuration data for loading Vista's WIM int \boot\bcd ie the "Windows Vista" should have a proper defnition in the bcd like "Windows Setup" no just loading the \Vista\bootmgr try to copy the settings of "Windows Setup" and change the paths of osdevice and device options

why u r trying to redo the vista installer as fizban2 asked ? AFAIK, u just make winPE script to run imageX to apply the created wim on target hdd and reboot then sysprep will do the rest on booting up the target machine

bootmgr is the "bootloader" not the Boot Configuration Data (aka BCD) the dvd bootsector ( etfsboot.com ) always loads the bootmgr from ROOT of the DVD this bootmgr checks for the boot configuration data in <DVD_ROOT>\Boot\bcd file (This is same as what u seen in HDD install too The bootmgr in C: drive loads only C:\Boot\bcd) So you have to edit the <DVD_ROOT>\Boot\bcd store in order to load any other u did wat is to instruct <DVD_ROOT>\bootmgr to load <DVD_ROOT>\Vista\bootmgr --> Okay this is working but then <DVD_ROOT>\Vista\bootmgr searches <DVD_ROOT>\Boot\bcd and loads the file Thus it goes in a loop. Okay to solve the issue first understand how <DVD_ROOT>\Vista\Boot\bcd loads the OS ( bcdedit /store <DVD_ROOT>\Vista\Boot\bcd /enum /v ) then copy the same conf to <DVD_ROOT>\Boot\bcd by creating ne entry in the store u should change the bcd parameters like osdevice which by default will be ramdisk=[boot]\boot.wim,{GUID} to ramdisk=[boot]\<properpath>\boot.wim,{GUID}

to do 888111 follow this way: extract 888111 with -x switch look for the commonfiles folder in it Add this folder to nlite driver integration section from now onwards u can install u r own chipset's driver (Realtek, SigmaTel,AD,C-Media...) once this has been loaded by windows (ie after the 34 min mark) i usually install reaktek driver by RunOnceEx by setup -s switch To nuhi: gr8 work for both nLite 7 Vlite, u made my XP &Vista rocking can u make this automatically in nLite (adding UAA driver to driverslist wen adding the 888111 hotfix) ? plz...

try the exe - "winload.exe" or caused by 32bit editing tool unable to detect the 64bit exe Arch, and resource locations in the binary.....

ya, i think it is possible, i could do that from isolinux wen i tried havnt tried on easyboot it is quiet possible, bcoz etfsboot.com is similar to the cd boot image for XP and 2003, with some updates and instead of "SETUPLDR.BINBOOTFIX.BINI386" string in XP this uses "BOOTMGRBOOTFIX.BINBOOT" string so may quet similar

try "-store" instead of "/store" The command require Admin Privilages bcoz it uses HKLM registry hive so in XP u require Admin account & in Vista aministrator Privilaged Command Window

Try the old way "Trial & Error" I remoed movie maker and DVD maker in my build later i mountted original wim and coped the folders from dvd to Program files got some dll missing error, copied it too, regd the dll -- got them working u can also come this way.....

oops, i didnt see u r post u can try this [link]http://www.msfn.org/board/index.php?showtopic=99823[/link]

To create multiboot dvd with XP and Vista, first we have to add XP to bcd store of Vista DVD's bcd copy vista dvd to folder say d:\vista-l Copy XP CD to the same folder (i386,WINIP etc should be in the root of the disc along with sources, boot etc) open cmd and type (get bcdedit.exe from Vista DVD's boot folder) bcdedit /store D:\vista-l\boot\bcd /create {ntldr} /d "Windows XP setup" bcdedit /store D:\vista-l\boot\bcd /set {ntldr} device boot bcdedit /store D:\vista-l\boot\bcd /set {ntldr} path \I386\SETUPLDR.BIN bcdedit /store D:\vista-l\boot\bcd /displayorder {ntldr} /addlast bcdedit /store D:\vista-l\boot\bcd /set {bootmgr} displaybootmenu yes okay, now the boot store is ready. Now create the DVD image as usual using cd image cdimage -lXP_Vista -j1 -u1 -e -m -h -bD:\vista-l\boot\etfsboot.com D:\vista-l d:\xp-vista.iso Similarly any NT based os (atleast XP, 2003) can be booted using bootmgr Even More!!! u can use boomgr without vista source ie, it can be used for creating multiboot dvd of XP, 2003 etc only u need the "boot" folder and "bootmgr" at root of DVD/CD Testing : I did it with vLited Vista and nLied XP Pro UPDATE: 1. Delay in XP setup due to UDF filesystem It is been reported that -u1 switch for cdimage causing delay in XP setup. Possible reason 4 this will be due to XP setup reluctantancy to load files from mirror UDF filesystem than joliet (-j1) file system. AFAIK joliet filesystem max. single file size is 2GB if u r install.wim is < 2GB then no problem occurs on avoiding -u1 otherwise u need u include -u1. 2. multibooting vista/server 2k8 Since the path (and name) of install.wim is hardcoded to <DVD_ROOT>\Sources\install.wim it is impossile to install them along in same dvd using bootmgr. If anybody know workarounds please post it. Suggested solution is to merge the install.wim's Thus making single install.wim with versions of Vista and Server 2k8 (like merging Vista x86 & x64 into one wim) and selecting required version from unattened.xml 3. To remove ems support (the vista entry shows Windows Vista Setup [EMS Enabled]) bcdedit -store D:\vista-l\boot\bcd /bootems {bootmgr} OFF

I agree neo Bitdefender is best, i m using it more than a yr in XP and now in Vista abt 7 months only problem u suffer is memory use ~ 25 mb is used