Phogoff

Is there a way to add the entire driverpack? I actually went through and populated the [sysprepMassStorage] section with all of the device id's... but it puts out errors. I don't think I have the time to go through and get everything working this way. Has anyone done this without having to add the device id's to the [sysprepMassStorage] section? Thanks for the response though Lighsout... it is appreciated

OK - I have everything working wonderfully except the massstorage during TextMode. I am trying to add the massstorage driverpack to an existing image and have sysprep populate the [sysprepmassstorage] section with all of the drivers. this is not happening... everytime sysprep runs it just populates the [sysprepmassstorage] section with the regular pnp storage drivers. What am I missing? I realize I may be missing something simple.... somebody please point me in the right direction Cheers!

Will this method work for everything including the MassStorage pack? If not, what would you think would need to be done to assure that the MassStorage pack is properly integrated? Thanks!

I take it back... The NIC portion is working ok. The MassStorage is not. I'll post when I get it figured out.

Seems I was overcomplicating this. For the NIC drivers I did the following: 1. I extracted the LAN Driverpack 2. I added the INf files to the I386\INF folder 3. I added the SYS files to the I386\System32\Drivers folder 4. I added all other misc files to the root of System 32. For the MassStorage drivers I did the following: 1. I extracted the MassStorage Driverpack 2. I flattened the folder structure to have one folder for each driverset. If a folder was named 3, and had 3 subfolders, I just made 3 folders called 31, 32, and 33, and placed each driverset within. 3. Once finished I copied the entire folder into I386\System32 folder 4. I edited the winpeoem.sif to have the following lines: [OemDriverParams] OemDriverRoot=MassStorage OemDriverDirs=31, 32, 33, A1, A2, A3, A4, A5, A6, A7, A8, AD1, AD2, AD3, AD4, AD5, AD6, AD7, AD8, AD9, ADA, AM, AR, AT, AU1, AU2, AU3, AU4, D, H1, H2, H3, H4, H5, I1, I2, IN1, IN2, IT, L1, L2, L3, L4, N4A, N4AR, N4I, N4IR, N123, P1, P2, P3, P4, P5, P6, P7, P8, Q1, Q2, Q3, Q4, S1, S2, S3, S4, S5, S5, S6, S7, S8, S9, SA, SB, SC, SI1, SI2, SI3, V1, V2, VM Everything seems to be working well now...

Yep, this is for OSD. Like we've spoken about in previous threads, I have an image that is working wornderfully. Now I am trying to build a custom PE2005 with as many NIC and Mass storage drivers in it as possible and am running into some problems.

Hello all, I have sifted through a bunch of posts regarding integrating the drivers in the driverpacks into WinPE, but they all end up pointing to BartPE information. I need to be able to integrate the Lan and Mass Storage driverpacks into Microsoft's WinPE 2005. Can anyone explain this to me? I know there is a difference between integrating the Mass Storage and the LAN driverpacks, but I can't seem to get either working. When I try to use Drvinst.exe and point to each LAN driver it kicks back errors saying the inf's are referencing files that arent there. If anyone has done this successfully could you please post a quick how to? I would greatly appreciate it! Cheers!

Hey Lightscout.... Just a quick update; I checked everything out and I am indeed using the BTS driverpacks with method 2 and KTD. Everything works great for me.

Hey Lightscout, I am currently on an out of town gig... as soon as I get home I will check everything out in my lab and get back to you. I am fairly positive I used method 2, and have used it on many different hardware platforms (I like to use it in my BDD\SMS OSD design sessions just to show off a bit). I just want to be positive about a few other things before I post more info. Ill be flying home for the weekend, so Ill post something then. Cheers!

Could you possibly go into a bit more detail about what exactly needs to be done with the masstorage drivers? Thanks!

Hey Lightscout.... I am currently using SMS OSD with the DriverPacks, but I used method 2 and Keep The Drivers. From my research on this site it looks like most people that are using Sysprep based imaging techniques (Like OSD) have been using method 2. This may work out better for you... just a thought.

Im using sysprep, Ill post before tonight, thanks for the reply.

OK, I am currently building a master image for 3 seperate pc models, and have successfully integrated drivers for everything... except it doesnt find the correct chipset drivers until after the image has been installed; at which point it finds the drivers and prompts for numerous reboots. What am I doing wrong?

OK - I've been setting everything up for my company to move to using SMS 2003 OS deployment instead of RIS... and so far so good. My only problem is finding a way to continue using the naming feature of RIS (OSD Feature Pack doesnt have a built in solution for naming). Anyways, Im wondering if any of you know of a way for me to grab the name RIS assigns to PE when it boots. What I would like to do is grab the name that RIS assigns to PE and have it modify the OSDNEWMACHINENAME value to the name that was given to PE when it first started... any ideas or points in the right direction would be greatly appreciated! Thanks - Geoff