Alanoll

if you see the screen with the logo saying "Please Wait" that is NOT the kernel, it is rather OOBE running in the background. I wouldn't recommend changing the kernel until after first boot, as there might or might not be a few check. On another note, ntoskrnl.exe is the single kernel, ntkrnlmp.exe is the multikernel. I would recommend NOT replacing the kernels as they're named on the source (in I386) but to rename them like you have. Without knowing the error I don't believe I know what you're talking about Thanks Aaron for forwarding this

try... XPSP2.exe /X Then go to the update directory and type update.exe -s:C:\XPCD are you trying this on a W2K or XP or 2003 system?

you could go to the store

you do indeed need a modified DLL for that key to work, or you need Kernel Debugger.

http://www.msfn.org/board/index.php?showto...indpost&p=78558 Who doesn't remember Gosh? But they are a part of OOBE or something related to OOBE.

does no one read anymore? or do I have a really good memory? @prathapml In an untampered setup of SP2 RC2 build 2149, the files I places in $OEM$\$Docs were indeed copied over. But I should point out, they are copied over fairly late in Setup. Perhaps at first logon. Wasn't checking that closely, I stopped checking at T-13. But the files were there, so there you go.

see, now here you go trying to get me to slipstream my XP disc with a copy of SP2......if someone doesn't get there before me, I'll test it later....on an unmodified copy of XP.

If you use All Users folder, then there won't be any misnamings.....that would be my guess for the purpose of $Docs

the real question is, did you disable/remove OOBE? $Docs and $Progs aren't really part of the OEM PreInstall, but I believe more of a part of OOBE.they're copied over during GUI setup (the Blue windows screen, with those annoying ads) instead of txtmode.

because no one has any objections I changed it that way.Benjamin sure....right when I finalize the current incarnation of the disc, you come up with a new beta version.... looks like I'll be testing two programs on the next one, nLite and this

the old ones /q /n /z and whatnot are supposed to become legacy switches. I thought I read they'd still apply, but they won't be the visible switches in the /? window. I personally like the "legacy" switches as they're smaller and you can't mistype the word

Good bye cruel SVCPACK.INF file....how thee wilst be missed.... The thing I'm interested in knowing, is when it is final and it's to the "80 meg" size that's supposed to be the released, I wonder how much of a space difference it's going to make......

@mike503 Sorry, I got you and RuNnaH confused on the XML bit. I thought you were the one posting the image, but either way it was the Neworking Pack. RuNnaH is using XPlode so his is XML. My bad..... but you are right on the kiss a$$ thing. There really isn't a need to post that But atleast Solid did learn his lesson from his mistake the last time he thought he was sure. Did you get it working?

lets not forget the one hotfix that uses the latest installer with the /integrate switch It's all difference versions of the hotfix installer, but except for the Type 2 hotfix, they should all be able to use the same switches as Type except for the ones that don't use the update.exe to install (MDAC for example)

Sorry what was that again? I knew it was the advanced networking package that caused the error, but you didn't read the post... But....then again, you did say you ran it from GUIRunOnce, but as I said, user error. It may be an error in the XML your using...never know. But that'd still be user error Looks like I was right, right?

it gets the files from it, as specified by the INFs listing in the setup source. If you add stuff to it, setup does not know what they are as it does not know the INF file that tells it what it is.

I should point out... you're slightly incorrect. There is not a type 4 hotfix yet, as that is about to start beta testing. type 3 is only in ONE hotfix, and the only difference is a /integrate switch the switches may look different in your "type 3" and "type 4" but they are truly the same. Notice the only diffence between your "type 4" and "type 1" switches is a - instead of a /. They're the same switch. HighMat isn't really a hotfix though. It's added features like WMP9 and the Networking Package. Same with .NET. Good find on the DOTNET by the way. If you're interested in a bit of reading... http://www.microsoft.com/technet/prodtechn...t/winupdte.mspx or here http://support.microsoft.com/default.aspx?kbid=262841 (the types here, that I and most others refer to, are the different types of switches, as opposed to revisions of the update.exe)

it's because you're probally not including the INF files in the path. The difference between the $OEM$ method and the other way you're doing, is that you're assuming that just by putting the driver files there, it will look for them there and know how to use them. You have to inlcude the INF file, and most of the time, will require to be edited. Most INF files are in %windir%\INF and that's in the device driver search path. It's not a bug, it's user error

by god.... just set DLAUTO=NO in the ini file, download SP2 yourself, and put it in the SPACKS folder. After that, remove all updates. Add what you want. **You have any problems, don't come here complaining some update didn't apply. Use at your own risk** @Virindi Instead of supporting SP2 (till released anyways), just give this. It's alot simpler and then clears your hands

regsvr32.exe /s (FILE)

Well, I'll be...someone linked to one of my posts..... Thanks mazin, saved me from trying to type it all again

@SolidasRock Ah but you didn't say it now did you? And actually, it's KB if it's a knowledge base article that got addressed. The name really shouldn't have any difference. I rename all mine to just the numbers for simplicity. Haven't had a problem.

I see it a few times, but not with multi-word searches.

ditto, it's always good to have descriptiong....except for when it's [Nero] [*]Install Nero like it is now

whoops, need to be clearer It waited at the screen to press Next at Installation Selection. I used the AutoInstall switch (i believe, I double check when trying to recreate it later, don't have the source files or the drive to burn the ISO) As for the tree structure.... I would think Subtree 1.2 shouldn't be deselected, if Subtree1.2 is it's own command. However, if Subtree1.2 didn't have a command, then it would be deselected. Using the nero example from the other day, if Nero install was Subtree1.2 and the unregistering of the codecs were the sub-items, then by deselecting all the subitems wouldn't stop Nero from installing....