Wraith

Yes, I know. The datacentre where my site was being hosted seems to have disappeared off the face of the planet. So I've been bitching to them these past 3 days about getting it up and running, and responses are getting fewer and farther between. It's looking more and more like they're just gonna shut down and take my money with them. Remind me never to get hosting above and beyond the cheapest ever again.

You can already do that. Can't just use pskill or something? Can already do that. You'll need to explain further. I'm not going to add support for dependencies - this tool wasn't really intended just to be given to people who have no knowledge of how the software works. The plan was for the sysadmin to install what they need, and hence, should know which to install when. Same reason as the previous response - if you need multiple setups, either handle it through the include tags I've added recently, or figure out a way to copy a specific XML when starting the installation. No time. Sorry. That has been on the cards since I started the new plugin system in XPlode2. At this stage it's not a priority. The main reason for this thread was for SYSTEM functionality suggestions - editing registry, moving files, etc. etc. At this stage I'm looking for more things along those lines, rather than adding stuff to the core module. We shall see about other things later.

Save it as Unicode, not UTF-8.

@prathapml: That will be dependent on the display plugin used - at this stage I'm thinking of going with creating both the original XPlode and the XPlode2 layouts - the latter supports named colours by default (IE HTML renderer). @drew: I've been writing the guide this past 24 hours, while I wait for people to give me ideas ;-)

Post them below.

Something you people might find useful: <XPlode3> <items> <include file="#XPLODE#\#COMPUTERNAME#.xml" /> </items> </XPlode3> I'm sure I'm not the only one who can see potential in such a setup. Including files is working in my current development copy... may put it up for download and/or testing soon. ----------------- Long version: XPlode3.xml: <XPlode3> ... <items> <item display="test1"> </item> <include file="#XPLODE#\#COMPUTERNAME#.xml" /> <item display="test2"> </item> </items> </XPlode3> Hailstorm.xml: <XPlode3> <items> <item display="test3"> </item> <include file="#XPLODE#\#COMPUTERNAME#.xml" /> <item display="test4"> </item> </items> </XPlode3> Logfile: >>> Log session start at: 04/12/04 16:59:20 XPlode3 { Parsing XML: d:\Programming\XPlode3\bin\XPlode3.xml { Environment variables { ... %COMPUTERNAME% = 'HAILSTORM' ... } strings { } tokens { ... } Display module: d:\Programming\XPlode3\bin\XPlodeFullDisplay.xip { } Items Block { Item Block { } Parsing XML: d:\Programming\XPlode3\bin\HAILSTORM.xml { Items Block { Item Block { } Item Block { } } } Item Block { } } } test1 { } test3 { } test4 { } test2 { } } >>> Log session end at: 04/12/04 16:59:20 Note that it doesn't include itself. Not sure if I want to check ALL loaded XML's or just the current. Will see if it's needed later.

OK cool. Sorry. Same sort of message as above, so all is well.

Yeah, they should be translated - XPlode uses a system function to get the error message, so all is well. At least, I assume that the translation was correct.

Okay... here's the first batch of tests we're going to start. At the moment, I need people to test the core module. Nothing terribly interesting, but it needs to be done. Check it out at: http://xplode.voidfx.com/testing/ Post any errors you may be getting below. You should end up with a logfile very similar to this: >>> XPlode3 session start at: 04/12/03 17:58:06 XPlode3 { Parsing XML: D:\Programming\XPlode3\bin\XPlode3.xml { Environment variables { %ALLUSERSPROFILE% = 'C:\Documents and Settings\All Users' ... ... %XPLODE% = 'D:\Programming\XPlode3\bin' %SOURCEPATH% = 'G:' %SOURCEDRIVE% = 'G:' %TEST% = 'This is a long **** test of something & something.' } strings { } tokens { AccessToken::LogonUser(Spike) failed - Logon failure: unknown user name or bad password. AccessToken::LogonUser(Jet) failed - Logon failure: unknown user name or bad password. } Display module: D:\Programming\XPlode3\bin\XPlodeFullDisplay.xip { } Items Block { } } } >>> XPlode3 session end at: 04/12/03 17:58:06 If not, then I will need to speak with you. Get testing people!

Schedule updated... you might find that this week it's a little more aggressive :-) At the moment, I'm contemplating releasing XPlode3 without the XML creator. With my current work commitments, there's going to be little to no time for me to work on such a thing, so at this stage, it's going to have to be left out. I've also made a final decision regarding conditional statements... and they will not be put in. There's no real need for me to do so as far as I can tell, and creating the syntax for such a thing is going to be a major problem.

This is a known issue, and at this time, I'm unable to find a reason as to why this is happening. I will be speaking to you regarding testing XPlode3 in the near future though.

<execute display='Extras' program='net' arguments='user aspnet /delete' hide='true' />

You could always do a net user blah /delete command, with the hide="true" attribute. That way the command window wouldn't be shown.

It also searches %PATH%. Err. n/m. I didn't read the other post.

No chance right now, unless you want something which has no visible function There may be an opportunity soon, for testing purposes, proper functionality will be implemented later.

Just thought you people might like to know, I'm moving over all of the XPlode stuff from my old hosts, to the new hosts, tonight. So, if you see this topic, chances are everything has been moved over, or will be done so soon. If the site is still unable to be accessed on Sunday night, then post below. --------------------------------------- Update: Test #1: http://xplode.voidfx.com/ Test #2: http://www.voidfx.com/xplode/ #2 *is* working, if #1 does not look like #2, then your DNS servers haven't been told of the change. Give them a few hours. In the meantime, the second site works.

Explain your concept of "variables". As for encryption - nothing as of yet. For the moment, if you don't want people to know passwords and whatnot, delete the XML once you're done with it. Querying file versions etc. is no point as of now, without conditional statements. Implementing them would just convolute the scripts more than they are now. If there's an overwhelming majority of people that would like them, then there may be a possibilty of working on them.

Chirstmas might be too early - I now have my first full-time job (shock, horror! ), and finding any motivation to do MORE coding is a bit hard at the moment. We shall see. Actually, I'll try and get more stuff going tonight.

Put username="blah" password="chunks" in the execute tag. Obviously you'll need to change this to what is applicable for you. At the moment though, it requires full paths of applications, and only works with EXE's - with an MSI, you *will* need to run msiexec, with the msi file as the argument. This setup will change in XPlode 3.00, as it will be running off tokens, and as such, all operations can be run through another user account.

Dates changed.... exams are over, but I have a couple of projects to finish off first. We'll see how things go...

I'm in the middle of exams. Ask me next week. Sorry.

Week 57. I'm in the middle of exams, so there is no production going on - the dates should pretty much be pushed back 3 weeks.

Back when I did it, it was all registry tweaks and hotfixes. So nothing of any real interest. I've always installed my programs from a deployment share on the network, as I'd stated before. And, for future reference, it's XPlode, not Explode

http://www.msfn.org/board/index.php?showforum=80

The UserExecute portion of winnt.sif. I think it was UserExewute, been a long time since I did anything...