fredm54 wrote:

Are there any leftover folders or files on the hard drive now that are no longer needed and can be deleted?

No. DriverPacks Finisher cleans up after itself.  You could check the root of your c: drive if a residual \D\ folder exists (it should have been deleted by default).  Other than that, you're fine.
Welcome to the world of DriverPacks. smile

Have you tried using DriverPacks BASE to integrate dpms into your XP source?  If so, can you post your DPs_BASE.log?
Can you post your HWID list using the tool in my signature?

fredm54 wrote:

So how do I tell which folders in the DP are 64 bits drivers?

Easy, none!  We don't support XP-64 in fact we actively remove 64-bit drivers wherever possible.
We also actively discourage nlite.  Never use nlite for drivers and you'll be happy.

453

(14 replies, posted in News)

Woohoo!  That's 645 idiots we don't have to deal with.  Thanks Wim!

454

(14 replies, posted in News)

352 blocked spammers since 2012-04-08 14:04:04
Last 24 hours: 10
Last 7 days: 74
Last 30 days: 352

I wish there was a "total" number.

Well, I don't know what to tell you but that file isn't in any of the DriverPacks. 
It's not missing, it was never there to begin with.

It's part of Microsoft Visual C++ Redistributable package.

You answered your own question.

artdesign wrote:

I have a motherboard Biostar P4TSE ver 1.1

http://www.biostar.com.tw/app/en/mb/int … &tab=3

Incidentally, those drivers are already in DriverPacks.

457

(2 replies, posted in Feedback and Support - DriverPacks Base)

Normally, there should be no problems with that many drivers other than space.  Keep in mind that there is a hard 4096 character limit in the "driver path" setting.  Keeping the folder names as short as possible is critical.
This problem is in our FAQ.
Your other option is to use our SAD2 script which doesn't have those limitations.

458

(2 replies, posted in Other)

You can use nlite to modify your source if you wish, but do NOT use nlite to integrate any drivers.  Use only DriverPacks BASE to integrate drivers.  This should be clear in the tutorial.

459

(2 replies, posted in Site & Forum Issues And Feedback)

TechDud wrote:

From one of the Misc Guides: http://driverpacks.net/docs/miscellaneo … er-attempt
search for "Private Webcam Seite"

Done!

Excellent first post!  Welcome to DriverPacks.
I can see that you will fit in nicely with our rag-tag bunch o' misfits! big_smile

Thanks for the tip.  I'll add that in for the next release.

BTW, seeing as you know what you're doing, I've upgraded your account to the "testing team".
Welcome to the team.  You'll find more areas of the forums unlocked for you.

461

(2 replies, posted in DriverPack Sound)

We don't support Apple hardware.
But Apple does.  You should contact them.

Boot Camp Software Update 3.3 for Windows
http://support.apple.com/kb/DL1443

The Boot Camp Assistant should download the correct drivers for your computer, then offer to place them on a CD or USB external storage device. These drivers are designed for use with Windows 7. Windows XP and Windows Vista drivers are not supported for these computers.

462

(1 replies, posted in Windows 7 tools)

More information: http://www.microsoft.com/download/en/de … x?id=25175
Not directly supported by DriverPacks, but is favored among IT professionals for preparing deployment images.

Microsoft Deployment Toolkit (MDT) 2012 is the newest version of Microsoft Deployment Toolkit, a Solution Accelerator for operating system and application deployment. MDT 2012 supports deployment of Windows 7, Office 2010 and 365, and Windows Server 2008 R2 in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP.

Interesting!  I'll have to take a look.

Can you post the HWID list from that target system (use the tool linked in my signature)?  I'm sure that the system doesn't contain all 3 HWIDs you posted, but only one.  I need to know which one is in your system.
Odd that MSI links to an older version of the RST drivers.  Maybe I need to reshuffle the HWIDs again.

465

(2 replies, posted in Software)

LOL, that site is awesome!

Please post your DPs_BASE.log, DPsFnshr.log and the HWID list from the target system please.

467

(14 replies, posted in DriverPack Sound)

Via is in DriverPack Sound A.

DriverPack Graphics C is for legacy hardware.

469

(88 replies, posted in DriverPack LAN)

SamLab wrote:

mr_smartepants - When the expected release 12.04r1?

Want my smartass answer?  Sometime between now and 1 May (non-inclusive). wink

Seriously, I got super busy over the weekend.  I hope to have it online tonight.  But no promises.

That's just a ridiculous password length.  Not so much a pass-word than a pass-paragraph. sad

471

(36 replies, posted in DriverPack Sound)

If you're unclear on how to use DriverPacks, I recommend reading our tutorial (linked in my signature) as a starting point.  It's about 2 years out of date, but many things have not changed much since then.

472

(36 replies, posted in DriverPack Sound)

As indicated above, this was fixed last year.

The recovery console is removed because DriverPacks BASE sets the option (UnattendedInstall="Yes") in the winnt.sif file.
This is by design.
If you have (OemSkipEula="Yes") set then the license agreement is skipped.
For more winnt.sif options you can read here: http://unattended.msfn.org/unattended.xp/view/web/19/

You could post a request in the appropriate threads (with links to the drivers). 
Basically, the way SAD2 works is it extracts all DP_*.7z files and as long as all the files required by each .inf are available, dpinst will install the drivers.

Pichorra wrote:

Anyway, you didn't aswer this question:
--------------
Ah, since i'm posting this, is those drivers integrated there?
http://www.msfn.org/board/topic/51140-i … i-drivers/
&&
http://www.msfn.org/board/topic/107504- … d-drivers/
--------------

No.  We don't use any modified drivers in dpms.