Wraith

Perhaps it's easier to attach the HTML....? Knowing other people's incapability with getting stuff working, perhaps it's not the best thing to get people to modify things they don't know much about.

Try it and see. All the selection plugin is doing is embedding an IE window, so DHTML stuff should work fine. The ones included were only hacked together, so it's as basic as I could make them - I'm sure people could do a LOT more with it - I haven't done much with Javascript etc. If you can make something that's good, be sure to attach it here for other peoplet o use.

FileOps and Shortcut should be this weekend, hopefully. As for the XML... if it works the way you want, that's all that matters, no?

There's no "limitations" - the parser is (mostly) XML compliant, so you can use either ' or " to enclose strings.

What's stopping you from using " instead of ' to enclose the string?

Because that's the drive you installed windows from. As for that logfile, do another one from CMDLINES.TXT, not from your desktop.

Added colour key so people can tell what's happening.

Can I get you on IRC to test?

I'll look into it.

If you can get on irc, I can give you a test version with a few things that have been updated. irc.voidfx.com / #XPlode

Serves me right for not reading things again Your XML syntax is wrong: What you have: <item display="Testing Registry"> <execute token="Test User"> <execute display="Installing Mozilla Profile"> <program>#SOURCEDRIVE#\Software\Internet\mozilla\profile.exe</program> <wait>true</wait> </execute> </execute> </item> What it should be: <item display="Testing Registry"> <execute token="Test User" display="Installing Mozilla Profile"> <program>#SOURCEDRIVE#\Software\Internet\mozilla\profile.exe</program> <wait>true</wait> </execute> </item> One thing to note, the execute plugin waits by default, so it's not necessarily needed.

Sorry, I really should read things properly before posting. The following is how to get network shares working during Windows setup. All I can say is, make sure the secondary logon service is started, and test logging in afterward. This is a known issue with WindowsXP - an inf setting was not created properly when the XP CD's were built. MS KB Article + Fix: http://support.microsoft.com/default.aspx?...b;EN-US;Q314543 The secondary logon service still needs to be started - use <netstart>seclogon</netstart> This should work, but let me know if it doesn't. I haven't been able to test logging on during windows setup.

Soon.

@minos197: The logfiles are useful. If he didn't do them, then there would be no clue as to why things aren't running. When he gets it working, THEN he should take the /log:"..." out. Seeing as it ISN'T working, then it's a good idea to have it in. @saitoh183: Something is wrong with XPlode trying to open the XML - after the: XMLParser::LoadFile() Error reading file: there should be the filename it's trying to open. For some reason XPlode isn't getting the filename right, so it'll require looking into this weekend. For the moment, try renaming GFXInstall.xml to XPlode.xml, and running without the /xml"..." tag.

I'll remove the error in the next version of XPlode.

<execute> <program>net</program> <arguments>accounts /maxpwage:unlimited</arguments> <hide>true</hide> </execute> As for file copying... it doesn't exist yet.

The whole of section 4 in docs.pdf tells you how to link it in. If you want anything more extravagant, you'll have to improvise, but the basics are mentioned there.

By reading the sample XML's. I'm sure I threw comments in at least one of them.

I don't know if CMDLINES.TXT supports this, but I assume it would - try putting this in there: echo %CD% pause That'll tell you exactly where the current directory is - you can then work out how many times you need to ..\ and whatnot in order to point to XPlode.

http://www.msfn.org/board/index.php?showtopic=38748

Here's what you do when you have a problem: Search the bloody forum first. Please, please, please search. Read the documentation. EVERYTHING is explained in the included PDF. Make a logfile. I see people complaining that things don't work, yet they don't even create a logfile to get the smallest clue as to why. XPlode.exe /log:"#SYSTEMDRIVE#\XPlode.log" READ the logfile. Go to the place where it's going wrong and look WHY. If it's a problem where an application isn't running properly, check the logfile for any clue why it isn't. Check the validity of the program's arguments. Problems of this type are almost ALWAYS user error. If these STILL don't answer your question, THEN post. When posting a problem, be as descriptive as is humanly possible, preferably zip up your XML and your logfile, and attach it to the post. Do NOT leave serial numbers in. If people don't follow these, I will close your topics. If there is anyone who wishes to add anything, post below. Have a nice day! ------------------------------------------------------------------------------------------------------ EXTRACTION PROBLEMS Read the **** agreement like you were asked! Any topic posted regarding an inability to extract XPlode WILL be closed as soon as it is seen. Moderators: If they haven't been closed already, please close such topics, preferably directing them to this topic.

Try the attachment first. Send me the XML / log if it still isn't working. XPlodeExecute.zip

Nanaki: Wait works fine for me in the latest release. As I had said before, none of the code has changed regarding the execute plugin or XPlode - it was bugfixes with other plugins, so I've no idea why yours isn't working. Would you mind PM'ing me with your XML and the logfile?

XML is the sample Original Install one. Images are attached. images.zip

Logfiles are definitely needed. Not ones from when you test it in a normal environment, but the one from within windows setup.