unattended ATI catalyst

[biatche]

for 10.02 and above

what are the switches, anybody know?

[johnhc]

for 10.02 and above

what are the switches, anybody know?

biatche, I use this for CCC, after extracting the CCC only DL (run DLed .exe, then cancel after extraction and copy files from the ATI folder). The driver I inject using DISM in W7 and nLite in XP.

SetUp.exe -INSTALL

Enjoy, John.

Edited December 27, 2010 by johnhc

[biatche]

CCC only DL? DLed.exe ? I don't understand you here but I have these already ready:

Bin
Bin64
Config
Images
Packages
mfc80u.dll
Microsoft.VC80.ATL.manifest
Microsoft.VC80.CRT.manifest
Microsoft.VC80.MFC.manifest
Microsoft.VC80.MFCLOC.manifest
Microsoft.VC80.OpenMP.manifest
msvcp80.dll
msvcr80.dll
Setup.exe
Setup.exe.manifest

So wait, you have setup.exe -INSTALL but you inject drivers as well?

Is what you're doing == inject drivers with dism and then unattended setup.exe -install to install catalyst software?

What happens if you don't inject drivers? Will setup.exe -install install both catalyst AND drivers?

btw, heard of:

/UNATTENDED_INSTALL /FORCE_HIDE_FIRST_RUN /FORCE_CLOSE_WHEN_DONE /AUTOACCEPT_ALL /ON_REBOOT_MESSAGE:NO"

I'm currently using this, despite reading negative feedback on it. Am not sure about the consequences. Care to comment?

Thanks

[johnhc]

biatche, on the AMD site you can DL (Down Load) the complete Catalyst, the Driver only or CCC (Catalyst Control Center) only. DLed.exe is DLed .exe (blank after DLed), DLed (Downloaded) .exe file (CCC, Driver or all). I cannot answer some of your questions because I have not tried them. I am telling you what I use that works for me. I inject the drivers (DISM or nLite) so that my monitor has a current driver as soon as Windows is installed. I assume if you try to install CCC and there is no Catalyst driver, the install will fail. I do not know, however, what ,if any, Catalyst driver is included in the Windows (version?) for installation. Your list of files/folders looks like my extracted CCC, but I cannot know that is so. You might try the -INSTALL switch on the Setup.exe and see if it works.

Is what you're doing == inject drivers with dism and then unattended setup.exe -install to install catalyst software?

YES.

I have not seen the switches you are using, so I cannot comment. Enjoy, John.

Edited December 28, 2010 by johnhc

[biatche]

-install works fine so far. thanks.

mind giving me details on how you integrate the drivers? i've integrated mine, but for some funny reason, it's still using ms default. my other drivers work though.

[ricktendo]

Yes, has happened with me too, they dont like to be integrated

[johnhc]

biatche and ricktendo64, the drivers are a problem in DISM, but I have been able to accomplish it. AMD has chosen a compression that DISM does not like. In the driver is a folder named B109234 (10-12) or something like Bxxxxxxxx. It contains 54 files (10-4) most of which are compressed into xxx.yy_. If these are extracted with the Expand command the file name remains xxx.yy_. DISM errors out on missing files. I used 7-Zip (need the latest version, 9-20) and it works fine. Just replacing the the compressed with the 7-Zip extracted files allows DISM to run and the driver to install fine. I am currently using 10-4 but will install 10-12 soon as I had a mouse pointer problem that my be a driver problem. For this run I re-compressed the files using MakeCab but have not tried DISM on them yet. Hope this helps. Enjoy, John.

[ricktendo]

Thanks for the tip, will try (I usually just grab the driver from driverstore)

Edited December 29, 2010 by ricktendo64

[biatche]

I think I did everything you've mentioned, but help me double check this:

This is a crappy script I use to extract everything one shot and have the files i need in output dir

@echo off

set zip="%ProgramW6432%\7-Zip\7z.exe"
rem --------------------------------------------------------------------------------

echo.
echo === Cleaning up directories
rd /s /q "%~dp0tmp\" >%~dp0update.log
mkdir "%~dp0tmp\" >>%~dp0update.log

rd /s /q "%~dp0output\" >>%~dp0update.log
mkdir "%~dp0output\" >>%~dp0update.log

rem --------------------------------------------------------------------------------

echo.
echo === Extracting setup file
for %%f in ("%~dp0setup\*_legacy_vista32-64_dd_ccc.exe") do (
	%zip% x -y -r -o"%~dp0tmp" "%%f" >%~dp0update.log >>%~dp0update.log
)

rem --------------------------------------------------------------------------------

echo.
echo === Listing files in main directory:
dir /b /ogne "%~dp0tmp\$_OUTDIR\Packages\Drivers\Display\LH6A_INF\"

xcopy /q /y "%~dp0tmp\$_OUTDIR\Packages\Drivers\Display\LH6A_INF\*.inf" "%~dp0output" >>%~dp0update.log
xcopy /q /y "%~dp0tmp\$_OUTDIR\Packages\Drivers\Display\LH6A_INF\*.cat" "%~dp0output" >>%~dp0update.log

rem --------------------------------------------------------------------------------

for /f "tokens=*" %%f in ('dir /b /ad "%~dp0tmp\$_OUTDIR\Packages\Drivers\Display\LH6A_INF\"') do (
	echo.
	echo === Extracting files from %%f
	mkdir "%~dp0output\%%f" >>%~dp0update.log
	%zip% x -y -r -o"%~dp0output\%%f" "%~dp0tmp\$_OUTDIR\Packages\Drivers\Display\LH6A_INF\%%f\*.*_" >>%~dp0update.log
	del /q "%~dp0tmp\$_OUTDIR\Packages\Drivers\Display\LH6A_INF\%%f\*.*_" >>%~dp0update.log
	xcopy /q /y "%~dp0tmp\$_OUTDIR\Packages\Drivers\Display\LH6A_INF\%%f\*" "%~dp0output\%%f\" >>%~dp0update.log
)

echo.
echo === Cleaning up directories
rd /s /q "%~dp0tmp\" >>%~dp0update.log
mkdir "%~dp0tmp\" >>%~dp0update.log

pause

and my output:

 Volume in drive W is workhome
 Volume Serial Number is 8CA3-D0EB

 Directory of W:\win7\drivers.pre\install\graphics_atilegacy\output

2010-12-28  10:32 PM    <DIR>          .
2010-12-28  10:32 PM    <DIR>          ..
2010-12-28  10:32 PM    <DIR>          B_95503
2010-02-19  06:31 AM            76,482 CH_95951.cat
2010-02-19  06:31 AM           186,699 CH_95951.inf
               2 File(s)        263,181 bytes

 Directory of W:\win7\drivers.pre\install\graphics_atilegacy\output\B_95503

2010-12-28  10:32 PM    <DIR>          .
2010-12-28  10:32 PM    <DIR>          ..
2010-02-11  12:49 PM            51,712 amdpcom32.dll
2010-02-11  12:49 PM            52,224 amdpcom64.dll
2010-02-11  01:29 PM            43,520 ati2edxx.dll
2010-02-11  12:34 PM            53,248 ati2erec.dll
2010-02-11  01:29 PM           325,632 ati2evxx.dll
2010-02-11  01:29 PM           952,320 ati2evxx.exe
2010-02-11  12:48 PM           168,448 atiadlxx.dll
2010-02-11  12:48 PM           135,168 atiadlxy.dll
2008-10-22  01:51 AM           118,784 atibrtmon.exe
2010-02-11  12:43 PM            53,248 aticalcl.dll
2010-02-11  12:43 PM            42,496 aticalcl64.dll
2010-02-11  12:42 PM         3,235,840 aticaldd.dll
2010-02-11  12:43 PM         4,197,888 aticaldd64.dll
2010-02-11  12:43 PM            53,248 aticalrt.dll
2010-02-11  12:43 PM            50,688 aticalrt64.dll
2010-02-11  01:32 PM           442,368 atidemgx.dll
2010-02-11  01:21 PM         2,396,160 atidxx32.dll
2010-02-11  01:29 PM            59,392 atiedu64.dll
2009-04-24  06:29 AM           189,051 atiicdxx.dat
2010-02-11  03:42 PM         5,352,960 atikmdag.sys
2010-02-11  01:30 PM            12,800 atimuixx.dll
2010-02-11  01:19 PM        15,983,104 atio6axx.dll
2009-04-17  12:19 AM            15,577 atiogl.xml
2010-02-11  12:58 PM        11,513,856 atioglxx.dll
2010-02-11  01:30 PM           416,768 atipdl64.dll
2010-02-11  01:30 PM           348,160 atipdlxx.dll
2010-02-11  01:30 PM           120,320 atitmm64.dll
2010-02-11  01:12 PM         5,205,504 atiumd64.dll
2010-02-11  01:03 PM           152,496 atiumd6a.cap
2010-02-11  01:05 PM         5,025,792 atiumd6a.dll
2010-02-11  01:17 PM         3,839,488 atiumdag.dll
2010-02-11  01:00 PM           152,496 atiumdva.cap
2010-02-11  01:00 PM         4,946,432 atiumdva.dll
2010-02-11  01:30 PM           274,432 oemdspif.dll
              34 File(s)     65,981,620 bytes

     Total Files Listed:
              36 File(s)     66,244,801 bytes
               5 Dir(s)   5,579,350,016 bytes free

dism:

Installing 43 of 49 - W:\win7\drivers.pre\install\graphics_atilegacy\output\CH_95951.inf: The driver package was successfully installed.

[ricktendo]

I grab the driver/extracted files from DriverStore so I'm pretty sure they are extracted correctly...I dont think the decompressed files was my problem

Also if the files are not correctly extracted then the driver would be seen as not digitally signed and would warn you (I think)

Edit: I saw in the other post your driver is the 10.2 legacy...try using the /forceunsigned switch because its digitally signed but only by ATI (I think with /forceunsigned you have to specify the INF name)

dism /image:<MountPath> /add-driver /driver:<Path>\<InfName>.inf /forceunsigned

Edited December 29, 2010 by ricktendo64

[johnhc]

biatche, I need to admit that I am just a hacker when it comes to scripts. It looks fine to me but your real test will come when you install on HW. I am skeptical of the $_OUTDIR created when I use 7-Zip to extract the DLed drivers, so I use the technique of canceling an install (on my VM) after extraction and capturing the files. The fact that DISM accepted the driver is a great indication.

ricktendo64, I do not use /forceunsigned and have no problem and don't think biatche should need it. Here's a link to the original solving of this problem.

Enjoy, John.

[ricktendo]

Yea I figured, /forceunsigned is only needed if dism gives error, this driver is signed so it will not error (even if its only signed by ATI) its was worth a try

Edited December 29, 2010 by ricktendo64

[biatche]

Will need to do more testing, but as for now, the ATI driver is integrated but isn't used.. and I need 10.02 because latter versions don't support old cards.

setup.exe -install works for now and I shouldn't really care. What I don't like to see is Aero not being utilized. This happens with my new nvidia cards often.. since I use purchase nvidia cards way more than ati.

btw, i have been using forceunsigned, which still integrates signed drivers as well as unsigned this time.

[johnhc]

Will need to do more testing, but as for now, the ATI driver is integrated but isn't used.. and I need 10.02 because latter versions don't support old cards.

setup.exe -install works for now and I shouldn't really care. What I don't like to see is Aero not being utilized. This happens with my new nvidia cards often.. since I use purchase nvidia cards way more than ati.

btw, i have been using forceunsigned, which still integrates signed drivers as well as unsigned this time.

biatche, are you saying that the integrated driver is not being used after you install your W7? Perhaps Windows is assuming that the one present in Windows Setup is more up to date than the 10-2 (I assumed you had a legacy card). Perhaps you can find the drivers already in the image and remove them. There is a DISM command for this, thus:

Dism /Image:E:\Mount /Get-Drivers
DISM /Remove-Driver /Image:E:\Mount /Driver:oem9.inf

Also, Windows will not allow Aero to run unless your WEI (Windows Experience Index) is above a certain level. I don't remember the minimum index value, so do some searching. To see your index value, go to Properties on Computer and click on Windows Experience Index. I think you may be able to fake your WEI by going into F:\Windows\Performance\WinSAT\DataStore and changing the values in the .xml files. Enjoy, John.

[biatche]

Precisely. The ATI drivers that I integrated are not being used but rather the ones Microsoft gave. Good idea though, I might considering tampering WinSAT scores. That's my only beef with integrating drivers. I hate not having Aero although Aero is definitely capable in my system and then needing to change the theme after everything's done. Will test this out.

Good feedback. Much obliged.