M4M

lol, yea, you are right gfincher, I didnt notice this until after I posted this when I was playing around with it a bit. But, I guess for those that love using dos this does work, but for an eaiser way do as what gfincher said.

OK. We all want our formats/re-installs to be easer, and we all know that MS releases hotfixes on a regular bases (well, almost regular). Here is the method I use to download the hotfixes that I know that my PC needs. 1: First, find out what hotfixes are installed on your PC. To do this open up your control panel and then open up the add/remove progams list. Normally, on a SP2 machine, it wont show you the hotfixes. To make it show you the hotfixes, put a check-mark in the box at the top of the screen that says "Show Updates". Now if you scroll down your list and you will see your installed hotfixes. The hotfixes will have a name like "Windows XP Hotfix - KB891781" or something along that line. What we are looking for is the "KB891781" number at the end of the line. 2: Now we know what hotfixes we need to download. Here is a command script I wrote to make going to the M$ website easer to download the hotfixes. Just copy and paste the following code into notepad..... "C:\Program Files\Internet Explorer\iexplore.exe" http://support.microsoft.com/?kbid=%1 When you have that code in notepad, save it as hotfix.cmd. be sure it saves with the extention of *.cmd or else it wont work. 3: Now that we have that cmd file made, browsing the M$ site is real easy. open up a command prompt and browse it to where you have hotfix.cmd file. to get the update, using the sample hotfix listed in step 2, type "hotfix.cmd 891781" (without the quotes). BE SURE NOT TO INCLUDE THE KB LETTERS OR ELSE IT WONT WORK!!! Now when you hit enter, it will take you to the website of that hotfix and you can read up on it and download it if you wish. I hope that this helps those on the quest on downloading hotfixes!

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!

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.

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

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!

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

you could try this.... take the driver (inf, cab, exe, whatever) and open it in wordpad, notepad, any text editor, and once it fully opens (lol, trust me, it could take a while), then just close it. it *MAY* trigger windows into changeing its modified date, and that is what windows *MIGHT* go off of when it looks for drivers. Please keep in mind, I am no expert, nor have I tried this myself, its just an idea I had.

Well, I tried playin with the registry, tried command options, and the "normal" unattend method still hangs at file types waiting for imput from user. The only workaround I found for this is to use InstallRite. InstallRite was the only one I found that will make an unattended install of NeroVision and not throw you an error when tring to compile the exe like what wininstall LE does. How to do it.... Install InstallRite and let it load. Use the wizard, making sure to change the default options so it only watches the "C:\" drive and all of the registry. Once that is done follow trough the wizard. When it asks to launch the app, launch it from within InstallRite and go through the normal install process. When done installing InstallRite will pop back up. Click on the next button to get the after snapshot. When done click on create installer and it will automaticly compile the changes into a single exe file, when done it will give you the options if you want it to run as unattened, reboot required, reboot only if needed, or no reboot allowed. Go with the "unattended" and "no reboot allowed" and also check the "only overwrite older files". click on done and thats it, a fully working silent install of nerovision express 2! I hope this helps out

well, I have tried importing the reg files and it still hangs asking for the extention associations. it seems that this just might be hard-coded in the installer.

well.....ummm..... I guess the title says it all! OH, and, yea, its good to be here! I have found tons of usefull info! thanks for a great board!

Hey all. I would like to start off by saying hi, and that this is my first posting. Now, for the topic at hand. I also have been fighting with this and with my audigy gamer drivers, but I am tracking down what is needed in order to make this a silent install. here is what I found out..... 1) if you try a silent install even after it is already installed, it runs flawlessly. 2) when you uninstall it and run the unattended install, it hangs again at the file types, so we now know that it is infact a reg setting issue we are dealing with. I have used wininstall LE to watch the install and found a registry listing about a mile long. I am gonna attempt to shorten it up to the "bare-bones" to try to make it: 1) universal for all users 2) only contains what is needed to make this install unatted, nothing more or less. I will let you know how I am progressing with this....