Alanoll

for the updates, the easiest thing for you to do, as a beginnner may verywell be to use XPCREATE http://greenmachine.msfnhosting.com It's a program created by GreenMachine, and it autodownloads ALL the updates, and adds them to the Install the way Microsoft has in the documentation. Just put in your disk in your CDROM, edit the included INI file to reflect the location (read the site for more options) and double click the XPCREATE.CMD file, first time it will create the directories and exit, second time, wait for 30 minutes to 1 hour, and you're CD will be completely updated. As for DVD, just think of a DVD as a REALLY big CD. Everything is the same. XPSP1 can be ANY version of XP. THe only things that might be different is stuff in the Winnt.sif file, which you create with the setupmgr.exe program anyways.

i don't think it's anything on your end.... It may be a hiccup in the server again, or for some reason the list is in the wrong place...

who's to say that SP2 marks the end of the beta builds of nLite? nuhi's time tables don't revolve around when it comes out.... also..... please post in the proper section...as SP2 being released is NOT directly nLite related....

as for starting.... assuming you have Software in the root of your CD, and CMDLINES.TXT in $OEM$ it would actually be.... [COMMANDS] "..\software\wihu\wihu.exe /skipautorestart /autoinstall 0" as for the commands to the software, I believe if you just have \Program\setup.exe it will find it... if Program is in the same folder as WIHU

I"m guessing his friends machine was an OEM edition, as he had that little sticker at the bottom, and those don't come in the retail packs..... For legallity purposes, you could atleast contact either the system supplier or Microsoft for a replacement disc. They may charge for replacement parts, but it won't be anywhere near the cost of buying a retail copy in the store to replace his lost OEM copy

i should point out, that theoretically..... up untill Wraith changed the extensensions (you could maybe change them back) you could replace the old plugins with the updated ones, without replacing the kernel of XPlode.

by the way.... did you not read what I posted about the <hidewindow> tag? IT ONLY HIDES WINDOWS THAT IT FINDS IN THAT SECTION THAT ARE RUNNING WHEN XPLODE/XPINSTALL IS STARTED. Sorry for all the caps, but had to get the point across. As for actually hiding them, you'll need to find their individual switch if it has one to do that.....but it's not a function within XPlode/XPInstall

well, I put DX9 and your workaround in SVC-PRE. That folder, the files are just copied over to the distro, added to SVCPACK.INF and switches /Q:A /R:N are added.

why did you open a new topic? why oh why? NOT NEEDED. What OS are you trying to do? Windows 2000, XP ,2003? YOu have totally disregarded what I've been saying, and I"m contemplating not even trying any more. YOu have yet to post what I requested to try and help you. Screenshots, and possibly even your hexed files.

if you look at the thread "SOLVED: DRIVERS FROM CD" in the drivers forum, the guy there made a program that creates the paths and whatnot, and adds it to that key. So I guess it would be possible.

@Tobe, I have no problem running this workaround with XPCREATE. I rename it so it runs AFTER DX9 is installed, put it in SVC-PRE and it works fine.

alright..... look.... CODE ERROR5 is a problem with booting the NT shell, NOT CDSHELL or ANYTHING IN WINDOWS. It can't find certain files.

sweeet... is that in the latest XPlode or the one your currently working on?

it could be you don't have your theme and associated files correctly placed.....

the Gosh Method? Reducing Source and then adding it to Multiboot?

just make your own. Look in the nLite forum, there is a post by RaveRod showing where and what you need to edit in the uxtheme.dll file to hack it for SP2, then do what the page says, and you're done. Or you can get a SP2 uxtheme.dll file for YOUR version of SP2 and do what the page says, and you're still done.

alright, that's what I get for leaving the board to go to a Drum Corp show..... jrzycrim is correct. It's just he Microsoft .NET Framework Don't ask where to get 2.0 though, it's still in BETA

#XPLODE# is XPLODEs current directory, and depending on how you execute XPlode, it will work like you want. #SOURCEPATH# is the entire path to where Windows was installed (\\Netshare\WinXP, just an example, could be CDROM as well) #SOURCEDRIVE# is just the drive letter and colon where Windows was installed from. All XPLODE specific variables, can ONLY be used within XPLODE (or it's commandline arguments /log and /xml)

gets I better get out the old IRC proggie.....

it's called selected.ini and it's in your nLite directory.

XPCREATE is the same for XP and 2000 and 2003. Same program. Check in his download section, the link right below his XPCREATE link, there is one there called MAKEIE. Check that out. It may be easier to just use XPCREATE as it then also adds the latest hotfixes as well.

what did you select in nLite? If you wish to post your INI file, do ATTACH it, not copy paste.

It's not CDShell.... It's something when you modified the files.....

i just PMed him a link to a proper uxtheme.dll file....hopefully that works.... I'm still opting for either the theme is copied over, or there is a problem with the theme itself (Bad path or something)

OEMPreInstall shouldn't be under GUIUnattend also make, sure that if you are installing from CD, $OEM$ is along side I386, while if network share, or whatever it's inside I386. Try putting a pause within install.cmd, to see if it actually runs. As if you don't have any error checking stuff, and it can't find ANY of your installation files, it will just ZIP right through, and depending on the speed of your system you might not see the window (I don't) Are you drivers DigitallySigned? If not, they most likely won't be used, even if you disable DriverSigning. DriverSIgning just lets you use NonSigned drivers without that little prompt to make sure, it does not mean it will use the driver above a signed Windows Generic Driver. It's stupid, I know, but that's Microsoft. Also, Make sure the paths point to the folder containing the INFs for the drivers. And then there are those picky ones that require then installation method using their setup routine to work (My printer)