well, there's your problems. I take it you burn XPCD to a CD? if so, then ALL your paths ARE WRONG in your XML file, so it errors out. You're PostInstall folder is not on #SYSTEMDRIVE# as it's at the root of your CD not your harddrive.
helps to know what you're doing. Files, how you saved your XML, what version. Little tiny details like that. Also try to use /log so a log is created. You need to specify the full path.
i meant, was there a reset between installation of the video drivers and the capture? Not chained one after the other, but let there be a full restart in between.
was there no driver letter ECHO'd? file not found for findcd? did you add it to the Win98 image. you don't have to modify WIN51. It's FINDCD.EXE that you have to modify. Post screen shots?
latest version is XPlode 1.1.2 i think. It's in the sticky. XPinstall was the old name, till it was brought there already was a program called XPinstall. what do you mean by GUI mode-window?
are you using the EXACT things I am? in your AUTOEXEC.BAT file, just after FINDCD.EXE put ECHO %CDROM%PAUSEPAUSEand see if it displays the correct CDROM
yes, follow the instructions.....you will get it. It will download all the little individual files that are neccesary, if you'll lookin for one package with it all done for you, you'll either have to do it yourself, or ask, or search.
oooh, you don't have the drivers... you would go to the manufacturer's website, and download the drivers. Then extract them. Typicaly there is an setup.exe and then drivers folder. THEN reference back to the link I gave you.
@mukeshnuna typically, its the folder that is labels XP in some sort of way, with an INF file inside of it, and some DLLs along with it. http://unattended.msfn.org/xp/drivers.htm
the easiest thing to do, might be the CDShell way, but then you'd have to work out the specifics as that stucture isn't neccesarily like the multiboots you'll find here. However, it does look like it includes the ISOs as well, so you could start with those if you start with CDShell.
I've expierenced that cmdlines.txt does not like variables. Sometimes it does in PATHS in the arguments, but not in this. A work around... cmdow @ /HIDstart /wait %systemdrive%\Install\Xplode.exeEXITsave that in $OEM$ as say....xplode.cmd and then in cmdlines.txt that is also in $OEM$ [Commands]"xplode.cmd"Link to cmdow http://www.commandline.co.uk/cmdow/index.html
hmmm it might not be too large after you create the image with CDImage. Might bring it right down to size. could you take a screenshot of the directory structure? I'm just curious about the disk. but without looking at it directly, I'd say 00 might be your best bet. OR, you could use CDShell and created your own menu, and then jsut download the boot files for a normal disk. It'd up doring the same thing, just with CDShell and then you could make it look like whatever you want.
the partition is most likely hidden, not encrypted. I thought by license, OEMs had provide a WindowsXP disk? without any of their junk on it. I believe that all those recovery disks are, is either a "ghost" image type partition (where is just copies the files over, and everything is back to square one) it is some sort os sysprepped. I got no idea how to just get WindowsXP out of that without tinkering withit my self. But i also don't believe you broke any rules (But this is just another reason to build your own PC and then buy the software)
unless you have a completely seperate PC (like me) then you may want to use VMWare or VirtualPC. Then no burning, and no restartint, and no not doing other stuff ont ehc omputer. XPCreate : greenmachine.msfnhosting.com/xpreate
anyone search? Anyone post in a thread that doesn't have the titile "Completed XP Setup Screens" Font size is in winntbbu.dll Color is in hex, and you have to edit so other file (search for it) As is the "Setup will complete in" text. It's in sysetup.dll or something like that. maybe one of DLLs right next to winntbbu.dll