lyledg

No not really, guess I like to keep all the commands in one batch file, easier to manage over time.. Cheers

No probs, glad I could help!

Did you you use the -/qb switch on the end of the msiexec command?

This has certainly got something to do with your boot.ini file. I was getting the same result and had to change the volume number to 2 to get it to work for me

Hey all I need to run a script that normally would have been launched from cmdlines.txt, but I am unsure how to incorporate that file, and\or if there is a replacement in WinPE 2.0 that will do the same job? Cheers Lyle

As I have spent quite a lot of time to solve this puzzle, I have finally cracked it and thought I would share this and my scripts with others: I was getting symptoms of the textmode setup looping and running twice...and then getting the error: Scripts that I used to get this to work.. DiskpartActivate.txt Select Disk 0 Clean CREATE PART PRI SIZE=32000 ASSIGN LETTER=C: Active Exit STARTNET.cmd @echo off Echo Intialising WinPE 2.0 environment wpeinit Regedit /s fixbootxp.reg cls Echo Executing Diskpart script Diskpart /s DiskpartActivate.txt Cls Echo Formating drive..please wait Echo Formatting C: drive echo y | Format c: /fs:ntfs /V:SYSTEM /Q /X cls MD C:\Build MD C:\Build\i386 Xcopy /CHERKY F:\I386\*.* C:\Build\i386 echo Preparing boot sector... bootsect /nt52 c: /force cls echo Beginning Windows XP installation... C: cd build\i386 Winnt32.exe /syspart:c: /unattend:C:\Build\i386\winnt.sif exit A few things to note: 1) If you follow the recommendations from MS, it says to use the /syspart:c: with the /tempdrive:C switch...I think this was the switch giving me hassles as after I removed this I found it worked for me in the end, omitting the /tempdrive:C in the command line 2) I copied the i386 locally first...I guess the /makelocalsource command would do the same thing, just not tested. 3) I used the Bootsect.exe (110k) from the OPK...not the WAIK...again I am sure they are the same 4) The Drive letter "F" in my startnet command is my CD ROM Hopefully this helps the next guy Cheers

Never Mind, i now realise I had to go back to the root folder of the CD drive. Sorry

Guys I have seen numerous posts with regards to the topic, but nothing definitive. Basically I am trying to integrate and launch a WinXP installation from a CD\DVD (I don't a have a server for deployments), using WinPE 2.0 I can successfully create the WinPE 2.0 image, edit the startnet.cmd and the recapture the changes into a *.iso. But have no idea where to place or integrate the XP i386 folder where winnt32.exe is located. I have read that the i386 folder should not be placed into the WIM, which I understand, but then where does the i386 folder get placed? Once I boot up Winpe and navigate to the root (x:) I only see the following folders: Program Files Users Windows Sorry if this is a dumb question, but I am stumped! I'd appreciate your help Cheers

Guys I am having issues in the fact that I have managed to launch Winnt32 with the following procedure, but setup fails to go into the GUI portion of setup This is my current Startnet.cmd @echo off wpeinit regedit /s fixxpboot.reg cls Echo Executing Diskpart script Diskpart /s DiskpartActivate.txt Cls Echo Formatting C: drive..please wait echo y | Format c: /fs:ntfs /V:SYSTEM /Q /X echo Preparing boot sector... bootsect /nt52 c: /force cls echo Beginning Windows XP installation... F:\WinXP\I386\winnt32.exe /s:F:\WinXP\I386 /syspart:C /tempdrive:C /unattend:F:\WinXP\I386\winnt.sif /makelocalsource Winnt32.exe launches , however after XP copies the files locally, runs the text mode setup once and reboots, the process is repeated..meaning the Blue textmode setup runs again, instead of going into the GUI portion of the Windows setup routine.. I am completely stumped! Any ideas why this happens? Also, I noticed that Bootsect.exe from the OPK is 110k in size, compared to that of the WAIK of 83k...does it matter which one is used? I have tried both without success Cheers

Guys I have played around with this msi and got it to install completely silently. I edited the msi's properties table to include the parameters : "USERPASSWORD=pcpassword USERVERIFYPWD=pcpassword USEREMAIL=email@email.com USERWEBPASSWORD=password LicenseType=free ", instead of passing them via the coomand line as others have done before.....Just neater this way and less room for error. Trep - I got the same error as you, and edited the msi with ORCA and dropped the DEPLOYID row in the PROPERTIES section of the *.msi. That seems to get around the error you mention Also, in relation to this issue I found using the /qb- switch instead of the /qn, it ignores the ..."profile does not exist" error and the msi installs successfully Cheers

Mate, thanks so much for this...this has solved my problem! Cheers

Hi I am wanting to add a custom folder with some files into the BDD 2007 structure, but I have no idea where to do this? Would I create a script to copy this folder and place it in the Task sequencer, or is there a way to either edit the CustomSettings.ini or place the pre-populated folder with contents in the \Distribution\$OEM$ share somewhere?? Any help would be greatly appreciated! Thanks!

Has anyone any ideas on this please? I have a problem where temporary folders created by MS hotfix installations are not being deleted after an install, thus leaving a mess on the HD. When I try to delete them, I get an access denied. This is because the ACL gets screwed at installation time and hence I need to restore the ACL using XCACLS So, I need to do 3 things here 1) Find ALL folders as shown in the attached Pic. All these folders share the common structure of: C:\<RANDOM File Name Created here>\sp2\update 2) Once they have been found, repermission the folder using XCACLS 3) Finally, delete the temp folder with all sub dirs

Hi Guys Has anyone come across this problem before? Basically, I am having an issue with Hotfix temp folders not being deleted after it has successfully installed. If I try and delete the folders, I get access denied. The hotfixes are installed via a domain admin service account, It seems the ACL's get screwed along the way. I have managed to find a work around by taking ownership of the folder first and then manage to delete it, but I need to automate the deletion script The problem is because the folder names that get generated are made up out of very random characters, there is no real way to detect the folder names via a batch script or anything else for that matter??? Please see the attached pic to see what I mean.. Any help would be much appreciated!! Cheers

Best way I have found to do manual replication is using robocopy from the Win2k Server Resource kit...

Does anyone know how to bypass this nag screen (via the regsitry or anything else) at the first logon after Win2003 SP1 is installed? See the attached pic.. Cheers!