No, you are right, but maybe you missed something. The NTLDR (the real one) will parse boot.ini and, based on user selection, will invoke ntdetect.com to boot if a NT/2K/XP/2003 has been chosen or simply pass control to a bootsector. The "PE" NTLDR (actually SETUPLDR.BIN renamed to NTLDR) will read WINNT.SIF and boot whatever is specified there. See also my posts here: http://www.911cd.net/forums//index.php?showtopic=17538 If I get right your original setup, you had in boot.ini an entry like: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP" /fastdetect that booted XP, and one like: C:\bootsect.dat="Windows PE" Since the boosect.dat is actually a bootsector, it will try to load another NTLDR. So you have now a situation where the data in the bootsector, which contains partition information, is no more correct (since you changed partition size), and thus it cannot find the file. The use of GRLDR is very convenient, but if you want, it is possible to fix the problem in some other way. I need to understand how your original setup was made, and how your hard disk is currently formatted if it is FAT16 or 32, recreating a bootsector is very convenient using bootpart, then you can rename setupldr.bin to (for example) PELDR and hexedit the bootsector accordingly.... Or, you can use, even from batch a combination of dsfo and gsar to copy your current bootsector to a file, then sustituting in it "NTLDR" wit "PELDR".... jaclaz