GreenMachine
Content Type
Profiles
Forums
Events
Posts posted by GreenMachine
-
-
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...
0 -
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.TXT
I cannot believe that the code is running to the end if the pause never happens.
0 -
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?
only 2 of the type twos are verified for a non running systemTo eliminate any double negative type confussion, I assume you mean that the 2 listed hotfixes are OK to slipstream.
Thanks.
0 -
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.
0 -
Wrap the string with enviroment variable is quotes.
echo Desktop Stuff
copy "%systemdrive%\install\desktop\*.*" "%ALLUSERSPROFILE%\Desktop\"
echo.0 -
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?
0 -
@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.
0 -
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 ...
0 -
Lookin' good. I think HE prefers Creator to Creater ...
0 -
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.)
0 -
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?
0 -
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.
0 -
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?
0 -
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.
0 -
; --------- 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.
0 -
RHSM V2, Cool!
Glad to see you left the fixes in the I386\SVCPACK directory, I feel safer that way.
I should have waited, 'cause I guess now I'll have to go modify my own version of the code I stole from you ...
As you said, gotta be careful with the unsupported stuff. Nice to make it easy, but I don't have time on the clock to do MS's debugging. So perhaps those that know can post a list of good and bad?Type 2 is not official.Thanks for sharing.
0 -
I have seen that others here install and then kill the process once the actual install is over. I prefer the simple method: I just copy all the winamp files and shortcuts to the target machine, then run a .reg file for creating the file associations. All winamp settings are in it's .ini file. (I wish they were all like this ...)
0 -
Windows XP was supposed to have QCHAIN functionality built into the hotfixes, but it turns out that some of the earlier patches do, in fact, still need it. The exact date is somewhere on MS's site.
For info: Hotfixes create a list of system files to replace on the next boot. This list is created in the order the hotfixes are run. If run out of order, an older file version may overwrite a newer one. QCHAIN sorts the list of files to be replaced, putting the files in a oldest to newest order to prevent this problem.
I used this method before integrating the hotfixes into the install, and even if run when not needed, it will not harm the instalation / fixes.
0 -
I believe the settings are not saved until you logoff. Compare a registy export from before the changes, and after the changes + logoff / logon.
0 -
NTUSER.DAT contains the HOT_KEY_CURRENT_USER keys, not the HOT_KEY_LOCAL_MACHINE key.
0 -
Oh, Man, I should never have let you look at my code. In less than 24 hours, you busted my program execution order in svcpack.inf, and now my files are no longer correctly digitally signed!
Of the four type 2 fixes I do, I think two are IE and OE updates. I renamed them to the corrosponding KB article because ... because I'm that way.
I do almost all the critical and recommended upates. When I go to Windows Update, there are only 4 (was three until a couple of days ago) recommended updates: (I just checked: now there is a new 5th recommended). These are: Journal Viewer, Windows Messenger, Advanced Networking Pack (Q817778), and now Windows Right Management and KB822603.
I wonder about the sp1.cat file. It would help to know how the installer works: if t finds a newer version in I386 (newer than that inside the cab file), could it use it instead? Even if it does not like the versioning, there is only one single version in the possible multiple copies. so what's it going to do about it? The newer versions do have a signature somewhere, in some .cat file. Could that be found?
On a side note: We build the svcpack.inf file. What about adding everything else there as well: Java, WMP/MM, IE6.1, MDAC, RegEdit /S?
Also, perhaps when building the svcpack.inf, list the directory by date in the loop to create the file names, after having merged the two types of fixes.
0 -
@RyanVM: For Q823980, the original Blaster Patch, this was the case. (Thread Here) It's only one example, but one is enough for me. I, too, remove all remaining uninstall keys. Note that the above example has been superceeded with another, so it is no longer "active", but I am no longer silly enough to believe I won't see this again. Burn me once, shame on you. Burn me twice, shame on me.
0 -
Frustrating, isn't it? I would say from the looks of things, you have us all stumped. The syntax looks fine to me. I can only offer you some hints for further debugging:
Seperate the commands, perhaps with a pause in between, to determine which of the two is guilty.
I have it working on my system with this code:
NET USER SysAdmin SysAdmin /ADD /COMMENT:"System Administrator Account" /PASSWORDREQ:YES
NET USER User User /ADD /COMMENT:"Local User Account" /PASSWORDREQ:YES
NET LOCALGROUP Administrators SysAdmin /ADD
NET USER Administrator /ACTIVE:NOReplace yours with this, and see if that works (Perhaps Sky and Windows do not jive - anything is possible at this point). (Pay attention, my code disactivates the administrator account, and creates the users SysAdmin and User, both with passwords. But DON'T modify my code, as it works, and in doing so you are adding one more unknown to the debugging. After you get it working as I have it, makes changes one at a time, until you find the error.)
Open a command prompt in the setup, just before the NET commands:
START CMD
Try your commands, either by stepping through the batch file from one pause to the next, and see if anything is happening in the Users List - You can get to the Local Users and Groups Snap-In as such:
From the command prompt, type "mmc" (without the quote - same applies for following examples)
This will open a Microsoft Management Console.
Select File - Add/Remove Snap In.
Click "Add" in the new window.
Select "Local users and Groups", then click "Add".
Select "Local Computer" and click "Finish".
Click"Close".
Click "OK".
You should now have the familiar Local users and Group Snap-In running in the console.While you have the command prompt, try anything else you can think of...
Now you've got me curious. Give some or all of that a try, and let us know what you discover.
0 -
It's the "pretty sure" and "should" that worry me ... If a problem should arise, you are at a handicap from the start in determining the cause, and I am not a fan of debugging Windows.
Windows Update has also been known to rely on the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall key do determine if a certain hotfix is present.
I am not trying to belittle anyone's ideas, but as neither Windows nor their HotFixes are known to be the most stable, and I have no desire to increase that instability.
0
cmdlines.cmd
in Unattended Windows 2000/XP/2003
Posted
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.