Alanoll

do you know how to remove it in the first place?

there already is one, built into Windows Installer. INSTALLDIR It should also be usable via INI, if not I'll add it next revision, but it should always be available via command-line

I'm not sure of this, as I've had no need in trying.... ut what you could do is indeed replace it with %ProgramFiles%, but just to test, start setup with -f1"setup.iss" but without the -s. It SHOULD read in the iss file and fill in the values as presets.

$Prog and $Docs are actually a part of OOBE for Windows XP. That's where they get their functionality. So no....

STFW? I know STFU....but now STFW. lol so far, none of that has made it, probally because I'm writing the manual they're supposed to be read.....now wouldn't that be one of the most annoying books? You're reading a section, then it says to read the same section because you didn't read it. Talk about a paradox and an infinite loop. Kinda like looking up definitions in the dictionary....gotta look up hundreds of words just to understand the word you were looking for.

Plus besides Aaron and xper, I've the only other one with access (perhaps the other admin as well). Hopefully my sarcasm doesn't make it to the guide Sure most of the time it gets the point across, but in a guide, it's not suitable. I don't think I've used any yet. I might in some of the FAQ answers though....

I meant to change it to "common answers" instead of problems. More positive. You didn't p*** me off, and it's not the credit. Let the thread continue. I'm sorry. Just disregard my post. Let the thread continue, and we'll see where it goes. @Tsunami FINALLY!! Someone who knows how to use the search!

@Wai_Wai You do know all that nLite does to change the install path and such is just create a Winnt.sif file right? You do ALSO know that Microsoft has a program to do this as well. The ONLY difference an nLite CD might have versus as Microsoft one is removed components. the Unattended part can be done with both, using the SAME METHODS.

@Pezzie Sometimes, it's people like you taht get on my nerve. I've had a thread open now for almsot 3 weeks, for people to suggest additions to the Unattended website. But do you? no. You make a thread in the forum adjacent to mine. Now here's why I'm gonna say it's a waste of time here... Problem 2, I plan on addressing with a page dedicated to descriptions and screenshots of the user created apps. That would have solved this problem. Problem 3, I plan on an entire SECTION devoted to customizing the Windows install, from Setup up to Themes and such. Well well, that pretty much solves that. Now.... last I saw, there was a THREADS OF INTEREST in the sticky section. It is meant to be the "problem solving" thread, as it links to threads that answers many questions. I would suggest you add to that instead of opening a new thread.

the greenmachine guide tells you to edit TXTSETUP.SIF NOT WINNT.SIF Just remove those entries form your WINNT.SIF file. try making it capitalized as well.

actually, it depends on how much you wanna spend.... You can still legally acquire an XP RTM CD, but not from a store. Now, if you were to purchase one of those MSDN OS licenses or above that includes the OSs, you should be able to download them. My friend has a OS license and he's able to download OSs back to Windows 98, even though it's not supported. They're still available because people still use it, and MSDN is primarily for developers. But like I said, how much you wanna spend? How can you POSSIBLY even know if it's service pack free without opening it? SP1 came out what..... 2001? You most likely have a nice retail SP1 slipstreamed CD.

i was intending to have three ways.... the one using nLite. one using a batch script I might whip up (asks the user for hte path) and then showing step by step what to do manually.

as soon as someone who has ALOT of time of their hands, and speaks german and english fluently, and has the drive to make it through the entire thing.

@Dynaletik it's part of the Sonic Burning components. @midiboy Curses. But I knew there would be atleast one bug. lol. Guess I gotta go try and find a WAV file.

Remove the GUIRunOnce section. The guide says to use CMDLINES.TXT. USE IT. put RunOnceEX.cmd in $OEM$ in the SAME folder as CMDLINES.TXT

move your RunOnceEX.cmd file into your $OEM$ folder. slightly off topic, didn't you just have another topic on this same issue the other day?

I was thinking of starting it Wednesday. I'm sure there are gonna be bugs, so just giving a few days for people to find those. Also, the registering associations works, just as in the same release. What doesn't work is the "User can install the audio components, but still not have Winamp associated to it". That's what's gonna be changed next update. The INI file is the SAME form the last release, it's good to go. @Sneakyghost Guess you're still not seeing the examples There are NO "/" for the switches. the ONLY "/" you should have is for the /qb or the /qn. All the others are just XFULL=1 or XAUDIO=1 and you just list them out.

looks like it's a NSIS. try /S Also, read forum rule #12. And remember on your next topic start.

I'm not sure all of prathapml's suggestions will make it into the update So far, the "Graduate" section of the site, is an oddbal assortment of leftovers. lol.

i believe there are examplse of COMMAND-LINE usage in the first post. The original Winamp switch (/S) doesn't work as well....this is an MSI. ALL Windows Installer command line commands should work (with the exception of /a which bring up a help; which isn't updated ) As for teh copy paste issue....I'll look into. You're the first to notice. lol. Probally just a check box I forgot to click

-------------------------------------------------------- Everything past this line, may not make it into the first update of the guide... Planning has started....

Just alittle something I noticed... the WIHU and WINNTBBU.DLL forums don't have Quick Reply buttons at the bottom.

I can't get the compression down to the same level as NullSoft's original, but the MSI is rebuild of the original (as close to it as possible) installer. EVERYTHING the original installer has this should have.

Closing thread ~ Posting for the sake of those subscribed to this thread to get the update http://www.msfn.org/board/index.php?showto...ndpost&p=233129

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 and http://www.msfn.org/board/index.php?showtopic=26923 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 XREGAUD = Associate Audio extensions. Default = 1; Any other will disable XREGVID = Associate Video extensions. Default = 1; Any other will disable 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\winamp5.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\winamp5.ini" NOTE: IF you want to use CDDB functionality, you MUST set XINET to 0 or 1. Updates Updated MSI to 5.0.8d. Shortcut problem appears solved, as does the burning thing. CDDB may require to you change the internet connection type, prior to it working. Download Link: MSI File | CAB Files Last Update: 1/29 03:25 GMT