When a installation of Windows XP starts up with RIS, it starts by copying the i386 folder to the local harddrive. if there is a distribution folder, it will also be copyed. next it starts the normal Windows XP instalation, no diffrent to if it was started by a bootable CD. With your method of installation, all the driverpacks will get copyed to the local harddrive by the distribution folder. A script will be started, unpacking the drivers and found by Windows XP plug-and-play under the installation. That's nice, but not if you have a newer netcard than windows XP supports. You will get an error that your netcard is unsupported, and then the network administrator has to include the driver in the installation by copying it to the i386 folder. (no need to copy it to the distribution folder because of the driverpacks inclued) The text portion of the Windows Installation need the drivers because it swithes from PXE (UNDI) to SMB mode. I also dont see the point of compressing the pnf files as they are auto-generated by the binlsvc service when you include a new driver. We have 21 Windows XP installations and 5 Windows 2003 installations in RIS. we also have about 15 diffrent client netcards. When a new client arrives, we have to include a new network adaptor, and the driverpacks from BTS is a wonderfull source. ---- Are you sure it's a good idea to compress all those files (in the guide) netcards supported by a normal Windows XP SP2 RIS installation is no longer supported when i compress the drivers (sys, inf files) ---- My posts are ment to improve your guide and not to question your knowledge about RIS and unattended Windows XP installations.