Alanoll

look at the above screen shot. If you tell setup to install something that has child (Audio for example), if you specify xaudio=1 but xwma=0, xwma will still be installed because the parent setting overrides the child. But yes, ANYTHING you don't set =1 will not get installed, as long as you do not set =1 to the parent with =0 to the child. If you don't want all Audio for example, then just exclude it and select the children you want to install. you put the slash wrong. it's /qb not \qb The INI and commandline do the same things. INI is just cleaner as there isn't a command that goes over 100 characters in length. But you must specify the path to the INI file to use with INI="PATHTOINI\winamp.ini" when calling the msi.

Check his update section at the bottom of the post. the OPK is just a silent install version for 9.0b. 9.0c /silent does the same job, and incorporates 839643

I have no problems what so ever with the K-Lite pack. The ONE time I had an error was because of the file you posted above, and that was because I forgot to kill AIM before starting the install. WHat processes do you have running when installin the pack?

hate to tell you, but no that line won't work. I didn't want to get into complex boolean expressions, so it's simple OR's (if that meant anything to ya ) Xfull=1 overrides Xagent=0 basically. One reason INI is good.....don't need that really long commandline to accomplish that. If there are enough bugs in this installer, I'll see about adding in more checking for switches or if I get bored tonight (which is what this installer is, I was bored last night)....

well now...that saves me the second it takes me to right-click Thanks

blast it all. I was hoping people read the whole thing There isn't a typo in the MSI though There are other typos in the post, but hopefully people understand colum is column

Posted, http://www.msfn.org/board/index.php?showtopic=23079

Topic Closed Check this place out http://www.msfn.org/board/index.php?showtopic=23079

Alrighty, here it is. Background: This MSI is meant as a complete replacement for the NSIS installer for Winamp. It is a complete recreation of the installer in the Windows Installer format. This conversion allows for command-line switches to be used. NOTE: This installer is not SILENT by default. You must still use /qb or /qn like you normally would. For more information, if you don't understand anything here (besides the INI part) refer to here: http://www.msfn.org/board/index.php?showtopic=17412 Switches: I'm lazy, and don't want to type up ALL the switches individually, so I believe I'll use an image. The switches are in the colum just to the RIGHT of all the components. They match up with the components they're in line with. Additional switches are Xfull = Install ALL components. XName = Username for Pro registration XKey = Product Key for Pro registration XDesktop = Creates the Desktop shortcut; Default is 1 XQuicklaunch = Creates the Quicklaunch shortcut; Default is 0 XStartmenu = Creates the Startmenu shortcuts; Default is 1 XAllShort = Creates all shortcuts; Default is 0 XSkinsetting = Specify the SKIN to use in Winamp. XINET = Specifies what internet connection you want. 0 = Always; 1 = Modem; 2 = Not Connect. Default is 2 Usage: To install a component, you MUST tell the installer to install it. By DEFAULT only the main executable (winamp.exe) is installed. All switches are =0. To signal to the installer to install a component, add the switch to the command line with =1. Examples: To install Audio and Video winamp.msi Xaudio=1 Xvideo=1 To install Agent winamp.msi Xagent=1 If you wanted EVERYTHING then use winamp.msi Xfull=1 and everything will be installed. The ONLY ones this does not apply to are XUser,XKey, and XSkinsetting. They are all strings, so use whatever you're supposed. If you used "Joe User" to register Winamp, then use winamp.msi Xuser="Joe User" XKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" INI Usage: Now for the fun part. New in this release is the ability to use an INI file rather then type it all out at the command line. This file can be called anything, and can be anywhere, because you specify where it is. If the path is not correct and it can't find the file, then the installer may perhaps error out on you. INI Syntax: [SETUP] XAUDIO=1 XVIDEO=1 XNAME=Joe User XKEY=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX I only included a set of the of arguments you could use. They are the exact same names and usage as from command line from above. Save this file ANYWHERE you want, and call it ANYTHING[/] you want. As long as you know where and what it's called. After you have create your INI file, start the install with winamp.msi INI="%CDROM%\Unattend\winamp.ini" the quotes ( " ) are only neccesary when there are spaces, and when used MUST enclose the whole argument. %CDROM% does NOT have to be %CDROM%. If you're files are in %systemdrive%\install\winamp, then use winamp.msi INI="%systemdrive%\install\winamp\winamp.ini" I think that's all.....ohyeah.....this screen was added to the installer..... Download Link: Linkage Last Update: 8/13 16:48 GMT

but what if people don't want video support? I personally don't like playing videos in Winamp Expect new MSI soon if you're interested.

You have the option of Creating stand alone ISO's correct? In those directories is what I believe you should run SP1 on. And obviosly there are difference updates for each CD on that disc. Disc 1 is Office, Disc 2 is OneNote on and on. SP1 for Office gets applied to the Office Disc part, OneNote's get's applied to OneNote. There are difference patches for difference parts of Office 2003. There is a patch for Office 2003 for Word,Acces,Excel and those normal ones, and then there is a seperate patch fiel OneNote,Visio and the others. The problem you might run into is the CD may turn up too large.

GEEEZE. Could you attach that thing instead of posting it all? Please be considerate to others. Product Key removed. Where is the error popping up at? Did you specify that file somewhere?

the SETUP.EXE just calls each of the 5 individual setups on their own. If you follow the slipstream guide to update the MSI's with the MSP(service pack) you will install SP1 when installing Office.

SP2 doesn't have WMP10 Also, what about those people who still use Win2k or Win2003?

why do you need another dxsetup.exe when the one already included works with /silent?

that sites is basically a , you place here and you're down. A good chunk of it is in PERL though, so.....if you don't know that, it would be better (even if you did know PERL as well) to come here.

in a batch file, if you use start /wait, the batch will wait before proceeding. In a RunOnceEX, it should wait on it's own there is a program in the download section of the unattend site, that is called sleep, you could use that if you program does some wierd things.

so why posting 3 times? Didn't someone have a accident with posting? I've never seen it besides in Win2K where you press CAD and it goes straight to Task Manager. Check for a registry key, as that's probally what enables it. It not the fact that you did something wrong, but more of a you didn't do something.

what's with the double %? If it's in CMDLINES, i don't think that will work. I know it won't in GUIRUNONCE.

and here I thought development was never going to continue. YOu were moving on to bigger and better thigns.

blast you two.... I've started development, but don't say that in that thread Also, Mac, looks like I accomplished our holy grail. INI file support. :woot: now it's jsut winamp.msi INI=winamp.ini lol Did you notice how there are over 200 NEW files in this release? There's a reason I waited on updating that MSI, they way Mac did it before...it's just a beast. All those components I gotta wade through.

Some people just don't read. Even the Microsoft documentation tells you that if you put WINNT.SIF in I386 it will become an Unattended disc from boot. You'll still need to arguments /u: if you want it Unattended through windows though (starting the intall from windows)

well, right now I"m still working on the INI part. That I'm mainly doing to see if I can It's almost done. INI workings complete. If you want an INI compatible version for the current MSI (5.0.3a) I can upload that real easily. I still have to replace files and whatnot to get it up to date. Basically, instead of a nasty commandline pass, ie winamp.msi XAUDIO=1 XVIDEO=1 XREG="asdsdfadjkhl" XKEY="asjdkhasdghauiorhgu" it now becomes winamp.msi INI=C:\winamp.ini and the INI has [Setup] XAUDIO=1 XVIDEO=1 XREG="asdsdfadjkhl" XKEY="asjdkhasdghauiorhgu"

tis true....I do like to help....still be interesting to see how many people of the some 130 downloads on the new link actually post here

Why is the poll if you've already decided to create a MSI. Do it, then. People like variety. But please, no more beta testing. haven't decided. Just trying to provide a point to Solid. I have decided to make the MSI for myslef, but the difference would be how extensive, as for myself it wouldn't NEARLY have all the features like it would I were to post it. I'd just do a simple setup capture and be done with it. I'm trying to see the interest before actually doing all the work....(which is alot. have you seen the inside of the one Mac made?)