Alanoll

basically..... Go to the "Addiging Hotfixes and Current Hotfixes" page. Look for the XP section, and then go to the Microsoft website, and then download the hotfixes. Just ignore number 5 for now. Till you have a working one without adding anything, it just complicates things.

you made the boot sector wrong. Simple as that. Broken paths, or the like. When editing the file in HEX, be sure to use CAPS

SourceDrive is a variable only available in XPlode, and no where else. Even if you call a batch file form XPlode to use SourceDrive it won't work. It's only available in XPlode.

Slight error on my part..... it isn't %SourcePath% , it's %SourceDrive%

is there a swflash.in_ on your original disk? if there isn't, it would explain why it can't find it. But if that's the log that was created, and you DIDN'T extract it from LOGFILES.CAB, then you're using an old version of XPC

reminds me vaguely of the Add/Remove thing in XP. what would be really cool, would be icons too. I wouldn't think the skinning thing would be neccessary since it would depend on teh active Visual Style of XP. So that's alittle less work what were you planning on adding? This would be a good program for people having a seperate disk to install stuff from. You made a program you don't use? (XPlode) cool. how's teh sourceforge site goin?

mmkay, you're new one has the same paths as the old one. Like I said before change %Systemdrive% to %Sourcepath% as for guiding you without copying files over.....you XML file should be fine....however....XPlode.exe to not be copied, I would suggest you look at the link in my profile, and READ. Everythign still pertains to XPlode, but it just has XPInstall in it.

what you posted is correct. Think of it this way, all those registry lines, aren't getting executed till that rundll32.exe command. They're just getting imported and saved.

I refering to line when you actually call XPlode. not in the xml. Xplode.exe /log:%systemdrive%\xplode.log as for the variable, use SourcePath If your new XML has the same paths as the old one, just replace SYSTEMDRIVE with SourcePath

there's only one way to find out I don't forsee any problems. the setups are like 2000 and XP's comparatively. Just different files being copied, but same routine. but personally, I suggest using a 98 bootdisk then a ME. Never liked ME. Never had anything to do with it. Installed ONCE, and within the hour was back on 98. lol.

you want the German version right? these are the languages I see for the bundle pack Link: http://oem.microsoft.com/script/contentpag...17953#DOWNLOADS You'll have to log in.

that is indeed strange. Especially if your original disk gets it too. Are you sure you're using your ORIGINAL and not another CUSTOM one? The original shouldn't have that problem. Especially if it came from Microsoft. Doesn't sound like an XPCreate error to me.

gooood. I really think alot of people don't ahve OEMSETUP.EXE on their disk, so they just use SETUP.exe and never run into the problem. Or they just used SETUP.EXE anyway. OEMSETUP.EXE is good for partitioning, but it doesn't allow for the option of which partition or the like. And it's quite stupid evidently with it's source

in your command file that does the import of all the Registry keys for the RunOnceEX add this line at the very end.... rundll32.exe iernonce.dll,RunOnceExProcess

well, actually....I don't really have all that much on my plate at the moment. Just finished a few projects I've been working on. But if I were to even considering trying to help, I would definately need more information then what you've provided. But it does sound as if ALOT of the questions you may have are answered on the website. It's in the signature. Also, if you did a few simple searches in REF.CHM (in the deploy.cab file on your XP disk, under Support\Tools) you'll get some good hits.

@Jedi you slipstreamed SP1. But the program is telling you it is RECOMMENDED not NECCESARY to slipstream SP2. You can leave it at SP1 and it will be fine. Define dangerous. If there are drivers taht could concievably be needed later on, then maybe. Otherwise no worries. Also, you don't need multiple ?'s. One will get the point across that it's a question

change the line Setup.exe /K "/IE /NF"to Setup.exe /IE /NF

i understood about this much of what you just said... yup, that's about it. UPDATE to the latest XPlode. Do this first. recreate your XML for the new version. READ, it's pretty simple. Also, is PostInstall going to be at the root of your CD? Take THIS into consideration, since if it is, it won't get copied over so SYSTEMDRIVE ISN"T THE APPROPRIATE VARIABLE. When running XPlode, add this line at the end of your execution string /log:%systemdrive%\xplode.logsee what errors come up.

oem.microsoft.com

no prob. no point having multiple different versions up for people to get confused. Good thing you didn't update while he downloaded mine (In case anyone was looking for the link, I've already removed it, and the file on the server)

wow. Have tried using just SETUP.EXE instead of OEMSETUP.EXE? format before that.

you lucky bastard......

good, it works. .NET is no real problem. I'm sure when I use the program, it will be just before I format anyway

if you wanna use some logic on your own.... http://unattended.msfn.org/xp/applications/innosetup.htm there are others, just highlight "Unattended XP CD" at the top, the "Applications" then near the bottom a few basic installs.

too bad it's using .NET framework. for some reason, I never really liked the framework. But it does make coding alot easier.