Topic: XP Slipstreamed SP3 Easyboot Temp inst file error
started by: zia abbas
Posted by zia abbas on Apr. 09 2010,03:20
Dear Balder,Now am trying to put XP SP3 and W2k3 on on DVD.
steps performed:
1.dir under disk1 WXP3
2.Copy contents of XP CD (entire CD) to WXP3.
3.Copy files (win51*.*) from root of XP CD to Disk1
4.Save bootsect file of XP CD to ezboot (all Caps)
5.Copy boot files via xp.bat to WXP3
6.Edit Setupldr.bin in WXP3 replace i386 with WXP3
7.Edit txtsetup.sif in the WXP3 sourcepath from \ to \WXP3.
8. Put run command WXP3.bin
Burn ISO.
I get error : XP setup cannot find the Temporary installation files.
The same thing done for W2k3 respected changes to W2k3.
I get error NTLDR is currupt setup cannot continue.
Help
Posted by balder on Apr. 09 2010,03:56
@ zia abbasQuote: “Now am trying to put XP SP3 and W2k3 on on DVD”
Attention one! You can only use wxp.bat to English version of WinXP and only to the original WinXP (no service pack)
Attention two! You cannot hex edit files that belongs to W2k3 (I guess we are dealing with server-2003-sp1 or sp2 correct?). If hex edit setupldr.bin in server-2003-sp1 it gets corrupted – read post nr; 9 < HERE >
Note: you can also use my patcher in easyboot-aio.script to patch setupldr.bin (only use this option if you choose to do everything manually)
I’m sure patching works for setupldr.bin in service pack-sp1, but unsure if sp2 has the same setupldr.bin
If you run WinXP you can use my script easyboot-aio.script to fix this (not working in Vista or Win7).
Or use Gosh solution < HERE >
followed by reading “Reduce source” < HERE >
I know – you have some hard “work” in front of you – but I’m sure you solve it in the end – life isn’t always easy – he, he so look on it from the “bright side”
Regards balder
Posted by zia abbas on Apr. 09 2010,09:47
Balder 
I Got my Win2k3 server SP2 on easyboot all credits goes to you.
The only issue is I get 20-25 file not found error while copying files to hdd (soon after which PC restarts and gui mode gets load)
See have made this Win2k3 sp2 CD by nlite and have server server drivers into it. The files which are not getting copied are into the given paths:
1.\W2K3\I386\NLDRV\003
2.\W2K3\I386\NLDRV\004
3.\W2K3\I386\NLDRV\009\apps\IntelAMT
It seems these paths must be set somewhere into txtsetup.sif which there "I386\NLDRV\009\apps" I tried changing the path to \W2K3\I386\NLDRV\009\apps but no solution.
Also tried the failed files into i386 folder and into WXP3 folder but the probs continues.
Help
Abbas
Posted by balder on Apr. 09 2010,10:20
@ zia abbasQuote: “See have made this Win2k3 sp2 CD by nlite”
This is a common problem
– especially if nlighting source that belongs to Win2k3.Most likely the “NoReboot”-command that basically “makes a call” to txtsetup-file to only copy files that it’s supposed to do.
If you look closer to you nlighted source I’m sure there are differences comparing to the original source (some odd file with information that is needed for the whole process is put in nlightet source but is missing in the original source).
Note: I can’t give any “universal” advice how to solve this issue, as this is not related to my script or to “Ghosh”-solution. It’s related to how nlight behaves. Sorry but that
But you partly solved your problem
– on the other hand – you generally shouldn’t run nlight to Win2k3. It’s not recommended to setup a server from nlighted source – it’s to sensitive in the end 
Edit: I was thinking
– as you always can have one folder i386 on the root (easyboot\disk1) you can preserve this to the nlighted Win2k3 sp2 and only making hex edit to WinXP-sp3 etcetera. In this way it’s possible that Win2k3 sp2 runs as expected.Note: copy folder (nlighted) i386 of Win2k3 sp2 with its tag-files (win51 etcetera) and other folders that belongs to this source to easyboot\disk1 and use menu command: run W2ksect.bin
Consequently always use one folder i386 on the root of build – and use this opportunity to the “difficult” one – in this case Win2k3 sp2
Regards balder