Jump to content

msi and runonceex dont play together?


M4M

Recommended Posts

ok, here is my lil problem. I am currently tring to install the ati drivers (latest) and I can get them to install for the most part..... except for the msi ones :realmad: the log files prove that the other exe ones install fine, just not the msi. Here is a snippit of the code.....

REG ADD %KEY%\015 /VE /D "ATI Graphics Driver v4.9" /f

REG ADD %KEY%\015 /V 1 /D "%CDROM%\Install\gfx\ACE\Install_Flash_Player_7.msi /qn /norestart" /f

REG ADD %KEY%\015 /V 2 /D "%CDROM%\Install\gfx\driver\setup.exe -s -f2\"%systemdrive%\logs\atidriver.log\"" /f

REG ADD %KEY%\015 /V 3 /D "%CDROM%\Install\gfx\cpanel\setup.exe -s -f2\"%systemdrive%\logs\aticpanel.log\"" /f

REG ADD %KEY%\015 /V 4 /D "%CDROM%\Install\gfx\ACE\ATI_Catalyst_Control_Center.msi /qn /norestart" /f

REG ADD %KEY%\015 /V 5 /D "%CDROM%\Install\gfx\wdm\setup.exe -s -f2\"%systemdrive%\logs\atiwdm.log\"" /f

The flash player (needed for the control center) and the control center itself wont install, but the driver, control panel and wdm drivers install fine. I ran the msi_file.msi /? to get the command switches, so I know that they are correct (I think anyway....), but they still wont install. is this because of tring to install them from the runonceex.cmd? if so how do I get around it?

Link to comment
Share on other sites


really? here is a command line switch that I pulled from msiexec....

-----------------------------------------------------------------------------------

Windows ® Installer. V 3.00.3790.2180

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent JPEG Group.

-----------------------------------------------------------------------------------

But, anyhow, ty for the tip and will try it, ty!

Link to comment
Share on other sites

errrr, now instaid of doing nothing, it throws an error at me that msiexec.exe can not be found. did I add it in correctly?

REG ADD %KEY%\015 /V 1 /D "%CDROM%\Install\gfx\ACE\msiexec.exe /i Install_Flash_Player_7.msi /qn" /f

Link to comment
Share on other sites

Ive been trying to find a workaround for this prob with several of my appz that worked with sp1 unattended but now having integrated sp2 they dont seem to run and give this error on install

windows installer could not be accessed. This could occur if you are running windows in safe mode, or if the windows installer is not corrctly installed.

Anyone any ideas re this

Link to comment
Share on other sites

well, the way that I have it now it works with one problem. the flash player does install (I looked into the add/remove programs) but the control center still does not install. if you are wondering, here is how I changed the line so it now does work for the flash player anyway...

REG ADD %KEY%\015 /V 1 /D "%CDROM%\Install\gfx\ACE\Install_Flash_Playe_7.msi /qn" /f

But, if that works, then the control center should install also, but it doesnt. could it be because of the order that I am tring to install them? Right now I am tring to install the control panel before the control center. maybe I need to install the center before the panel?

P.S., just as a reminder, I am tring to install these from the cd in the runonceex.cmd command.

Link to comment
Share on other sites

SUCCESS!!! I found the problem!

I tried installing the msi right from windows (no scripts, command prompts, ect, just double-clicked on the msi file) and when I did that msiexec reported an error that issetup.msi was missing and the install will be aborted. well, their is no issetup.msi file within the driver package so I tried installing it from the exe that was in the same folder as the two msi files (flashplayer.msi and controlcenter.msi) and it installed with no problems.

So, in short, if there is an exe file with the msi file(s), save yourself some headaches and just use the exe and not the seperate msi files! Now, to make an iss file so I can silently install it...

Ty all for the help and effort!

EDIT:

well, it doesnt use an iss file for unattend, but rather it uses the setup.exe /s /v"/qn REBOOT=Suppress" command for an unattended install, so your final command should look like this....

REG ADD %KEY%\015 /V 3 /D "%CDROM%\Install\gfx\ACE\setup.exe /s /v"/qn REBOOT=Suppress"" /f

So, it is possable to completely install the ati drivers completely unattended now. I hope this helps others in installing the ati gfx drivers!

Link to comment
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.
×
×
  • Create New...