1 Reply by Northland

(33 replies, posted in Universal Imaging)

Hi, mr_smartepants.

Thanks for the clarification.  I would be willing to test a separate mobile drivers folder (with a sysprep image) if it becomes a reality, although I realize that it would probably be a lot of work, and may not be feasible if the DPBase is coded with hard paths.  I don't know if others have experienced the same results as I have, nor do I know if this is the direction the DriverPacks.net development team wants to take.  I do want to express my thanks to all of you who have contributed. I appreciate your help.

Go to forum: Universal Imaging

2 Reply by Northland

(33 replies, posted in Universal Imaging)

Howdy.

Thanks for your input mr_smartepants and Jaak.  I have been following the discussion, and am interested in any additional ideas you may have.  I would like to find a way to not have to address this driver specifically, although Overflow's idea may end up being the only one that allows for an automated install. A separate mobile drivers folder is interesting. A separate folder may allow for excluding it in an image for testing purposes to see if issues like this are caused by other drivers (although I am not sure how this would be possible as most ATI drivers I have seen reference the mobile drivers - and editing the ATI infs break the security....)

Go to forum: Universal Imaging

3 Reply by Northland

(33 replies, posted in Universal Imaging)

Hi Overflow.

Fixing the line in the mobility.inf files was one of the first things I did to try and resolve this issue. The results are the same - the driver appears to install under device manager, but XP uses its default VGA driver instead.  I am thinking that I may just have to install this one manually (post sysprep.)

Go to forum: Universal Imaging

4 Reply by Northland

(33 replies, posted in Universal Imaging)

Thanks for the idea OverFlow. Unfortunately, I don't think that will work unless I stop using the entire ATI driverpacks folder in A1.  The ATI inf files reference the X300 (the mobility.inf does not - as someone commented out the X300 entry. -I think they should add it back in and fix the hardware id of ati2mtag_M22, PCI\VEN_1002&DEV_5461 to 5460 instead of the x200's 5461 - which is why I think it is commented out.)

Even if I did somehow update the XP driverstore with newer drivers, I think (correct me if I am wrong) they would not install if the driverpacks drivers were also in my image (unless the driverpacks drivers were older than the driver I used to update XP's driverstore.)  I have played around with updating Vista's driver store using pnputil.exe, but have not had the need to do so in XP.

Go to forum: Universal Imaging

5 Reply by Northland

(33 replies, posted in Universal Imaging)

Well, I can verify that manually installing the Dell driver does indeed also install a newer version of ati2mtag.sys, even though it does not show up in the setupapi.log.  Why it is not documented like it is when sysprep tries to install it is beyond me. I do now that the 1307 error is seen with every ati2mtag.sys file that I have tried to install through sysprep. At first I thought that this was the problem, perhaps some sort of MD5 hash issue, but I have seen this error on original ATI drivers that have never been modified.  I have also seen the error with the Dell drivers that install just fine if installed manually (not to mention all of the driverpacks drivers.)  Of course, this may not even be the problem...

Go to forum: Universal Imaging

6 Reply by Northland

(33 replies, posted in Universal Imaging)

The Dell driver does have a setup.exe, but I manually installed it using only the driver files which I extracted from the Dell installer.  I see what bigfoot is saying about the ati2mtag.sys file that does not appear to be referenced in the setupapi.log file.  The file version that appears in device manager for ati2mtag.sys  is 6.14.10.6568, which is the version of the Dell X300 drivers as reported by the CX_25030.inf file.  I am wondering why the ati2mtag.sys isn't being reported in the setupapi.log file... Is something weird going on between the Default XP Driver Store driver from 2004 and this driver?  Perhaps the ati2mtag.sys is not copied over and XP uses the already installed driver store version... It looks like I will have to redeploy the no driverpack sysprep image and take a closer look at the XP driverstore X300 driver & then compare it to a manual Dell X300 driver install.

Go to forum: Universal Imaging

7 Reply by Northland

(33 replies, posted in Universal Imaging)

This is what the setupappi.log looks like for a manual install of the Dell driver after sysprep:


[2008/06/25 13:05:53 2300.2311 Driver Install]
#-406 Obtaining rollback information for device "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008":
#-019 Searching for hardware ID(s): pci\ven_1002&dev_5460&subsys_20061028&rev_00,pci\ven_1002&dev_5460&subsys_20061028,pci\ven_1002&dev_5460&cc_030000,pci\ven_1002&dev_5460&cc_0300
#-018 Searching for compatible ID(s): pci\ven_1002&dev_5460&rev_00,pci\ven_1002&dev_5460,pci\ven_1002&cc_030000,pci\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" C:\WINDOWS\system32\devmgmt.msc /s
#I063 Selected driver installs from section [ati2mtag_M6] in "c:\windows\inf\atiixpag.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
[2008/06/25 13:05:37 2300.2304]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" C:\WINDOWS\system32\devmgmt.msc /s
#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci\ven_1002&dev_5460&subsys_20061028&rev_00,pci\ven_1002&dev_5460&subsys_20061028,pci\ven_1002&dev_5460&cc_030000,pci\ven_1002&dev_5460&cc_0300
#-018 Searching for compatible ID(s): pci\ven_1002&dev_5460&rev_00,pci\ven_1002&dev_5460,pci\ven_1002&cc_030000,pci\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-019 Searching for hardware ID(s): pci\ven_1002&dev_5460&subsys_20061028&rev_00,pci\ven_1002&dev_5460&subsys_20061028,pci\ven_1002&dev_5460&cc_030000,pci\ven_1002&dev_5460&cc_0300
#-018 Searching for compatible ID(s): pci\ven_1002&dev_5460&rev_00,pci\ven_1002&dev_5460,pci\ven_1002&cc_030000,pci\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#I022 Found "PCI\VEN_1002&DEV_5460&SUBSYS_20061028" in c:\documents and settings\administrator\desktop\r104771_2kxp_inf\CX_25030.inf; Device: "ATI MOBILITY RADEON X300 "; Driver: "ATI MOBILITY RADEON X300 "; Provider: "ATI Technologies
Inc."; Mfg: "ATI Technologies Inc."; Section name: "BR_24912_ati2mtag_M22".
#I023 Actual install section: [BR_24912_ati2mtag_M22]. Rank: 0x00000001. Effective driver date: 07/06/2005.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [BR_24912_ati2mtag_M22] in "c:\documents and settings\administrator\desktop\r104771_2kxp_inf\cx_25030.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008".
#-336 Copying file "c:\documents and settings\administrator\desktop\r104771_2kxp_inf\.\B_24906\ati2dvag.dl_" to "C:\WINDOWS\system32\ati2dvag.dll" via temporary file "C:\WINDOWS\system32\SETD.tmp".
#W190 File "C:\WINDOWS\system32\SETD.tmp" marked to be moved to "C:\WINDOWS\system32\ati2dvag.dll" on next reboot.
#-336 Copying file "c:\documents and settings\administrator\desktop\r104771_2kxp_inf\.\B_24906\ati2cqag.dl_" to "C:\WINDOWS\system32\ati2cqag.dll" via temporary file "C:\WINDOWS\system32\SETF.tmp".
#W190 File "C:\WINDOWS\system32\SETF.tmp" marked to be moved to "C:\WINDOWS\system32\ati2cqag.dll" on next reboot.
#-336 Copying file "c:\documents and settings\administrator\desktop\r104771_2kxp_inf\.\B_24906\ati3duag.dl_" to "C:\WINDOWS\system32\ati3duag.dll" via temporary file "C:\WINDOWS\system32\SET12.tmp".
#W190 File "C:\WINDOWS\system32\SET12.tmp" marked to be moved to "C:\WINDOWS\system32\ati3duag.dll" on next reboot.
#-336 Copying file "c:\documents and settings\administrator\desktop\r104771_2kxp_inf\.\B_24906\ativvaxx.dl_" to "C:\WINDOWS\system32\ativvaxx.dll" via temporary file "C:\WINDOWS\system32\SET14.tmp".
#W190 File "C:\WINDOWS\system32\SET14.tmp" marked to be moved to "C:\WINDOWS\system32\ativvaxx.dll" on next reboot.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [BR_24912_ati2mtag_M22.Interfaces] from "c:\documents and settings\administrator\desktop\r104771_2kxp_inf\cx_25030.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008".
#W100 Query-removal during install of "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008" was vetoed by "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27ea4097&0&0008" (veto type 6: PNP_VetoDevice).
#W104 Device "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008" required reboot: Query remove failed (install) CfgMgr32 returned: 0x17: CR_REMOVE_VETOED.
#I121 Device install of "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008" finished successfully.

This is similar to what happens during sysprep, but I found this info just below it and it is not in the setupapi.log when the driver is enumerated during sysprep:

[2008/06/25 13:05:11 2300.1840 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_1002&dev_5460&subsys_20061028&rev_00,pci\ven_1002&dev_5460&subsys_20061028,pci\ven_1002&dev_5460&cc_030000,pci\ven_1002&dev_5460&cc_0300
#-018 Searching for compatible ID(s): pci\ven_1002&dev_5460&rev_00,pci\ven_1002&dev_5460,pci\ven_1002&cc_030000,pci\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" C:\WINDOWS\system32\devmgmt.msc /s
#I063 Selected driver installs from section [ati2mtag_M6] in "c:\windows\inf\atiixpag.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#-124 Doing copy-only install of "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008".
#-019 Searching for hardware ID(s): pci\ven_1002&dev_5460&subsys_20061028&rev_00,pci\ven_1002&dev_5460&subsys_20061028,pci\ven_1002&dev_5460&cc_030000,pci\ven_1002&dev_5460&cc_0300
#-018 Searching for compatible ID(s): pci\ven_1002&dev_5460&rev_00,pci\ven_1002&dev_5460,pci\ven_1002&cc_030000,pci\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#I063 Selected driver installs from section [BR_24912_ati2mtag_M22] in "c:\windows\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.

And also this:

[2008/06/25 13:10:32 1828.238 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_1002&dev_5460&subsys_20061028&rev_00,pci\ven_1002&dev_5460&subsys_20061028,pci\ven_1002&dev_5460&cc_030000,pci\ven_1002&dev_5460&cc_0300
#-018 Searching for compatible ID(s): pci\ven_1002&dev_5460&rev_00,pci\ven_1002&dev_5460,pci\ven_1002&cc_030000,pci\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" C:\WINDOWS\system32\devmgmt.msc /s
#I063 Selected driver installs from section [BR_24912_ati2mtag_M22] in "c:\windows\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.

Any ideas?

Go to forum: Universal Imaging

8 Reply by Northland

(33 replies, posted in Universal Imaging)

Well, I tried incorporating the registry changes in a new sysprep image as depicted in the link bigfoot sent (and the link referenced in that link,) but neither change made any difference.  I also made a sysprepp image with no driver packs, and discovered that Microsoft XP's driver store had a driver for the D610 laptop (from 2004.) I was surprised to see a non-800x600 screen resolution on first boot after sysprep was done. I then manually installed the Dell driver and rebooted the laptop. The Dell driver installed correctly.  Installing manually does not seem to be the problem.  Something is happening during the sysprep process that keeps the X300 driver from installing properly....

Go to forum: Universal Imaging

9 Reply by Northland

(33 replies, posted in Universal Imaging)

Hi OverFlow.

Manually installing the drivers has never been a problem.  Getting them to install during the sysprep process is the problem.  It takes a while to create each image, but tomorrow I will create a sysprep image with no driverpacks and then manually install the Dell drivers post-sysprep to verify.  I was also planning on creating an image with the information bigfoot referenced. I tried making the registry changes suggested in the link, but they did not resolve the problem. I believe the registry changes need to be in the master image prior to running sysprep in order for it to be a valid test.

Go to forum: Universal Imaging

10 Reply by Northland

(33 replies, posted in Universal Imaging)

Thanks for the reply bigfoot. 

I will look into the link you sent.  The surprising thing about the error 1307 is that I thought that this may have been caused by something manipulating/editing the ati2mtag.sys file.  So I made a custom driver pack with "official" ATI drivers and tested it.  I got the same 1307 error....  I have tried the 710, 804, and 806B Graphics A driverpacks with the same results.

Go to forum: Universal Imaging

11 Reply by Northland

(33 replies, posted in Universal Imaging)

Hi OverFlow.  Thanks for the response.

I have tried so many combinations of drivers that I forgot if I had tried the OEM ones from Dell, so today I created an image with the 2005 Dell drivers and got the same results......  I am wondering if either another driver is interfering (doesn't seem to matter what X300 video driver I use) or perhaps some weird Dell\Sysprep\ATI compatibility problem. With that in mind I removed every driver pack folder from my image except the ATI drivers and also got the same results.... This is getting frustrating.

Go to forum: Universal Imaging

12 Reply by Northland

(33 replies, posted in Universal Imaging)

Hi Bigfoot and OverFlow. 

Thanks for responding.  Yes, my image has .NET 1, 2, and 3 installed.  You are also right in that my devicepath key is fairly long - but it does not seem to be a problem.  During the hardware enumeration phase of the deployed sysprep image, the correct driver is located from the registry's devicepath key, but something is keeping it from being fully recognized by the OS.  The driver seems to install properly when looking in device manager, but the OS wants to use its generic VGA driver, and displays the message I previously posted.  Any ideas?

Go to forum: Universal Imaging

13 Topic by Northland

(33 replies, posted in Universal Imaging)

Hello.

First I want to express my gratitude for everyone who has contributed to the driverpacks.  Thank You.

I am trying to develop a customized sysprep image of Win XP SP2  and am 99% there.  I am using the following packs in my image:

dp_chipset_wnt5_x86-32_803
dp_cpu_wnt5_x86-32_804
dp_graphics_a_wnt5_x86-32_806b
dp_graphics_b_wnt5_x86-32_804
dp_graphics_c_wnt5_x86-32_804
dp_lan_wnt5_x86-32_8052
dp_massstorage_wnt5_x86-32_806c
dp_modem_wnt5_x86-32_806
dp_sound_a_wnt5_x86-32_805
dp_sound_b_wnt5_x86-32_805
dp_wlan_wnt5_x86-32_803

I am basically placing all of these drivers in a "drivers" folder and reference the inf file locations in  the registry.  This has worked very well for me in the past.

However, I am having difficulties getting the ATI Mobility X300 driver to install properly.  When I deploy my syprepped image to a Dell D610, the correct driver is found but it does not seem to install properly.  When I select the display properties-settings tab I get the following message:

"The currently selected graphics display driver can not be used. It was written for a previous version of Windows, and is no longer compatible with this version of Windows.

The system has been started using the default VGA driver.

Please contact your hardware manufacturer to get an upgraded driver, or select one of the Microsoft provided drivers."

The interesting this is that the driver appears to install properly. Device manager shows it is installed and working properly, and all the driver files seem to be there.  I can also successfully reinstall the driver manually using the same driver files.

Here is what  setupapi.log is reporting:

#-019 Searching for hardware ID(s): pci\ven_1002&dev_5460&subsys_20061028&rev_00,pci\ven_1002&dev_5460&subsys_20061028,pci\ven_1002&dev_5460&cc_030000,pci\ven_1002&dev_5460&cc_0300
#-018 Searching for compatible ID(s): pci\ven_1002&dev_5460&rev_00,pci\ven_1002&dev_5460,pci\ven_1002&cc_030000,pci\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe -newsetup -mini
#I022 Found "PCI\VEN_1002&DEV_5460" in c:\drivers\dp_graphics_a_wnt5_x86-32_806b\d\g\a1\cx_63034.inf; Device: "ATI MOBILITY RADEON X300"; Driver: "ATI MOBILITY RADEON X300"; Provider: "ATI Technologies Inc."; Mfg: "ATI Technologies Inc."; Section name: "ati2mtag_M22".
#I023 Actual install section: [ati2mtag_M22]. Rank: 0x00002001. Effective driver date: 05/12/2008.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ati2mtag_M22] in "c:\drivers\dp_graphics_a_wnt5_x86-32_806b\d\g\a1\cx_63034.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
[2008/06/20 10:55:51 784.316 Driver Install]
#-406 Obtaining rollback information for device "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008":
#-019 Searching for hardware ID(s): pci\ven_1002&dev_5460&subsys_20061028&rev_00,pci\ven_1002&dev_5460&subsys_20061028,pci\ven_1002&dev_5460&cc_030000,pci\ven_1002&dev_5460&cc_0300
#-018 Searching for compatible ID(s): pci\ven_1002&dev_5460&rev_00,pci\ven_1002&dev_5460,pci\ven_1002&cc_030000,pci\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe -newsetup -mini
#I063 Selected driver installs from section [ati2mtag_M6] in "c:\windows\inf\atiixpag.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
[2008/06/20 10:55:50 784.310]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup.exe -newsetup -mini
#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci\ven_1002&dev_5460&subsys_20061028&rev_00,pci\ven_1002&dev_5460&subsys_20061028,pci\ven_1002&dev_5460&cc_030000,pci\ven_1002&dev_5460&cc_0300
#-018 Searching for compatible ID(s): pci\ven_1002&dev_5460&rev_00,pci\ven_1002&dev_5460,pci\ven_1002&cc_030000,pci\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#I022 Found "PCI\VEN_1002&DEV_5460" in c:\drivers\dp_graphics_a_wnt5_x86-32_806b\d\g\a1\cx_63034.inf; Device: "ATI MOBILITY RADEON X300"; Driver: "ATI MOBILITY RADEON X300"; Provider: "ATI Technologies Inc."; Mfg: "ATI Technologies Inc."; Section name: "ati2mtag_M22".
#I023 Actual install section: [ati2mtag_M22]. Rank: 0x00002001. Effective driver date: 05/12/2008.
#-019 Searching for hardware ID(s): pci\ven_1002&dev_5460&subsys_20061028&rev_00,pci\ven_1002&dev_5460&subsys_20061028,pci\ven_1002&dev_5460&cc_030000,pci\ven_1002&dev_5460&cc_0300
#-018 Searching for compatible ID(s): pci\ven_1002&dev_5460&rev_00,pci\ven_1002&dev_5460,pci\ven_1002&cc_030000,pci\ven_1002&cc_0300,pci\ven_1002,pci\cc_030000,pci\cc_0300
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ati2mtag_M22] in "c:\drivers\dp_graphics_a_wnt5_x86-32_806b\d\g\a1\cx_63034.inf".
#I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008".
#-336 Copying file "c:\drivers\dp_graphics_a_wnt5_x86-32_806b\d\g\a1\.\B_64119\ati2mtag.sys" to "C:\WINDOWS\system32\DRIVERS\ati2mtag.sys" via temporary file "C:\WINDOWS\system32\DRIVERS\SET11.tmp".
#E249 Failed to apply security to file "C:\WINDOWS\system32\DRIVERS\ati2mtag.sys". Error 1307: This security ID may not be assigned as the owner of this object.
#-336 Copying file "c:\drivers\dp_graphics_a_wnt5_x86-32_806b\d\g\a1\.\B_64119\ati2dvag.dll" to "C:\WINDOWS\system32\ati2dvag.dll" via temporary file "C:\WINDOWS\system32\SET13.tmp".
#W190 File "C:\WINDOWS\system32\SET13.tmp" marked to be moved to "C:\WINDOWS\system32\ati2dvag.dll" on next reboot.
#-336 Copying file "c:\drivers\dp_graphics_a_wnt5_x86-32_806b\d\g\a1\.\B_64119\ati2cqag.dll" to "C:\WINDOWS\system32\ati2cqag.dll" via temporary file "C:\WINDOWS\system32\SET14.tmp".
#W190 File "C:\WINDOWS\system32\SET14.tmp" marked to be moved to "C:\WINDOWS\system32\ati2cqag.dll" on next reboot.
#-336 Copying file "c:\drivers\dp_graphics_a_wnt5_x86-32_806b\d\g\a1\.\B_64119\ati3duag.dll" to "C:\WINDOWS\system32\ati3duag.dll" via temporary file "C:\WINDOWS\system32\SET16.tmp".
#W190 File "C:\WINDOWS\system32\SET16.tmp" marked to be moved to "C:\WINDOWS\system32\ati3duag.dll" on next reboot.
#-336 Copying file "c:\drivers\dp_graphics_a_wnt5_x86-32_806b\d\g\a1\.\B_64119\ativvaxx.dll" to "C:\WINDOWS\system32\ativvaxx.dll" via temporary file "C:\WINDOWS\system32\SET17.tmp".
#W190 File "C:\WINDOWS\system32\SET17.tmp" marked to be moved to "C:\WINDOWS\system32\ativvaxx.dll" on next reboot.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ati2mtag_M22.Interfaces] from "c:\drivers\dp_graphics_a_wnt5_x86-32_806b\d\g\a1\cx_63034.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008".
#W100 Query-removal during install of "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008" was vetoed by "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27ea4097&0&0008" (veto type 6: PNP_VetoDevice).
#W104 Device "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008" required reboot: Query remove failed (install) CfgMgr32 returned: 0x17: CR_REMOVE_VETOED.
#I121 Device install of "PCI\VEN_1002&DEV_5460&SUBSYS_20061028&REV_00\4&27EA4097&0&0008" finished successfully.

Rebooting the computer after sysprep has finished does not resoolve the problem.

Does anyone have any ideas as to what is wrong? I admit I am not an expert at reading the setupapi.log.

I have also tried the past two dp_graphics_a_wnt5_x86-32 packs and get the same results.

Any help would be greatly appreciated.

Go to forum: Universal Imaging