Search options (Page 154 of 159)

Maybe at a future date.  For now, let's just concentrate on getting it working. 

I can't tell the differences either. 
I'm guessing that the panel itself had some "HD" indicator on it.  My case (and the client's case) doesn't have any markings at all on it.  His machine worked fine using the AC97 front panel install with the Intel CP so that's what I'm getting together for now.  If we want to add the choice functionality in a later DP (can o' worms if you ask me) then we can add that into the DPbase and an ini.

I'll upload a test maybe tomorrow or Sat (I'm swamped at the moment).

First:  Welcome to Driverpacks!
Second:  You should not be unpacking the driverpacks and integrating manually, the DP Base application will do this for you. (link to tutorial)
Third:  Your Intel issue is being addressed in a testing driverpack by jtdoom.  Be patient. 

Personally, I feel that only webcams that are built into systems (ie. notebooks or monitors with embedded cameras) should be supported since external webcams can always be installed later by downloading the appropriate drivers.
That's just my opinion though.

I install the drivers for my logitech fusion after everything is setup and the installer auto-downloads the latest release upon install anyway.

You'd need a special adapter for that.  You should connect it to an actual notebook for testing.

I just re-read this thread from the beginning. 
Aside from the licensing issues, I believe your problems are with your source.  You said you are using a Dell restore disk to build a custom XP disk to use on a non-dell system.  Good luck with that.  Everytime I have ever tried with that type of source I have failed.  I only use hologramed original CDs as source and I've never had a problem. 
The chances of this Dell disc having the drivers you need for a non-Dell system is slim to none.

I installed again last night using a test driverpack I built just for this machine and it installed perfectly.
I'll be doing a comparison between the release DP and my DP to look for bugs in the next few days.

I just tested on a desktop x300 radeon.  No errors! 

QSC should have had nothing to do with your initial integration.  QSC only speeds up subsequent integrations because all the hard work (compressing/decompressing/shifting) has already been done and the DPbase just pulls files from the cache instead of doing all the hard work again.
FYI, I always disable QSC because I am always changing the DriverPacks (averaging 2 integrations per day for testing).

As for the "method 1 slimming".
If you're only installing on a limited hardware base, you can open each DP, delete the folders not needed, then repack and integrate.  Double-check to ensure the folders you deleted are not referenced in the DP ini file for each ini.
Make sure you delete the files in the QSC if you pursue this method since DPbase will pull files from the QSC first and your changes will not be used (unless you renumber your DriverPacks with a higher number.

Method 1 is your problem.
There's a limitation in the way Windows handles the driver entries (path string statement limit of 4096 characters.) and method 1 exceeds that limit when using all the DriverPacks.
Your best bet is to use Method 2 and if you need access to all the drivers post-install then enable KTD (keep the drivers).
Method 2 is much faster than method 1 anyway and should be the default.

Just make sure the floppy is inserted immediately following the "press any key to boot from CD" prompt.