Looking for a good DriverPacks Tutorial... (Page 1 of 3)

All you basically need is to use the BASE to slipstream the DriverPacks into your source.

There is no decumentation pre se, yet, however, all options are pretty self-explanatory.

Judging by your comments, the best thing for you to do is using Method 2 and KTD ALL.
QSC is only needed when creating more than one CD - to speed up things.
Finishing method is arbitrary as long asyou don't chose custom.

Just give it a try on a Virtual Machine (VMware) or Virtual PC (MSFT).

Also, make sure integrating the drivers is the very last step before making the ISO (which cannot be done with the DriverPacks BASE, yet).

Last edited by Bâshrat the Sneaky (2006-09-01 04:52:09)

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

Sorry,I don't understand this Line...Do you just mean that DBase.exe file can't make an ISO Image ? I know that...

I can Do that with a Number of Softwarez...Making ISO image and CD writing is not a big deal....

What is Slipstream ? may be a dumb question....

DBase.exe can Automatically Integrate all those Drivers Pack in our Windowsxp Source code and making Entries in different files just to Inform Windowxp that there is a Huge Collection available to be check... Am i Right...

WindowsXP will automatically search the appropirate Hardware drivers and Install it....???

Or I have to Configure any Manual setup...I don't want any Popup Or Configuration Screen after Windows Login Screen Comes,Becoz this way is quite Bad...All Packege should be as Microsoft Always Do with XP....

OK....
I will Choose Option 2 with KTD ALL.....

Yes, that's what I meant.
However, if you are doing other things to your source (you mentioned somehotfixes), this always has to be done BEFORE applying th DriverPacks.
So using the BASE is the last step before making the ISO.

Sure, but you need to include the bootimage somehow, else the CD won't be bootable.

Slipstream is what you call the integration of the SP1/2, the hotfixes or even the DriverPacks to your source CD.

Absolutely correct.

Check.

That's the whole point.
If there were any manual steps involved it wouldn't be a proper UWXPCD (Unattended WinXP CD).

Just as a sidenote:
KTD ALL will enable Windows to search in the DP drivers when you install new hardware after you've already installed Windows (eg new sound card).
Very handy if you change a lot of hardware, else you won't need it.
However, then, XP will only search in the MS supplied driver for the new hardware ignoring those that came with the DriverPacks.

The only downside is that it will take up a bit of HDD space.
Obviously it has to store those new drivers somewhere

Personally, I use nLite, because I need that anyway to slim my CD down.
Then I'm using nLite to integrate the German version of RyanVM (Sereby's Update Packs), hotfixes and addons.
You can do that with the Update Pack standalone, but since I have nLite running anyway, why not do it that way?
There's no difference in the ending result.

As I said, above, both methods are basically identical.
Use whatever you prefer.
If you use nLite anyway, just integrate the packs through that, saves you one step.

In fact, as I stated previously, you NEED to integrate all updates and hotfixes BEFORE applying the DriverPacks.
So yes, it is compatible, in fact, it's the only way to do it, if you try it the other way round you will screw things up.

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

That depends on the method you will be using. Method 1 will require about 600 MB, method 2 290.

Usually, the official nLite Fora would be the best place to ask, but seeing that a least I am making heavy use of it, I'll try to answer your question.

I am just pointing this out in case you might not find the desired answers here, NOT to tell you off.

So far, it has always worked for me, so double (or triple) check there is no error on your behalf (mistyped key).

Before using nLite, I would manually enter my key, also to great success.
You can do the same or at least verify what nLite did by opening the file WINNT.SIF in the I386 folder with your favourite text editor.

[UserData]
ProductKey = "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"

is how the proper entry has to look like (obviously you replace the Xs with your own key).

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

Usually I my self don't need to change hardware devices....Just for Getting Information If i Install my Windows with KTD default and unexpectedly i have to change my AGP/SOUND card,then what will happen ?
Does it ask me for Putting Winxp CD in CD Rom...

KTD All Offcource will Put all the crazy Stuff on my Hardrive....:)

1.7 GB with Or Without Windows [Total] ?

What I know is....
KTD ALL is a nice Option But I am sure that it will double the Windows Total Intallation Time....

-----------------------------------------------------------------------------------
KTD OPTONS...(Choose One)

[ ] DISABLE KTD ???
[ ] ENABLE KTD FOR ALL SLIMSTREAMED DRIVERPACKS [OK]
[ ] ENABLE KTD FOR ALL DRIVERPACKS I SELECTED  [Ok]
[ ] ENABLE KTD FOR THE DRIVES IN THE PATH I ENTER  ???
[ ] ENABLE KTD FOR THE DRIVERS THAT MATCH THE PETTERN I ENTER  ???

KTD CACHE LOCATION (Choose One)

[ ] DEFAULT {%SYSTEMROOT%\DRIVERPACKS} 
[ ] CUSTOM

Just the drivers, of course.
Everything else qould be pointless since everyone's UWXPCD installation would look different (nLite'ed, add-on packs, add. software)

Still, seeing as you'll have a hard time finding a prebuilt consumer model with less than 100GB as of now, those 1.7% space for drivers are easy to bear IMO.
Should customers complain, try selling them another drive or tell them not to DL so much pr0n ;P

Yeah, that version is already in the works, or so I think
Quite a welcome change, I can tell you!
(so far, applying KTD takes about as much time as installing XP+addons...)

Wonder where the next beta version is, it's been a while I tested one

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

hi
a network moderator at my regular hangout uses Nlite, and in our private rooms I told him that when I tried N_Lite to slip  RVM's post SP2 august's hotfixes, + all unpacked BT the Sneaky's driverpackss, it failed.

it went like this..
script error 6502 (or something like it....).

Nlite worked fine for doing things it was intended for.
ALL packs was probably beyond its capabilities.

my noob "haves a go at it'  txt is the KIS principle at work.

RVM (let it do what it was built for.) (Doesn't make changes to winnt.sif)

+ Bâshrat the Sneaky method 2 (if you had a winnt.sif for unattended, it would filter and add the required lines. If you don't have one, you find one with just two entries and can use the enhanced product to get to recovery console on a difficult machine...)

since then, that DVD worked for me in five machines so far.
the sixth  has that CPU thing issue.

Then which format we should follow ?

Ist Using RVM Integrator for Update Patches + Addons
2nd Using NLite for Removing Unneeded Windows Components.
3rd Driver Packs Base for SlipStreaming Drivers.

Then we can again Point out the Updated WindowXP Source folder to Nlite for Making WinXP.ISO Image file....

Am I Right ?

Are you saying that once you intergrate drivers with the DriverPacks BASE you can no longer do anything to your source? (e.g. edit text, add or remove programs, add remove hotfixes etc)

Again, once you intergrate drivers with the DriverPacks BASE you can no longer do anything to your source? (e.g. edit text, add or remove programs, add remove hotfixes etc). Does that mess something up?

Another question..Does anyone make their own unattended source disk manually without using others program/tools? I just ask because I am trying to learn this and feel the only way to get a true understanding of what you are doing is do it yourself hands on.