skinlayers and everyone

Thank you skinlayers for such turorial that I am testing now step  y step. I hope it will work for me.

My remark is I don't see where you call the drivers to be installed.

For example in another Topic, The user somebody

Added a new section Under [GuiRunOnce] in sysprep.inf file, under which He added a new line

Command0=C:\DP_Install_Tool.cmd

In order to call DP_Install_Tool.cmd to install the drivers.

Or in case I am wrong, the drivers in your tutorial are installed automatically or what exactly.

Again thank you and anyone for your explanations.

If I were you I would have started a new thread for this. this one is quite old and your post is on the 5th page. Let's start new please.
Thanks it looks awesome, and very well detailed.

Hope we see you around sir

Jeff

Thank You! Thank You! Thank You!

Want to see the rest? Then go here http://forum.driverpacks.net/viewtopic.php?id=4849

V TO P

Dell GX 620
GX 240
GX 260
Otiplex 755
Will test more and upload a video or something when I got time

I was just wondering if you ever posted your simplified process for using driverpacks with sysprep.  I've searched these forums and am still having trouble.  Please let me know if you have posted your guide/instructions.

Thank you,

LAN

i'm confused a little concerning what tools should be used,

Offlinesysprep
Sysprep driver scanner,
Mysysprep,

for example, if offlinesysprep is used, does that mean we don't need the other two tools listed

Yes, that's correct. At one point in time if you needed to do HAL detection at first boot then you needed to use MySysprep. But I've now added that capability to OfflineSysPrep. In fact, OfflineSysPrep handles a couple extra HALs that MySysprep doesn't support: MySysprep will only handle swaps between uniprocessor and multiprocessor, whereas OfflineSysPrep handles those as well as acpipic and standard HALs.

Also, OfflineSysPrep used to make use of Sysprep Driver Scanner, but that task has now been replaced by an internal function so Sysprep Driver Scanner is no longer needed too.

Regards,
Galapo.

So simple in fact that even a non techie could do it!  I'll post more later, but for now I'm doing a test to see if everything is working as intended.

I would include chipset and LAN via devpath. since most drivers depend on chipset it should be available to minisetup. Failure to do so may require you to run SAD twice. IE if chipset is not installed then any devices that depend on chipset will need reinstalled after chipset is installed (cut down or eliminate re-enumeration).

So integrate Mass textmode. Devpath Chipset, CPU, and LAN. SAD M2 for Graphics, Sound, WLAN and Mass (for PnP mode drivers).

I did not think you were a noob . I meant it in so far as you clarified it. You, just like me, have a unique perspective to sysprep with DriverPacks. It's the perspective of unfamiliarity, again that is a GOOD perspective for creating a guide... you are more likely to avoid the pitfalls of making assumtions and skipping over provideing details of seemingly obvious steps.

I'm a newb when it comes to integrating both systems together.

Here is my standard procedure for my DVD installs of XP

XP PRO + SP3 Slipstreamed
1 Piece Update Pack (for updates beyond SP3)
Make .ISO
Add my OEM Scan project to the source
Make .ISO
Add Driverpacks to the Source
Add modified WINNT.SIF and Custom WINNTBBU.DLL theme
Make .ISO

Test the living h*ll outta it

The reason I make so many .iso's is so I can easily go back and change something if I want.  If I go from SP3 base to Driverpacks and miss a step somewhere it's a pain in the @#$ to fix. =/

I've done sysprep before and had no problems.  If I had a choice, I'd make a base HII of XP + SP3 + Updates and include only Mass Storage and LAN drivers in the base image.  Once it loads XP after the mini setup I'd run Method 2 of the Driverpacks, but I still haven't found a way to do this.

I'm also wanting to run oemscan via the runonce command as well.  This is because I want to sysprep an HII for systems that come in the door for repair, but don't use VLK's.

I know I'm on the right path, and I know method 2 can be used for after sysprep..... but with the current guide it includes Method 1 which is a bit less than friendly.

=/

Wiki is here http://driverpacks.net/docs  as I stated earlier (win 7 documentation is started AKA DISM)

I've done sysprep for years, I've done driverpacks for years, but I've never combined them.

If Detard or someone else can point me in the right direction it would be greatly apprecated.  Perhaps we need a wiki of some sorts?

Same thing can be said for the Windows Vista / 7 Driverpacks.

I don't do sysprep... I HATE sysprep, I would rather do root canal . But the other crazy sysprep guys are here for you!