Current development

[chezy666]

probably the new feature is a modular setup runtime, in order to select with check box the program we want to preinstall. Suppose you own only five AV license, you will so able to not bypass number of licenses and at the same time to have only a DVD for all the installation,

Second , maybe some of use doesn't need it by I think XPlode could integrate both alternative, full unattended ot interactive program setup.

i guess he replied in the wrong window

[fillalph]

For a long time I was using batch files to control my unattended install of apps and such. I then did some looking at alternative solutions and XPlode looked really cool. However, Iread that users were unable to use XPlode 1.1.2 with Windows XP SP2 RC1 +. Instead I use runonceex. Since you are back to programming it, my request would be to make it compatible with SP2 +.

Thanks

]Bonkers[

[Wraith]

Don't worry, I said that one of the main things for XPlode 2 was to work with SP2.

It *has* been reported to work with SP2 by at least one person, so YMMV.

[prathapml]

It *has* been reported to work with SP2 by at least one person, so YMMV.

Who told you that XPlode had problems with SP2 (any version)?

I haven't even upgraded XPlode to the newest version (I have the later ones, but use v1.00 - logically the older version should have more bugs) and still, I see that it is perfect from every angle on RC1.

[mmarable]

There was an issue with some of the more recent versions of XPLode and SP2-RC1. Since RC2 has come out I haven't had any problems running XPLode, so Microsoft fixed what ever it was that caused the problem.

I wish it would work with Win2003. I've tried XPLode, XPDeploy, and even went back to XPInstall and they all bomb out.

I like the idea of having a list (like XPDeploy) when you can select the apps you want to install, like a series of check boxes, and off it goes to install them. I couldn't begin to guess if such a thing is possible, but it sure would be a godsend for me personally.

I also don't know if it's possible, but can the logging be expanded? Let's say an install bombs, can the error kicked back be logged? I suppose that all depends on the error handling of each individual installer, so who knows how feasible something like that would be.

That's about all that I can think of adding to what you already have, Wraith. You've put together an awsome tool.

[Wraith]

I haven't had any problems with Server2003, so I can't really help you with that. It seems to be a bit iffy, some people report non-functionality for SP2, some report it for 2003, and some confirm on both accounts.

As for the logging, it's already as verbose as I can get it - the error messages I get back from windows are put straight into the logs, nothing else can be added, without doing some major trickery to find out what files had changed and stuff. Stuff that isn't as important as say, the core XPlode module.

The list will more than likely be implemented - it will probably be much like the XPdeploy interface, with optional checkboxes etc.

I'm still at a conceptual stage for these, but that's going to be the general idea.

I should have the core done by the end of the week - XML, plugin architecture, execution. Everything else will be handled by the modules.

Of course, it still won't be usable until I get the modules written, so I guess we'll see how long things take from there.