Alanoll

i have no idea then. What i suggest is adding things ONE at a time, instead of all at once. It's easier to narrow down where the problem arises.

the problem i see with relative paths in Winnt.sif is that everything that in there gets loaded in the registry, and so there is no path like cmdlines.txt is. cmdlines.txt is a command prompt in essence where as GUIRunOnce is like RunOnceEX, so there is no context from which the source directory is. That would be the reason for the full paths. I guess you didn't like my SETX idea. lol.

uh.... just think about this now... you need a user to logon for those batches to execute. But you want to create a user in one of the batches that requires a user to execute. What user are you planning are executing the batches from? perhaps that answered the question

was I being harsh again? i just really don't like lazy people. Well, I'm lazy, but there is an extent of how much someone can be lazy. and if your gonna point links, atleast make them for the lazy people, don't take out the tt Xtreme would be alittle happier

if there aren't too many, I'd go with Winnt.sif. If there are a few, you could just copy them into your favorites folder. I have no idea about the removing of links though

the point of taskkill is to kill a program that would halt the execution of the setup. The transformation pack may not need it. So you may be able to remove it all together. I'm not sure. But is there a window that pops up AFTER the setup screens? Like Winamp does? If there is, you want to find the exe name for THAT window, and replace it in the taskkill command.

if you used the file from the unattended.msfn.org website, the sfc_os.dll file, replace that in your i386. the then in hivesft.inf i belive, add the line the page tells you (on the website). That will disable WFP right then and there. the process should then go Install Transform, apply tweaks, then renable. The tweaks can actually be done before or after or whenever you want. cleanup.cmd should always be last if it has your delete command. What you have is correct. However, the SFCDisable is no longer neccesary and should be removed when you use the hacked dll. SFCDisable never worked in the first place unless you have a kernel debugger to go with it.

that's what I meant I was typing from memory, and wasn't really sure of the exact syntax, but wanted to give you atleast some sort of idea. however, your taskkill won't work if it is meant to kill the tansformation pack install itself. RunOnceEX doesn't advance till the program executing is finished. You may want to check during installation, what program is actually running, and then use that name instead. and just so you know, I never atually used the batch file method of importing the RunOnceEX keys. I always used INFs. Was cleaner and easier to understand. That and I could have one large INF that did everything for me, instead of half a dozen batches and reg files

as far as I am aware, 2k doesn't support the Oobe folders. i.e. $Docs and $AllUsers hmmm, the shortcut.exe program could come in handy, but it's not in the XP deploy kit, and I don't have the resource kit oh wellz.

@big-gie was that really neccesary? I mean, they're on the mainpage, and I linked the thread at Nullsoft showing the release and the links. was it truly neccesary? @toreach I wasn't meaning to bite your head off your anything. Sorry if you got that. I just don't see the point of posting links all over to the same thing when they're on the mainpage. It'd be like crossposting in different forums, a MOD would come by and tell you not to do it and then delete/close the thread.

@kingroach i posted a bugreport about XPlode not being working in SP2. But it may be a bit before it is fixed as SP2 is still in RC stage, and Wraith is alittle busy lately, and may decide to fix it when SP2 official is released.

when does the file get copied over? if you're running it at GUIRunOnce and copying over, then starting XPlode, you could just point XPlode to use the XML file directly on the network. you could try the /G /K /X one might work, dunno

they haven't updated the mainpage, true true... but it is here in their forums.... http://forums.winamp.com/showthread.php?threadid=174107

hopefully

@toreach the links have already been posted on the mainpage, no need to post the links on a page requesting an MSI be made.

taskkill can be used from RunOnceEX. its a WinXP program in SYSTEM32. as for the porting.... %REG%\KEY1 = %systemdrive%\Install\LHTP4\Longhorn Transformation pack 4.0.exe /S %REG%\Key2 = taskkill.exe /F /IM xxxxxxxx.exe

somehow i KNEW somebody would ask for this! I always thought the main reason behind the MSI's was for the fact of REMOVING the AOD? It's supposedly been removed from the latest build. if so, you could just use the /S switch to install it, then TASKKILL to kill winamp.exe unfortunately, this won't get rid of VIDEO support. Why would you want to? Sure save ALITTLE space, but just don't set the associations and you won't have to worry about it.

you appear to have looked at the wrong section. http://unattended.msfn.org/xp/autologon.htm

this forum is to ask questions, but typically most people can read about the commands in ref.chm that is included with deploy.cab from Microsoft. It is very full of details of numerous methods. It's just i see you asking questions of what does this do, what does that do, and it could be easily answered without posting in that file.

DOSNET.INF as well. d1,(filename) should do you fine if you ever add programs using this method, like oemkrnl.exe or something....be sure to modpe it before creating the ISO or you may get an error about the file being corrupt.

no one said SP2 doesn't work. UpdateXP is a different program, and used for a different purpose. Like i said before, it could also be that SP2 is registering XPlode.exe as a malicious program.

AdminPassword=Null have you tried either searching before asking or testing yourself? Or maybe possibly reading the documention from Microsoft?

have you tried searching yet? those are really well known, and a simple search would bring it up.

you would have to set the autologon check unattended.msfn.org for more details

just because I'm curious.... have you tried creating a custom visual style that contains all the settings you want? You will need a custom uxtheme.dll file however, which I'm sure might be against company policy, but it might get you on the right track to finding the correct solution