Search options (Page 163 of 213)

Welcome to DriverPacks

please provide the info outlined in "read before you post" in my sig
(which is missing - LOL)

primarily your DPs_BASE.log and HWID's

looking forward to assisting you.

; Pieter's INF version 3.238
; http://www.laptopvideo2go.com

; NVIDIA Windows 2000/XP Display INF file
; Copyright (c) NVIDIA Corporation. All rights reserved.

Is what i find... lol (but that was in pack 8011 LOL)

Well that is how it was / has always been done...

The inf seeding that used to be done by m1 was dropped by me a few releases ago.
the separation of the OS platforms is no longer required. (unless they are unique - and they are not)

going forward there will be a new folder layout and we will need to populate the ini file to make DriverPacks chipset compatible with PE.

Thanks G!

Graphics C is mostly legacy drivers

and since graph c is mostly targeting older hardware there are few updates required.

relative to A and B of course

Welcome

http://forum.driverpacks.net/viewtopic.php?id=2695

the search feature may help you too

Thanks for the feedback and sample of what worked for you SamLab!

I agree code tags are considered required forum etiquette, especially for posts that include Code

since he is populating the registry key there is no 4096 limit.
this only applies to the winnt.sif (or equivalent) OEMpnpPath entry.

so i don't belive the extra work is required...
SysPrep is not my favorite method so i may have missed something...

Please use code tags... it makes for a diffucult read when you don't.
I updated your post, this time, please use good etiquette in the future...

well it seems to me you burned a lot of time re-inventing the wheel.
if you were more familiar with DriverPacks you would realize all this functionality is already built into the base program.

We call it KTD (Keep The Driver) it has been a feature for years
and is a Heck of a lot easier than to even think about useing all that garbage you posted.
And does the exact same thing...

So i have to ask myself "why would any one want to do it your way?" {confused}

now obviously mass storage requires a little work to get into sysprep, but the rest of teh packs work fine.

Also if you had familiarized yourself a little more you woluld have realized there is yet an easier method to use.
That post is in the forum i am going to move this post to (yes you put it in the wrong place also)
please see skinlayers and DeTards posts and see what others are doing with sysprep.

PS we are not noobs...

Most people steer away from this method because of the 1.5 gig the packs burn on the local HDD when you do it this way.
If you insist on KTD then i recomend that you use method 1 with KTD and QSC=on
this will yield a folder in the 500 meg range. (a 1 Gig Savings)
windows can use cabbed drivers without extracting them so this saves space and is accessable at the same time.
The cabbing process can take a long time the first time
on subsequent runs QSC will have a copy of the cabbed files ready to copy and save a lot of time

the finisher will not only populate the registry keys to find the drivers
but it also creates cache files of the infs for fast searching by windows.
 

have a nice day.

http://forum.driverpacks.net/viewtopic. … 159#p20159

you can use a program like nLite to remove unneeded files from your original OS (XP)
such as games or windows tour ect...
most of us have moved to dvd installs as it has become increasingly difficult to make it fit in 700 meg.
that and dvd readers are less than 20 bucks each.