Wraith

Nah, nobody does that.

I fyou're running off the CD, then you'll notice that #SOURCEDRIVE# is mapped to the CD itself. So if you have your apps in CD:\Install\Apps\..., then you can use #SOURCEDRIVE#\Install\Apps\... etc. etc.

Just the usual poll... what the hell do you people want?

Look, if you're not going to make an effort to attempt to learn how to use it, then nobody should make an effort to help you. I've had enough of the bitching. Topic closed.

Nice work. Just been mucking around with Flash, set this up... Obviously adding animation and whatnot isn't terribly hard, maybe I'll clean the javascript up and attach it later.

Sorry, I replied before you edited the post. I don't see anything wrong with the XML, the logfile is complaining about unable to find fileio-rmdir - there is no XPlodeFileOps.x4e, so naturally, there is no file commands accessible. I assume that your problem is the non-deleting stuff, because everything else looks fine. Just put the fileops plugin in and see if it works then.

...

Can you make a logfile please?

Try reading the sample XML's. They are fairly self explanatory, and help you to understand how the documentation ties in with it. With both the XML's and the documentation side-by-side, you should be able to work it out with a little effort.

Never mind.... Alanoll saves the day once again... the first two lines were the culprit...

Soooo... I get the error in the attached images... Any ideas? I know it's XPCREATE, because the XPSP2 source I'm using works fine normally. Been a while since I've used XPCREATE... what files should I be posting? (Error typed out for search purposes if other people get it at some point along the line... the attachments may not always be there,,,) Fatal Error An error has been encountered that prevents Setup from continuing. Internal Setup data structures are corrupted (phase 0). Press OK to view the Setup log file.

There is a reason why it's an executable. Doesn't take a rocket scientist to figure out what to do with it.

Not really, you download XPlode from the site again, and it'll work for another three weeks. It doesn't expire because you've extracted it - it expires regarding the build date. And the syntax won't change, so even if you write it for this version, it will still work for the next.

It was mainly put there so people could hide windows before XPlode launched, and for running shutdown.exe after execution, depending on how people have set up their XPCD's...

I forgot to add - if you're wondering why there is so little difference between the "free" and "corporate" versions, I had to remove a couple of things from the corporate version due to some buggy code. Needs a bit more testing before release. I won't say what, because it may take some time to get rectified.

$10. The reason I chose the three week limit is this - I have given out just over 120 corporate test license requests since I took XPlode 4.1 off downloads, and assuming that only 2% of them decide to pay for XPlode, that means that I should have had ~4 clients. There have been nearly 20 academic licenses granted. Guess how many corporate clients? That's right, you got it, 0. Going off the response from you people, XPlode isn't such a bad product. So to me, those numbers seem a bit lop-sided. The conclusion: the "corporate" version was too easy to download, and ignore the licensing. From other "hobbyists" I have talked to that have used XPlode, they are content with rebuilding their XPCD's whenever they need to format, and hence, the free version of XPlode would suffice. They get their config working, download the latest build, burn it off, and they're good to go. I'm sorry if that has turned you of XPlode, but it is being developed essentially for no benefit of my own - with the amount of ungrateful responses regarding the EULA, I have little problem with making XPlode time-limited. That said, I have no problem providing a free non-restricted version to prominent members of MSFN - they've given back to the community, I have no problems helping them out too. I'm sure that down the line, they've helped me with something in particular.

Indeed. From experience, 99% of the hobbyists that use XPlode rebuild their CD's just before they format. Thus three weeks will suffice. That is, assuming you build your XPCD the same day as an XPlode build. XPlode will be rebuilt each Wednesday morning here, and I'm sure everyone's figured out how to tell what date XPlode was built on.

Get it here: http://xplode.voidfx.com/ Check the changelog in the docs for more information. As is always the case, post bugs at the bugtracker: http://bugs.voidfx.com/ Original install plugin: GFX Install plugin:

I have no problem with people who want to share their configurations, I just object to redistributing the executables.

.... yeah? this to the sideways xplode???!!!111oneoneone

.... so, you have XP installing from CD in the location: #SOURCEPATH# = 'D:\I386' and XPlode is placed: #XPLODE# = 'D:\SingleImage\XPCD\$OEM$\$1\Install' .... does anything seem wrong to you?

I have another idea. And it'll be done soon. Hopefully.

You'll have to wait until XPlode 4.2. Hopefully tonight sometime.

Yeah, that is pathetic. And they just postponed the release of XPlode 4.2, which I had planned to make available this afternoon. Oh well, doesn't worry me. I don't have to wait for myself to release it. *wanders off to format*

XPlode always makes #XPLODE# the same directory in which XPlode.exe resides. If it has the directory in which it's stored on your HD, then you must be running it from your HD. XPlode should have no knowledge of the disks outside the VM, so you must not be doing it properly. How are you running it? From CMDLINES.TXT, it's from your HD, not from the $OEM$ folder. Don't mix and match logfiles and setup scripts. Nobody is going to be able to help if you're posting conflicting data.