I saw again your edited first post and saw your site - no info about this. while you mention there to put the i386 directory under the PRO1 directory, in my case the PRO1,PRO2, and PRO3 are *the* i386 folders. [maybe that was a crucial difference and that's what is causing errors for all these people, but I see no reason why it can't be adapted to my directory structure] I already said : 3. i've edited txtsetup.sif - SetupSourcePath = "\PRO2\" is the only modification i made. I changed the path appropriately in each of these - PRO1, PRO2, and PRO3 are the former I386 directories. To describe what I did: PRO1 is NOT containing any other files or the I386 folder. It is *the* I386 folder itself (renamed and no other mods except for txtsetup.sif). So, for example, if E:\ is my cd drive, I edited E:\PRO1\txtsetup.sif as per above. My cd idents are not corrupted and are in the root of the CD (just to remove ambiguousness, they aren't in a folder "ROOT" on the cd, they exist directly as files in the CD's root). >> It would be easier to use boot folders to boot the cd from. if you meant this - C:\$WIN_NT$.~LS - rename this folder to install C:\$WIN_NT$.~BT - rename this folder to BOOT (all capital letters) I tried to keep modifications to a minimum, so I'm not using the "reducing source" at all. if you mean that I can put the boot sectors of the CD in a single folder, i'm already doing that. I use EasyBoot. Before anybody says that the problem could be with using EasyBoot, see the relevant "point No.2" in my previous post here. Some more details - 1. my setupldr.bin is in the PRO1,PRO2,PRO3 folders (which were previously the I386 folder). 2. That's the proper location, and it's properly hexed, that's actually why the text-mode install starts up at all. So that rules out any error with the setupldr.bin or the xpboot.bin 3. Just to clarify, I declare I don't have any other setupldr.bi_, txtsetup.si_,dosnet.in_ and such lying around on this CD - the only such files are the edited ones. I tried editing dosnet.inf from to because PRO1 is my I386 folder now. But dosnet.inf can't be the reason because as far as i know it's used only at the file-copy stage, and here, I haven't even got past the EULA. I even tried leaving txtsetup.sif at default: SetupSourcePath = "\" It still doesn't work. To be exact, this is the problem many of us here are facing: 1. Starting the normal install after booting from CD gets past the "press Enter to setup windows", "Press R to use Recovery Console", "F3 to exit setup" stage. Pressing Enter brings up the Agreement screen - it then searches a bit for the EULA, and gives up saying "eula.txt not found, press F3 to exit setup". That's the end of that route. 2. On the other hand, booting and choosing the unattended setup directly pops up a screen saying "this is an upgrade CD, please insert the retail CD, or press F3 to exit setup". No option works at that stage, except to exit. My opinion is this variance with unattended happens because the winnt.sif file was accessed and it tells setup to skip the initial screens and stop for input at disk partitioning. But right where it is supposed to show the EULA and "Press F8 to agree", it finds that it isn't able to even see the eula.txt file that's meant to be skipped. So it deduces somehow that it's got to be an upgrade CD and not a retail. I am puzzled seeing that if it is able to follow the winnt.sif file, why not also see the eula.txt. In both cases, Setup loads as it normally would - with all the million RAID and SCSI hardware drivers. I hope this post gives enough info for someone to detect the error, or for someone to duplicate the error, and tell us what's wrong. Cheers !!!