Topic: Found new hardware during RunOnceEx

Hi, i was doing an unattended installation, but when RunOnceEX has launched to install programs, the wizard of new hardware found has appeared. It seems that the driver graphics has not been installed properly.
Here is DPs_BASE.log:

2007-05-11 12:53:37 : <INIT> DriverPacks BASE 7.04 initialized.
2007-05-11 12:53:37 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2007-05-11 12:53:37 : <INIT> Created temporary working directory.
2007-05-11 12:53:37 : <INIT> Imported proxy settings from Internet Explorer.
2007-05-11 12:53:37 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2007-05-11 12:53:37 : <INIT> 	Detected DriverPack Chipset 7.05.6!
2007-05-11 12:53:37 : <INIT> 	Detected DriverPack CPU 7.04.1!
2007-05-11 12:53:37 : <INIT> 	Detected DriverPack Graphics A 7.04!
2007-05-11 12:53:37 : <INIT> 	Detected DriverPack Graphics B 7.04!
2007-05-11 12:53:37 : <INIT> 	Detected DriverPack Graphics C 7.04!
2007-05-11 12:53:37 : <INIT> 	Detected DriverPack LAN 7.0415!
2007-05-11 12:53:37 : <INIT> 	Detected DriverPack MassStorage 7.05.8!
2007-05-11 12:53:37 : <INIT> 	Detected DriverPack Sound A 7.04.2!
2007-05-11 12:53:37 : <INIT> 	Detected DriverPack Sound B 7.041nightly!
2007-05-11 12:53:37 : <INIT> 	Detected DriverPack WLAN 7.04.1!
2007-05-11 12:53:37 : <INIT> 	Detected 3rd party DriverPack(s).
2007-05-11 12:53:37 : <INIT> 	Finished scanning.
2007-05-11 12:53:37 : <INIT> Detected settings file "C:\DriverPacks 7.0.4\DPs_BASE.ini".
2007-05-11 12:53:37 : <INIT> Windows XP Professional -  SP2 detected.
2007-05-11 12:53:37 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2007-05-11 12:53:37 : <INIT> Imported settings from settings file.
2007-05-11 12:53:37 : <INIT> QuickStream Cache directory not found!
2007-05-11 12:53:37 : <GUI>  Initialized GUI.
2007-05-11 12:53:37 : <GUI>  Created a list of all available language files.
2007-05-11 12:53:37 : <GUI>  Set the last used language, English, as the GUI language.
2007-05-11 12:54:47 : <GUI>  Refreshed UpdateChecker with success.
2007-05-11 12:55:03 : <GUI>  Saved settings!
2007-05-11 12:55:03 : <GUI>  Closed GUI.
2007-05-11 12:55:03 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.
2007-05-11 12:55:08 : <PREP> Removed all attributes from \I386.
2007-05-11 12:55:09 : <PREP> Created a backup of \I386\winnt.sif.
2007-05-11 12:55:09 : <PREP> Created a backup of \I386\txtsetup.sif.
2007-05-11 12:55:09 : <PREP> Created a backup of \I386\dosnet.inf.
2007-05-11 12:55:10 : <PREP> Cleaned up \$OEM$\cmdlines.txt.
2007-05-11 12:55:10 : <SLIP> Created necessary directory structure for method 2.
2007-05-11 12:55:12 : <SLIP> Copied files necessary for method 2.
2007-05-11 12:55:12 : <SLIP> Extracted files necessary for method 2.
2007-05-11 12:55:13 : <SLIP> Created \I386\presetup.cmd file.
2007-05-11 12:55:13 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2007-05-11 12:55:13 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2007-05-11 12:55:51 : <SLIP> Copied DriverPacks to \OEM.
2007-05-11 12:55:53 : <SLIP> Updated \I386\svcpack.inf file to support KB888111 and KB921401.
2007-05-11 12:55:56 : <SLIP> Updated \I386\txtsetup.sif file to support KB888111.
2007-05-11 12:56:00 : <SLIP> Updated \I386\dosnet.inf file to support KB888111.
2007-05-11 12:56:00 : <SLIP> Updated \I386\dosnet.inf file to support KB921401.
2007-05-11 12:56:00 : <SLIP> Updated \I386\winnt.sif to support method 2.
2007-05-11 12:56:00 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2007-05-11 12:56:00 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2007-05-11 12:56:00 : <SLIP> Slipstream finished in 57 seconds.
2007-05-11 12:56:37 : <CLNP> Temporary working directory successfully deleted.
2007-05-11 12:56:37 : Program terminated.

And here is DPsFnshr.log:
http://rapidshare.com/files/32006048/DPsFnshr.log.html

And here is the image:
http://img444.imageshack.us/img444/7650/dibujoct2.th.jpg

Last edited by Major (2007-05-19 01:59:35)

Re: Found new hardware during RunOnceEx

Major - you are on the testing team, are you not?  then it seems silly for me to have to ask you for your HWID's doesnt it?

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!.

Re: Found new hardware during RunOnceEx

And why are you using DPBase 7.04 with 7.05 nightlys?
Kind of a mismatch don't you think?

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Found new hardware during RunOnceEx

I am sorry, here are the HWIDs:

=========== 
PCI devices 
=========== 
PCI\VEN_1002&DEV_4371&SUBSYS_00000000&REV_80\3&267A616A&0&A4: Puente PCI estándar de PCI a PCI
PCI\VEN_1002&DEV_4372&SUBSYS_13971043&REV_82\3&267A616A&0&A0: ATI SMBus
PCI\VEN_1002&DEV_4373&SUBSYS_13971043&REV_80\3&267A616A&0&9A: Controlador de host de PCI a USB mejorado
PCI\VEN_1002&DEV_4374&SUBSYS_13971043&REV_80\3&267A616A&0&98: Controladora de host USB OpenHCD estándar
PCI\VEN_1002&DEV_4375&SUBSYS_13971043&REV_80\3&267A616A&0&99: Controladora de host USB OpenHCD estándar
PCI\VEN_1002&DEV_4376&SUBSYS_13971043&REV_80\3&267A616A&0&A1: ATI IDE Controller
PCI\VEN_1002&DEV_4377&SUBSYS_00000000&REV_80\3&267A616A&0&A3: Puente PCI ISA estándar
PCI\VEN_1002&DEV_437B&SUBSYS_13931043&REV_01\3&267A616A&0&A2: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_1002&DEV_5A31&SUBSYS_00000000&REV_01\3&267A616A&0&00: Puente PCI de CPU host estándar
PCI\VEN_1002&DEV_5A3F&SUBSYS_00000000&REV_00\3&267A616A&0&08: Puente PCI estándar de PCI a PCI
PCI\VEN_1002&DEV_5A62&SUBSYS_13921043&REV_00\4&1CF2FBB4&0&2808: Controladora de vídeo (compatible VGA)
PCI\VEN_10EC&DEV_8139&SUBSYS_10451043&REV_10\4&B4B0D3&0&00A4: Realtek RTL8139/810x Family Fast Ethernet NIC
PCI\VEN_1180&DEV_0476&SUBSYS_13971043&REV_B3\4&B4B0D3&0&08A4: Controladora de CardBus Ricoh R/RL/5C476(II) o compatible
PCI\VEN_1180&DEV_0592&SUBSYS_13971043&REV_08\4&B4B0D3&0&0AA4: Dispositivo base del sistema
PCI\VEN_1180&DEV_0822&SUBSYS_13971043&REV_17\4&B4B0D3&0&09A4: Controladora de host SD compatible con el estándar SDA
PCI\VEN_14E4&DEV_4318&SUBSYS_120F1043&REV_02\4&B4B0D3&0&18A4: Adaptador de red Broadcom 802.11g
16 matching device(s) found.
 
=========== 
USB devices 
=========== 
USB\ROOT_HUB\4&239E3EF5&0                                   : Concentrador raíz USB
USB\ROOT_HUB\4&2D6BD385&0                                   : Concentrador raíz USB
USB\ROOT_HUB20\4&39B6CC71&0                                 : Concentrador raíz USB
USB\VID_062A&PID_0000\5&13956077&0&2                        : Dispositivo de interfaz humana USB
USB\VID_174F&PID_A311\5&31FA4345&0&5                        : USB2.0                  
5 matching device(s) found.

Thanks

Re: Found new hardware during RunOnceEx

viewing the HWID and moblity.inf, only it is supported PCI\VEN_1002&DEV_5A62&SUBSYS_13921043, so i think, in order to support the HWID posted above i have to add the line:
PCI\VEN_1002&DEV_5A62&SUBSYS_13921043&REV_00
It is that true?
Please, i am sorry for my annoying question. I am trying to understand it better.

How can i know to what hardware it refers this input?
PCI\VEN_1180&DEV_0592&SUBSYS_13971043&REV_08\4&B4B0D3&0&0AA4: Dispositivo base del sistema.

What is the input for the modem in the HWID, as i don´t see the word "modem"?

Thanks very much

Re: Found new hardware during RunOnceEx

It does seem the modem is not in the list... it may not be plug and play compatable or may depend on a device that is not installed yet.

the PCI\VEN_1002&DEV_5A62&SUBSYS_13921043 should match the PCI\VEN_1002&DEV_5A62&SUBSYS_13921043&REV_00 device.

ATI Radeon Xpress 200M is the driver that should match the card but i suspect taht this is a laptop and it has a proprietary chipset provided by the distrubuter ( toshiba or dell or whoever it is)

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!.

Re: Found new hardware during RunOnceEx

@OverFlow
Yes it is Laptop Asus. Please what do you suggest to fix that problem? thanks.
Have you seen the yellow point exclamation, I don´t know to which hardware it refers, could be the culprit?
PCI\VEN_1180&DEV_0592&SUBSYS_13971043&REV_08\4&B4B0D3&0&0AA4: Dispositivo base del sistema

P.S. I have the disc of the drivers of this Laptop, here are the characteristics of the Laptop:
Processor: Mobile Intel Celeron M440
MotherBoard: Asus A6000Rp Series Notebook
Chipset: ATI Radeon Xpress 200M
Graphic Card: ATI Radeon Xpress 200M series

Thank you very much

EDITED
The HWID is RICOH memory stick, so it is not the culprit.

Now the unique problem remained, how can i fix the .inf to match the card graphics?

New EDIT
Looking within the Driverpack Graphics A and the Driver that come in the CD, i see it misses a few sections for ATI M200, here are:

[ati2mtag_RC410M.Services]
.......
[ati2mtag_RC410M.SoftwareSettings]
......
[ati2mtag_RC410M_SoftwareDeviceSettings]
.........
[ati2mtag_RC410M.GeneralConfigData]
...................

I will add it to the driverpacks and test it, i will inform you
Thanks.

Other EDIT
I see other entries "ati2mtag_RC410", so surely is a confusion, as it does not exist any HWID "RC410". I will add "M" to that entries and i will test.

Last edited by Major (2007-05-22 13:37:45)

Re: Found new hardware during RunOnceEx

Major wrote:

Chipset: ATI Radeon Xpress 200M
Graphic Card: ATI Radeon Xpress 200M series

The ATI Radeon Xpress 200M is not supported by the Catalyst drivers in the Graphics_A pack.  This was discussed in this thread:
http://forum.driverpacks.net/viewtopic.php?id=1504

The 200M series is supported by a separate download. Here: http://ati.amd.com/support/drivers/xp/i … ed-xp.html
I suppose you could make that into a 3rd party driverpack.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Found new hardware during RunOnceEx

Please, so why are these entries in mobility.inf:
"ATI RADEON XPRESS 200M Series" = ati2mtag_RC410M, PCI\VEN_1002&DEV_5A62
"ATI RADEON XPRESS 200M (ASUS A6Rp)" = ati2mtag_RC410M, PCI\VEN_1002&DEV_5A62&SUBSYS_13921043

And this entry "ati2mtag_RC410" is referred to a HWID or is a confusion?
Thanks

Re: Found new hardware during RunOnceEx

That's a good question!
I'll take a look when I get home from work.  I know that the xpress 200m chipset is not supported by the 'official' ATI catalyst suite, it's supported by separate dl because of the integrated chipset drivers.  It's possible that the graphics-half & chipset-half are included in the graphics_a/chipset DriverPacks respectively in which case all you'd need to do is verify driver locations and edit the inf's accordingly.
That could be answered by someone from the main team or someone intimately aware of the DP's composition.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Found new hardware during RunOnceEx

Well I inform you.
I have found a mistake in the entries, there are entries "ati2mtag_RC410M" and "ati2mtag_RC410". i have changed ati2mtag_RC410 to RC410M. Then i have edited mobility.inf, i changed all the entries concerning ati2mtag_RC410M with the ones coming in the CD of drivers. After i have added 2 archives which are missed in the directory: "D\G\A\1\B_44319", the files are "atidemgr.dll, atioglx1.dll"
I have made the test, the first thing, there is no prompt of new hardware device, neverthless, it has not been installed properly. Finally i decided to install it manually, it request me the archive "ati2mtag.sys" in the directory:
"c\d\g\a\1\.\B_44319". It seems that it has not found that file or the file .sys is not the suitable, neverthless manually it has been installed correctly.
MY question:
should i change the file .sys with the one coming in the CD?
should i edit some file?
the path is correct?

Thanks very much

Re: Found new hardware during RunOnceEx

Please post in the right place next time.

http://forum.driverpacks.net/viewforum.php?id=10


Helmi bashrat ,can one of you move this one please?

Last edited by muiz (2007-05-23 16:34:39)

Re: Found new hardware during RunOnceEx

Sorry. At the first, i did not know what was the true probem. Now i know the problem is due to Ati Xpress 200M, you can move it please.
Thanks.

EDITED
Please, would anyone please help us to fix the problem of this driver, i have seen a lot of people has this problem. Thanks very much.
well, i have made the changes i have written above, and it seems it pick up the drivers in the mobility.inf, but it is not installed properly. The strange is when i wanted to install it manually, picking up update the controller using the same drivers came up in DPGA704 (i have extracted it), it tells me that it has not found any controller better. Then i uninstalled it, reinitiate the PC and has prompted for new hardware, so i indicate it the new path of the driverpack extracted before "C:\Doc.....\Desktop\DPGA704\D\G\A\1"

The first thing happened: it tells me the file "ati2matg.sys" has not been found from: "C:\d\g\a\1\.\B_44319"
Why it has saved that path in his memory, since it must copy it from "C:\Doc.....\Desktop\DPGA704\D\G\A\1\.\B_44319"

I indicated it the new path manually "C:\Doc.....\Desktop\DPGA704\D\G\A\1\B_44319" and pick up correctly, but then it tells me it is not signed, i pick continue, finally it has been installed and worked perfeclty.

So i don´t know why it has not been installed unattended, perhaps the problem is from the non driver signed?
If anyone please would like to help to fix this problem.
Thanks.

Last edited by Major (2007-05-25 00:27:08)

Re: Found new hardware during RunOnceEx

Is there anyone expert please who could help us?

Thanks very much

Re: Found new hardware during RunOnceEx

I am going to try to tackle this over the weekend. 
Just because the driver has the same filename doesn't make it the same driver (found out the hard way).

I'll try to repackage the integrated chipset catalyst suite as a test.
Maybe the main team can add an exception to the ini file as a test too.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Found new hardware during RunOnceEx

OK, here's what I found so far:
The ATI GART driver is in the Chipset DP D\C\AT\ and matches the official ATI driver exactly (your HWID are not listed)
From the GARTnt.INF:

In order to install this driver, go to device manager, right-click on the PCI-PCI
; bridge which represents your AGP bridge and select "Properties". Then select the
; "Driver" page and push the "Update Driver" button. Go through the update driver
; wizard and on the "Locate Driver Files" page select "Specify a location" and then
; enter the location of your new INF and driver.

So the ATI GART driver from the chipset DP should match your HWID here (but doesn't):
PCI\VEN_1002&DEV_5A3F&SUBSYS_00000000&REV_00\3&267A616A&0&08: Puente PCI estándar de PCI a PCI

There's also an error (possibly) in the latest nightly graphics_a DP that might be interfering with the install:
From the mobility.inf:

;--- on ASUS notebooks (zorro1) ---
"ATI MOBILITY RADEON X700 (ASUS notebooks)" = ati2mtag_M26, PCI\VEN_1002&DEV_5653&SUBSYS_11B21043
"ATI MOBILITY RADEON X700  (ASUS notebooks)" = ati2mtag_M26, PCI\VEN_1002&DEV_5652&SUBSYS_19621043{1 funny characters are here}"ATI MOBILITY RADEON X700 (ASUS A6Rp)" = ati2mtag_M26, PCI\VEN_1002&DEV_5653&SUBSYS_11221043

"ATI MOBILITY RADEON X800" = ati2mtag_M28, PCI\VEN_1002&DEV_5D4A
"ATI MOBILITY RADEON X800 XT" = ati2mtag_M28, PCI\VEN_1002&DEV_5D48 {3 funny characters are here}"ATI RADEON XPRESS 200M Series" = ati2mtag_RC410M, PCI\VEN_1002&DEV_5A62{1 funny characters are here}"ATI RADEON XPRESS 200M (ASUS A6Rp)" = ati2mtag_RC410M, PCI\VEN_1002&DEV_5A62&SUBSYS_13921043{1 funny characters are here}

Basically, anywhere you find the keystring "ati2mtag_RC410M", somewhere in that line of code you'll find these odd/funny box characters (invalid CR?).

The mobility.inf is also missing some critical entries (taken from the ASUS drivers):

[ati2mtag_RC410M.Services]
AddService = ati2mtag, 0x00000002, ati2mtag_Service_Inst, ati2mtag_EventLog_Inst
AddService = Ati HotKey Poller,, Ati2evxx_Generic_Service_Inst, Ati2evxx_EventLog_Inst

[ati2mtag_RC410M.SoftwareSettings]
AddReg = ati2mtag_SoftwareDeviceSettings
AddReg = ati2mtag_RC410M_SoftwareDeviceSettings
AddReg = ati2mtag_Mobile_SoftwareDeviceSettings
AddReg = atioglxx_OpenGLSoftwareSettings
DelReg = ati2mtag_RemoveDeviceSettings
AddReg = ati2mtag_MobileLargeDesktopSettings

[ati2mtag_RC410M_SoftwareDeviceSettings]
HKR,, DALRULE_NOTVANDLCDONCRTC,             %REG_DWORD%,    1
HKR,, WmAgpMaxIdleClk,                      %REG_DWORD%,    0x20
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run",ATIModeChange,,"Ati2mdxx.exe"
HKR,, DALR6 CRT_MaxModeInfo,                  %REG_BINARY%,00,00,00,00,40,06,00,00,B0,04,00,00,00,00,00,00,3C,00,00,00 
HKR,, SMOOTHVISION_NAME, %REG_SZ%, "SMOOTHVISION 2.1"
HKR,, DisableQuickApply3D,                %REG_DWORD%,    1
HKR,, R6GxO_UseI2cLayer, %REG_DWORD%, 1
HKR,, GI_DEF, %REG_SZ%, 0
HKR,, ASTT_DEF, %REG_SZ%, 0
HKR,, ASD_DEF, %REG_SZ%, 0
HKR,, ASTT_NA, %REG_SZ%, 1
HKR,, 3to2Pulldown_NA, %REG_SZ%, 1
HKR,, Transcode_NA, %REG_SZ%, 1
HKR,, DALNonStandardModesBCD1, %REG_BINARY%,08,00,04,80,00,00,00,60,10,24,04,80,00,00,00,60,10,24,06,00,00,00,00,60,12,80,06,00,00,00,00,60,12,80,07,68,00,00,00,60,14,00,10,50,00,00,00,60
HKR,, ATIPOLLINTERVAL,             %REG_DWORD%,    2000
HKR,, ExtEvent_EnablePolling,      %REG_DWORD%,    1
HKR,, ExtEvent_BroadcastDispChange,      %REG_DWORD%,    0
HKR,, GCORULE_DisableHotKeyIfOverlayAllocated,          %REG_DWORD%,    1
HKR,, GCORULE_DisableHotKeyIfDDExclusiveMode,          %REG_DWORD%,    1
HKR,, ExtEvent_LCDSetMaxResOnDockChg,      %REG_DWORD%,    0
HKR,, GCORULE_DisableGPIOPowerSaveMode,   %REG_DWORD%,    1
HKR,, DALRULE_NOCRTANDDFPONSAMECONTROLLER,      %REG_DWORD%,    1
HKR,, GCORULE_IntTMDSReduceBlankTiming,      %REG_DWORD%,    0
HKR,, TVDisableModes,   %REG_DWORD%,    0
HKR,, GCORULE_ENABLERMXFILTER, %REG_DWORD%,   1
HKR,, DALRULE_RESTRICT2ACTIVEDISPLAYS,      %REG_DWORD%,    0
HKR,, DALRULE_POWERPLAYOPTIONCOLORDEPTHREDUCTION,      %REG_DWORD%,    0
HKR,, R6LCD_FOLLOWLIDSTATE,   %REG_DWORD%,    0
HKR,, DisableSWInterrupt,      		   %REG_DWORD%,    1
HKR,, ExtEvent_BIOSEventByInterrupt,      %REG_DWORD%,    0
HKR,, DisableD3DExclusiveModeChange,             %REG_DWORD%,    1
HKR,, DisableOpenGLExclusiveModeChange,             %REG_DWORD%,    1
HKR,, ExtEvent_EnableChgLCDResOnHotKey,                  %REG_DWORD%,    0
HKR,, DisableDalValidateChild,        %REG_DWORD%,    0
HKR,, DALRULE_ENABLESHOWACSLIDER,                  %REG_DWORD%,    1
HKR,, DALRULE_ENABLESHOWDCLOWSLIDER,                  %REG_DWORD%,    1
HKR,, R6LCD_RETURNALLBIOSMODES,              %REG_DWORD%,    1
HKR,, GCORULE_PPForceBlankDisplays,             %REG_DWORD%, 1
HKR,, ExtEvent_OverDriveSupport,      %REG_DWORD%,    1
HKR,, DisableAGPSizeOverride,      %REG_DWORD%,    1
HKR,, Main3D_DEF, %REG_SZ%, 3
HKR,, AntiAlias_DEF, %REG_SZ%, 1
HKR,, AntiAliasSamples_DEF, %REG_SZ%, 0
HKR,, AnisoType_DEF, %REG_SZ%, 0
HKR,, AnisoDegree_DEF, %REG_SZ%, 0
HKR,, TextureOpt_DEF, %REG_SZ%, 0
HKR,, TextureLod_DEF, %REG_SZ%, 0
HKR,, TruformMode_DEF, %REG_SZ%, 0
HKR,, VSyncControl_DEF, %REG_SZ%, 1
HKR,, SwapEffect_DEF, %REG_SZ%, 0
HKR,, TemporalAAMultiplier_DEF, %REG_SZ%, 0
HKR,, ExportCompressedTex_DEF, %REG_SZ%, 1
HKR,, PixelCenter_DEF, %REG_SZ%, 0
HKR,, ForceZBufferDepth_DEF, %REG_SZ%, 0
HKR,, EnableTripleBuffering_DEF, %REG_SZ%, 0
HKR,, ColourDesktopGamma_DEF, %REG_SZ%, "1.0 1.0 1.0"
HKR,, ColourDesktopBrightness_DEF, %REG_SZ%, "0 0 0"
HKR,, ColourDesktopContrast_DEF, %REG_SZ%, "1.0 1.0 1.0"
HKR,, ColourFullscreenGamma_DEF, %REG_SZ%, "1.0 1.0 1.0"
HKR,, ColourFullscreenBrightness_DEF, %REG_SZ%, "0 0 0"
HKR,, ColourFullscreenContrast_DEF, %REG_SZ%, "1.0 1.0 1.0"
HKR,, 3D_Refresh_Rate_Override_DEF, %REG_DWORD%, 0
HKR,, Display_Detection_DEF, %REG_DWORD%, 0
HKR,, Panning_Mode_DEF, %REG_DWORD%, 0
HKR,, Mouse_Track_Orientation_DEF, %REG_DWORD%, 1
HKR,, Force_TV_Detection_DEF, %REG_DWORD%, 0
HKR,, CatalystAI_DEF, %REG_SZ%, 1

[ati2mtag_RC410M.GeneralConfigData]
MaximumDeviceMemoryConfiguration=256

I'll report back if I find anything else.  So far you have two problems:
1) Chipset DP missing your HWID (GARTnt.INF).
2) Badly formated mobility.inf in Graphics_A DP

I'm checking the MassStorage DP now for the IDE controllers.
*Edit
MassStorage DP is good.  Your HWID is listed.

Last edited by mr_smartepants (2007-05-25 05:45:35)

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Found new hardware during RunOnceEx

Try replacing your GARTnt.INF file contents with this code and repack (added HWID and string):

;
; Copyright (c) 2000-2004 ATI Technologies Corporation
;
; GartNt.INF  -- This file contains descriptions of all the AGP Miniports
;             supported in Windows NT
;
; In order to install this driver, go to device manager, right-click on the PCI-PCI
; bridge which represents your AGP bridge and select "Properties". Then select the
; "Driver" page and push the "Update Driver" button. Go through the update driver
; wizard and on the "Locate Driver Files" page select "Specify a location" and then
; enter the location of your new INF and driver.
;

[Version]
Signature="$WINDOWS NT$"
Class=System
ClassGuid={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%ATI%
DriverVer=04/15/2005,5.0.2196.1015
CatalogFile = atisgkaf.cat

; =================== Common for all AGP devices =========================
[DestinationDirs]
DefaultDestDir = 12        ; DIRID_DRIVERS

[Manufacturer]
%ATI_MFG%=ATI_AGP

[SourceDisksNames.x86]
1 = %DiskId%,,,""

[SourceDisksFiles]
atisgkaf.SYS=1

[ControlFlags]
ExcludeFromSelect=*

[AGP_Filter_Reg]
HKR,,"UpperFilters", 0x00010000,"CABOAGP"
HKLM,"SYSTEM\CurrentControlSet\Services\caboagp","FW_SafeVideoCards",0x00030001,10,02

[pci_ServiceInstallSection]
DisplayName    = %pci_svcdesc%
ServiceType    = %SERVICE_KERNEL_DRIVER%
StartType      = %SERVICE_BOOT_START%
ErrorControl   = %SERVICE_ERROR_NORMAL%
ServiceBinary  = %12%\pci.sys
LoadOrderGroup = "Boot Bus Extender"

; =================== ATI Chipset ========================
[ATI_AGP]
%PCI\VEN_1002&DEV_4371.DeviceDesc%=CABO_Install,PCI\VEN_1002&DEV_4371
%PCI\VEN_1002&DEV_7010.DeviceDesc%=CABO_Install,PCI\VEN_1002&DEV_7010
%PCI\VEN_1002&DEV_5838.DeviceDesc%=CABO_Install,PCI\VEN_1002&DEV_5838
%PCI\VEN_1002&DEV_7838.DeviceDesc%=CABO_Install,PCI\VEN_1002&DEV_7838

[CABO_Install]
CopyFiles=@atisgkaf.SYS

[CABO_Install.HW]
AddReg = AGP_Filter_Reg

[CABO_Install.Services]
AddService = caboagp,0,caboagp_ServiceInstallSection
AddService = pci, %SPSVCINST_ASSOCSERVICE%, pci_ServiceInstallSection

[caboagp_ServiceInstallSection]
DisplayName    = %caboagp_svcdesc%
ServiceType    = %SERVICE_KERNEL_DRIVER%
StartType      = %SERVICE_DEMAND_START%
ErrorControl   = %SERVICE_ERROR_NORMAL%
ServiceBinary  = %12%\atisgkaf.sys
LoadOrderGroup = PnP Filter


; =================== STRINGS and CONSTANTS ========================

[Strings]
ATI_MFG = "ATI"
ATI = "ATI"
PCI\VEN_1002&DEV_4371.DeviceDesc = "ATI RADEON XPRESS 200M PCI to AGP Bridge"
PCI\VEN_1002&DEV_7010.DeviceDesc = "ATI RADEON IGP 340/340M/MOBILITY RADEON 7000 IGP AGP"
PCI\VEN_1002&DEV_5838.DeviceDesc = "ATI RADEON 9000/9100 IGP AGP"
PCI\VEN_1002&DEV_7838.DeviceDesc = "ATI RADEON 9000/9100 PRO IGP AGP"
DiskId       = "ATI Technologies Inc. Installation DISK (AGP)"

;service descriptions
caboagp_svcdesc = "ATI Cabo AGP Filter"
pci_svcdesc = "PCI Bus Driver"


;*******************************************
;Handy macro substitutions (non-localizable)
SPSVCINST_ASSOCSERVICE = 0x00000002
SERVICE_KERNEL_DRIVER  = 1
SERVICE_BOOT_START     = 0
SERVICE_DEMAND_START   = 3
SERVICE_ERROR_NORMAL   = 1
Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Found new hardware during RunOnceEx

@mr_smartepants, Thank you very much for your reply

The mobility.inf is also missing some critical entries (taken from the ASUS drivers):

I have already added those missing entries.

Try replacing your GARTnt.INF file contents with this code and repack (added HWID and string):

Replaced and repacked. I will make a test and i will report back.

Thanks very much again for your help.

First EDIT
Tested without success, it has not been installed properly. I have forgotten to mention before, that also i have added 2 files which are missing from the directory B_44319. The 2 files are "atidemgr.dll, atioglx1.dll"
I think that prehaps could be a problem of conflict with another HWID or the problem of Non signed drivers.
I am going to do another test with another idea i have to see if that works, and i will inform you later.
Best Regards.

Last edited by Major (2007-05-25 20:02:30)

Re: Found new hardware during RunOnceEx

@mr_smartepants
I think i have found the culprit, is the catalog file .cat. I have made 2 tests:
First test: with the drivers from asus removing mobiliy.inf, i means i have used (CX_31831.inf, CX_31831.cat, \B_31521)
It has been installed perfectly
Second test: with the drivers from asus but without CX_31831.cat i means (CX_31831.inf, \B_31521)
it has not been installed properly, so it is clear the cluprit is the catalog file.

Well, as it can be installed manually perfeclty from the fixed moblility.inf and the directory B_44319, so if we can avoid the catalog file, i think it can be installed perfectly. What do you suggest please?

Re: Found new hardware during RunOnceEx

From what I understand, if you remove the .CAT file, you also need to remove any references to that .CAT file from any .INF files.  All this breaks is "driver signing" (which is disabled by DP Base anyway).

If you don't modify any HWIDs in the INF files then the .CAT file can stay.  The .CAT file is the "driver signed" checksum for the package and will give errors if any of the included files don't match the checksum (INF, SYS, DLL).  The mobility.inf file doesn't have a .CAT file associated with it.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Found new hardware during RunOnceEx

hi
many drivers have a (note, "a") reference to a CAT file which is not there but no reference to it in "sourcediskfiles".

gor instance, in mass storage, AU-1
a reference to catalog and then this
[SourceDisksFiles]
aliide.sys =1;
(here there is no reference)

When it is listed as a sourcefile to be copied, a log will show you if that this file was missing.
(I've seen logs like these, and it is not a critical error.)

The answer was 42?
Kind regards, Jaak.

Re: Found new hardware during RunOnceEx

Ok, I think that the prompt of the drivers signed has broken the unattended install, so it has not been disabled by the DSPdsblr.exe. Because i could install the drivers manually from the mobility.inf fixed and the directory  B_44319 but it has prompted the confirmation of the drivers signed and i have picked continue, then it has been installed correctly.