Wraith

I do my installations off a network share after first boot. Manually. I don't have a specific need to place them on the CD, nor copy to the HD. As for XPlode in the root directory, I have no idea. It's been over 6 months since I've even looked at windows installations, and I never did mine through cmdlines.txt anyways. Anyone else know?

# was added because certain variables (%XPLODE%, %SOURCEPATH%) are handled by the commandline, rather than XPLode, depending on how you call them. On the command line, these would be set to a blank string, so it screws s*** up. Using # works fine there.... In the XML, both are interchangeable.

Front page of site updated. And something of interest - commands will now be able to be executed under a different user's context - not limited to just executing things as another user - can copy files, etc. etc. under another account. More information will be added later, but essentially it means there's no reason why per-user settings can't be done without manually running programs.

Try it.

Actually, it's more due to the fact there was no documentation written for it, and I haven't touched it in over 6 months. 'There *should* be docs done for XPlode3, so.... we shall see. Also, good work on that setup screen.... haven't seen too many minimalistic ones... that one is cool

Yeah, there is... but I don't remember how. Anyone?

If you find out the exact problem, please post the fix. I've had this prob for ages, but no time to figure out why. I usually just set it to install, and go do something for a 3-4 hours... it's usually only just completed by the time I get back. And yes, before you ask, I've been using CDIMAGE.

You should theoretically only be able to do so if you have 64-bit drivers. This has been the main issue with me upgrading, as finding usable ATi XP64 drivers is all-nigh impossible. At least, it was when I cared about trying XP64. 32-bit is doing me fine for the moment...

And if you're interested as to what Qyoob2 is: http://space-eng.voidfx.com/uploads/2004-1...0Pics%20Upload/ Don't blame me for the pictures... I didn't take them...

Nah, don't bother. Just say you are, and they'll be none the wiser Works for me

The new domain has already been set up - I just haven't had the time to move it over.

The XML parser was done last week, so I'm ahead of schedule

Can you remove the link from your post now that that site is back up? And in future, ask me before providing a mirror.

Yes, I know you can't download it. Yes, I know the server is down. No I won't be posting any alternate URL's. I've switched webhosts - the old one is a **** joke. I have NOT moved everything over. I don't have time to do so. Give me a couple of weeks and I'll see what I can do.

Yeah well, has to wait - I need to finish Qyoob2 first.

No. The %'s will be parsed by the commandline, and may end up being blank in the cases of XPLODE and SOURCEPATH etc. The #'s are to not let the commandline parse it, but XPlode will. # and % both work in XPlode, it's just that the % versions may not get sent to XPlode by the shell.

XPlode2 isn't finished, and a heap of things aren't done the way I really should've done them in the start.

As you know, there have been delays left right and centre, nearing the amount Valve has had with HL2. As you may or may not have noticed, I've decided to make an XML creator to go along with XPlode2, so the n00bs can have a chance at getting something right for once. Unfortunately, to do this, I'm going to have to rewrite XPlode again, and start from scratch. You lot are going to love it. XPlode3 will be the next version. There's going to be a large enough difference that I'm just going to split the codebase and start again. Anyways, here's the current schedule for XPlode3: November 22: XPlode3 silent install module (done) December 4: XPlode3 core module - XML parser (done - finally supports both ASCII and Unicode) December 4: XPlode3 core module - Data storage (done) December 5: XPlode3 full display module December 6: XPlode3 effects modules Other stuff will likely be added, and dates changed. You know how things go. Oh, and another note, I'm more likely to work on it if there are some incentives.. (think about it )

I guess it's settled then. The hunter will be hunted. Or was it the creator will be created? Hmmm.

Some people don't understand how 1 + 1 = 2. Who knows. Expected timeframe: 2 months. University is taking up a lot of time at the moment, so I get only a few hours a week to work on XPlode. Kinda annoying, but that's life. *BED*

Alright, I suppose I'd better tell you all what's really going on with XPlode2. I've been throwing around some ideas, mainly to do with automatic generation of the XML. I know I've said in the past that I would not make such a tool, but obviously some people are unable to grasp the whole XML thing, so I figure I may as well. The main reason for the holdup of XPlode2 has been my wanting to embed the documentation inside each plugin, and getting a usable way for this creator to tell the user what its capabilities are. Essentially this XML creator will be able to write the XML, and have the documentation for that plugin as you're writing it. It *should* also stop people from having problems with syntax and the unicode issue. Anyways, I know you've all been hanging out for it, but you're going to have to wait a while longer. I've added a poll for people to vote whether they think it's a good idea.

XPlode2 is weeks away. The display plugin is about 40% done, and none of the action plugins are written at all. So basically XPlode does nothing, and only does it halfway It's easily a month off.

So I guess 26 - 19 means I finish XPlode off... Bastards. Lets hope I have some time in the near future... stupid university. A *big* help would be people writing modules. Anyone up for it?

It runs fine on my Athlon64. Unless you meant that it'll run ONLY on them. Dunno

Pretty self explanatory.