bisabuelo

Someone PLEASE post a definitive, clear solution to the corrupt usbehci.sys file that many are experiencing when booting from their CD. I've seen so many posts, but many contradict one another. Anyone that's had success willing to share?

I am posting my runonceex.cmd file. Can someone look at it and tell me if it looks OK? All the exe files have been placed directly in the $OEM$ folder. Thanks! runonceex.cmd

can someone post instructions on what do when using the runonceex method?

am I correct in stating that everything in the $OEM$ folder is automatically copied to %systemdrive%\install? If so, do I just put all my application install files in that folder and then point the runonceex.cmd to that location? Also, where does one get .msi files for installing some applications like I see in many example .cmd files. Thanks. Nikhil

Hi, I'm brand new at this whole integration thing, so bare with me. I've copied the contents of my Windows XP Professional CD to my hard drive. This is a Dell OEM CD with no service packs already integrated. That part went fine. Now I am at the process of trying to integrate SP2. I've downloaded the network install with filename: WindowsXP-KB835935-SP2-ENU.exe. Using Nlite (latest beta available), I select the service pack file. It extracts fine, but when it begins to integrate, I get the following message: "This Service Pack cannot be integrated into a destination that also has integrated Software Updates. Consult the Serivce Pack documentation for more details about supported integration scenarios." And then it stops. Any ideas anyone? Help would be appreciated! Nikhil