Alanoll

@Wraith Guess taht means you'll have to make it more feature rich, while at the same time making it smaller

copy the winamp.ini file form your current winamp directory. Copy that over after the MSI runs.

you can, but I don't know waht /R is for though. or /norestart or /passive, as they're not MSI commands. second.... Taken from above. Those are ALL batch command calls. just put start /wait infront of it. NOTHING in my post tells you how to do RunOnceEX, it's all assumed you use batch calls.

technically, it installs the PRO version always, just if you don't have a KEY and NAME the features aren't activated. the INI looks fine, but I don't guaranty INSTALLDIR will work. That and you specified the default directory anyways.

read WINNT.SIF and search for ComputerNames. You could specify as many names as you want, and if SETUP finds the name already exists on the network, it should automatically shift to the next name.

First post Updated.

@Mac That's a simple setting in InstallShield to make each component into it's own cab, so it's entirely likely. Of course, I'm not sure what will happen if you tell it to install something that's not present, but if that what you people want, I'll recompile tomorrow and rar it and upload it as a seperate link for people to respond back to. As for removing stuff not in the original installer, everything is exact like the old. The problem is InstallShield's compression isn't as good as nullsoft's. And I can't find where to set it. I just see Optomize for size, and that's about it.....

does your P4 support Hyperthreading? If yes, then mp, if not, then the ntoskrnl.exe

whooops. the file is new, the date isn't. I copied the first post from teh other thread, and changed the link. My bad, will correct in a minute. @Orsi What doesn't work? Nothing? try encasing the INI argument with quotes. ( INI="C:\winamp.ini" )

you've already done the ncessary actions. If it doesn't work, don't use PIstart.exe whatever that is, or remove the ,\

CMDLINES.TXT if present during setup, is executed automatically.

incorrect. You forgot to specify XKey

As promised, new MSI is up... **Thread Closed** (I will not be updating the 5.04 MSI anymore, consider discontinued) http://www.msfn.org/board/index.php?act=ST&f=80&t=26923

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" NOTE: IF you want to use CDDB functionality, you MUST set XINET to 0 or 1. Updates New MSI, fixed a couple of string error (wrong name). Also tried to make smaller, but probally didn't succeed. Also uploaded a RAR file with the MSI broken down into CAB files. Delete the cab's you don't need. There should be ONE cab for each component switch. DON'T DELETE CORE.CAB!! Download Link: MSI File __ CAB File Download Last Update: 9/8 05:52 GMT

what do you mean start? define start

I don't know what you people are talking about Finishing a DVD, and starting on the new one? HAHA My burned ones are just workable tests.... I don't think I've ever actually completed one yet.

ntoskrnl.exe is the single prcoessor kernel ntkrnlmp.exe is the multi-processor

0x34 or so in the bitmap file (it's tru address is something like 0x00000034 or so)

what? If you mean to use your own image instead of the default XP one, yes. But if that is indeed your question, there is a section of the forum that deals with that.

http://www.msfn.org/board/index.php?showtopic=26739 Read that. Look for a post I made concerning it.

it could be the fact of invalid XML syntax. Didn't close a tag or something.

don't worry about it. If the DAT files are in the same folder as CDSH, remove the /. If not, you're going to have to assume its right and test. (You can burn a CD with just the CDSH and DAT files to test the menu fully). Basically, with / , it's looks for the files specified in the root of the current drive. Which is why a CD works, and HDD doesn't. When it finds the file, the error you should get in CDSHW.COM is something about COMMAND NOT AVAILABLE

Just a few more hexing tips.... The XP kernel does a fade when loading. There will be a second of color then a fade in, to get rid of that..... replace everything from 0x34 to 0x74 (it's around there, it's the pallete in the BMP file) with 00 and then replace it in the kernel.

Slight update.... I got around to redoing the MSI today.... I added in dynamic paths and such to the files, so from each new version, assuming there aren't new files (ones that are BRAND new not Update), all I'd have to do is copy the installed files to the new setup paths, and be done with it. Rebuild, and post the link. The new MSI is going under some testing, before I post the link to it here (there'll be a new thread, since it's a new version. No need for people to get confused and see all these error messages ) And I believe I figured out the CDDB thing, so yeah.... I expect Monday (bout 20:00 GMT or early in the morning before I leave again) for the link to be up.