biatche

unattended ATI catalyst

21 posts in this topic

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 by johnhc
0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

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 by johnhc
0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

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

Edited by ricktendo64
0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

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

atisig.png

Edited by ricktendo64
0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

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 by ricktendo64
0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

I have never had a problem with aero on 1st boot with integrated drivers, even with my Geforce Go 7300

0

Share this post


Link to post
Share on other sites

Not the same for cards made after win7 was released. example nvidia GT2xx. generic drivers are used.

0

Share this post


Link to post
Share on other sites

I know it's an old thread!

However, I was fighting with an old "ATI graphic card X300 series" and I use this method to resolve the silent installation on Windows 7 OS:

- 1 - First: integrate drivers "ATI Catalyst Display Driver 9.3" inside install.wim image mounted

"C:\Program Files\Windows AIK\Tools\x86\Servicing\Dism.exe" /Image:"C:\work" /Add-Driver /driver:"C:\Drivers" /ForceUnsigned /recurse

http://support.amd.com/us/gpudownload/windows/Legacy/Pages/radeonaiw_vista32.aspx?type=2.4.1&product=2.4.1.3.13〈=English

Any customers using a combination of a ATI Radeon™ HD 2000 Series, ATI Radeon™ HD 3000 Series, or ATI Radeon™ HD 4000 Series product with any of the legacy products listed above in a single PC system must use the ATI Catalyst 9.3 or earlier driver. All future ATI Catalyst™ releases made available past the ATI Catalyst™ 9.3 release will not include support for the legacy products listed above or any of the features associated with those legacy products.

2 - Installed "9-11_legacy_vista32-64_dd_ccc.exe" om my computer

3 - Created an SFX file using (to install silently ATI 9-11):

config.txt


;!@Install@!UTF-8!
GUIMode="2"
RunProgram="hidcon:cmd /c xcopy \"%%T\\*.*\" %SYSTEMDRIVE%\\ATI\\Support\\9-11_legacy_vista32-64_dd_ccc\\ /s /e /i /y"
RunProgram="hidcon:cmd /c Path.cmd"
RunProgram="%SYSTEMDRIVE%\\ATI\\Support\\9-11_legacy_vista32-64_dd_ccc\\Setup.exe -INSTALL"
;!@InstallEnd@!

4 - Create a batch file

Path.cmd


@echo off
cmd /c mkdir "%SystemDrive%\Program Files\ATI Technologies"
exit

5 - Using all the files inside: C:\ATI\Support\9-11_legacy_vista32-64_dd_ccc\ and create an 7z archive

6 - Create an ATI-9-11.exe file

Silent installation for ATI 9-11 doesn't work on Oracle VirtualBox, but works really fine on my Computer!

Remember: Old timers have a saying:" The newest driver is NOT always the best."

Driverpacks Tutorial

I hope that can help! :rolleyes:

Regards

Edited by myselfidem
0

Share this post


Link to post
Share on other sites

Remember: Old timers have a saying:" The newest driver is NOT always the best."

Yes, I guess I am an old timer now. After I installed Diablo III, it says "oh hey there is a new driver available for your video card" and I say "NO!" :lol:

I did a (well peimg) integration of a Radeon driver on a Vista image by installing the software on a system, and then use the old Driver Magician to get the driver file to inject into the wim.

0

Share this post


Link to post
Share on other sites

Yes, I guess I am an old timer now. After I installed Diablo III, it says "oh hey there is a new driver available for your video card" and I say "NO!" :lol:

I did a (well peimg) integration of a Radeon driver on a Vista image by installing the software on a system, and then use the old Driver Magician to get the driver file to inject into the wim.

:rolleyes: Oh, yes! Well done.

Regards

0

Share this post


Link to post
Share on other sites

I made a new test and this config.txt works fine also.

Adapt the ATI version to your needs!

Note: We need to create the folder: "C:\Program Files\ATI Technologies", if we want an successful silent installation:

config.txt (for ATI Radeon X300 series 9-11)


;!@Install@!UTF-8!
;// Full silent no GUI
GUIMode="2"
;// Set environments
SetEnvironment="Var1=C:\\ATI\\Support\\9-11_legacy_vista32-64_dd_ccc\\"
SetEnvironment="Var2=\"%ProgramFiles%\\ATI Technologies\""
RunProgram="hidcon:cmd /c xcopy \"%%T\" \"%Var1%\" /s /e /i /y"
RunProgram="hidcon:cmd /c \"%Var1%\\Setup.exe\" -INSTALL"
;!@InstallEnd@!

Cheers

*Edit: We can see all switches after extraction, using: (example)

C:\ATI\Support\9-11_legacy_vista32-64_dd_ccc\Setup.exe /? (or /help)

Silent switches


-INSTALL[-Use /package path] - This will install packages in silent mode.
-Use /package path is optional.
E.g.
1)-INSTALL:will install the whole packages in silent mode.
2)-INSTALL -Use c:\packages\Drivers\:will install the defined packages in silent mode
-UNINSTALL- This will uninstall all packages in silent mode.

/FORCE_FIRST_RUN- forces the first run wizard each time(good if you're debugging or showing a demo of the initialization wizard and need it to appear on every run).

/FORCE_HIDE_FIRST_RUN- forces the first run wizard to hide even if it is the first run.

/INSTALL- run in install mode (this is what a CD autorun could use to run Monet)

/UPDATE- run in uninstall mode (this is what a toolbar or tooltray could use to launch Monet UI)

/UNINSTALL- run in uninstall mode (this is what a toolbar or tooltray could use to launch Monet UI)

/PACKAGE_SELECTION_LISTBOX- a listbox is shown for package selection, instead of toggling throughicons (this is more useful in debugging because in the past I have sometimes encountered multiple installed versions of the same package).

/VERBOSE_TRACE- This is absolutely necessary to always be in command line if you want tohave "/TRACE_RM" and "/FORCE_CORECOM_TRACE". The intention of this option was that we should always trace a minimum on an end system due to performance issues.... if you're at all interested in tracing UI or UI<-->Core commmunication, then make sure this is always in the command line

/FORCE_CORECOM_TRACE:<path> - Traces all communication between core and UI use this with a target file e.g. with <path> equal to "C:\my_directory\core_ui_log.txt"

/TRACE_RM- Trace all messages relevent to risk mitigation.

/DISPLAY_FULL_VERSION- Display the full version and timestamp

/PASS_TO_CORE- Will pass any command line in quotes into the core for processing. Example usage /PASS_TO_CORE:"-a -b -c -d -e -f -g" will pass the command line:"-a -b -c -d -e -f -g" to the core. (Note: if you need to pass " character, then use a ' and it willbe converted to " before being passed to the core.

/UNATTENDED_INSTALL<:><files/path><;><file/path> - This puts InstallManagerApp into unattended install mode by using the comma-separated list of files/paths.
E.g.
1)/UNATTENDED_INSTALL:"c:\direc1;c:\direc2\filea.msi;c:\direc3"
2)/UNATTENDED_INSTALL:"c:\drivers"
3)/UNATTENDED_INSTALL:"c:\drivers\graphics_driver.msi"

/UNATTENDED_UNINSTALL- This will uninstall all packages in unattended mode.

/AUTOACCEPT_ALL- This will autoaccept all legal agreements (for internal use only). If you don't use this command line, you'll have to stick around, read and accept/deny EULA's. This option won't be published.

/ON_REBOOT_MESSAGE:<value> - This takes the answer in advance from the user asto whether s/he needs to reboot once complete. Valid <values> are "YES" or "NO".

/FORCE_REBOOT- On completion of an install/update/uninstall, force a reboot request to OS.Note that the reboot request will only be issued after the application is closed.

/FORCE_CLOSE_WHEN_DONE- This will automatically close the last wizard page on completion.

/OEM:<value>- Change the OEM look and feel. Valid <values> must have an entry in the OEM folder the the same folder name

/NO_CUSTOM_UI:<value>- Ignore UI color setting changes from configuration files.

/HELP- Display this message and exit.

Cheers

Edited by myselfidem
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.