Ok, but from my understanding, using the method you mentioned above, the after textmode support is done VIA oempnpdrivers path in the winnt.sif. I ONLY want to use pyron's method for After textmode drivers (it allows for easy integration of driver pack update + additions, so I don't have to keep slimstreaming) and plus the drivers remain on DVD. ← Then there's something WRONG with your understanding Method 2 = Pyron's Method != OEMPnPDriversPath in wint.sif *only* Pyron's method *after* textmode setup? It's impossible to use Pyron's method DURING textmode setup, which leaves as only option... after textmode setup. If you still don't understand what it all exactly does, please contact me through MSN... ← Ok, I have just added you to msn. I thought with Pyron's method, drivers are unpacked from the dVD on to the HD, and then his setdevicepath.exe reads the infs in the directory, and tricks the GUI portion into looking there for the drivers? I thought it makes nO entries in the winnt.sif? I have been using this method all along from this sticky http://www.msfn.org/board/index.php?showtopic=12566 "Normally there is one way to integrate drivers in Windows 2k/xp/2k3. Specify oempnpdriverspath in winnt.sif / unattend.txt / ristndrd.sif / sysprep.inf or patch the resulting DevicePath Registry Value directly using SetDevicePath.exe by Pyron. The problem is there is a length limit of 4096 characters." I am using the setdevicepath.exe