Denney

Yep. That's exactally the problem. Terminal Services need to be running. Are you using nLite and removed Terminal Services? If so, then there's your problem.

@Astalavista: If you look at my first post, you'll see I've directed people to follow the instructions at the unattended website for integrating this file. Anyway, all you have to do is edit the "HIVESFT.INF" file in I386 and add the following line after the "SfcQuota" line (search for it). HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","SFCSetting",0x00010001,0xFFFFFF9D

@DingoDaddy: What hacked file did you use? The one attached to my post? Try adding SFCDisable=0x00000000 to the registry and then change SFCSetting=0xffffff9d.

Well, I've decided to get on the utility bandwagon. I made this program for myself but I thought maybe someone else could use it. What does it do? This program will import INF files based on a group. How does it work? It scans a given folder for all INF files matching the name of a group (*_GROUPNAME.inf). Why did you make it? If you have MANY registry entries of RunOnceEx values, putting them in seperate files makes it easier to manage and update. How do you use it? MSAINFImporter.exe "PATH TO INF FILES" "BASE DIRECTORY CONTAINING GROUP FILE TO CHECK FOR" "LIST OF COMMA SEPERATED GROUP NAMES" When importing more that one group of files, it checks for the existence of a file name "GROUP NAME" in the base directory. If it exists, it will import that group of INF files. Example... My INF files: 1_Global.inf 2_Global.inf 3_Global.inf 4_Global.inf 1_RaveRod.inf 2_RaveRod.inf 1_MissCath.inf Run with the following command: MSAINFImporter.exe C:\MSA\RegEdits C:\MSA Global,RaveRod,MissCath The program will check for "*_Global.inf" in the "C:\MSA\RegEdits" directory, the import them. It will then look for a file named "RaveRod" in the "C:\MSA" directory, and if found, will import the "*_RaveRod.inf" files. It will then do the same for "*_MissCath.inf" files. A couple of problems though: 1. You CANNOT have spaces in your paths (use 8.3 notation if you do). 2. DO NOT put "'s around the parameters. I hope you all understand this but if not, just ask. v0.11.0.0 (29.08.04): MSAINFImporter.zip

Thanks for the help guys. It seems that there isn't a problem using "!" all the time.

Most things on the website will work with SP2. Some things won't (I haven't found any yet though). If you find SP2 works for you, stick with it. The main reason most people haven't moved to it is the compatibility problems with some software. I, personally, have rolled out SP2 onto our network and it's works great. Especially when reduced with nLite.

I use this method for some stubborn registry tweaks. I use RunOnceEx though. Basically, I add all my RunOnceEx commands numbered like so: 1000,4000,8000,9999,etc. With my last command, I have it add some more RunOnceEx keys numbered: B21000,B24000,B28000,B29999,etc. That way, on first boot, it executes the "0000" numbered ones, then another command file adds the "B2" numbered ones and they get executed on second boot. I hope you understood that. If not, let me know and I'll take my time and explain it a little better.

This is aimed at GreenMachine but I would like anyones information on this. I've just come across a problem where I have to use "enabledelayedexpansion" and "!" rather than "&" in my batch files. My question is, would it be OK to use "!" for ALL variables now or just for the ones that require it? The reason I was thinking about using it for everything is that I don't really understand this "Delayed Expansion" thing and it would be easier for me just to use one type of variable and not both. Thanks in advance.

There are NO hotfixes for SP2 yet, except for one that you need to ring Microsoft for (not one that should be installed on every computer though!).

You do know that you only need the winnt.bat if you run Windows from a 32-bit environment. If you want to install straight from CD (via Text Setup) then you don't need this file. Just incase someone didn't know.

Just so people know. Putting: [IEPopupBlocker] ShowInformationBar = Noin your WINNT.SIF file will disable the information bar completely. Putting: ;Dont Show The Information Bar Dialog [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\InformationBar] "FirstTime"=dword:00000000into your registry entries will disable the PROMPT but still show the information bar.

Were you guys, by any chance, on the beta program?

I'm using the latest version of Messenger Plus! and installing it via "msgplus3.exe /silentinstallnosponsor" and I don't need any of that taskkill stuff. Nothing runs if you perform a silent install.

I've gone one step further and compressed it, put it in I386 and added it to DOSNET.INF and TXTSETUP.SIF.

Well, this is what I've found: I can nest IF statements: if a==b ( if b==c ( d ) ) I can include a for statement inside an IF statement: if a==b ( for %%i in (a b c d) do ( e ) ) I can include an echo statement with () IF they're in quotes: if a==b ( echo "Something (lala)" ) I can't include an echo statement with (): if a==b ( echo Something (lala) ) Don't ask me how this all works but I've fixed my problems now so it's all OK. And the []'s look better than the ()'s in my log file anyway.

OT: I have to say thankyou for this program. There are a LOT of useful features in this program. I can now ditch half of my utilities and re-write my batch files.

I'm curious how I could test for this problem. What programs can cause this problem?

If you installing something NEW like those updates, QCHAIN won't help much. QCHAIN is only needed when a hotfix is going to overwrite an older file. With SP2, all new hotfixes will contain the /integrate option.

@evilvoice: After my IF statement I have a whole lot more things and the batch continues fine. I didn't post the entire file because that's not the problem. When I say nested, I mean something like this: if %floppy%==y ( echo. >> %log% echo COMPSETUP.CMD [20]: Setting up MSA floppies: >> %log% if not exist A:\MSAXP.FPY ( echo COMPSETUP.CMD [23]: No MSA update floppy detected. >> %log% cls %systemdrive%\MSA\UTILITIES\CMDOW.EXE @ /HID echo Please place an MSA update floppy into your A: drive. pause %systemdrive%\MSA\UTILITIES\CMDOW.EXE @ /HID ) ) Edit: DOH! Nevermind. It was because I wasn't UNHIDING my command file. LOL.

Do you have "OEMPreinstall" in your WINNT.SIF file? You require "OEMPreinstall=Yes" for it to work.

Well, the nested IF statements has buggered my whole idea up really. I really wanted to nest those things. Ahwell... What I've done to fix my IF statement is to change the "()" to "[]". Answering "n" or anything other than "y" and it skips the IF statement fine. I don't seem to have any problems with the ":".

BAH! GreenMachine, you are the man! Removing the () around my echo statement INSIDE the IF statement fixed it. After all that. Edit: ****, that also means I cannot have nested IF statements.

I answered your question and tried your suggestion but that didn't work. I'm totally lost as to what this problem could be. :S

That my friend, is my way of telling another cmd file which user we are installing for. Seeing as I couldn't work out global variables that can be used in another batch file, I've made my batch file create an empty (echo.) file name the name of the user I'm installing this for. Later on in the installation, in another batch file, I can test to see which user I am installing Windows for. I use it to import user-based registry edits mainly and because I'm only doing a few computers with this particular CD, I can have my command files check which PC I'm installing it on. Also helps for when I install an application like Visual Studio that I use by no-one else in the house does. I just have the cmd file that install Visual Studio check for a file named "RaveRod" in the MSA directory. Hope that straightens things out for you.

Oops, yeah. I was talking about the RunOnceEx window. My mistake.