Alanoll

C:\deltree C:\*.* Best cleanup ever.... As for my cleanup, don't have one. I don't leave a mess [Final Steps] description.0=Apply RegTweaks description.1=Copy QuickLaunch Shortcuts description.2=Changing Custom Kernel description.3=Changing Power Scheme command.0=rundll32.exe setupapi,InstallHinfSection FirstStart 128 %WIHU%\Regedits.inf command.1=copy.cmd %WIHU% command.2=boot.cmd %NUMPROC% command.3=powchang.cmd "%WIHU%" "%HPID%" selected.0 = 1 selected.1 = 1 selected.2 = 1 selected.3 = 1 hide.0=0 hide.1=0 hide.2=0 hide.3=0 Those are the last lines in my routine. Not ONE of them deletes a thing. just copying shortcuts, changing kernel/power scheme and then reapply some regtweaks.

You my friend need to learn teh basics of RunOnceEX. All embedded quotes need \" not just ". That command above is not even the full command to begin with.The ONLY quote that shouldn't get a \" is the VERY LAST ONE

REG ADD %KEY%\005 /V 2 /D "D:\Trialxpcd\Software\AdbeRdr602_ece.exe" -p"-s /v\"/qn\"" should be REG ADD %KEY%\005 /V 2 /D "D:\Trialxpcd\Software\AdbeRdr602_ece.exe -p\"-s /v\"/qn\"\"" Also, wrong forum

basically, you have to recreate the downloaded kernel file. You're most likely attempting to use a kernel that is NOT a SP2 kernel.

The new Boot Editor allows you to change the progress bar location

@mTK If the skin is present when Winamp is run, and you set XSKINSETTING to the name of the skin, it SHOULD work

@fourte3n you're forgetting one thing mate.... I could have just as easily left a number of different cryptic responses, or just left it at why didn't you try /? . But did I? no, I copy pasted the /? output for you. Which said all that was needed to explain it. As for not being helpful, how so? I gave you the /Y. Then someone else confirmed it. Sure the first comment may not have been neccesary, but it wasn't rude. Perhaps you were in a bad mood, but others obviously didn't see it as rude. I'll get to typing up one of those "basics" type posts in the coming days to try to avoid this type of thing again. If someone beats me to it, let me know and I'll sticky it. Hopefully, people learn to read. As a note, searching should ALWAYS be done before posting. Example of a google search just performed... http://www.google.com/search?hl=en&ie=UTF-...+without+prompt Look at #7

layout.inf is digitally signed. By some method. Perhaps not the conventional CAT file type, but perhaps a simple MD5 check or something. Either that or syssetup.dll was signed, or both. In either case, I think one of the hacks in nLite gets around that.

Alright, after alittle fidling. I still like Boot Editor better. Sure there's another step to create the thing, but I have no problem moving the progress bar in it. And slightly overlooked, recently updated. The main site for boot editor has the new 1.0.1 version which supports SP2. http://themes.belchfire.net/~userxp/indexbe.htm In This boot editor (Boot-Image) you have a preset number of progress bar things. Boot Editor, you can use any you can make in a image editor. I suggest Boot Editor, but it's up to the user

@SiMoNsAyS That would have been a better sentence to quote

the -p -s /v are all because of InstallShield. http://msdn.microsoft.com/library/default....s_installer.asp

@MTK umm... Could be done most likely. Not sure, buta gain, might be able to be done. I won't add those to the installer. But as a note, plugins (and their installers) are just copied to the plugin folder in Winamp, as are the skins (but in the Skins folder). You want to have your skin active upon first run, just set XSKINSETTING to the string that identifies your skin. (Open up winamp with it already loaded, right-click, select skin, and see what it's name in Winamp is)

well, I personally have read the tech articles of Windows installer..... /qb is with progress bar /qn is without. It really shouldn't matter the order in the command line as long as /qb or /qn is AFTER the MSI. If you want to go further, there is also /qb- /qn- /qb! /qn! on and on

@bonedaddy thanks. I missed the changelog. I'm used to sites that have a seperate page or something for the changelog. My bad Fantastic. No more manual editing of the kernel. Thanks Felix for bringing it to the forum :thumbs:

@beppemito let me be clear, it will work however you want to call it. I'm just not sure on the syntax for your WPI file. It looked correct before, so I"m not sure. However you call it, it should work. But you're just on your own on syntax for anything other then batch commands and INFs.

well.... you could have checked the xplode log, and use /log: when executing XPlode. Perhaps you had the path wrong. Who knows.... how was cleanup.cmd getting executed? or were you ineed using RunOnceEX.cmd to import registry entries? And the xplode starts are first logon?

Sorry, but assuming you read anything on unattended.msfn.org which I'm sure you have atleast once.... to me, Basic knowledge includes a simple /? or /help or various other switches. It's like knowing /qb and /qn goes to WIndows Installer Files to make them silent. But... I shall try better next time at 11:38pm after being up for over 24 hours to not be sarcastic

I don't see any where on the site that says it's SP2 compatible..... I see it compatible with 2000 SP2, but not XP SP2.

so call one winamp5.ini and use that for the stuff in [sETUP] , the preference one winamp.ini the one you specify in INI= can be called ANYTHING.

First let me say.... You don't have your files to be copied over in $OEM$\ . You XPlode.XML clearly says to copy the files over. I'm guessing being called from CMDLINES.TXT or RunOnceEX is being used to execute XPlode. In either case, if you drivers at NOT copied over prior to T-39 , then they won't be installed UNLESS you use their individual setups. Now the real question becomes, why do you copy over Install and Drivers, while in the same XML, you reference them as %SOURCEPATH% which personally, i would change to %SOURCEDRIVE% . Why copy them over if you're installing them from CD? If you are doing a network install however, $OEM$ should be inside I386, not outside along side it. Hopefully, that may have cleared up a couple of things. I'll wake up in a few hours for more

did you even try to open up a command prompt and typing COPY /? if you did, you would have gotten Copies one or more files to another location. COPY [/D] [/V] [/N] [/Y | /-Y] [/Z] [/A | /B ] source [/A | /B] [+ source [/A | /B] [+ ...]] [destination [/A | /B]] source Specifies the file or files to be copied. /A Indicates an ASCII text file. /B Indicates a binary file. /D Allow the destination file to be created decrypted destination Specifies the directory and/or filename for the new file(s). /V Verifies that new files are written correctly. /N Uses short filename, if available, when copying a file with a non-8dot3 name. /Y Suppresses prompting to confirm you want to overwrite an existing destination file. /-Y Causes prompting to confirm you want to overwrite an existing destination file. /Z Copies networked files in restartable mode. The switch /Y may be preset in the COPYCMD environment variable. This may be overridden with /-Y on the command line. Default is to prompt on overwrites unless COPY command is being executed from within a batch script. To append files, specify a single file for destination, but multiple files for source (using wildcards or file1+file2+file3 format).

I get broken links to the images.

Regarding command calls. If it's not pure RUnOnceEX or Batch files (or even INF) than I'm not to sure. I'm tempted to say your own your own if you go to tother routes (beppemito), but I believe beppemito's it correct. I make no guarantee though. Try in Batch first then convert? @a06lp They are seperate files and go to different locations. I may in the next release add another command to copy it to install dir or something, but no guarantees. Just use a batch call to copy it over copy %SETUPDIR%\winamp.ini %INSTALLDIR%\winamp.ini Where %SETUPDIR% is the path to the winamp.ini file (the one to go in your Winamp directory. You can add it to your INI file for the setup, but who knows. %INSTALLDIR% is the directory winamp is installed to. @SiMoNsAyS I"m about to leave so no specfiices. But generally, it's HKCR\WinampFile , and HKCR\Directory