Alanoll

And that is where people will get confused with the Microsoft docs They will be misled to believe that a share and on CD(media) is the same, when it's not. Darn that MS for making it just that little bit more confusing.

That's what I meant. I didn't mean specifically AUTORUN.INF but the file that auto starts. What most people have done is just make their own... If you know HTML, it's rather simple to do. Then all you have to do is change the extension to .HTA and have the AUTORUN.INF file point to it instead. Or you could use a professional tool (AutoPlay Menu Studio) to create menu as well.

I think he means the ones that run just before SVCPACK (T-13). And no, you can't hide them. They're even there during a normal Windows Setup.

I'll be sure to make sure it's noted the differences between Network and Media distributions. In my mind when I hear shares, I think network. And the only reason it's WITHIN I386 and not on CD, is simply the way setup is started and how the paths are configured at that point.

Here's the problem.... you're modifying the Autorun file yes? There hasn't really been any success stories of editing it to satisfaction. I'd have to tinker a bit to figure out anything, so it may be a couple days till I have time. The guide on site and in the forums, regards teh billboard during setup.

this is either a custom action or a installer property, neither of which can be determined without looking at the MSI file itself.

bad burn/read. That's the most likely cause if you're just doing a basic disc.

CMDLINES.TXT runs at T-12 if present. So yes, as long as the file is there and there are valid commands in it, it will still execute.

Do you know how many times a "database" has been requested? I've heard the request and dang it, I'm working on it, but it takes time to make sure there aren't bugs in the programming as well as the search. It will be a part of the Unattended site. Now as for Step-By-Step instructions, I have to disagree. I personally am under the belief that if the member learns on their own without a direct step by step walkthrough they can then port their experiences to other software as well. People learn more from vague instructions (not too vague, but not direct either) as they have to think and problem solve (both of which is not emphasized in most educations). Now....if you would be observant (no offense meant, but more of a look this way), look at the bottom of EVERY topic and you'll see a SEARCH TOPIC box to narrow down the search even farther. NO ONE should expect a fully working applicaiton right CD after one day.

that's odd, I could have sworn the MP10SETUP.EXE /Q:A /C:"SETUP_WM.EXE /Q /R:N /DisallowSystemRestore" was the command execute from that SFX file. I'll double check later.

http://www.msfn.org/board/index.php?showtopic=34056&hl=xuser And yes, all you have to do is use /qb, but you won't have any advanced Winamp stuff installed without using another switch ( XFULL ) or similar.

well, in that case.... you have two options... typically you can create a folder "Frontpage" and add the entire Frontpage setup source into that folder and it should work. You will have to have them install seperately. You can't combine the two installs into one. You can however have like a batch file or similar launch both installs silenced. The Resource Kit to make the transform is documented on the site.

all of office is a WIndows INstaller. So yes, just add Frontpage just like any other program. The only reason an volume version would be needed is to make the admin point to integrate the service pack and hotfixes, otherwise you just install them AFTER office is installed.

REG ADD %KEY%\004 /VE /D "Winamp 5.08d" /f REG ADD %KEY%\004 /V 1 /D "%PP%\Winamp\winamp508.msi Xfull=1 Xuser="Unattended" XKey="xxxxxxxxxxxxxxx" /quiet /norestart" /f should be REG ADD %KEY%\004 /VE /D "Winamp 5.08d" /f REG ADD %KEY%\004 /V 1 /D "%PP%\Winamp\winamp508.msi Xfull=1 Xuser=\"Unattended\" XKey=\"xxxxxxxxxxxxxxx\" /qb" /f If that's my installer, then /quiet and /norestart are not valid switches, nor are they for ANY Windows Installer file (MSI). REG ADD %KEY%\064 /VE /D "Mega K-Lite Codec Pack 1.17" /f REG ADD %KEY%\064 /V 1 /D "%PP%\KliteCodec\klmcodec117.exe /silent /loadinf=".\silent.inf"" /f Should be REG ADD %KEY%\064 /VE /D "Mega K-Lite Codec Pack 1.17" /f REG ADD %KEY%\064 /V 1 /D "%PP%\KliteCodec\klmcodec117.exe /silent /loadinf=\".\silent.inf\"" /f You're problem is the program you used to create this file (RunOnceEX Creator or RunOnceEX Maker?) did not escape the quotes for you. By escape, I mean if you look at the Winamp section above, you'll see I added a \ infront of the quotes WITHIN the outer quotes. So... REG ADD %KEY%\XXX /V 1 /D "%PP%\someprogram.exe /user="MySelf" /variable1="what the freak?"" /f THen the quotes around MySelf and what the freak? must be escaped REG ADD %KEY%\XXX /V 1 /D "%PP%\someprogram.exe /user=\"MySelf\" /variable1=\"what the freak?\"" /f

try doing it the manual way. Could just be a problem with nLite. http://unattended.msfn.org/beginner/slipstream.htm#manual

try /qn ?

HKEY_CURRENT_USER is the hive for the currently logged on user. During T-12 it's the system account so they're MOSTLY transfered to all accounts created there after. HKEY_USER\.DEFAULT is the hive that is loaded when NO user is logged in. It's the one active during login screens and shutting down. Now, if you look at the HKEY_USER\SID-##### those are the hives of the users of the system. They're mapped to HKEY_CURRENT_USER when that user is logged in.

Just remember, without the WINNT.SIF file, you'll have to type in everything setup needs.

@Alex PLEASE! Notice the difference between REPORT POST and ADD REPLY! REPORT POST gets a message sent to the Moderator thinking someone broke the rules. When it's just a simple message like what you've had, it's just plain annoying. Please try to remember that in the future.

\OOBE Sorry....

what link are you trying to download from? Simply because there is NO .ZIP PDF file.

1. Goes in $OEM$\$$\System32 2. Replace wtih real name. The quptes ARE the names of the accounts. 3. Yes.

http://unattended.msfn.org/advanced/cosmet...lboard/text.htm Do search HARDER next time. Also, most stuff is covered on the site.

When you run the initial file you download, it probally extracts itself to %systemdrive%\ATI\support\(some package id) In there you'll find folders for each component, and the names are pretty obvious