[Jeroeneke]

I have been searching all day for this.
XPlode 4 won't load from my cmdlines.txt file. When Win2003 is installed, nothing happened. But if i start xplode after Win2003 install, it installs my programs, like it should do in the installation.

This is my cmdlines.txt file (placed in the $OEM$ directory):

[COMMANDS]
"%SystemDrive%\Install\XPlode\XPlodelog.cmd"

This is my XPlodelog.cmd file (placed in $OEM$\$1\Install\XPlode\):

@echo off
start /wait %SystemDrive%\Install\XPlode\XPlode.exe /xml:"#XPLODE#\XPlode-GFXinstall.xml" /log:"C:\XPlode.log" /console
pause

This is my XPlode-GFXinstall.xml file (placed in $OEM$\$1\Install\XPlode\):

<XPlode4>
	<config>
		<!-- include the standard config stuff -->
		<include file="#XPLODE#\include-StdConfig.xml" />
		<!--
			Block containing all settings for the current display plugin.
			   
			This will be dependent on which plugin used, so check 
				documentation for that specific plug.
		-->
		<display plugin='#XPLODE#\XPlodeGFXInstall.x4d'>
			<show total='16' after='8' subcount='true' />
			<font face='Verdana' antialias='true' small='8' large='13' />
			<!-- note the position attribute - it is listed in 'x,y' positions. -->
			<!-- 0..8 still may be used. -->
			<window width='420' height='410' position='5' /> <!-- background="#XPLODE#\images\gfxinstall.png" -->
			<windowmode border='true' ontop='false' />
			<colours>
				<!-- the text colour and position for the header text -->
				<header x='4' y='27' fore='#FFFFFF' />
				<!-- the text colour and position for the footer - 
					width tells XPlode how wide the footer is (including progress) -->
				<footer x='4' y='380' width='400' fore='#FFFFFF' />
				<!-- standard progress bar colours -->
				<progress border='#000000' back='#FFFFFF' fore='#526FA3' />
				<!-- text colours, position and width for the items listing -->
				<main x='16' y='65' width='388' fore='#FFFFFF' current='#FFFF00' description='#FFFF80' overlay='#FFFFFF44'/>
			</colours>
		</display>
	</config>
	
	<!-- include the items list -->
	<include file="#XPLODE#\include-Items.xml" />
</XPlode4>

This is my include-Items.xml file (placed in $OEM$\$1\Install\XPlode\):

<XPlode4>
	<pre-execute>
		<hidewindow>
			<title>ConsoleWindowClass</title>
		</hidewindow>
	</pre-execute>
	<post-execute>
		<showwindow>
			<title>ConsoleWindowClass</title>
		</showwindow>
	</post-execute>
	
	<items>
		<item display="BSplayer 1.37.826">
			<execute display='Programma'>
				<program>%SystemDrive%\Install\Apps\BSPlayer_1.37.826.exe</program>
				<arguments>/S</arguments>
			</execute>
		</item>
	</items>
</XPlode4>

At the moment I have only BSPlayer as an app because I want to make XPlode work before adding all my apps etc.

hope someone finds what I'm doing wrong!

thanks in advance!
jeroen.

[Synapse]

haven't really used xplode, but what does the log file C:\xplode.log say?

[Jeroeneke]

It doesn't say anything, because the file isn't there. XPlode isn't even opened.

If I run XPlode manually after install, then it says this:

>>> Log session start at: 2005/12/27 01:37:13
XPlode4
   XMLParser::LoadFile(C:\Install\XPlode\XPlode-GFXinstall.xml)
	  Importing file: 'C:\Install\XPlode\include-StdConfig.xml'
	  XMLParser::LoadFile(C:\Install\XPlode\include-StdConfig.xml)
	  Import context: 'XPlode4(0).config(0)', from 'C:\Install\XPlode\include-StdConfig.xml' succeeded.
	  Importing file: 'C:\Install\XPlode\include-Items.xml'
	  XMLParser::LoadFile(C:\Install\XPlode\include-Items.xml)
	  Import context: 'XPlode4(0)', from 'C:\Install\XPlode\include-Items.xml' succeeded.
   Reading environment variables from XML
	  #DISPLAY.TITLE# = 'XPlode Installation'
	  #DISPLAY.COMPLETE# = 'completed'
	  #ACCTMGMT.ADDUSER# = 'Adding user: #1#'
	  #ACCTMGMT.DELUSER# = 'Deleting user: #1#'
	  #ACCTMGMT.ADDGROUP# = 'Adding group: #1#'
	  #ACCTMGMT.DELGROUP# = 'Deleting group: #1#'
	  #EXECUTE.STRING# = 'Executing: #1#'
	  #MISC.SFCOS-DISABLE# = 'Disabling Windows File Protection'
	  #MISC.SFCOS-ENABLE# = 'Enabling Windows File Protection'
	  #MISC.NETSTART# = 'Starting #1#'
	  #MISC.NETSTOP# = 'Stopping #1#'
	  #MISC.SLEEP# = 'Sleeping for #1# seconds'
	  #REGISTRY.READ# = 'Reading from registry'
	  #REGISTRY.WRITE# = 'Writing to registry'
	  #FILEIO.COPY# = 'Copying: #1# to #2# (#3# of #4#, #5# of #6#)'
	  #FILEIO.MOVE# = 'Moving: #1# to #2# (#3# of #4#, #5# of #6#)'
	  #FILEIO.DELETE# = 'Deleting: #1# from #2# (#4#)'
	  #FILEIO.RENAME# = 'Renaming: #1# to #2#'
	  #FILEIO.SHORTCUT# = 'Creating shortcut to #1#'
	  #FILEIO.RMDIR# = 'Deleting: #1# from #2# (#4\)'
	  #FILEIO.MKDIR# = 'Creating directory: #1#'
   Reading tokens from XML
	  AccessToken::SetupTokens(Spike)
		 Username: Spike
		 Domain: HOME
		 Password: *****
	  AccessToken::SetupTokens(Jet)
		 Username: Jet
		 Domain: HOME
		 Password: *****
   Active environment variables
	  #ACCTMGMT.ADDGROUP# = 'Adding group: #1#'
	  #ACCTMGMT.ADDUSER# = 'Adding user: #1#'
	  #ACCTMGMT.DELGROUP# = 'Deleting group: #1#'
	  #ACCTMGMT.DELUSER# = 'Deleting user: #1#'
	  #ALLUSERSPROFILE# = 'C:\Documents and Settings\All Users'
	  #APPDATA# = 'C:\Documents and Settings\Administrator\Application Data'
	  #CLUSTERLOG# = 'C:\WINDOWS\Cluster\cluster.log'
	  #COMMONPROGRAMFILES# = 'C:\Program Files\Common Files'
	  #COMPUTERNAME# = 'HOME'
	  #COMSPEC# = '%SystemRoot%\system32\cmd.exe'
	  #DISPLAY.COMPLETE# = 'completed'
	  #DISPLAY.TITLE# = 'XPlode Installation'
	  #EXECUTE.STRING# = 'Executing: #1#'
	  #FILEIO.COPY# = 'Copying: #1# to #2# (#3# of #4#, #5# of #6#)'
	  #FILEIO.DELETE# = 'Deleting: #1# from #2# (#4#)'
	  #FILEIO.MKDIR# = 'Creating directory: #1#'
	  #FILEIO.MOVE# = 'Moving: #1# to #2# (#3# of #4#, #5# of #6#)'
	  #FILEIO.RENAME# = 'Renaming: #1# to #2#'
	  #FILEIO.RMDIR# = 'Deleting: #1# from #2# (#4\)'
	  #FILEIO.SHORTCUT# = 'Creating shortcut to #1#'
	  #FP_NO_HOST_CHECK# = 'NO'
	  #HOMEDRIVE# = 'C:'
	  #HOMEPATH# = '\Documents and Settings\Administrator'
	  #LOGONSERVER# = '\\HOME'
	  #MISC.NETSTART# = 'Starting #1#'
	  #MISC.NETSTOP# = 'Stopping #1#'
	  #MISC.SFCOS-DISABLE# = 'Disabling Windows File Protection'
	  #MISC.SFCOS-ENABLE# = 'Enabling Windows File Protection'
	  #MISC.SLEEP# = 'Sleeping for #1# seconds'
	  #NUMBER_OF_PROCESSORS# = '1'
	  #OS# = 'Windows_NT'
	  #PATH# = '%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem'
	  #PATHEXT# = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
	  #PROCESSOR_ARCHITECTURE# = 'x86'
	  #PROCESSOR_IDENTIFIER# = 'x86 Family 15 Model 2 Stepping 8, GenuineIntel'
	  #PROCESSOR_LEVEL# = '15'
	  #PROCESSOR_REVISION# = '0208'
	  #PROGRAMFILES# = 'C:\Program Files'
	  #PROMPT# = '$P$G'
	  #REGISTRY.READ# = 'Reading from registry'
	  #REGISTRY.WRITE# = 'Writing to registry'
	  #SESSIONNAME# = 'Console'
	  #SOURCEDRIVE# = 'D:'
	  #SOURCEPATH# = 'D:\I386'
	  #SYSTEMDRIVE# = 'C:'
	  #SYSTEMROOT# = 'C:\WINDOWS'
	  #TEMP# = '%USERPROFILE%\Local Settings\Temp'
	  #TMP# = '%USERPROFILE%\Local Settings\Temp'
	  #USERDOMAIN# = 'HOME'
	  #USERNAME# = 'Administrator'
	  #USERPROFILE# = 'C:\Documents and Settings\Administrator'
	  #VERSION# = '4.3.51210.1523'
	  #WINDIR# = '%SystemRoot%'
	  #XML.FILE# = 'C:\Install\XPlode\XPlode-GFXinstall.xml'
	  #XML.PATH# = 'C:\Install\XPlode\'
	  #XPLODE# = 'C:\Install\XPlode'
	  #XPLODE.BASE# = 'C:\Install\XPlode'
   Loading XPlode plugins
	  Loading display plugin: 'C:\Install\XPlode\XPlodeGFXInstall.x4d'
		 Plugin load successful: 'C:\Install\XPlode\XPlodeGFXInstall.x4d'
	  Loading effects plugins
		 Plugin load successful: 'C:\Install\XPlode\XPlodeRegistry.x4e'
		 Plugin load successful: 'C:\Install\XPlode\XPlodeMisc.x4e'
		 Plugin load successful: 'C:\Install\XPlode\XPlodeFileOps.x4e'
		 Plugin load successful: 'C:\Install\XPlode\XPlodeExecute.x4e'
		 Plugin load successful: 'C:\Install\XPlode\XPlodeAcctMgmt.x4e'
   Registering XPlode commands
	  Registering commands in 'C:\Install\XPlode\XPlodeRegistry.x4e'
		 Command registered: <registry ... />
	  Registering commands in 'C:\Install\XPlode\XPlodeMisc.x4e'
		 Command registered: <sfcos-enable ... />
		 Command registered: <sfcos-disable ... />
		 Command registered: <netstart ... />
		 Command registered: <netstop ... />
		 Command registered: <hidewindow ... />
		 Command registered: <showwindow ... />
		 Command registered: <sleep ... />
	  Registering commands in 'C:\Install\XPlode\XPlodeFileOps.x4e'
		 Command registered: <fileio-copy ... />
		 Command registered: <fileio-move ... />
		 Command registered: <fileio-delete ... />
		 Command registered: <fileio-rename ... />
		 Command registered: <fileio-rmdir ... />
		 Command registered: <fileio-mkdir ... />
		 Command registered: <fileio-shortcut ... />
	  Registering commands in 'C:\Install\XPlode\XPlodeExecute.x4e'
		 Command registered: <execute ... />
	  Registering commands in 'C:\Install\XPlode\XPlodeAcctMgmt.x4e'
		 Command registered: <adduser ... />
		 Command registered: <addgroup ... />
		 Command registered: <deluser ... />
		 Command registered: <delgroup ... />
   Executing tag: 'XPlode4(0).pre-execute(0).hidewindow(0)'
	  Error during execution: Window not found..
   Spawning display plugin
	  Install log: Starting dialog
	  Install log: Execution thread
	  Executing tag: 'XPlode4(0).items(0).item(0).execute(0)'
		 Install log: Running: 'C:\Install\Apps\BSPlayer_1.37.826.exe /S'
   Executing tag: 'XPlode4(0).post-execute(0).showwindow(0)'
	  Error during execution: Window not found..
>>> Log session end at: 2005/12/27 01:37:23

[Wraith]

From that logfile, there does not seem to be any problem with XPlode.
The pre- and post-execute errors are just that it can't find windows with those names, so it has an error.
If it's running too fast, I'm going to guess and say that the BSplayer install launches a secondary process then exits, which XPlode is unable to handle.

This post has been edited by Wraith: 26 December 2005 - 07:12 PM

[Synapse]

hmm, everything looks normal. your cmdlines.txt file is in the $OEM$ folder right?

but i may be wrong about this, but you may have to have the xplode.cmd file next to the cmdlines.txt file.. then have your cmdlines.txt file look like this..

Quote

[COMMANDS]"xplode.cmd"

and in your xplode.cmd file have

Quote

cmdow @ /HID (if you have cmdow copy to system32 keep this line.. if not remove this line)
@echo off
start /wait %Systemdrive%\Install\XPlode\XPlode.exe /xml:"#XPLODE#\XPlode-GFXinstall.xml"
EXIT

*edit*
by the way... i find it's easier to rename the XPlode xml file you want to use to XPlode.xml.. this will remove the need of the "/xml:"#XPLODE#\XPlode-GFXinstall.xml"" in your code.. and just running the xplode.exe without any parameters will start it.

if you rename your XPlode-GFXinstall.xml to XPlode.xml you should be able to start XPlode from cmdlines.txt something like this..

Quote

[COMMANDS]
"\xplode\XPlode.exe"

and have your entire xplode folder in the $OEM$ folder.

This post has been edited by Bi0haZarD: 26 December 2005 - 07:42 PM

[Alanoll]

is XPlode even being copied over to the harddrive?

[Jeroeneke]

Alanoll, on Dec 27 2005, 05:48 AM, said:

is XPlode even being copied over to the harddrive?

Yeah, XPlode is being copied over to the harddrive.

@Bi0haZarD, I will try it later today, will let you know if it has fixed the problem,

@ Wraith, What's it with those pre- and post-execute errors? Should I fix something? And about it's running too fast, what do you exactly mean ?
I have to say that XPlode works like it should when Windows is started and I run XPlode manually (by the batch file)! (BSPlayer is installed like it should be)


Thx,
jeroen

This post has been edited by Jeroeneke: 27 December 2005 - 04:26 AM

[Wraith]

Jeroeneke, on Dec 27 2005, 09:26 PM, said:

@ Wraith, What's it with those pre- and post-execute errors? Should I fix something? And about it's running too fast, what do you exactly mean ?
I have to say that XPlode works like it should when Windows is started and I run XPlode manually (by the batch file)! (BSPlayer is installed like it should be)


Thx,
jeroen

Don't mind me. I didn't read your actual problem - I thought you were referring to the pre- and post-execute errors.
Getting XPlode to run isn't something I've had a lot of experience with - most of the time I use XPlode is off a network share, after I've logged in and I feel like installing stuff manually.
I'd say check the guide or follow other people's instructions.

[Jeroeneke]

K, thanks anyway

I just did what Bi0haZarD told me to doe, but it still didn't load.


cmdlines.txt file:

[COMMANDS]
"Install\XPlode\XPlodelog.cmd"

XPlodelog.cmd file:

@echo off
start /wait %SystemDrive%\Install\XPlode\XPlode.exe /log:"C:\XPlode.log" /console
pause

I think the problem is in one of those two files!

[Synapse]

*edit* since i dont' want it lookin liek i'm double posting lol.

I have gotten this to work using.. cmdlines.txt

Cmdlines.txt

Quote

[COMMANDS]"C:\Install\XPlode\XPlode.exe"

have the entire XPLode folder in
$OEM$\$1\Install\

and rename the xplode xml file to XPLode.xml (for which ever one you want.. i personally used the XPLode-GFX.xml.. just renamed to XPLode.xml...

i'm sure theres a way to run this without the hardcoded path.. maybe from a cmd file, i'll try that now.

This post has been edited by Bi0haZarD: 27 December 2005 - 07:26 AM

[Jeroeneke]

I was just thinking, is it possible to install from cd using the cmdlines.txt method? This saves me a lot of time because otherwise I always have to wait for about a half an hour to test something out.

I would do it using the CD.txt method:

FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\CD.txt SET CDROM=%%i:

[Jeroeneke]

It finally worked!
It installed via XPlode from the cd

this is my cmdlines.txt flie:

[COMMANDS]
".\$1\Install\XPlode\XPlodelog.cmd"

This is my XPlodelog.cmd file:

@echo off
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\CD.txt SET CDROM=%%i:
start /wait %CDROM%\$OEM$\$1\Install\XPlode\XPlode.exe /log:"C:\XPlode.log" /console
pause

Hope it works for you too!


EDIT: By installing from the cd, you can test out your XPlode file, looks verry handy to me! When my XPlode file is correct, I will try to install from the HD like you said before!

greetz,
jeroen.

This post has been edited by Jeroeneke: 27 December 2005 - 07:49 AM

[Synapse]

yeap i was just trying the ".\" method as well... heres what i got..
in cmdlines.txt i got

Quote

[COMMANDS]".\XPlode\XPlode.exe"

and just have the XPLode folder in my $OEM$ folder..
this is completly off the CD (yours copies all the files over to the harddrive, then runs it.. *you'll see your files being copied after the 100% of the txtsetup*)

[Jeroeneke]

Didn't think about that immediately! Better to do that as it hans't got any sence to copy those files to the hard drive.

Will see later to install everything from the cd.

jeroen.

[Jeroeneke]

Strange,
it seems I can't install from any other folder than $OEM$\$1\Install\XPlode.
I edit both the cmdlines.txt and XPlodelog.cmd file to the new directories (and replace the XPlode folder to that directory) but it doesn't seem to work!


I think it is something in cmdlines.txt, as I have seen it doesn't do anything if there are any mistakes in it (tested it by giving some folders etc. that don't exists).
strange thing!

[Alanoll]

try this...

[Commands]
".\XPlode\XPlode.exe /log:C:\XPlode.log"

With XPlode.exe within a folder called XPlode within $OEM$

[Synapse]

are you running the xplodelog.cmd file? or the xplode.exe file?

also, what does your C:\Windows\Setuperr.log file say?

[Jeroeneke]

cmdlines.txt file:

[COMMANDS]
".\XPlode\XPlodelog.cmd"

XPlodelog.cmd file:

@echo off
FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\CD.txt SET CDROM=%%i:
start /wait %CDROM%\$OEM$\XPlode\XPlode.exe /log:"C:\XPlode.log" /console
pause

XPlode dir is in the $OEM$ folder.
Nothing wrong in my eyes ...
it doesn't do anything

C:\Windows\Setuperr.log, is that a log file from the windows installation or something? Will see it when it's completely installed

oh, btw, i'm installing Windows 2003, there is no difference with the Windows XP installation is there? (eccept for those lines in winnt.sif)

[Synapse]

try what alanoll has suggested, that should allow the logging option if you want it. and you won't have to worry about a .cmd file.

and to my knowledge, there should be no diffrence between installing on win2003 or winxp

the setuperr.log is where all the errors are kept that occur during windows installation.

This post has been edited by Bi0haZarD: 27 December 2005 - 09:38 AM

[Jeroeneke]

This is what setuperr.log says:

Warning:
Setup was unable to invoke external program .\$1\Install\XPlode\XPlodelog.cmd because of the following error:
CreateProcess returned error 2 (2).


***

Error:
Setup was unable to execute the commands in $OEM$\OEMFILES\cmdlines.txt.

***

Will try what alanoll says, that is indeed easier than messing around with those .cmd files