Wraith

@RyanVM: Is your thing going to actually extract all the hotfixes, and insert the files and reg stuff manually? (i.e. Should I bother doing my own? )

Anyone got a zip with all of them? I'm lazy

You aren't using that plugin - you'd have <adduser ... /> and <addgroup ... /> if you were. Those are the normal app switches, perhaps ask in the application switches forum?

I dont have any mirrors for it. Anyone else?

HMMMM. I'll get back to you.

And for people that haven't seen it:

Seeing as very few people frequent the XPlode forum nowadays, I figure I may as well post here. Check this post out: http://www.msfn.org/board/index.php?showtopic=28698 I need a bunch of people to test it and HOPEFULLY I can find someone that gets the same application error listed. People that have had this problem (quite a few) seem to post it and never come back again, so PLEASE, test, and get back to me. If you haven't used XPlode before, it accepts two arguments: /xml:#XPLODE#\XPlode.xml and /log:#XPLODE#\XPlode.log The #XPLODE# is essentially what would normally be %XPLODE% - environment variables. As %XPLODE% does not actually exist until XPlode runs, using %XPLODE% from a command prompt would make it blank. All other available environment variables are accepted in both %xxxxx% and #xxxxx# forms. The xml argument specifies the XML file to use (funnily enough), and defaults to XPlode.xml within the XPlode directory. The log arg tells XPlode where to write its logfile, defaulting to no logfile if unspecified. Please test for me, trying to get the project going again, but with no people to test, it's kinda hard, as things work on my comp but not others.

Seeing as nobody has replied, here's a kick in the pants. If you're having any problems related to The application failed to initialize properly (0xc00000005). Click OK to terminate the application. etc. etc., you need to try XPlode2 without any plugins present. i.e. Run XPlode2.exe, without any *.xip or *.xep in the same folder. Run with logging on AND off, to try and narrow down what could be causing the problem. Think about what could be causing your problem, and try to eliminate as much as is possible. The MINIMUM test I'd say to use is no logging, and an almost blank XML. (Remove everything non-essential.) Big enough for you? Need to know ASAP, as I'll probably have to change the XML parser if so. XPlodeDisplayTest.zip

Ahh. You can't do that, normally. Search the unattended forum for "RegImport".

By using the syntax in the example? You probably need to state the full path to regedit - %WINDIR%\regedit.exe should work. Been a while since I used the running under different credentials code...

Huh? Do what manually?

Post a screenshot of your CD's hierarchy.

I *is* compatible with 2003. I've tested it myself. I have absolutely no idea why those things happen. Very very weird. Can you try removing all the plugins and seeing whether it runs by itself? The only thing that hasn't changed in virtually any version of the program has been the XML parser. So if it's still screwing up, I think I may have to rewrite that. Yuck, Let me know if it's still a problem without plugs.

It doesn't - but there's no reason as to why a plugin can't be made to do such a thing. I'll be posting the DLL interfaces in the next week or so, still a few things to iron out and there's still stuff I need to do for uni, so... yeah. Final date's being pushed back further...

Nah, keep it going. Always need some competition to promote evolution

For a start, XPlode2 won't load the plugins from 1.1.2, so don't bother trying. I'm going to have to talk to you later about testing more.

You could create a plugin to ask for one, which could set an environment variable if used. Then, with the basic checks I'm adding for conditional statements, you could get it to check that variable, and hence select which things to use. If I get time, I'll try and implement a simple thing for that.

I can't provide support for XPlode 1.1.2, but can I get you to please test the XPlode2 executables I've posted in the other topic? I'd like to narrow down why plugins aren't loading, and hopefully eliminate it in XPlode2.

I shall redo it soon. I've had a bastard of an assignment to do this week... taken about 40 hours by itself. Ugh. Due in 2 hours, just have to wander in and submit it. I'll get some XPCREATE lovin' going when I get back

Errr. Save it in unicode with notepad. Read the logfile next time.

Just a quick thing - with XPCREATE rewriting the OEMPnPDriversPath entry in the winnt.sif, it's chopped off after a certain amount of characters, and the amount is quite small. Just add RyanVM's storage drivers pack, and put them all in there - if DOPATH is set to yes, then it only gets through a few drivers before screwing up. I'm sure it's been mentioned already, but I'm tired, bored , and hungry, so I thought I'd lay some of the anger on GM Just another random rant from me when randomly changing the ini entries.

I should also point out that there's an error when deleting the postinstallation files too. Same error, look for a string that isn't enclosed by quotes.

Open up the XML in Firefox. It'll say the XML is wrong, view the source of it. The funky thing with Firefox is, the syntax colouring usually points out the problem, as it sticks out like a sore thumb. You'll find that in the Ad-aware block, the program attribute has not been closed properly. As in, you've opened the string with a quote ( ' ), but it isn't closed. And if you haven't switched to Firefox yet, I'd advise doing so. You can thank me later

The aim is to have an option in the <display> block to see if it's supposed to be attended or not. I'll be adding a selected='true' attribute to each item and effect, telling XPlode whether items are selected. If in attended mode, it just means the states of the checkboxes, if unattended it'll determine whether things are installed. If attended, it'll act like it does now, if unattended these are the things I'll be doing: Removing the checkboxes Removing items that aren't selected in the XML Removing the buttons and resizing the window to suit Now I must stress that ALL of the information I just said applies ONLY to this display plugin. Other ones (when they're written) will depend on things differently.

You'll have to explain the problem a bit before people can help. Are you getting syntax errors, things not installing, what? Might be wise running with logging active so you can see what's going on.