Search options

You are following the old method of install driverpack as in using the C:\makepnf c:\D.

You do not want to makepnf as i was told by a pro on this forum and they are really bad and hes 100 precent correct.

Question,

do I need to do anything in regards of the HAL. I took a look at the offline sysprep and its pretty much just a gui but are all the things mentioned by Galepos necessary? I mean I have been doing it since day one the way listed above and even before I started using driverpacks my sysprep command stayed the same -->  c:\sysprep\sysprep.exe -reseal -activated -mini -pnp -quiet

Just wondering
Thanks

Jeff;

Well after testing and testing with the driverpack i ended up doing it the following way.

1) Add all the 3rd party drivers i needed into 3rd party folder
2) Run the db_base command and select SAD
3) Select all the drivers but de-selecting the MASS storage check box
4) Select method 1 etc,
5) Keep the other parts default and then slipstream it.
6) After slipstream is completed i copy it over to a usb key and drop it over to the root of C of the ghosted pc

Run the following commands
7) c:\devpath.exe c:\d
8) sysprep\ROE.exe 937
9) Then my sysprep command --> c:\sysprep\sysprep.exe -reseal -activated -mini -pnp -quiet

Pc turns off after sysprep completes and then i boot it up into the network and dump the image using ghost onto the network.

Once its completed I then give it a try and let it load into Windows, sysprep runs and honestly everything gets install prefectly on the three laptops and the sound even works as well. (I will explain what I mean later on, on why the sound didnt work.)

I then take the same image and dump it onto the other 2 computers, 1 of them installs perfectly and the other one also installs itself but except for the following two drivers; as I need to update them within device manager after the image gets installed; they are

Video --> q35 chipset
Lan --> 3 com

Now the strange apart about that is that the drivers are within the driverpack (not as a 3rd party) but you will need to point to the driver folder to update them as they are marked with a yellow symbol in device manager after sysprep does its thing.

**************************
Now I started this thread because after I install Windows xp with SP3 and with no drivers installed yet, I run the DB_install to see if all the drivers gets installed. Everything gets installed but the sound does not work even after a reboot. So I would have to un-install UAA and then let windows pickup the new device and it gets installed from using the driver from the driverpack.

I then noticed I needed to do this to every pc when I dump this image without sysprep as I would just run the db_install file. Then it came to my attention maybe it needs sysprep and let sysprep force the driver. So I did the following steps listed above and as of now it worked on 2 of the laptops, i still need to test the other two computers when I get back to work on Monday. Will keep you posted if it worked.

********
Now in regardes of the Mass Storage support. Within my sysprep.ini it only contains the windows mass storage files under mass stroage. I did not borther with adding the mass storage drivers to that section as it seemed to work without it. Do I need it? Do you think I should of selected the Mass Storage check box within DB_base?

Anyhow what do you think about the above method? Personally I think its great but if you know even an eaiser way with using sysprep then please tell.

Thanks Again

P.S. I was more then happy to donate, and its not the last time thats for sure.

Best
Paul

OverFlow this post will be long.

Ideally, All that I am doing or want to do is the following which so far it is working. We have 3 different kinds of pc at our workplace so which means we hace 3 different images that were created by myself back in the days but now there are getting harder and harder to maintain with SMS and WSUS. Pc are --> P5B-VM DO, P5E-VM DO, P5LD2-VM

Never the less, I am starting from starch from a fresh image so taking one of the 3 pc listed above (example P5B-VM DO) I am doing the following.

1) Install Windows Pro SP2
2) Windows Update --> SP3
3) Installing MS Word 2003

Everything else will be done by SMS as I want to keep this universal image as basic as possible. So once the above is done, I do not install any drivers for that pc yet, so which mean everything in device manager is not installed.

4) Before I begin sysprep, I delete the processor information in the registry command --> "sc config intelppm start= disabled", Then I reboot then within device manager I delete the Processor, I DO not reboot and then delete the registry key "intelppm"
5) At this point on another computer I have prepared all the necessary files that I need to sysprep and integrate the driverpacks. This folder gets copied over to the root of C without the folder, so just the files.

What contains in this folder. (Imaging Folder)
- D folder --> Extracted all the driverpacks drivers. (C/G/L/M/S/W) Note, For the Chipset folder I only kept the Intel stuff as the AMD were giving me errors when it ran
- Sysprep Folder --> My sysprep.inf that I have modified and been using for years now. I have added the following entry in my sysprep.ini file for driverpacks according to the sticky in this section.

*********************
[Unattended]
UpdateInstalledDrivers = Yes
DriverSigningPolicy = Ignore

[SysprepMassStorage]

*********************
- Sysprep Folder --> ROE.exe is also located in the sysprep folder also with all the other default sysprep files (setupcl.exe etc)
- Within the root of the Imaging folder I have the following files as well.
   - devcon.exe
   - DevPath.exe
   - DpsFnshr.exe
   - DPsFnsher.ini file

Here is what my DPsFnsher.ini file looks like after I modified it:

***********************************
DPsFnsher.ini file
[Settings]
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!)
DPsRoot    = "%SystemDrive%"
; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU!
KTD = "paths:D\C;D\G;D\L;D\M;D\S;D\W"
; system variables supported (see remarks for a list) one location cannot be used as
; KTDlocation: the root directory specified in[Settings]\DPsRoot
KTDlocation    = "%SystemRoot%\Options\Drivers"
; system variables supported (see remarks for a list)
logLocation = "%SystemRoot%"
; enables/disables debug mode (enabled by default)
debug = "true"
***********************************

   - All the DriverPack_*_wnt5_x86-32.ini files that are provided with the download.
   - DSPdsblr.exe
   - makePNF.exe
   - mute.exe
   - pmtimer.exe
   - MassStorage.cmd --> This is a batch script that was made by someone on this forum to add all the chipset drivers I have within the d:\D folder to
     my [SysprepMassStorage] section.

******
Now listed above are files that get transferred over to the pc that I will be running sysprep on.

Steps that I take to prepare before sysprep and up to sysprep.
Note* The following commands are being done on the pc that is being used to build the image*

Note, the below two steps are already down as part of the files/folder that gets transferred to the pc image.
1) sysprep.exe -bmsd  --> As you know this will get all windows pci drivers and places them into the  [SysprepMassStorage] section.
2) run masstorage.exe D\M --> This will print out to a file all of the Mass-storage within the driverpacks. After it spits it out into a file, I make sure there are no broken links aka gaps, I then insert then into the [SysprepMassStorage] section.

****
3) c:\devpath.exe c:\d
4) c:\makePNF.exe c:\d --> I was running this command, until you told me not to in the other post
5) sysprep\ROE.exe 937  (At this point I do not reboot as it will run this command)

And last but not least my sysprep command
6) c:\sysprep\sysprep.exe -reseal -activated -mini -pnp -quiet

At this point the sysprep will run for about 20-25 mins or so. However sometime the sysprep runs for only 1 mins and I know there is something wrong so I then let it finish and re-do the above steps again, not sure why this happens but oh well.

**********
After sysprep takes its time the pc then turns off.  At this point I will then insert my multibootdisk that I made to dump the image to the network but before that I want to make sure everything got installed and ran perfect. I know by letting it bootup and letting sysprep run again I will need to do the above steps again.

So sysprep runs it takes its time as its installing the drivers and then when login into windows the driverpack runs. Apparently it is claiming cleaning registry in the bottom left corner and then it moves my d folder to --> C:\windows\system32\options, which is what I want as the team that are deploying these images would like to have the drivers said in a folder rather then carrying there usb stick that have the drivers. Dont ask why they just want them stored on the pc just in case.

Note run the dbsfinsih runs, I get a prompted to Install Intel (R) Q35 (Graphics B). If I hit ok it looks for the driver in C:\windows\system32\options\g\i2 and all I have to do is hit next and it install with no problem. At this point everything in device manager is installed just nicely, but questions is which is why this thread started to begin with is why I’m I being prompted if it knows the driver is there. I personally dont really care about this, one prompt is better then a lot of prompts. As of now I have no problem leaving it like that and deploying the image like that. I am prompted when dbsfnshr is running for the driver install.

Anyhow OverFlow, the above is the exact step I do from start of the image to the end. Do you for see any problems on how I am doing this. I have read up many posts and I think I got it down pat. Answer to your questionYes then it is true KTD that I want to use.

If I leave it the way I am doing it, it should be good no? Honestly I didn’t even use DPs_BASE, I just extracted the drivers from the driverpacks.

Let me know what you think.
Sorry for the long post

Thanks Again

Excellent just the answer that I was looking for.

Best

OverFlow, Very interesting read for sure, going back and fore. Anyhow after reading everything in that post; I still do not understand how to create the SAD file and how to run it.

As you mentioned in the other post, its possible to move the drivers to a different location after the image is dumped, which is what I want to, because thats how my KTD file is setup.

Do I create this SAD file or is there one already made and what commands do I run before sysprep.

Please advise
Once again, thank you for the support

OverFlow, Your the man brother. It worked like a charm the patch was missing.

Thanks again.

Perfect, will give that a try.

Question
Would i just add the patch before sysprep to my image for sysprep to install the required drivers?

thanks

windows xp

Thank you was wondering where to post.
Thanks again.