• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bionicwarrior

  • Birthday 07/11/1980

Contact Methods

  • Yahoo
  1. Well, I will answer my own question. I tinkered along with the files and found out the solution myself. The problem seemed to be the vast number of folders in the extracted files. I changed it to 2 level directory structure and it seemed to work just fine. If anyone out there has a better suggestion, please post them. Thanks.
  2. I have been using nlite since quite some time and it is a wonderful program for the likes of us who are not satisfied with want microsoft gives us. Well I have also been using Bâshrat the Sneaky's DriverPacks along with nlite and find that the OemPnpDriversPath far exceeds the limit if I use all the driver packs. So I wondered if I cud integrate all those drivers directly with nlite without the DBase file. I extracted all the driverpack files and then proceeded to integrate them using the driver integration option in nlite. All the driver files are correctly detected, however, when the integration begins, nlite gives an error and closes immediately. I could not get the error message as it doesnt give time to read before closing. If I try to repeat the procedure, nlite gives the message that the windows installation files are broken and to use a fresh copy before proceeding. I am not sure what the reason is, but am guessing that the huge number of drivers is the cause. Also the total file size is around 2GB. Has anyone else tried doing this? Is there any fix around this problem?