• From: Manchester, England
  • Registered: 2007-06-07
  • Posts: 27

Topic: Using driverpacks on a ready built image?

Can you safely "roll your own" dpsfnshr.ini ?   

I ask as I've built my new "universal" image using our standard practices ie. plain xp cd, manually install all updates/software/etc..  The differences this time round beyond this is I'm building it for the first time on vmware and not on the actual hardware that it's going to be installed on (yes we lived in the dark ages until recently and hand rolled every image on the hardware it was destined for, until I got fed up of trying to maintain 15different images!!!)

I've basically got to the point where I believe I'm just about to check the final bits and realised I'd not really checked what needed to be done for dpsfnshr (many thanks to JakeLD for information he passed to me..)  I'll be using the sysprep driver scanner to embed the drivers into the system, but what needs to be done for dpsfnshr to execute correctly (in particularly regarding KTD)?

Hope I've made sense there!  I've not my appologies I've been at this all week!

Rob

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/Av2BDsDf_iiqO8a4dpI49DKicUs_0zEQtEPcTGyCqV4/perpetual:forever/userbar/tester-1.png

On a mission to re-educate users the Clue stick way!
  • JakeLD
  • Moderator, Sysprep & BartPE Master
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-07-05
  • Posts: 872

Re: Using driverpacks on a ready built image?

I will give you the info ASAP rob, right now I'm at job. The good news is DSPFNSHR.exe is finally working. I will post the INI file in these forums. Just a quick tip, in VMWare  make sure you are using an IDE disk driver, instead of SCSI. Don't install any kind of drivers even the vmware tools, you don't want to keep those in your image.  Make sure you uninstall the SCSI and video driver before running sysprep or imaging. If its not done you will get BSOD.

Last edited by JakeLD (2007-10-27 05:49:48)

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/n4W97qgvXb9IR64MNwT_BbnsRgjGDd0hpeGIqqmpZZ0/perpetual:forever/userbar/team-2.png

Donate!

JakeLD's Website

  • JakeLD
  • Moderator, Sysprep & BartPE Master
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-07-05
  • Posts: 872

Re: Using driverpacks on a ready built image?

[Settings]
DPsRoot    = "%SystemDrive%"
KTD=""
KTDlocation="%SystemDrive%\DP"
logLocation="%TMP%"
debug="true"

Don't try anything else, it won't work. If you want to keep the drivers, just don't use DPsFnshr.exe.

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/n4W97qgvXb9IR64MNwT_BbnsRgjGDd0hpeGIqqmpZZ0/perpetual:forever/userbar/team-2.png

Donate!

JakeLD's Website

  • From: Manchester, England
  • Registered: 2007-06-07
  • Posts: 27

Re: Using driverpacks on a ready built image?

JakeLD wrote:

I will give you the info ASAP rob, right now I'm at job. The good news is DSPFNSHR.exe is finally working. I will post the INI file in these forums. Just a quick tip, in VMWare  make sure you are using an IDE disk driver, instead of SCSI. Don't install any kind of drivers even the vmware tools, you don't want to keep those in your image.  Make sure you uninstall the SCSI and video driver before running sysprep or imaging. If its not done you will get BSOD.

Aha! I got something right then!  (on the 2nd time round *ahem* roll)

I'd initially started the process off on one of our new ESX servers (someone in our network team loved virtualisation so much they spent waaay too much money on it!) but after much head scratching as to why certain things didn't want to work (usb mainly as I need the image to support smart card readers) that version was quickly canned and I moved over to the workstation and a pretty "naked" install with like you mentioned an ide drive & no vmtools..  I have to admit I wish I'd done imaging with vm MUCH sooner.. It's so much bloody easier!

JakeLD wrote:

Don't try anything else, it won't work. If you want to keep the drivers, just don't use DPsFnshr.exe.

Hmm.. Wouldn't not running the finisher stop parts of certain drivers being installed correctly??  Admittedly 95% of the hardware this image is being made for is all intel chipset & integrated gfx HP or Dell, but the remaining 5% will have either an ati or nvidia card due to requiring higher res gfx.

Thanks again for all your help JakeLD and of course everyone else who's experimenting with universal images as if it wasn't for you lot i'd still be doing this the hard way! lol smile

Rob
(edited for terrible spelling lol!)

Last edited by unseen (2007-10-27 11:17:10)

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/Av2BDsDf_iiqO8a4dpI49DKicUs_0zEQtEPcTGyCqV4/perpetual:forever/userbar/tester-1.png

On a mission to re-educate users the Clue stick way!
  • JakeLD
  • Moderator, Sysprep & BartPE Master
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-07-05
  • Posts: 872

Re: Using driverpacks on a ready built image?

Hmm.. Wouldn't not running the finisher stop parts of certain drivers being installed correctly??

You are right but that represents probably less than 5% of the hardware. The best choice is to use it with the INI I posted.

Tip of the day: Instead of imaging prior to sysprep, with VMWare you can take a snapshot and lock it (you make sure it won't be overwrited). Snapshots is faster then restoring images with a PE CD in ISO format. I also suggest you use UBCD4Win as PE CD. It's the best PE project out there if you wish to restore universal image.

I wish I could emulate a 1GBs network card in vmware without installing VMWare tools, cause drivers transfer is kinda slow at 100 MBs. Maybe we could install the vmware tools, do the file transfer and when we are done uninstall the vmwaretools...I just want to make sure there's no traces on the image.

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/n4W97qgvXb9IR64MNwT_BbnsRgjGDd0hpeGIqqmpZZ0/perpetual:forever/userbar/team-2.png

Donate!

JakeLD's Website

  • From: Manchester, England
  • Registered: 2007-06-07
  • Posts: 27

Re: Using driverpacks on a ready built image?

JakeLD wrote:

You are right but that represents probably less than 5% of the hardware. The best choice is to use it with the INI I posted.

If after using that ini and it removes the DP's..  Would there be any issues "later on in life" installing additional hardware?  Would windows bitch (more than usual!) about the sudden disappearance?


JakeLD wrote:

Tip of the day: Instead of imaging prior to sysprep, with VMWare you can take a snapshot and lock it (you make sure it won't be overwrited). Snapshots is faster then restoring images with a PE CD in ISO format. I also suggest you use UBCD4Win as PE CD. It's the best PE project out there if you wish to restore universal image.

Ok now I'm concerned.. thats 2 things we do right! smile  I've been using UBCD since early on v2 after banging my head too much making plain ol bart pe easier to use for some of my "collegues"

JakeLD wrote:

I wish I could emulate a 1GBs network card in vmware without installing VMWare tools, cause drivers transfer is kinda slow at 100 MBs. Maybe we could install the vmware tools, do the file transfer and when we are done uninstall the vmwaretools...I just want to make sure there's no traces on the image.

That's something I may test actually if the initial run through is successful..  (If it works I'll have more time to 'play' with other options)  I managed today inbetween other service calls to finish up the mysysprep config and tweak my sysprep file to cope with all the intel hardware using the DP (pinching some parts from others attempts here) unfortunetly I ran out of time to see if my efforts were successful as after about 45mins of sysprep processing I had to leave, so tomorrow (today) i'll either return to a shut down vmware waiting to be ghosted OR something will have goofed and sysprep will have been running all night!  I'll keep my fingers crossed and report back tomorrow.

Rob

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/Av2BDsDf_iiqO8a4dpI49DKicUs_0zEQtEPcTGyCqV4/perpetual:forever/userbar/tester-1.png

On a mission to re-educate users the Clue stick way!
  • JakeLD
  • Moderator, Sysprep & BartPE Master
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-07-05
  • Posts: 872

Re: Using driverpacks on a ready built image?

If after using that ini and it removes the DP's..  Would there be any issues "later on in life" installing additional hardware?  Would windows bitch (more than usual!) about the sudden disappearance?

So far no it's been working like a charm. I installed 3 different PC this weekend with my universal image, it worked flawlessly.

Last edited by JakeLD (2007-10-30 14:26:23)

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/n4W97qgvXb9IR64MNwT_BbnsRgjGDd0hpeGIqqmpZZ0/perpetual:forever/userbar/team-2.png

Donate!

JakeLD's Website

  • From: Manchester, England
  • Registered: 2007-06-07
  • Posts: 27

Re: Using driverpacks on a ready built image?

JakeLD wrote:

So far no it's been working like a charm. I installed 3 different PC this weekend with my universal image, it worked flawlessly.

Just what I wanted to hear!!....   Just wish the initial run had been successful here! sad  Came back into work to find that the script had finished running, but hadn't forced a shutdown so windows was just sat at the desktop!...  Just trying to think now when it bailed out.  I think somewhere near the end of the mysysprep part of the script but I'm unsure.  Would mass-storage drivers not located cause it to just "bail" or would they stick sysprep in a loop?

It's probably something VERY stupid and simple so with fresh eyes and lots of coffee I'm going to have another look today.

Rob

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/Av2BDsDf_iiqO8a4dpI49DKicUs_0zEQtEPcTGyCqV4/perpetual:forever/userbar/tester-1.png

On a mission to re-educate users the Clue stick way!
  • From: Manchester, England
  • Registered: 2007-06-07
  • Posts: 27

Re: Using driverpacks on a ready built image?

ACK!!!

What an idiot I am....  I've just realised while looking through my sysprep file that the extra intel Mass Sotrage I added were for driverpack 7.06 whereas I've got 7.09.2...  Guess I know why it stopped now!!!...  I'll go through the script now and change all the file location/name references and see if that remedies everything.

Rob

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/Av2BDsDf_iiqO8a4dpI49DKicUs_0zEQtEPcTGyCqV4/perpetual:forever/userbar/tester-1.png

On a mission to re-educate users the Clue stick way!
  • JakeLD
  • Moderator, Sysprep & BartPE Master
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-07-05
  • Posts: 872

Re: Using driverpacks on a ready built image?

Tip of the day: Each time you update the Driverpack Storage in your image, you MUST verify all HWIDs and INF name under the sysprep MassStorage section, or your PC won't shutdown after the sysprep process which means there is a non existing HWID or a duplicated one. If you get the "Cannot update registry" message, I think it's because the path to at least one INF is incorrect.

2 INFs file using the same HWIDS cant coexist with syprep even if both INF have different names.

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/n4W97qgvXb9IR64MNwT_BbnsRgjGDd0hpeGIqqmpZZ0/perpetual:forever/userbar/team-2.png

Donate!

JakeLD's Website

  • From: Manchester, England
  • Registered: 2007-06-07
  • Posts: 27

Re: Using driverpacks on a ready built image?

JakeLD wrote:

Tip of the day: Each time you update the Driverpack Storage in your image, you MUST verify all HWIDs and INF name under the sysprep MassStorage section, or your PC won't shutdown after the sysprep process which means there is a non existing HWID or a duplicated one. If you get the "Cannot update registry" message, I think it's because the path to at least one INF is incorrect.

2 INFs file using the same HWIDS cant coexist with syprep even if both INF have different names.

Hmmmm sounds like this could indeed be the issue i'm hitting.  I vaguely remember reading something about an experimental mass storage pack that might eliminate this problem?  Or is there a more simple fix?  At the moment if I can support the windows generic mass storage and intel I think that would cover 99% of the PC's I'm trying to generate this image for.

As for verifying the names, I borrowed Chuds small script that scanned thru the D\M\ Folder and added the items to the end of the sysprep file.  Unfortunetly after 5hrs processing (yes I've deleted a LOT of drivers that I think aren't needed now!) it still did the same thing.  So i'm just trying it again with the pruned driverpack and will see if that has helped.

Thanks again for all your help Jake!

Rob

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/Av2BDsDf_iiqO8a4dpI49DKicUs_0zEQtEPcTGyCqV4/perpetual:forever/userbar/tester-1.png

On a mission to re-educate users the Clue stick way!
  • JakeLD
  • Moderator, Sysprep & BartPE Master
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-07-05
  • Posts: 872

Re: Using driverpacks on a ready built image?

I need to update the mass storage pack then I will post my sysprep.inf here which contains the proper HWIDs for Intel, Generic, nvidia and ati/amd.

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/n4W97qgvXb9IR64MNwT_BbnsRgjGDd0hpeGIqqmpZZ0/perpetual:forever/userbar/team-2.png

Donate!

JakeLD's Website

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: Using driverpacks on a ready built image?

Hi
I uploaded a mass with a change in Nvidia, but could not reach you.

The answer was 42?
Kind regards, Jaak.
  • JakeLD
  • Moderator, Sysprep & BartPE Master
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-07-05
  • Posts: 872

Re: Using driverpacks on a ready built image?

i notice every nightlies, you dont need to warm me. I did small changes to the 11X version, I will upload ASAP.

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/n4W97qgvXb9IR64MNwT_BbnsRgjGDd0hpeGIqqmpZZ0/perpetual:forever/userbar/team-2.png

Donate!

JakeLD's Website

  • JakeLD
  • Moderator, Sysprep & BartPE Master
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-07-05
  • Posts: 872

Re: Using driverpacks on a ready built image?

Sysprep.inf for DP MassStorage 12X

[Unattended]
    ;Expand the OS partition to take all available space
    ExtendOEMPartition=1
    ;Regenerate page file
    KeepPageFile=0
    ;Skip license agreement window
    OemSkipEula=Yes
    ;Allow unsigned drivers
    DriverSigningPolicy=Ignore
    ;Set temp folder for syprep files (c:\sysprep)
    InstallFilesPath="C:\Sysprep\i386"
    ;Update installed drivers with the ones in (%SystemDrive%\D)
    UpdateInstalledDrivers=Yes

[GuiUnattended]
    ;Local administrator password
    AdminPassword=password
    EncryptedAdminPassword=No
    AutoLogon=Yes
    ;Autolog once for DPsFnshr.exe 
    AutoLogonCount=1
    ;Skip the regional settings window
    OEMSkipRegional=1
    ;East=35
    TimeZone=35
    ;Skip the welcome window
    OemSkipWelcome=1

[UserData]
    ProductID=VLK CDKEY
    FullName="User"
    ;OrgName="Org"
    ;* Random computer name
    ComputerName=*

[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    ;Monitor refresh rate
    Vrefresh=60
    ;Auto confirm if there's any resolution change
    AutoConfirm=1

[TapiLocation]
    ;107 = Canada
    CountryCode=107

[RegionalSettings]
    LanguageGroup=1
    ;00000c0c = Canadian french
    SystemLocale=00000c0c
    UserLocale=00000c0c
    ;Set canadian french keyboard 
    InputLocale=0c0c:00001009

[Identification]
    JoinWorkgroup=WORKGROUP
    ;DomainAdmin=domain.com\user
    ;DomainAdminPassword=password
    ;JoinDomain=domain.com
    ;MachineObjectOU = "OU = myou,OU = myparentou,DC = mydom,DC = mycompany,DC = com"

[Networking]
    InstallDefaultComponents=No

[NetClients]
    MS_MSClient=params.MS_MSClient

[SysprepMassStorage]
	primary_ide_channel=%WinDir%\inf\mshdc.inf
	secondary_ide_channel=%WinDir%\inf\mshdc.inf
	;nVidia nForce 4/5/6
	PCI\VEN_10DE&DEV_0266&CC_0101=%SystemDrive%\D\M\N\4\NVATA4.INF
	PCI\VEN_10DE&DEV_0267&CC_0101=%SystemDrive%\D\M\N\4\NVATA4.INF
	PCI\VEN_10DE&DEV_0266&CC_0104=%SystemDrive%\D\M\N\4\NVRAID4.INF
	PCI\VEN_10DE&DEV_0267&CC_0104=%SystemDrive%\D\M\N\4\NVRAID4.INF
  ;PCI\VEN_10DE&DEV_003E&CC_0104=%SystemDrive%\D\M\N\4IN\NVRAID4IN.INF
  ;PCI\VEN_10DE&DEV_0036&CC_0104=%SystemDrive%\D\M\N\4IN\NVRAID4IN.INF
  ;PCI\VEN_10DE&DEV_0267&CC_0104=%SystemDrive%\D\M\N\4IN\NVRAID4IN.INF
  ;PCI\VEN_10DE&DEV_0266&CC_0104=%SystemDrive%\D\M\N\4IN\NVRAID4IN.INF
  ;PCI\VEN_10DE&DEV_037E&CC_0104=%SystemDrive%\D\M\N\4IN\NVRAID4IN.INF
  ;PCI\VEN_10DE&DEV_036F&CC_0104=%SystemDrive%\D\M\N\4IN\NVRAID4IN.INF
  PCI\VEN_10DE&DEV_037F&CC_0101=%SystemDrive%\D\M\N\5\nvgts5.inf
  PCI\VEN_10DE&DEV_0054&CC_0101=%SystemDrive%\D\M\N\5\nvgts5.inf
  PCI\VEN_10DE&DEV_0055&CC_0101=%SystemDrive%\D\M\N\5\nvgts5.inf
  PCI\VEN_10DE&DEV_044D&CC_0106=%SystemDrive%\D\M\N\5\nvgts5.inf
  PCI\VEN_10DE&DEV_037F&CC_0104=%SystemDrive%\D\M\N\5\nvrd325.inf
  PCI\VEN_10DE&DEV_0054&CC_0104=%SystemDrive%\D\M\N\5\nvrd325.inf
  PCI\VEN_10DE&DEV_0055&CC_0104=%SystemDrive%\D\M\N\5\nvrd325.inf
  PCI\VEN_10DE&DEV_044C&CC_0104=%SystemDrive%\D\M\N\5\nvrd325.inf
  PCI\VEN_10DE&DEV_0554&CC_0106=%SystemDrive%\D\M\N\6\nvgts6.inf
  PCI\VEN_10DE&DEV_0558&CC_0104=%SystemDrive%\D\M\N\6\nvrd326.inf
  ;*_NVRAIDBUS=%SystemDrive%\D\M\N\6\nvrd326.inf
  ;*NVRAIDBUS=%SystemDrive%\D\M\N\6\nvrd326.inf
  ;*NVRAID20=%SystemDrive%\D\M\N\6\nvrd326.inf
	;Intel ICH5R 82801ER 
  PCI\VEN_8086&DEV_24DF&CC_0104=%SystemDrive%\D\M\IN\1\IASTOR55.INF
  ;Intel ESB 6300ESB
  PCI\VEN_8086&DEV_25B0&CC_0104=%SystemDrive%\D\M\IN\1\IASTOR55.INF
  ;Intel ICH6R 82801FR
  PCI\VEN_8086&DEV_2652&CC_0104=%SystemDrive%\D\M\IN\2\IASTOR70.INF
  ;Intel 82801FR SATA AHCI 
  PCI\VEN_8086&DEV_2652&CC_0106=%SystemDrive%\D\M\IN\2\IAAHCI70.INF
  ;Intel 631xESB/632xESB SATA RAID
  PCI\VEN_8086&DEV_2682&CC_0104=%SystemDrive%\D\M\IN\3\IASTOR76.INF
  ;Intel 82801GR/GH SATA RAID
  PCI\VEN_8086&DEV_27C3&CC_0104=%SystemDrive%\D\M\IN\3\IASTOR76.INF
  ;Intel 82801GHM SATA RAID 
  PCI\VEN_8086&DEV_27C6&CC_0104=%SystemDrive%\D\M\IN\3\IASTOR76.INF
  ;Intel ICH8R/ICH9R SATA RAID 
  PCI\VEN_8086&DEV_2822&CC_0104=%SystemDrive%\D\M\IN\3\IASTOR76.INF
  ;Intel 82801HEM SATA RAID 
  PCI\VEN_8086&DEV_282A&CC_0104=%SystemDrive%\D\M\IN\3\IASTOR76.INF
  ;Intel 82801FBM SATA AHCI
  PCI\VEN_8086&DEV_2653&CC_0106=%SystemDrive%\D\M\IN\3\IAAHCI76.INF
  ;Intel 631xESB/632xESB SATA AHCI
  PCI\VEN_8086&DEV_2681&CC_0106=%SystemDrive%\D\M\IN\3\IAAHCI76.INF
  ;Intel 82801GR/GH SATA AHCI
  PCI\VEN_8086&DEV_27C1&CC_0106=%SystemDrive%\D\M\IN\3\IAAHCI76.INF
  ;Intel 82801GBM SATA AHCI
  PCI\VEN_8086&DEV_27C5&CC_0106=%SystemDrive%\D\M\IN\3\IAAHCI76.INF
  ;Intel 82801HR/HH/HO SATA AHCI
  PCI\VEN_8086&DEV_2821&CC_0106=%SystemDrive%\D\M\IN\3\IAAHCI76.INF
  ;Intel 82801HEM/HBM SATA AHCI
  PCI\VEN_8086&DEV_2829&CC_0106=%SystemDrive%\D\M\IN\3\IAAHCI76.INF
  ;Intel ICH9 SATA AHCI 
  PCI\VEN_8086&DEV_2922&CC_0106=%SystemDrive%\D\M\IN\3\IAAHCI76.INF
  ;Intel EP 80579 SATA AHCI
  PCI\VEN_8086&DEV_5029&CC_0106=%SystemDrive%\D\M\IN\3\IAAHCI76.INF
  ;Intel IDE controller
  PCI\VEN_8086&DEV_2680=%SystemDrive%\D\C\I\xp\ESB2ide.inf
  PCI\VEN_8086&DEV_269E=%SystemDrive%\D\C\I\xp\ESB2ide.inf
  PCI\VEN_8086&DEV_244B=%SystemDrive%\D\C\I\xp\ich2ide.inf
  PCI\VEN_8086&DEV_244A=%SystemDrive%\D\C\I\xp\ich2idem.inf
  PCI\VEN_8086&DEV_248B=%SystemDrive%\D\C\I\xp\ich3ide.inf
  PCI\VEN_8086&DEV_248A=%SystemDrive%\D\C\I\xp\ich3idem.inf
  PCI\VEN_8086&DEV_24CB&CC_0101=%SystemDrive%\D\C\I\xp\ich4ide.inf
  PCI\VEN_8086&DEV_24CA&CC_0101=%SystemDrive%\D\C\I\xp\ich4ide.inf
  PCI\VEN_8086&DEV_24C1&CC_0101=%SystemDrive%\D\C\I\xp\ich4ide.inf
  PCI\VEN_8086&DEV_24D1&CC_0101=%SystemDrive%\D\C\I\xp\ich5ide.inf
  PCI\VEN_8086&DEV_24DB&CC_0101=%SystemDrive%\D\C\I\xp\ich5ide.inf
  PCI\VEN_8086&DEV_25A2&CC_0101=%SystemDrive%\D\C\I\xp\ich5ide.inf
  PCI\VEN_8086&DEV_25A3&CC_0101=%SystemDrive%\D\C\I\xp\ich5ide.inf
  PCI\VEN_8086&DEV_2651&CC_0101=%SystemDrive%\D\C\I\xp\ich6ide.inf
  PCI\VEN_8086&DEV_2652&CC_0101=%SystemDrive%\D\C\I\xp\ich6ide.inf
  PCI\VEN_8086&DEV_2653&CC_0101=%SystemDrive%\D\C\I\xp\ich6ide.inf
  PCI\VEN_8086&DEV_266F=%SystemDrive%\D\C\I\xp\ich6ide.inf
  PCI\VEN_8086&DEV_27C0=%SystemDrive%\D\C\I\xp\ich7ide.inf
  PCI\VEN_8086&DEV_27C4=%SystemDrive%\D\C\I\xp\ich7ide.inf
  PCI\VEN_8086&DEV_27DF=%SystemDrive%\D\C\I\xp\ich7ide.inf
  PCI\VEN_8086&DEV_2820=%SystemDrive%\D\C\I\xp\ich8ide.inf
  PCI\VEN_8086&DEV_2825=%SystemDrive%\D\C\I\xp\ich8ide.inf
  PCI\VEN_8086&DEV_2828=%SystemDrive%\D\C\I\xp\ich8ide.inf
  PCI\VEN_8086&DEV_2850=%SystemDrive%\D\C\I\xp\ich8ide.inf
  PCI\VEN_8086&DEV_2922=%SystemDrive%\D\C\I\xp\ich9ahci.inf
  PCI\VEN_8086&DEV_2923=%SystemDrive%\D\C\I\xp\ich9ahci.inf
  PCI\VEN_8086&DEV_2920=%SystemDrive%\D\C\I\xp\ich9ide.inf
  PCI\VEN_8086&DEV_2921=%SystemDrive%\D\C\I\xp\ich9ide.inf
  PCI\VEN_8086&DEV_2926=%SystemDrive%\D\C\I\xp\ich9ide.inf
  PCI\VEN_8086&DEV_2928=%SystemDrive%\D\C\I\xp\ich9ide.inf
  PCI\VEN_8086&DEV_292D=%SystemDrive%\D\C\I\xp\ich9ide.inf
  PCI\VEN_8086&DEV_292E=%SystemDrive%\D\C\I\xp\ich9ide.inf
  PCI\VEN_8086&DEV_2440=%SystemDrive%\D\C\I\xp\ICH2Core.inf
  PCI\VEN_8086&DEV_2480=%SystemDrive%\D\C\I\xp\ich3core.inf
  PCI\VEN_8086&DEV_24C0=%SystemDrive%\D\C\I\xp\ich4core.inf
  PCI\VEN_8086&DEV_24CC=%SystemDrive%\D\C\I\xp\ich4core.inf
  PCI\VEN_8086&DEV_24C3=%SystemDrive%\D\C\I\xp\ich4core.inf
  PCI\VEN_8086&DEV_244E=%SystemDrive%\D\C\I\xp\ich4core.inf
  PCI\VEN_8086&DEV_2448=%SystemDrive%\D\C\I\xp\ich4core.inf
  PCI\VEN_8086&DEV_24D0=%SystemDrive%\D\C\I\xp\ich5core.inf
  PCI\VEN_8086&DEV_24DC=%SystemDrive%\D\C\I\xp\ich5core.inf
  PCI\VEN_8086&DEV_24D3=%SystemDrive%\D\C\I\xp\ich5core.inf
  PCI\VEN_8086&DEV_25A1=%SystemDrive%\D\C\I\xp\ich5core.inf
  PCI\VEN_8086&DEV_25A4=%SystemDrive%\D\C\I\xp\ich5core.inf
  PCI\VEN_8086&DEV_25AB=%SystemDrive%\D\C\I\xp\ich5core.inf
  PCI\VEN_8086&DEV_25AE=%SystemDrive%\D\C\I\xp\ich5core.inf
  PCI\VEN_8086&DEV_25AC=%SystemDrive%\D\C\I\xp\ich5core.inf
  PCI\VEN_8086&DEV_2640=%SystemDrive%\D\C\I\xp\ich6core.inf
  PCI\VEN_8086&DEV_2641=%SystemDrive%\D\C\I\xp\ich6core.inf
  PCI\VEN_8086&DEV_2642=%SystemDrive%\D\C\I\xp\ich6core.inf
  PCI\VEN_8086&DEV_266A=%SystemDrive%\D\C\I\xp\ich6core.inf
  PCI\VEN_8086&DEV_2660=%SystemDrive%\D\C\I\xp\ich6core.inf
  PCI\VEN_8086&DEV_2662=%SystemDrive%\D\C\I\xp\ich6core.inf
  PCI\VEN_8086&DEV_2664=%SystemDrive%\D\C\I\xp\ich6core.inf
  PCI\VEN_8086&DEV_2666=%SystemDrive%\D\C\I\xp\ich6core.inf
  PCI\VEN_8086&DEV_27B0=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_27B8=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_27B9=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_27BD=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_27DA=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_27D0=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_27D2=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_27D4=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_27D6=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_27E0=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_27E2=%SystemDrive%\D\C\I\xp\ich7core.inf
  PCI\VEN_8086&DEV_2810=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_2811=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_2812=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_2814=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_2815=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_283F=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_2841=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_2843=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_2845=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_2847=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_2849=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_284F=%SystemDrive%\D\C\I\xp\ich8core.inf
  PCI\VEN_8086&DEV_2910=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2911=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2912=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2913=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2914=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2915=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2916=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2918=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2932=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2940=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2942=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2944=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2945=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2946=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_2948=%SystemDrive%\D\C\I\xp\ich9core.inf
  PCI\VEN_8086&DEV_294A=%SystemDrive%\D\C\I\xp\ich9core.inf
	;Silicon Image 3112 (ATI Xpress 200)
  PCI\VEN_1002&DEV_4379=%SystemDrive%\D\M\S\5A\SI3112R.INF
  PCI\VEN_1002&DEV_437A=%SystemDrive%\D\M\S\5A\SI3112R.INF
  ;Silicon Image SiI 3112 SATARaid
  PCI\VEN_1095&DEV_3112=%SystemDrive%\D\M\S\5\SI3112R.INF
  ;Silicon Image SiI 3512 SATARaid
  PCI\VEN_1095&DEV_3512=%SystemDrive%\D\M\S\5\SI3112R.INF
  ;ATI 436E Serial ATA
  PCI\VEN_1002&DEV_436E=%SystemDrive%\D\M\S\5\SI3112R.INF
  ;AMD 690G
  PCI\VEN_1002&DEV_4380=%SystemDrive%\D\M\AT\AHCIX86.INF
  PCI\VEN_1002&DEV_4349=%SystemDrive%\D\M\AT\ATIIDE.INF
  PCI\VEN_1002&DEV_4376=%SystemDrive%\D\M\AT\1\ATIHDC2.INF
  PCI\VEN_1002&DEV_438C=%SystemDrive%\D\M\AT\1\ATIHDC2.INF
  PCI\VEN_1002&DEV_4369=%SystemDrive%\D\M\AT\1\ATIHDC.INF
  PCI\VEN_1002&DEV_436E=%SystemDrive%\D\M\AT\1\ATIHDC.INF
  ;AMD EIDE
  PCI\VEN_1022&DEV_7409=%SystemDrive%\D\M\AM\AMDEIDE.INF
  PCI\VEN_1022&DEV_7411=%SystemDrive%\D\M\AM\AMDEIDE.INF
  PCI\VEN_1022&DEV_7441=%SystemDrive%\D\M\AM\AMDEIDE.INF
  PCI\VEN_1022&DEV_7469=%SystemDrive%\D\M\AM\AMDEIDE.INF
  ;VMware SCSI Controller
  PCI\VEN_104B&DEV_1040=%SystemDrive%\D\M\VM\VMSCSI.INF
  ;Windows XP default storage drivers
	*pnp0a00=%WinDir%\inf\machine.inf
	*pnp0a01=%WinDir%\inf\machine.inf
	*pnp0a04=%WinDir%\inf\machine.inf
	*pnp0a03=%WinDir%\inf\machine.inf
	pci\cc_0604=%WinDir%\inf\machine.inf
	pci\cc_0601=%WinDir%\inf\machine.inf
	pci\cc_0602=%WinDir%\inf\machine.inf
	pci\cc_0600=%WinDir%\inf\machine.inf
	pci\cc_0500=%WinDir%\inf\machine.inf
	root\ftdisk=%WinDir%\inf\machine.inf
	root\swenum=%WinDir%\inf\machine.inf
	root\update=%WinDir%\inf\machine.inf
	root\mssmbios=%WinDir%\inf\machine.inf
	root\dmio=%WinDir%\inf\machine.inf
	lptenum\microsoftrawport958a=%WinDir%\inf\machine.inf
	root\rdpdr=%WinDir%\inf\machine.inf
	root\rdp_mou=%WinDir%\inf\machine.inf
	root\rdp_kbd=%WinDir%\inf\machine.inf
	*pnp0000=%WinDir%\inf\machine.inf
	*pnp0001=%WinDir%\inf\machine.inf
	*pnp0003=%WinDir%\inf\machine.inf
	*pnp0004=%WinDir%\inf\machine.inf
	*pnp0100=%WinDir%\inf\machine.inf
	*pnp0101=%WinDir%\inf\machine.inf
	*pnp0103=%WinDir%\inf\machine.inf
	*pnp0200=%WinDir%\inf\machine.inf
	*pnp0201=%WinDir%\inf\machine.inf
	*pnp0800=%WinDir%\inf\machine.inf
	*pnp0b00=%WinDir%\inf\machine.inf
	*pnp0a05=%WinDir%\inf\machine.inf
	*pnp0a06=%WinDir%\inf\machine.inf
	*pnp0c00=%WinDir%\inf\machine.inf
	*pnp0c01=%WinDir%\inf\machine.inf
	*pnp0c02=%WinDir%\inf\machine.inf
	*pnp0c04=%WinDir%\inf\machine.inf
	*pnp0c0b=%WinDir%\inf\machine.inf
	*pnp0c0c=%WinDir%\inf\machine.inf
	*pnp0c0d=%WinDir%\inf\machine.inf
	*pnp0c0e=%WinDir%\inf\machine.inf
	*pnp0c15=%WinDir%\inf\machine.inf
	acpi\dockdevice=%WinDir%\inf\machine.inf
	acpi\dockdevice&_sb_.pci_.oak_=%WinDir%\inf\machine.inf
	acpi\dockdevice&_sb_.pci_.isa_.slce=%WinDir%\inf\machine.inf
	acpi\fixedbutton=%WinDir%\inf\machine.inf
	acpi\thermalzone=%WinDir%\inf\machine.inf
	pci\ven_10aa&dev_0000=%WinDir%\inf\machine.inf
	pci\ven_1025&dev_1435=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1445=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1489=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1449=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1523=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1533=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1451=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1521=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1621=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1647=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1651=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1531=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_1541=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_5243=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_5247=%WinDir%\inf\machine.inf
	pci\ven_10b9&dev_7101=%WinDir%\inf\machine.inf
	pci\ven_1022&dev_7007=%WinDir%\inf\machine.inf
	pci\ven_1022&dev_700d=%WinDir%\inf\machine.inf
	pci\ven_1022&dev_700f=%WinDir%\inf\machine.inf
	pci\ven_1022&dev_740b=%WinDir%\inf\machine.inf
	pci\ven_1022&dev_7413=%WinDir%\inf\machine.inf
	pci\ven_1022&dev_7443=%WinDir%\inf\machine.inf
	pci\ven_1022&dev_7451=%WinDir%\inf\machine.inf
	pci\ven_1022&dev_746a=%WinDir%\inf\machine.inf
	pci\ven_1022&dev_746b=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_0001=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_0002=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_1000=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_2000=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_ae29=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_ae2b=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_a0f0=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_a0f3=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_a0f7=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_ae2a=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_ae31=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_ae69=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_ae6c&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_ae6c&cc_0604=%WinDir%\inf\machine.inf
	pci\ven_0e11&dev_ae6d=%WinDir%\inf\machine.inf
	*cpqa0ef=%WinDir%\inf\machine.inf
	*cpqae08=%WinDir%\inf\machine.inf
	*cpqae30=%WinDir%\inf\machine.inf
	*cpqae3b=%WinDir%\inf\machine.inf
	*cpqae3c=%WinDir%\inf\machine.inf
	*cpqae4a=%WinDir%\inf\machine.inf
	*cpqae4b=%WinDir%\inf\machine.inf
	*cpqae4c=%WinDir%\inf\machine.inf
	*cpqae4d=%WinDir%\inf\machine.inf
	*cpqae53=%WinDir%\inf\machine.inf
	*cpqae54=%WinDir%\inf\machine.inf
	*cpqae55=%WinDir%\inf\machine.inf
	*cpqb05f=%WinDir%\inf\machine.inf
	*cpqb118=%WinDir%\inf\machine.inf
	*cpqb119=%WinDir%\inf\machine.inf
	*cpqb11a=%WinDir%\inf\machine.inf
	*cpqfa1b=%WinDir%\inf\machine.inf
	pci\ven_1080&dev_0600=%WinDir%\inf\machine.inf
	pci\ven_1078&dev_0000=%WinDir%\inf\machine.inf
	pci\ven_1078&dev_0002=%WinDir%\inf\machine.inf
	pci\ven_1011&dev_0001=%WinDir%\inf\machine.inf
	pci\ven_1011&dev_0021=%WinDir%\inf\machine.inf
	pci\ven_1011&dev_0022=%WinDir%\inf\machine.inf
	pci\ven_1011&dev_0024=%WinDir%\inf\machine.inf
	pci\ven_1011&dev_0025=%WinDir%\inf\machine.inf
	pci\ven_1011&dev_0026=%WinDir%\inf\machine.inf
	pci\ven_103c&dev_10c1=%WinDir%\inf\machine.inf
	pci\ven_103c&dev_10ed=%WinDir%\inf\machine.inf
	pci\ven_103c&dev_1219=%WinDir%\inf\machine.inf
	pci\ven_103c&dev_121a=%WinDir%\inf\machine.inf
	pci\ven_103c&dev_121b=%WinDir%\inf\machine.inf
	pci\ven_103c&dev_121c=%WinDir%\inf\machine.inf
	*hwpc209=%WinDir%\inf\machine.inf
	pci\ven_1014&dev_000a=%WinDir%\inf\machine.inf
	pci\ven_1014&dev_0017=%WinDir%\inf\machine.inf
	pci\ven_1014&dev_0022&rev_00=%WinDir%\inf\machine.inf
	pci\ven_1014&dev_0022=%WinDir%\inf\machine.inf
	pci\ven_1014&dev_0095=%WinDir%\inf\machine.inf
	*ibm006a=%WinDir%\inf\machine.inf
	*int0800=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_0008=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_0326=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_0327=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_0329=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_032a=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_0482=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_0483=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_0484=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_0486=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_04a3&rev_00=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_04a3&rev_01=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_04a3&rev_02=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_04a3&rev_03=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_04a3=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1130=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1131=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1161=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1225=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_122d=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_122e=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1234=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1235=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1237=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_123b=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_123c=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_123d=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_123f=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_124b=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1250=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1360=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1361=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1460=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1461=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1462=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1a21=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1a23=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1a24=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1a30=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_1a31=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2410=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2413=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2418=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2420=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2423=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2428=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2443=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_244c=%WinDir%\inf\machine.inf
  pci\ven_8086&dev_2483=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_248c=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2500=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2501=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_250b=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_250f=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2530=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2531=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3575=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2532=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2533=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2534=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2540=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2541=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2543=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2544=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2545=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2546=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2547=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2548=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_254c=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2550=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2551=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2552=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2553=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2554=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_255d=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2560=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2561=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2570=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2571=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2573=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2576=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2578=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2579=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_257b=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_257e=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2580=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2581=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2584=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_2585=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3340=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3341=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3576=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3578=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3580=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3581=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3584=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3585=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3590=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3591=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3592=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3594=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3595=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3596=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3597=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3598=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_3599=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_359a=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_359b=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_359e=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7000=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7030=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7100=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7110&cc_0680=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7110&cc_0601=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7110&rev_01&cc_0680=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7110&rev_01&cc_0601=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7113&rev_00=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7113&rev_01=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7113=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7120=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7122=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7124=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7180=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7181=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7190=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7192=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7191=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7194=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7198=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_719b=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_71a1=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7600=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_7603=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_84c4=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_84c5=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_b152=%WinDir%\inf\machine.inf
	pci\ven_8086&dev_b154=%WinDir%\inf\machine.inf
	pci\ven_1042&dev_3000=%WinDir%\inf\machine.inf
	pci\ven_1042&dev_3010=%WinDir%\inf\machine.inf
	pci\ven_1066&dev_0001=%WinDir%\inf\machine.inf
	pci\ven_1066&dev_8002=%WinDir%\inf\machine.inf
	pci\ven_1066&dev_0002=%WinDir%\inf\machine.inf
	pci\ven_100b&dev_0011=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00a8&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00a8&cc_0000=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00a9&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00aa&cc_0500=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00ab&subsys_00ab1033=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00ac&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00ad&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00ae&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00af=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00b0=%WinDir%\inf\machine.inf
	pci\ven_1033&dev_00b1&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1045&dev_c822=%WinDir%\inf\machine.inf
	pci\ven_1045&dev_c832=%WinDir%\inf\machine.inf
	pci\ven_1045&dev_c557=%WinDir%\inf\machine.inf
	pci\ven_1045&dev_c558=%WinDir%\inf\machine.inf
	pci\ven_1045&dev_c567=%WinDir%\inf\machine.inf
	pci\ven_1045&dev_c568=%WinDir%\inf\machine.inf
	pci\ven_1045&dev_c700=%WinDir%\inf\machine.inf
	pci\ven_1045&dev_c701=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0005&cc_0604=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0005&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0007=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0008=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0013=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0009&cc_0604=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0009&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0011&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0012&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0014&cc_0604=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0014&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0015=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0016&cc_0604=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0016&cc_0600=%WinDir%\inf\machine.inf
	pci\ven_1166&dev_0200=%WinDir%\inf\machine.inf
	pci\ven_110a&dev_001d=%WinDir%\inf\machine.inf
	pci\ven_1039&dev_0001=%WinDir%\inf\machine.inf
	pci\ven_1039&dev_0008=%WinDir%\inf\machine.inf
	pci\ven_1039&dev_0009=%WinDir%\inf\machine.inf
	pci\ven_1039&dev_0406=%WinDir%\inf\machine.inf
	pci\ven_1039&dev_0496=%WinDir%\inf\machine.inf
	pci\ven1039&dev_0540=%WinDir%\inf\machine.inf
	pci\ven_1039&dev_0630=%WinDir%\inf\machine.inf
	pci\ven_1039&dev_0635=%WinDir%\inf\machine.inf
	pci\ven_1039&dev_0730=%WinDir%\inf\machine.inf
	pci\ven_1039&dev_0735=%WinDir%\inf\machine.inf
	pci\ven_1039&dev_6001=%WinDir%\inf\machine.inf
	pci\ven_1055&dev_9460=%WinDir%\inf\machine.inf
	pci\ven_1055&dev_9463=%WinDir%\inf\machine.inf
	pci\ven_104c&dev_ac20=%WinDir%\inf\machine.inf
	pci\ven_1179&dev_0601=%WinDir%\inf\machine.inf
	pci\ven_1179&dev_0618=%WinDir%\inf\machine.inf
	pci\ven_1179&dev_0602=%WinDir%\inf\machine.inf
	pci\ven_1179&dev_0611=%WinDir%\inf\machine.inf
	pci\ven_1179&dev_0603=%WinDir%\inf\machine.inf
	pci\ven_1179&dev_0604=%WinDir%\inf\machine.inf
	pci\ven_1179&dev_0605=%WinDir%\inf\machine.inf
	pci\ven_1179&dev_0609=%WinDir%\inf\machine.inf
	pci\ven_1060&dev_8886=%WinDir%\inf\machine.inf
	pci\ven_1060&dev_886a=%WinDir%\inf\machine.inf
	pci\ven_1060&dev_e886=%WinDir%\inf\machine.inf
	pci\ven_1060&dev_8881=%WinDir%\inf\machine.inf
	pci\ven_1060&dev_0891=%WinDir%\inf\machine.inf
	pci\ven_1060&dev_e881=%WinDir%\inf\machine.inf
	pci\ven_1060&dev_e891=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0204=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0258=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0269=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_1204=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_2204=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3168=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3188=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3189=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3204=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3205=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_4204=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_7204=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0305=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0391=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0501=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0601=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0605=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0691=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3091=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0505=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0576=%WinDir%\inf\machine.inf
	pci\ven_1107&dev_0576=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0586=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0596=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0686=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3074=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3109=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_8231=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0597=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_0598=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3040=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3050=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3051=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3057=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_8235=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3099=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3101=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_3112=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_8305=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_8391=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_8598=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_8501=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_8601=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_8605=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_b091=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_b099=%WinDir%\inf\machine.inf
	pci\ven_1106&dev_b112=%WinDir%\inf\machine.inf
	pci\ven_1004&dev_0005=%WinDir%\inf\machine.inf
	pci\ven_1004&dev_0006=%WinDir%\inf\machine.inf
	pci\ven_1004&dev_0101=%WinDir%\inf\machine.inf
	pci\ven_1004&dev_0102=%WinDir%\inf\machine.inf
	pci\ven_1004&dev_0103=%WinDir%\inf\machine.inf
	pci\ven_1004&dev_0104=%WinDir%\inf\machine.inf
	*adp1540=%WinDir%\inf\pnpscsi.inf
	*adp1542=%WinDir%\inf\pnpscsi.inf
	*adp4215=%WinDir%\inf\pnpscsi.inf
	*adp1502=%WinDir%\inf\pnpscsi.inf
	*adp1505=%WinDir%\inf\pnpscsi.inf
	*adp1510=%WinDir%\inf\pnpscsi.inf
	*adp1512=%WinDir%\inf\pnpscsi.inf
	*adp1515=%WinDir%\inf\pnpscsi.inf
	*adp1520=%WinDir%\inf\pnpscsi.inf
	*adp1522=%WinDir%\inf\pnpscsi.inf
	*adp3015=%WinDir%\inf\pnpscsi.inf
	*adp3215=%WinDir%\inf\pnpscsi.inf
	*adp6360=%WinDir%\inf\pnpscsi.inf
	*adp6370=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_00cf=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_00c0=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_008f=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0080=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0081=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0050=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0051=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0010=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_8178=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_8478=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_8578=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_00c0&subsys_f6209005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_00c0&subsys_f6200e11=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0080&subsys_e2a09005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0080&subsys_e2a00e11=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0080&subsys_62a09005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0080&subsys_e2209005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0081&subsys_62a19005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0082&subsys_02109005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0050&subsys_f5009005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0051&subsys_b5009005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0010&subsys_a1009005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0010&subsys_a1809005=%WinDir%\inf\pnpscsi.inf
	pci\ven_1044&dev_a501&subsys_c0471044=%WinDir%\inf\pnpscsi.inf
	pci\ven_1044&dev_a501&subsys_c03c1044=%WinDir%\inf\pnpscsi.inf
	pci\ven_1044&dev_a501&subsys_c05a1044=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_005f=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_001f=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0010&subsys_21809005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0010&subsys_e1009005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_0011&subsys_01819005=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7895&subsys_78959004=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7895&subsys_78919004=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7895&subsys_78929004=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7895&subsys_78949004=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_8078&subsys_78809004=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_8078=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_8178&subsys_78819004=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_8778&subsys_78879004=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_3860&subsys_38699004=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_8278=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_8678=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_3b78=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_ec78=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7078=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7678=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7778=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7178=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7278=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7478=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7578=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_6075=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_6778=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_6678=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_6578=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_6478=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_6278=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_6078=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_6178=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_7860=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_5078=%WinDir%\inf\pnpscsi.inf
	pci\ven_9004&dev_5075=%WinDir%\inf\pnpscsi.inf
	detected\aha154x=%WinDir%\inf\scsi.inf
	detected\sparrow=%WinDir%\inf\scsi.inf
	pci\ven_0e11&dev_ae10=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0012&subsys_001b0e11=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_000b&subsys_60040e11=%WinDir%\inf\pnpscsi.inf
	*cpqfd17=%WinDir%\inf\pnpscsi.inf
	detected\cpqarray=%WinDir%\inf\scsi.inf
	pci\ven_8086&dev_1960&subsys_04711028=%WinDir%\inf\pnpscsi.inf
	pci\ven_101e&dev_1960&subsys_04711028=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_04931028=%WinDir%\inf\pnpscsi.inf
	pci\ven_101e&dev_1960&subsys_04931028=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_11111028=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_11121111=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_11111111=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_04671028=%WinDir%\inf\pnpscsi.inf
	pci\ven_1011&dev_0046&subsys_13649005=%WinDir%\inf\pnpscsi.inf
	pci\ven_1028&dev_0001&subsys_00011028=%WinDir%\inf\pnpscsi.inf
	pci\ven_1028&dev_0002&subsys_00d11028=%WinDir%\inf\pnpscsi.inf
	pci\ven_1028&dev_0002&subsys_00d91028=%WinDir%\inf\pnpscsi.inf
	pci\ven_1028&dev_0002&subsys_00021028=%WinDir%\inf\pnpscsi.inf
	pci\ven_1028&dev_0003&subsys_00031028=%WinDir%\inf\pnpscsi.inf
	pci\ven_9005&dev_00c5&subsys_00c51028=%WinDir%\inf\pnpscsi.inf
	pci\ven_1011&dev_0046&subsys_10c2103c=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_10c6103c=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_10c7103c=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_10cc103c=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_10cd103c=%WinDir%\inf\pnpscsi.inf
	pci\ven_101e&dev_1960&subsys_60e7103c=%WinDir%\inf\pnpscsi.inf
	pci\ven_101e&dev_1960&subsys_60e8103c=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_000c=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_000f=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_000a=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_000b=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0012=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0020=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0021=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0001=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0002=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0003=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0004=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0005=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0006=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_000d=%WinDir%\inf\pnpscsi.inf
	pci\ven_1077&dev_1020=%WinDir%\inf\pnpscsi.inf
	pci\ven_1077&dev_1080=%WinDir%\inf\pnpscsi.inf
	pci\ven_1077&dev_1240=%WinDir%\inf\pnpscsi.inf
	pci\ven_1077&dev_1280&subsys_01068086=%WinDir%\inf\pnpscsi.inf
	pci\ven_1077&dev_1280&subsys_00061077=%WinDir%\inf\pnpscsi.inf
	pci\ven_1077&dev_1216&subsys_00071077=%WinDir%\inf\pnpscsi.inf
	pci\ven_1077&dev_1016&subsys_00081077=%WinDir%\inf\pnpscsi.inf
	pci\ven_1077&dev_1216&subsys_01078086=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_9621&subsys_00018086=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_9641&subsys_00018086=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_96a1&subsys_00018086=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_3092&subsys_00018086=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_9622&subsys_00018086=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0020&subsys_10201de1=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0021&subsys_10201de1=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0020&subsys_10101de1=%WinDir%\inf\pnpscsi.inf
	pci\ven_1000&dev_0021&subsys_10101de1=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_03a2113c=%WinDir%\inf\pnpscsi.inf
	pci\ven_101e&dev_9010=%WinDir%\inf\pnpscsi.inf
	pci\ven_101e&dev_9060=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_0438101e=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_0466101e=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_0467101e=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_0490101e=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_0471101e=%WinDir%\inf\pnpscsi.inf
	pci\ven_101e&dev_1960&subsys_0471101e=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_0493101e=%WinDir%\inf\pnpscsi.inf
	pci\ven_101e&dev_1960&subsys_0493101e=%WinDir%\inf\pnpscsi.inf
	pci\ven_8086&dev_1960&subsys_0475101e=%WinDir%\inf\pnpscsi.inf
	pci\ven_101e&dev_1960&subsys_0475101e=%WinDir%\inf\pnpscsi.inf
	pci\ven_13e6&dev_3603&subsys_00461014=%WinDir%\inf\pnpscsi.inf
	pci\ven_13e6&dev_3603&subsys_004613e6=%WinDir%\inf\pnpscsi.inf
	pci\ven_13e6&dev_3603&subsys_004913e6=%WinDir%\inf\pnpscsi.inf
	pci\ven_13e6&dev_3603&subsys_00460900=%WinDir%\inf\pnpscsi.inf
	pci\ven_13e6&dev_3603=%WinDir%\inf\pnpscsi.inf
	pci\ven_1069&dev_0050&subsys_00541069=%WinDir%\inf\pnpscsi.inf
	pci\ven_1069&dev_0050&subsys_00521069=%WinDir%\inf\pnpscsi.inf
	pci\ven_1069&dev_0050&subsys_00501069=%WinDir%\inf\pnpscsi.inf
	pci\ven_1069&dev_ba56&subsys_00401069=%WinDir%\inf\pnpscsi.inf
	pci\ven_1069&dev_ba56&subsys_00301069=%WinDir%\inf\pnpscsi.inf
	pci\ven_1069&dev_0001=%WinDir%\inf\pnpscsi.inf
	pci\ven_1069&dev_0002=%WinDir%\inf\pnpscsi.inf
	pci\ven_1069&dev_0010=%WinDir%\inf\pnpscsi.inf
	pci\ven_1011&dev_1065&subsys_00201069=%WinDir%\inf\pnpscsi.inf
	pci\ven_1069&dev_ba55=%WinDir%\inf\pnpscsi.inf
	detected\dac960nt=%WinDir%\inf\scsi.inf
	pci\ven_10cd&dev_2300=%WinDir%\inf\pnpscsi.inf
	pci\ven_10cd&dev_1100=%WinDir%\inf\pnpscsi.inf
	pci\ven_10cd&dev_1200=%WinDir%\inf\pnpscsi.inf
	pci\ven_10cd&dev_1300=%WinDir%\inf\pnpscsi.inf
	pci\ven_10cd&dev_1300&subsys_133010cd=%WinDir%\inf\pnpscsi.inf
	pci\ven_1022&dev_2020=%WinDir%\inf\pnpscsi.inf
	gen_scsiadapter=%WinDir%\inf\pnpscsi.inf
	pci\ven_1101&dev_9500=%WinDir%\inf\pnpscsi.inf
	pci\ven_1101&dev_9400=%WinDir%\inf\pnpscsi.inf
	pci\ven_1101&dev_9401=%WinDir%\inf\pnpscsi.inf
	pci\ven_1101&dev_134a=%WinDir%\inf\pnpscsi.inf
	pci\ven_1101&dev_0002=%WinDir%\inf\pnpscsi.inf
	pci\ven_105a&dev_4d68&cc_0180=%WinDir%\inf\pnpscsi.inf
	pci\ven_105a&dev_4d30&cc_0180=%WinDir%\inf\pnpscsi.inf
	pci\ven_105a&dev_0d30&cc_0180=%WinDir%\inf\pnpscsi.inf
	pci\ven_105a&dev_4d38&cc_0180=%WinDir%\inf\pnpscsi.inf
	pci\ven_105a&dev_4d33=%WinDir%\inf\mshdc.inf
	pci\ven_1000&dev_008f=%WinDir%\inf\scsi.inf
	buslogic_scsi=%WinDir%\inf\scsi.inf
	detected\buslogic=%WinDir%\inf\scsi.inf
	*bus0042=%WinDir%\inf\scsi.inf
	pci\ven_104b&dev_1040=%WinDir%\inf\scsi.inf
	flashpnt_scsi=%WinDir%\inf\scsi.inf
	pci\ven_104b&dev_8130=%WinDir%\inf\scsi.inf
	cpqfws2e_scsi=%WinDir%\inf\scsi.inf
	detected\cpqfws2e=%WinDir%\inf\scsi.inf
	*fdc0000=%WinDir%\inf\scsi.inf
	detectedpci\fd16_700=%WinDir%\inf\scsi.inf
	fd16_700_scsi=%WinDir%\inf\scsi.inf
	detected\fd16_700=%WinDir%\inf\scsi.inf
	pci\ven_1036&dev_0000=%WinDir%\inf\scsi.inf
	*cpq4410=%WinDir%\inf\scsi.inf
	*cpq4411=%WinDir%\inf\scsi.inf
	ncrc710_scsi=%WinDir%\inf\scsi.inf
	detected\ncrc710=%WinDir%\inf\scsi.inf
	pci\ven_1103&dev_0004&subsys_00051103&rev_03=%WinDir%\inf\scsi.inf
	pci\ven_1103&dev_0004&subsys_00011103&rev_03=%WinDir%\inf\scsi.inf
	pci\ven_1103&dev_0004&subsys_00011103&rev_04=%WinDir%\inf\scsi.inf
	pci\ven_8086&dev_1222=%WinDir%\inf\mshdc.inf
	pci\ven_8086&dev_1230=%WinDir%\inf\mshdc.inf
	pci\ven_8086&dev_7010=%WinDir%\inf\mshdc.inf
	pci\ven_8086&dev_7111=%WinDir%\inf\mshdc.inf
	pci\ven_8086&dev_2411=%WinDir%\inf\mshdc.inf
	pci\ven_8086&dev_2421=%WinDir%\inf\mshdc.inf
  pci\ven_8086&dev_7199=%WinDir%\inf\mshdc.inf
	pci\ven_8086&dev_7601=%WinDir%\inf\mshdc.inf
	*pnp0600=%WinDir%\inf\mshdc.inf
	*azt0502=%WinDir%\inf\mshdc.inf
	pci\cc_0101=%WinDir%\inf\mshdc.inf
	pci\ven_10b9&dev_5215=%WinDir%\inf\mshdc.inf
	pci\ven_10b9&dev_5219=%WinDir%\inf\mshdc.inf
	pci\ven_10b9&dev_5229=%WinDir%\inf\mshdc.inf
	pci\ven_1097&dev_0038=%WinDir%\inf\mshdc.inf
	pci\ven_1095&dev_0640=%WinDir%\inf\mshdc.inf
	pci\ven_1095&dev_0646=%WinDir%\inf\mshdc.inf
	pci\ven_1095&dev_0646&rev_05=%WinDir%\inf\mshdc.inf
	pci\ven_1095&dev_0646&rev_07=%WinDir%\inf\mshdc.inf
	pci\ven_1095&dev_0648=%WinDir%\inf\mshdc.inf
	pci\ven_1095&dev_0649=%WinDir%\inf\mshdc.inf
	pci\ven_0e11&dev_ae33=%WinDir%\inf\mshdc.inf
	pci\ven_1042&dev_1000=%WinDir%\inf\mshdc.inf
	pci\ven_1039&dev_0601=%WinDir%\inf\mshdc.inf
	pci\ven_1039&dev_5513=%WinDir%\inf\mshdc.inf
	pci\ven_10ad&dev_0001=%WinDir%\inf\mshdc.inf
	pci\ven_10ad&dev_0150=%WinDir%\inf\mshdc.inf
	pci\ven_1106&dev_0571=%WinDir%\inf\mshdc.inf
	pci\ven_1055&dev_9130=%WinDir%\inf\mshdc.inf
	pci\ven_1179&dev_0105=%WinDir%\inf\mshdc.inf

Last edited by JakeLD (2007-10-31 11:00:44)

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/n4W97qgvXb9IR64MNwT_BbnsRgjGDd0hpeGIqqmpZZ0/perpetual:forever/userbar/team-2.png

Donate!

JakeLD's Website

  • From: Manchester, England
  • Registered: 2007-06-07
  • Posts: 27

Re: Using driverpacks on a ready built image?

Jake you are DA MAN!....

Rolled back to the "ready to image" (thank the lord for vmware snapshots!) snipped the relevant info from your sysprep file and LO!  The darned thing worked!!!!  Made a bit of a bugger up on something else so I will have to go back to the initial step again tomorrow (Forgot to set it to autologon once.. Might try editing the sysprep file with ghost explorer but if not no big just another silly mistake cause as usual I'm being rushed to get everything done!!!).. But for now I'm happy that it worked!!!.. 

One last quick question..  With ROE set..  Will dpfnshr reboot the pc?  I'm thinking of adding the landesk installer to the run once on the final finished article (this would then make it utterly idiot proof.. the kind of image we all want!) but thats something I'll play with later on I think..

So thanks again Jake.. Have yourself a nice big cold drink on me this halloween night!!

Rob
(Off to raid the kids goodie bags I think I deserve it! smile )

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/Av2BDsDf_iiqO8a4dpI49DKicUs_0zEQtEPcTGyCqV4/perpetual:forever/userbar/tester-1.png

On a mission to re-educate users the Clue stick way!
  • AceQ
  • DriverPacks newbie
  • Offline
  • Registered: 2007-11-08
  • Posts: 2

Re: Using driverpacks on a ready built image?

This topic is pretty interesting because I've been doing similar for a year or so with mixed results.

I have always used Method 1 and seeded an xp-boot cd with the drivers.  Loaded that image into VM and then extracted the image normally.  I would use D/L/M on the seeded xp install.  The result after sysprep was always positive and the vm'd OS would boot up on a a large variety of machines without issue.

-Until the late Dell hardware (390 / 690 )-

The process was failing and causing endless reboots or freezes.  The only way to avoid it was by putting the paths of the MSD/chipset directly into the sysprep.ini.  This was odd because it worked previously.  When I jumped into the forums to see if anyone else was having issues I noticed this thread with a large section dedicated to the BuildMassStorage area of the sysprep.ini.

If you are going to point Sysprep to the primary chipset/MSD drivers when you encapsulate the image - why would you run the KTD scenario?  I'm just curious as it seems almost redundant.  My understanding of the KTD process is very limited though, so please forgive the question of it's out of place.

To give a bit more on the current situation, method 2 would freeze after the sysprep on the sysprep blue 'Windows' mini setup screen.  Method 1 worked without LAN drivers because of the 4096 registry limitation.  MySysprep got around that and the universal works just fine ( as long as you play with the sysprep.ini a bit and ensure the correct drivers are in the BMSD area of the .ini similar to what was posted above or the newer hardware )

MySysprep is slick, I'm a big fan at the moment.

Thank you to everyone.

Last edited by AceQ (2007-11-08 01:29:10)

  • JakeLD
  • Moderator, Sysprep & BartPE Master
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-07-05
  • Posts: 872

Re: Using driverpacks on a ready built image?

method 1 ? method 2 ? Why are you running DP Base on sysprep image ? DP base is only valid for disk install. Doing your univerl image from a disk install with DP integrated is not the best solution either since you keep drivers that you don't need. I will post my sysprep.cmd here. Actually a universal image guide is required.

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/n4W97qgvXb9IR64MNwT_BbnsRgjGDd0hpeGIqqmpZZ0/perpetual:forever/userbar/team-2.png

Donate!

JakeLD's Website

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: Using driverpacks on a ready built image?

That is a good point - we are always covering sysprep - and a guide does seem needed

sysprep yech...

Last edited by OverFlow (2007-11-08 16:49:46)

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: Using driverpacks on a ready built image?

JakeLD wrote:

2 INFs file using the same HWIDS cant coexist with syprep even if both INF have different names.

Did you realise I have seen drivers where lines were simply completely repeated?..  Small wonder you use duplifind.

The answer was 42?
Kind regards, Jaak.
  • AceQ
  • DriverPacks newbie
  • Offline
  • Registered: 2007-11-08
  • Posts: 2

Re: Using driverpacks on a ready built image?

Well, I do it that way because it worked.  A few years ago when VM was coming into its own I played with getting a universal image out of VM without success.  The reasons were obviously a lack of MSD / HAL issues as everyone has seen I'm sure.  The DP concept worked great on CD's so the idea of image seeding came to mind.

I may not be the best way but it worked pretty well.  Create a standard DP .iso and load it into VM.  Keep the drivers and blammo, universal image when you prep it down and pull it out of VM.  Without the need to modify the sysprep.ini with hardware specific vendor ID's.

Sounds like a base OS -> VM -> MySysprep drivers -> Massage the Sysprep.ini for MSD/Chipset has the same effect with much more flexibility.

As always I appreciate any and all pointers, ideas, critiques and help.

-AceQ-

  • Registered: 2007-12-11
  • Posts: 3

Re: Using driverpacks on a ready built image?

I was going to ask a question about the finisher for use in imaging but after thinking about it would I be correct In assuming that when the finisher is run in KTD PATH:Foo that the inf/pnf files that are created also contain pointers to the .cpl .exe (exception files) that the finisher would have installed in normal mode (but only for the drivers (hardware) that is installed at the time.)i.e so after KTD any hardware, post installed would pick up exceptions if it had any because of the inf/pnf files.Is this true?
After reading many posts on this subject ive decided confusion rules and my summation of what the finisher does is, after installation of drivers finisher looks at the hardware via devcon checks against its exception list (.ini file)for those installed drivers and if there installs the exceptions,cleans up after itself and thats it. On the flip side if you keep the drivers it writes pnf's so if you installed hardware later it would pick up on the exceptions automagically.Is this correct??If so this would answer most my questions.Thanx Anybody!!
p.s If this is wrong it means that I am just as confused as everybody which would then lead me to my question is there any way to apply the finisher post install without it having to re write all the inf\pnf files if they are already there(if youve put them there for imaging)
THE finisher is what it says it is it just adds exceptions to the drivers that require them if they are installed.

One who asks a question is a fool for five minutes; one who does not ask a question remains a fool forever. or

You always admire what you really don't understand.

Last edited by AceofSpades (2007-12-12 01:47:35)

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: Using driverpacks on a ready built image?

there are quite a few posts on here about this - try to search for stuff. The link below is even stickied.
here is a starter link LINK

the finisher only runs once and deletes itself and will not run again. so no you will only get drivers after KTD is used.
no control panels or start menu shortcuts or setup programs will be run. PERIOD.

I have said this at least 500 times: ( at LEAST 500 )
KTD has no useful purpose on a normal machine. Its for a Technicians Test Bed (what i call an AIR machine.) that will have cards plugged in one after the other for purposes of verifing if they are working or not. (to eliminate windows as the problem by useing a Test Machine)
Look at it like this - suppose you load a machine for an end user with KTD (which takes up 1.5 gig of disk space) and then add hardware 6 months later - do you really want a 6 month old driver @ 1.5 gig. and no control panels - Heck No! that is a huge amount of disk space to backup / defrag / virus scan / waste especially when the odds it will ever be needed is near 0%.

how often do people add "NEW" hardware and don't have the disk that came with the "new" hardware.? (scratches head bewildered)

instead create a "drivers only CD" {Search the forums} and use the search removable media feature of windows add new hardware. let's face it if your adding a new device then you are at the machine arn't you??? take the driver disk with you DUH!

no the finisher will not run post install because the finishers inf files (that come bundled in the driverpacks) are deleted when the finisher runs and only the finisher will "automagicaly" finish the drivers.

dont do this - dont try to do this - its not a good plan and it doesn't give the desired results.

I am half tempted to remove KTD as a GUI option to eliminate this FAQ and confusion surrounding it.

side note MOST drivers in the packs do not need the finisher at all (i am guessing over 90%)
side note 2 the finisher will NOT install drivers only windows does that.

KTD should only be used IF you are loading a test machine on your workbench.

counter indexes to 501 times. steps down off soap box.

perhaps after i get BartPE on the run ill work on a  - RIS / syprep / OEM install -   platform in to a beta.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Registered: 2007-12-11
  • Posts: 3

Re: Using driverpacks on a ready built image?

Ah!Well youve almost created the perfect addition to the syspreppers (Acronis True Image) toolkit. Scenario create the system you want-add all Bâshrat the Sneaky drivers +inf/pnf's using (setupcopyoem.exe) or indeed THE FINISHER to the system uninstall  the existing machine specific drivers (or sysprep) shut down and image the system.Recover to different machine on its way up it finds and loads its drivers including some oem###.inf/pnf drivers (Bâshrat the Sneaky) no problem but they just happen to require THE FINISHER  no problem reboot with the finisher Required files extracted to root Run the finisher et voila exceptions added but all it needs is a couple of switches to stop it moving/deleting driver files if required and to stop it rewriting inf/pnf files if required ie using devcon hwid's compared against exception ini's to work PURELY as a finisher (exceptions only nothing fancy) dealing only with the exceptions.Hence all the questions.

But by reading them again and again finally I was able to grasp the essential part. What emotion, enthusiasm, enlightenment and confidence they communicated to me! I wept for joy.
Ho Chi Minh

Last edited by AceofSpades (2007-12-12 20:55:29)

  • Registered: 2007-12-11
  • Posts: 3

Re: Using driverpacks on a ready built image?

Does anyone know of a way to do this?Scenerio prior to shutting down for imaging the driver packs have been installed and finisher has been run with the sole purpose of putting the inf files in the inf folder and pointers on the devicepath %KTD%\whatever (dopnf) The image is put on another (different) machine and on starting up all new hardware is found and installed courtesy of the driver packs, if needed the Dsblr can be running.Now the new harware is installed time to reboot,reboot but now we would like to process for exceptions easy you can rerun the finisher this works but its slow as it wants to do its write inf/pnf thing is there a way to do this without this happening?? Any help much appreciated