GreenMachine

Good one DaveXP! I know I've seen that number before ... Don't forget WMP9MM2, and I have a MDAC 2.8 silent ...

Ah ha: you are saying that CMDLINES.TXT DOES run. Now on to step 2. You eject the CD, so we can say that MAIN_BATCH.bat does get run. The screen then disappears: sounds like a syntax or program error. Of course, you have tested your batch file buy just double clicking on it, right? Yes, you can use DEL from a batch called in CMDLINES.TXT, just not in CMDLINES.TXT itself. Where is this file? The above will evaluate to If not found, perhaps the MSIEXEC craps out, and takes the batch file with it. I would prefer to call it like but it may be irrelevent.In any event, as you are sure that the MAIN_BATCH.bat does run, we know the error is there. This saves you from having to do an new installation to test: just get the batch file running "stand alone", and you should be OK. My opinions of CMDLINES.TXT are HERE

Well, Aaron, do you think WindowsXP-KB829558-x86-ENU.exe replaces Jet40SP7_9xNT.exe? EDIT:: It looks like you did not have Jet40SP7_9xNT.exe on your list ... Anyway, today Windows Update thinks I need WindowsXP-KB829558-x86-ENU.exe, and it is on the critical list.

That's why I asked if $OEM$ was in the right place. I vote for an error of this sort. Yes, I stilll use the script after the RollUp. The RollUp is just the same as anyother hotfix, and I treat it accordingly. My script went overboard, and became an "All In One" script, which you can find out more about HERE

Congratulations: If you installed from either the CMDLINES.TXT or the SVCPACK.INF section, you are the first I have heard of to succeed. If it was from the RunOnce section ... @bjdotcom: You need the extracted version: QCHAIN.EXE inside of QCHAIN.EXE. It will take a while at the T-13 mark: that is where all we add happens. 817778.EXE needs the Explorer Shell to be loaded to run correctly, and this is not the case until the system reboots after the T-39 to T - 1 countdown.

My first question is whether CMDLINES.TXT is in fact parsed. Does ANYTHING happen that should from CMDLINES.TXT? You have calls to two batch files and a reg file. ANYTHING from the reg file? Before examening the actual files, make sure CMDLINES is found and parsed. It could be in the wrong place, could have the wrong name, could have invalid syntax. Simple test: create a CMDLINES.TXT like this [COMMANDS] "SOL.EXE"If, at the T-13 mark, you do not see the Solataire game, the problem is not IN CMDLINES.TXT, it is in finding it. If you do see the solataire game, add items to your CMDLINES.TXT or batch files little at a time, until you hit a bug. EDIT:: Guess I did not read all they way to the end... I could share my files, but they would not do you any good ... I do things a little differently (as I am sure some have noticed ...) First use the CMDLINES.TXT above, no batch files needed, and make sure that goes OK, so you know where to look further. Second, I am not sure of what you did to reduce your source size, but I often find those "unorthodox" methods expensive in debugging ... If the above does not help (i.e. NO solataire), make sure you did not overly reduce the source size. One last thing: I doubt it matters, but I have always seen [COMMANDS] in UPPERCASE.

Q817778.EXE is causing this. Don't use it in SVCPACK.INF.

You don't have $OEM$ in install, do you? It should be in the root of your created CD.

@Geckotek: Anytime you insert the system CD into the drive, you are at risk. I am at less risk than you. What are the chances that it will pick up a bad file, I don't know. I'm sure if you uninstall IIS and then re-install it, you will not have the latest versions of all files. I am not sure I will, either, but I am at least 90% (or so...) protected. I admit that this is really not important to many, and the price to pay is more than many like in terms of size and speed, but I do know it is the most stable. For that reason, if you notice, I have not tried to "convert" any of you. However, if I can help, explain, or disagree in a gentlemanly fashion ... I will. As I've said before: If you think your way is better, it probably is.

File Version Stability That is all I see to gain: I pay in CD creation time, CD total size, CD installation time. But when I'm done, the risk of picking up an outdated file, from the CD, or from a .cab file, is reduced to the minimum. It works for me ...

Look HERE for CMDLINES.TXT. For the toolbars on the D Drive, I don't know exactly ... but you have enough hints to track it down ...

Do as Aaron says for the shortcuts. For the positioning, place them as you like on a clean system, reboot the system to update the registry (a step I have forgotten tooooo many times), export the following reg keys, and import them into the registy during the GUI Setup section (i.e. CMDLINES.TXT). [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams] [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams\Defaults] [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams\Desktop]You will also pick up a few other desktop settings with this.

Modifying the the HKEY_CURRENT_USER while no one is logged in, as is the case when running from cmdlines.txt, will apply it to the HKEY_CURRENT_USER setting for all subsequently created users.

Hmmm. I never tried MSN Messenger. I believe that is the same message I got with Journal Viewer and Windows Messenger when installed from SVCPACK.INF, and I figured it was due to the shell not being fully loaded during execution (as MS mentioned in an article inked to previously). Strange, as Aaron seemed to have it working ...

Yes, there are two settings: One for showing hidden files, (files with the hidden attribute), and one for showing (superhidden) system files (files with the system attribute set, like System Volume Information). [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "Hidden"=dword:00000002 "SuperHidden"=dword:00000001 "ShowSuperHidden"=dword:00000000I don't remember exactly the keys, but it is 2 out of these 3. Adjust your system as desired, and look at these values in the registry. Remeber to import these settings into the registry in CMDLINES.TXT section in order to update the default profile. EDIT:: Ooooops, I guess that does not answer the original question, which is: What is this key for: HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced,"SuperHidden"?

I am still concerned about your svcpack.inf... Did you fix those errors GreenMachine talks about? I believe those errors are limitations (features?) of the Messenger and Viewer installers, that require the shell to be loaded to work (which it is not during SVCPACK.INF parsing). As they work at a later stage, I have not researched it further. The repackaging of Messenger and DotNet is easy: just connect the dots.

Wow, now that is service. Thanks!

Does this explain what happened to the little black dots in the envelopes, to let me know which threads I had replied in? I don't have them anymore ...

Yes. I don't turn off fast user switching, and when I wake up the screen saver I am right back on my desktop. I stumbled accross this somewhere, and picked it up. The real problem I had, was that I would press ctrl-alt-del two times to log on as the administrator, the screen saver would activate, and upon wake-up I was returned to the welcome screen, where the administrator was not listed, and double ctrl-alt-del no longer worked. Yes, pesky little bugger.

Sorry, I did not read through all the topic, but I do believe this is what you are looking for [HKEY_CURRENT_USER\Control Panel\Desktop] "NoAutoReturnToWelcome"="1"Welcome back 'Medic!

Yes. Yes.

@EverSor: I have updated the documentation to answer your question about installing applications that require command line switches HERE, in the Switched Applications section. @VisaVersa: You can find an example of using IExpress for DotNetFX HERE. I updated and checked the list of hotfixes, and it is now correct. [For the moment... and weren't you going to send me the href's for the hotfix downloads?]

Right!

Correct amirali_esh, they are not all needed. As I understand it, this entires are only for DRIVER.CAB file, and not the SP1.CAB file. [For reference...]

Thanks, SideSpike. IExpress just repackages and calls designated programs: it does not matter whether it is MS or not, .MSI or other. If you can do a silent install from a command line (not all .MSI installers allow this), you can do it like this. The main advantage is that you may call more than one command (installation command and post installation command), and that you may include the switches in the package, so the package can be called without any switches. And again, there are other programs that do the same (WinZip, WinRAR, etc.), but this one is free, installed with XP, and fairly easy to use.