BikinDutchman

Registry changes to HKU\.Default or HKCU during installation of windows, BEFORE the first logon are incorporated in the %SystemDrive%\Documents and Set-tings\Default User\NTUSER.DAT. New user profiles, including Local System, Local Services, and Network Services, are replicated from %SystemDrive%\Documents and Settings\Default User, and that includes .\NTUSER.DAT. That file is completely built before the first user logon, and cannot be edited directly by one of the registry editors (HKU\.Default is the Local System profile!). To modify %SystemDrive%\Documents and Settings\Default User\NTUSER.DAT, it must be loaded into HCU with a new key name, followed by applying modifications under that key and unloading. This can be automated with the Reg.exe command line utility.

It is not that difficult Assuming you have two drives, for instance your HDD and a CD or two partitions on your HDD Use Notepad to make a file Install.bat with the following 3 lines: SET InstallRoot=??? SET SetupFiles=%InstallRoot%\WinXP\i386 %SetupFiles%\winnt32 /s:%SetupFiles% /syspart:### /tempdrive:### Change ??? in the first line into the drive or path were your windows installation is (Example D:) Change ### in the third line into the letter of the drive were you want to install (example F) Execute Install.bat ### must be active on reboot, you can make drives active with FDISK If ### is the Win98 disk, the XP installation may overwrite your Win98 or you make it dual boot. Try at own risk, backup your critical data before going into this type of monkeying I also uploaded my Install.txt; you must rename to Install.bat yourself. Install.txt

you can try something like this from a Win98 session: -%SetupFolder%\winnt32 /s:%SetupFolder% /syspart:F /tempdrive:F %SetupFolder% is your new windows i386 folder F is the drive where you want to install The idea is that F becomes the active drive so that your computer boots from that one after restart

I do these installations a lot, I am not sure whether this was already mentioned in one of the many posts but the regular Microsoft method is: -You need to have your driver files (from the floppy) in CD\$oem$\Textmode -You need to have something like the following statements in your unattended file (CD\i386\WinNT.sif): [MassStorageDrivers] "Marvell 61xx SATA Controller Windows 32bit Driver" = OEM [OEMBootFiles] mv61xx mv61xx.cat mv61xx.inf mv61xx.sys mvnodrv.inf Txtsetup.oem -The entry under [Defaults] in txtsetup.oem should point to the correct configuration -Make sure the file locations in txtsetup.oem are correct (watch out for subfolders on the floppy) The details for your system are different. I do not know how nlite integrates this. This is not a normal driver integration. If you think this is the way to go I might give a little more detail for your system.

Had a similar problem after nLite 1.2.1 integration of video drivers (ATI and Intel): -Resulted in a failed DHCP request right after installation (the RCP server could not be reached). This was resolved after one restart but I decided to not integrate the video drivers.

I install nLite-WinXP in a WinPE session with the installation folder on a network location (no CD needed): %NetSetupDir%\winnt32 /s:%NetSetupDir% /syspart:C /tempdrive:C /udf:%ComputerName%,%UdbFile% /unattend:%AnswerFile% Works great with Xable's Update Pack. KB888111 integration works fine in nLite 1.3, except for one small thing: a copy error for portcls.sys during the GUI-Mode part of the set-up. I can fix that by removing DOSNET.INF > [ForceCopyDriverCabFiles] > portcls.sys, and everything works perfect with the SP2 version of portcls.sys copied. Would it be a problem for the final nLite 1.3 to leave portcls.sys out of the [ForceCopyDriverCabFiles] list? Nuhi, thanks for looking into this.