GreenMachine

Thanks for the Bart Info. I did have a question or two i would have liked to ask him, but I got the impression from his site that to do so might be fruitless. I respected that, and for the wealth of knowledge he has shared, I did not try to get in touch with him. Part of the problem I was having incorporating his PE in my ModBoot was that I was doing it the opposite from his example: Instead of using the PE CD to optionally load other images, I was using other images to load PE. That was all days, if not weeks, ago, so I am more than a little fuzzy on the details. Again, thanks for the info.

Chill out ... I believe this program is a simple generator, to fill the void left by the MS version that is included with every copy of XP. Use it as such: nobody is here to hold your hand. If you did not look in the included ref.chm, the complete authoritve guide to WINNT.SIF before asking this question, shame on you. In answer to your question, Branding is a marketing term, where as a company purchases a finished product, and adds their own Brand Name, Logo and Packaging. This term has been used by MS to refer to the repackaging of Internet Explorer, done with the IEAK (Adminstrators Kit) to distribute. Lesson over. Next time do your homework, or don't bother coming to class.

Stepped on you ... So now you do not see the "Hit.." message at all? You have to remember to pull the CD (virtually) out? So it is not the bootimg.bin itself, it is the presence of I386\bootfix.bin? I do not need to replace any files?

Don't say I didn't send you in the right direction ... just don't see how I overlooked that myself. As you say, that is just for generating the loader, not an inf for the loader itself. But it has to be there. I would think that the boot.bin should work fine: all the NT ones just seem to call a certain file on the CD (NTLOADER or something). Still, it does not explain the afore mentioned mystery using the boot image on it's own, or calling it from a boot loader. Keep us posted.

So Terminator3 what WINNT generator did you use? Looks good, devil-man! Personnaly I like that I can add only those sections which I select - as you said, more control over the final creation, as there are very few things I change. And even though I only change a few, I prefer that they all be availible for modification, as I hate the feeling of not having total control ...

The MS program only backs up the data, not the mail settings. Look at www.slipstick.com for extensive Outlook information. If she ain't got it, you'll have trouble finding it.

I have been looking for that as well, though I agree with others that for an XP installation which will unattendedly reboots, it is not a good idea. For further info: I created Bart's pseudo-"PE" (read free PE) boot CD, and that does not ask. Using Bart's ModBoot method I have included the Boot PE option on a CD, which boots the linux loader, asks which boot image to load, and loads it. When called this way, Bart's PE DOES post the "Hit Any Key" message, and I am calling the same boot image from the simple PE CD, and the ModBot CD. Not only do I not need it, I forget to hang around and hit it, so the PC boots off the HDD, or hangs with no OS. Maybe this can help your research. I did not find more info on Bart's site, either. I do seem to remember that there was an option in the PE creator to display or not display the question, and I selected not to display. This leads me to believe that the "show/no show" option is not embedded in the boot image, but the method in which the boot image is loaded. Good luck, and please let us (me?) know what you find out.

The .pst, "Personal Storage", file only contaings the mail and calender, etc. I have added a few options into the default account I see no point (for me) in adding more info, such as mailserver username, password, etc, as the installation then becomes specific for one user, and not generic. I would just "image" the system as I like it, and restore instead of re-instaling. But I digress: You will find most any Outlook (not Outlook Express, a completly different, and security hole ridden product) info you need at www.slipstick.com, including importing and exporting settings. I believe the best place for these settings are in fact in the Office Installation, which can be silent and customized.

Since this is one of those "down under" programs, how about a "Go Get Me A Fosters, Mate" option?

I'll bite, where is the copy command? I max out at about 20 lines of code. I'm tellin' ya, pipe to a log file, go have a beer, and when you come back you will have your answer. i.e. ECHO Installing q282010: Jet 4.0 Service Pack 7... >> LOGFILE.TXT

My ultimate goal here is to end setup that does not list any updates to do in Windows Update, critical or recommended. This is because there will always be someone who will do the update, as MS "recommends" it. I know it will happen: I've seen it often enough. For that reason I prefer to install before the end user, and adjust the system settings if need be. I think I prefer to fool Windows Update with the registry to than test the nightmare you propose! As i said earlier, I don't remember the details, but I could not even do a silent install from the command line without the afore mentioned error, and the switches I was using were all correct, as listed before my nose. What is even more strange, is this seems to be a typical type 1 hotfix, even if not listed as critical, so I thought it would be easy...

Sounds to me like there is a line crashing out the whole thing, no? If so, that would explain why you never see your pause. I'd start putting in a few other pauses, or better yet, pipe some text into a log file: i.e.: ECHO Starting ABC Update >> LOGFILE.TXT ...(run program / script command) ECHO ABC Completed Succesfully! >> LOGFILE.TXTIf you are the impatient type, you could also add something like this to the end of the script: NOTEPAD.EXE LOGFILE.TXTI cannot believe that the code is running to the end if the pause never happens.

Now we're getting somewhere: I'm batting at least 500, I use only these type 2 hotfixes in the slipstream: KB814078 (Might have been JS56NEN.EXE) Q327405 (Might have been HH_somethingoranother.EXE) Q330994 (As you mentioned - looks like an IE/OE update) Q822925 (Also something IE like) Any clues on the first two? To eliminate any double negative type confussion, I assume you mean that the 2 listed hotfixes are OK to slipstream. Thanks.

Sorry, by CMDLINES.TXT I am refering to a point in time, more than a program reference. It has become a de-facto standard to call a bat/cmd file from CMDLINES.TXT, as the syntax there is a bit too restrictive. As I recall, this is also the method that was originally in use. You can always use the activate welcome method, but that would be no better than auotlogon to the administrators account, creating a user, and forcing a reboot. The only problem I have with that method is that the autologon method is used. I disactivate the Administrators account from CMDLINES.TXT, and it is NEVER logged into. Fortunately, 'most everyone else is not like me. So if you do not have an objection to the autlogon, go for it. Concerning the real problem of not being able to create the user using the standard procedure: that would bug me to much. In fact it does already, but I cannot reproduce the problem. If I were you I would certainly have done a 99.9% clean install by now, only adding the user. If that works, then it's something else you are doing. If it don't work .. well you could always pull your hair out! Let us know which route you take.

Wrap the string with enviroment variable is quotes. echo Desktop Stuff copy "%systemdrive%\install\desktop\*.*" "%ALLUSERSPROFILE%\Desktop\" echo.

Yes, I read the MS description of the 817778 patch as well. I know what it is, what it is used for, and whether it is needed, now I'd like to know how to incorporate it into my setup. I played with it a bit when it came out, but had trouble installing, even from the command line. I got frustrated, determined the software to be at fault, as it did not behave as described in the documentation, and have not touched it since. Apparently, my strike did not encourage the powers that be to release a new version, so I am now looking for a work around. I'll try the command line Paul365 recommended, but I need it to run BEFORE the GuiReboot, as I'm done before that. Anyone else get it install? If so, which method?

@Spheris: I'm definitely for leaving the hotfixes in for the reasons you stated. That is what I was trying to say HERE. Can't remember who suggested removing them, but it looks kind of dubious to do so. I am considering extracting them into I386, but not including them in the svcpack.inf, and running them from CMDLINES.TXT instead. Or both. Just a thought. Anything other than NTDL.DLL that we should watch out for? @RoyalBox: Are you saying I just need a few more colored icons to get more girls? Does that work better than the golf course? Where do I sign! ... I will leave the type 2 code in my version, just not sure I will include any type 2s. I'm after an automated solution, not an id***-proof solution.

Chicken and egg. It'd be tough to log onto the new user account in GuiReboot, if hasn't been created yet. You could, I supose, make it even more complicated and use multiple reboots and scripts ... Sorry to see that creating user has not stopped bugging you yet. You could not get it to work in CMDLINES.TXT part of setup? Keep plugging ...

Lookin' good. I think HE prefers Creator to Creater ...

If anyone get's this one working truly unattended, preferably before the GuiRunOnce, I'm interested. I think there is a bug in it ... (It certainly does not use the switches listed correctly, even in direct command propt mode.)

My feeling is that after the ;SetUpMgr (or whatever ...) it don't matter. And if it does ... it certainly shouldn't: what's the point of all the headers otherwise?

I consider the two methods to be more or less equal in time. I have not stopwatched them, but it's close enough for me. They both run the hotfixes, this method runs them at t-13 minutes, the batch files from CMDLINES.TXT run immedatly after this. The benifit of the RHSM (Royal HotFix Scripting Method) is reliability, not timesaving. RHSM eliminates different versions of the same file. Watch out for the type 2s: if anyone has a list of those which don't work ... it'd help us all out. The 4 I do appear to work for me, but I almost never use XP (2003 for me), so my testing is, at best, inconclusive.

Has anyone tried the IEXpress setup creator? I look like it could simplify setup commands (eliminate all switches). I assume it has the /q option, as it is a wextract type installer. Anyone?

CMDLINES.TXT should look something like this: [COMMANDS] ".\INSTALLS.CMD"All your commands should be in the second file, INSTALLS.CMD in my example, which is in the same directory as CMDLINES.TXT. CMDLINES.TXT has funky/limited syntax, that is why it is easier to use the second script file. You need nothing in the GuiRunOnce, the fact that $OEM$\CMDLINES.TXT exists causes it to be parsed.

; --------- MP3 Files [-HKEY_CLASSES_ROOT\.mp3] [-HKEY_CLASSES_ROOT\mp3file] [-HKEY_CLASSES_ROOT\.m3u] [-HKEY_CLASSES_ROOT\m3ufile] [HKEY_CLASSES_ROOT\.mp3] "PerceivedType"="audio" "Content Type"="audio/mpeg" @="mp3file" [HKEY_CLASSES_ROOT\.mp3\OpenWithList] [HKEY_CLASSES_ROOT\.mp3\OpenWithList\wmplayer.exe] [HKEY_CLASSES_ROOT\.mp3\OpenWithProgIds] "mp3file"=hex(0): [HKEY_CLASSES_ROOT\.mp3\PersistentHandler] @="{098f2470-bae0-11cd-b579-08002b30bfeb}" [HKEY_CLASSES_ROOT\mp3file] @="MP3 Format Sound" [HKEY_CLASSES_ROOT\mp3file\DefaultIcon] @="C:\\WINDOWS\\system32\\quartz.dll,7" [HKEY_CLASSES_ROOT\mp3file\shell] @="Winamp" [HKEY_CLASSES_ROOT\mp3file\shell\play] @="&Media Player" [HKEY_CLASSES_ROOT\mp3file\shell\play\command] @="\"C:\\Program Files\\Windows Media Player\\wmplayer.exe\" /prefetch:6 /Play \"%L\"" [HKEY_CLASSES_ROOT\mp3file\shell\play\ddeexec] [HKEY_CLASSES_ROOT\mp3file\shell\play\ddeexec\Application] @="wmplayer" [HKEY_CLASSES_ROOT\mp3file\shell\play\ddeexec\Topic] @="System" [HKEY_CLASSES_ROOT\mp3file\shell\Queue] [HKEY_CLASSES_ROOT\mp3file\shell\Queue\command] @="C:\\Software\\MP3Tools\\Winamp\\Studio.exe /add \"%1\"" [HKEY_CLASSES_ROOT\mp3file\shell\Winamp] [HKEY_CLASSES_ROOT\mp3file\shell\Winamp\command] @="C:\\Software\\MP3Tools\\Winamp\\Studio.exe \"%1\"" ; --------- M3U Playlist Files [HKEY_CLASSES_ROOT\.m3u] "PerceivedType"="audio" "Content Type"="audio/x-mpegurl" @="m3ufile" [HKEY_CLASSES_ROOT\.m3u\OpenWithList] [HKEY_CLASSES_ROOT\.m3u\OpenWithList\wmplayer.exe] [HKEY_CLASSES_ROOT\.m3u\OpenWithProgIds] "m3ufile"=hex(0): [HKEY_CLASSES_ROOT\.m3u\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}" [HKEY_CLASSES_ROOT\m3ufile] @="M3U file" [HKEY_CLASSES_ROOT\m3ufile\DefaultIcon] @="C:\\Software\\MP3Tools\\Winamp\\Studio.exe,0" [HKEY_CLASSES_ROOT\m3ufile\shell] @="Winamp" [HKEY_CLASSES_ROOT\m3ufile\shell\Queue] [HKEY_CLASSES_ROOT\m3ufile\shell\Queue\command] @="C:\\Software\\MP3Tools\\Winamp\\Studio.exe /add \"%1\"" [HKEY_CLASSES_ROOT\m3ufile\shell\Winamp] [HKEY_CLASSES_ROOT\m3ufile\shell\Winamp\command] @="C:\\Software\\MP3Tools\\Winamp\\Studio.exe \"%1\""I install to C:\Software\MP3Tools\Winamp\. Adjust to fit your path. I also get rid of WMP options first, as such ;Remove WMP Right Click Options (Queue-it-up, etc.) [-HKEY_CLASSES_ROOT\CLSID\{CE3FB1D1-02AE-4a5f-A6E9-D9F1B4073E6C}] [-HKEY_CLASSES_ROOT\CLSID\{F1B9284F-E9DC-4e68-9D7E-42362A59F0FD}] [-HKEY_CLASSES_ROOT\CLSID\{8DD448E6-C188-4aed-AF92-44956194EB1F}]That's why the regfile includes WMP options. The MP3 files are reverted to their old style icons (blue speaker), and playlists have a winamp icon. My rule of thumb: If you don't need to use an installer, don't. PS: Install winamp on a seperate pc, add all your skins and components, define your preferences, and include them in the new install, so as to do the whole kit'n'kaboodle at once.