Alanoll

A. Wrong forum. There is an application switch section. B. Check to see what changes the plugin makes. It may be as simple as copying over the file and config file manually into teh Winamp plugin folder. C. If the above doesn't work, use AutoIT. Moving topic

I usually apply the quicklaunch tweak at both CMDLINES.TXT and GUIRUNONCE to get it to stick.

http://unattended.msfn.org/beginner/hotfix/svcpack.htm All the /INTEGRATE switch does, can be done by hand, and is detailed on that page. XPCREATE may be of better use though, as you just put the hotfixes in a folder, and it does all the hard stuff for ya. Do remember though, you'll need to commercial version as you're using it for a company.

so you want to leave the F6 option usable right? To add the install.cmd file to the copy portion of setup, you have two options.... A. Edit TXTSETUP.SIF and add the file (I've detailed how to do this before. Look up a post on DetachedProgram and topic starter was GreenMachine) B. Create a INF file, and have IT copy over the CMD file, and add it to the sysoc.inf file for "install" B may get complicated, where as A requires ONE line of code.

That's the extraction box. SELECT WHERE YOU WANT XPLODE TO BE EXTRACTED TO! Dude, seriously....it's VERY simple to activate the Continue button, just READ THE EULA!!

1. If you mean an XP cd that already has SP2 slipstreamed, then just skip the step of slipstreaming the service pack, and you're good. 2. If you go this route, the SP2 CD (I'm assuming it's the SP2 disc containing the service pack and nothing else) there is a file called xpsp2.exe at the root of the CD, and that is the "network" file referenced in the guide. 3. How many can you fit on the CD?

instead of CD-R's use a VirtualMachine. May be slower, but saves CDs.

please read his question next time, not just the topic title. He's refering to the screens during the Text mode of Window ssetup, where you select partition and whatnot. Not the bootlogo.

what does the little red box on the window say? And Don't Say you've read it, you obviously haven't.

Here's the problem with not updating the MSI.... soon, all the people who don't update to 5.0.8e will have their WMA files rendered useless when the plugin has to check the MS website to see if it's valid. So then becomes the decision....should I make it or not?

just cause I was curious, I have no msiexec.dll ANYWHERE on my system, but Windows Installer works fine. Listing your files, and SPECIFIC edits will help to solve this problem. And I mean SPECIFIC! Did you edit any file? What did you remove? WHat tweaks are you using? If you don't remember, start over AGAIN, and go STEP BY STEP adding something till it breaks.

hmm...I'll check my CD when I get back to my dorm...I'm in the Computing Lab atm. Do a search (using the Window sSearch function) and have it scan archives as well. Do remember that it could very well be msiexec.dl_ in I386

1.SetupSourcePath changes the location it looks for the setup files. Think of it's "ROOT" folder as a seperate CD. The SetupSourcePath just says, "The CD is really here!". So the structure is EXACTLY the same as on a normal CD, just within a folder on the multiboot. That make sense? This means EACH unattended windows you have on the Multiboot needs it's own $OEM$ folder. The only way around this, would be to have a script copy the files over during Setup, from the CD and this gets tricky. 2. WINNT.SIF should go in the BOOT folder. 3. The RAID drivers didn't load most likely as they weren't in the TXTSETUP file in the BOOT folder. My suggestion, is get a normal working CD, then Multiboot it. The RAID drivers may not make it over, as they might not be listed in the SETUPDISC section of TXTSETUP.SIF. To overcome this, just redo the process for the BOOT folder (same editing and copying of driver files). 4. It's the file system used to create the disk. Joliet/Extended Joliet should work fine. If you're using CDIMAGE, -j1 is the switch. If you go to the Unattended Guide ( http://unattended.msfn.org ) and look at the CDIMAGE page in the Reference section, there's a GUI for CDIMAGE that may be of use as well.

you could even try DefaultHide if you still wanted some prompts to appear. GUIAttended will make ALL the boxes appear. And thanks for using CODE tags

thank you.

so msiexec.dll is missing during install? but a repair fixes it? Are you repairing from your Unattended CD? or the original? verify the file is on the Unattended CD. verify if it is on the CD, that it's also listed in TXTSETUP.SIF. If the last two conditios turn to be false (they're not there) then you're doing something else and not telling us.

Now seriously, DON'T do it again. Next time you will have posting disabled. If nothing else, double/tripple posting will have members NOT even look in the topic.

you're not trying to install it as an upgrade are you? from within a current version of windows?

you have to have quotes around lines with spaces in the... ECHO. ECHO Installing Adobe Reader 6.0 ECHO Please wait... start "" /wait "%systemdrive%\install\applications\Adobe Reader\AdbeRdr60_enu_full.exe" -p"-s /v\"/qn\"" ECHO. ECHO Installing Client Access ECHO Please wait... start "" /wait "%systemdrive%\install\applications\Client Access\setup.exe" -s

1st - THANKS! Though you didn't quite succeed in using the CODE tags, I applaud you for having the intention 2nd - Only one OEMPreInstall line is needed. 3rd - Be sure that when creating the CD, that the file system doens't convert $OEM$ to _OEM_

Any reason you didn't edit the .Default registry hive?

Ghost installer is used in other programs... UltraEdit I think may be one. Not sure. I remember a HEX editor using it...

IDN was never enabled in IE. You have to download a plugin from the Windows Marketplace for it to work properly. Firefox was the first browser to have builtin support for it (as far as I'm aware). Though the internet registars should all follow the same guidelines regardless of language and nationality, otherwise we could have a bit of a mess on our hands with people registers msfn with other characters (like the spanish n) or something.

OEMPreInstall=YES Have that in your WINNT.SIF. And read THIS if you read nother else : http://www.msfn.org/board/index.php?showto...ndpost&p=270687 Second, you're batch file is set to install from the CDROM, not HDD. That's why when moving InstallApps to the root of the CD, it work. FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\win51ip.SP2 SET CDROM=%%i: Finds the CDROm SET PP=%cdrom%\InstallApps\ If you don't know what that is, then don't use it. And $OEM$ should go in the I386 folder ONLY when installing from a network share or similar. From CD installs, it goes along side the I386 folder.

http://unattended.msfn.org/intermediate/intro.htm I sir, call you a liar! Read the part of "OEM Preinstallation"