Using Xplode via CD

[saitoh183]

ok...well i found the error i think... I was missing a close tag for adduser and item...

If i put the xplode files in a folder called xplode ( ...\$OEM$\Xplode), in my cmdlines.txt it would have to look like this:

"xplode\XPlode.exe /xml:"#XPLODE#\GFXInstall.xml" /log:"C:\XPlode.log" /console"

??

EDIT: Now here is what i've tried:

1- I tried putting all the XPlode files in $OEM$ with this in my cmdlines.txt

"XPlode.exe /xml:"#XPLODE#\GFXInstall.xml" /log:"C:\XPlode.log" /console"

Result: At the T-13 I get a flicker of 2 DOS screens( 1 is a regtweak file that i run), the hourglass for a few seconds and then it continues on with no installation done and no log file.

2- I tried putting the Xplode files in $OEM$\Xplode with this in my cmdlines.txt

"Xplode\XPlode.exe /xml:"#XPLODE#\GFXInstall.xml" /log:"C:\XPlode.log" /console"

Result: Same as above

Once the installation was done in my VMware, i ran

XPlode.exe /xml:"#XPLODE#\GFXInstall.xml" /log:"C:\XPlode.log" /console

to genarate a log files and this is what i got:

>>> Log session start at: 2005/02/10 13:40:24
XPlode4
   Adding environment variables
      #XPLODE# = 'd:\$OEM$'
      #SOURCEPATH# = 'D:'
      #SOURCEDRIVE# = 'D:'
      #VERSION# = 'XPlode 4.00'
   XMLParser::LoadFile()
      Error reading file: 
>>> Log session end at: 2005/02/10 13:40:24


>>> Log session start at: 2005/02/10 13:42:10
XPlode4
   Adding environment variables
      #XPLODE# = 'c:\xplode'
      #SOURCEPATH# = 'D:'
      #SOURCEDRIVE# = 'D:'
      #VERSION# = 'XPlode 4.00'
   XMLParser::LoadFile()
      Error reading file: 
>>> Log session end at: 2005/02/10 13:42:10

And this

echo %CD%
pause

doesnt work.

Here is my GFXinstall.xml

GFXInstall.xml

[Power350]

**** disn't see that this had 2 pages

got lost in the xml file

Edited February 10, 2005 by Power350

[saitoh183]

what do you mean??...got lost?

[minos197]

saitoh183 why do you make your life diffcult with log files??If the xplode works on the creating maching then just put it in OEM with the other files offcourse and call it as I said. "XPLODE.EXE"

nothing more nothing less.The Logs are not neccessary unless you miss some minor details and try to fix it.Get it Up & running first and then try comands as the ones you try.In school they first teach number and then they teach the Algebra.

[Wraith]

@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.

[Derkan]

"xplode\XPlode.exe /xml:"#XPLODE#\GFXInstall.xml" /log:"C:\XPlode.log" /console"

saitoh183, try getting rid of the excess quotes in that command.

cmdlines.txt:

[COMMANDS]
"xplode\XPlode.exe /xml:#XPLODE#\XPlode.xml /log:C:\XPlode.log /console"

Edit: Gotta mull over some more problems here before posting more results.

[Derkan]

Okay, I figured out my problems and got (almost) everything to work the way I'd like it to.

Anyway, here are some comments:

If you want to add a user name like: Test User -- don't forget the quotes. That's what my main problem was. So this is correct:

 <item display="Adding users to #COMPUTERNAME#">
 	 <adduser display="Adding Test User">
    <username>"Test User"</username>
    <password>test</password>
    <group>Administrators</group>
 	 </adduser>
  </item>

Maybe it should be mentioned in the docs that the quotes thing still applies here?

@saitoh183

Removing the quotes as I wrote in my above post should work for you to install correctly from the CD. Since XPlode automatically specifies the #SOURCEPATH# (in my case the F: drive), no further drive lookup is necessary.

For testing purposes, I suggest you only try to install one item until you've got it to work. That'll save you a lot of time.

@Nanaki

I copy/pasted your code from your first reply in this thread and the following creates a problem (not for saitoh183 because that syntax is correct):

<execute display='Programma'>

You have to replace the single quotes with double quotes or XPlode can't execute:

<item display="BSplayer 1.1.814">
     <execute display="Programma">
        <program>#SOURCEDRIVE#\Install\Apps\bsplayer.exe</program>
        <arguments>/S</arguments>
     </execute>
</item>

If you didn't have a problem with this, good for you. But it was the double quotes that made it work for me.

[Nanaki]

I think the example files from the previous version were with single quotes, so that's why I use them. It works fine for me.

It may very well cause my problems with the latest version.

But ****, my XML is too big right now, I'll convert when I have time, XD.

[saitoh183]

Here is my new log file after trying Derkan cmdlines.txt

xplode\XPlode.exe /xml:#XPLODE#\XPlode.xml /log:C:\XPlode.log /console"

>>> Log session start at: 2005/02/12 09:44:21
XPlode4
   Adding environment variables
      #XPLODE# = 'C:\Documents and Settings\Administrator\Desktop\New Folder'
      #SOURCEPATH# = 'D:'
      #SOURCEDRIVE# = 'D:'
      #VERSION# = 'XPlode 4.00'
   XMLParser::LoadFile(C:\Documents and Settings\Administrator\Desktop\New Folder\XPlode.xml)
   Loading XPlode plugins
      Loading display plugin: ''
         Plugin load unsuccessful: ''
>>> Log session end at: 2005/02/12 09:44:21

Howcome the #SOURCEPATH# is always 'D'?

[Wraith]

Howcome the #SOURCEPATH# is always 'D'?

Because that's the drive you installed windows from.

As for that logfile, do another one from CMDLINES.TXT, not from your desktop.

[saitoh183]

I just tried installing my UA CD using this in my cmdlines.txt:

[COMMANDS] 
"REGEDIT /S regtweaks.reg"
"XPlode.exe"

and like this:

"REGEDIT /S regtweaks.reg"
"xplode\XPlode.exe /xml:#XPLODE#\XPlode.xml /log:C:\XPlode.log /console"

It still didnt work. I renammed the xml file to Xplode.xml. Once the windows is finish installing i ran the run_with_logging_.cmd directly off the iso file and this is what i get:

XPlode4
  Adding environment variables
     #XPLODE# = 'D:\$OEM$'
     #SOURCEPATH# = 'D:'
     #SOURCEDRIVE# = 'D:'
     #VERSION# = 'XPlode 4.00'
  XMLParser::LoadFile(D:\$OEM$\XPlode.xml)
  Loading XPlode plugins
     Loading display plugin: ''
        Plugin load unsuccessful: ''

For some reason the display plugin doesnt seem to want to load...

Here is the Config part of my script:

<config>
  <environment>
  <!-- strings for the original display plugin -->
 	 <display.title>Installation procedure</display.title>
 	 <display.complete>completed</display.complete>
  <!-- strings for the adduser plugin, #1# is replaced by the username/groupname-->
 	 <adduser.adduser>Adding user: #1#</adduser.adduser>
 	 <adduser.deluser>Deleting user: #1#</adduser.deluser>
 	 <adduser.addgroup>Adding group: #1#</adduser.addgroup>
 	 <adduser.delgroup>Deleting group: #1#</adduser.delgroup>
  <!-- strings for the adduser plugin, #1# is replaced by the program -->
 	 <execute.string>Executing: #1#</execute.string>
  <!-- strings for the misc plugin -->
 	 <misc.sfcos-disable>Disabling Windows File Protection</misc.sfcos-disable>
 	 <misc.sfcos-enable>Enabling Windows File Protection</misc.sfcos-enable>
 	 <misc.netstart>Starting #1#</misc.netstart>
 	 <misc.netstop>Stopping #1#</misc.netstop>
  <!-- strings for the registry plugin -->
 	 <registry.read>Reading from registry</registry.read>
 	 <registry.write>Writing to registry</registry.write>
  </environment>
  <!--
 	 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="17" after="8" subcount="true" />
 	 <font face="Tahoma" antialias="True" small="7" large="10" />
 	 <!-- note the position attribute - it is listed in 'x,y' positions. -->
 	 <!-- 0..8 still may be used. -->
 	 <window width="480" height="640" position="5" />
 	 <windowmode mode="GuiRedraw" border="true" ontop="true" />
 	 <colours>
    <!-- the text colour and position for the header text -->
    <header fore="#00F905" />
    <!-- the text colour and position for the footer - 
    width tells XPlode how wide the footer is (including progress) -->
    <footer width="410" fore="#FFFFFF" />
    <!-- standard progress bar colours -->
    <progress border="#000000" back="#FFFFFF" fore="#008800" />
    <!-- text colours, position and width for the items listing -->
    <main x="16" y="40" width="388" fore="#F9006B" current="#0087FF" description="#F94FFF" overlay="#FFFFFF44" />
 	 </colours>
  </display>
	</config>

All the Xplode files are directly in the $OEM$ folder

[Wraith]

I don't know what you've done, but you've managed to screw it up completely.

Try redownloading XPlode or something. I honestly have no idea why it isn't working. If it's still acting up, get on IRC.

[saitoh183]

Well i finally got it to work

I took my item section and pasted it in the example file and voila! But i decided to run it from the Runonceex.cmd instead of the cmdline.txt because i was getting errors during the installation. During the runonceex.cmd it works great but i wanted to know why when i run reg files right after i install a program, it asks me to confirm.

[Wraith]

I have the feeling that it had something to do with character encoding...

Oh well, all good now.

[saitoh183]

I think your right becuase i looked at the encoding for the example xml's and they are in ANSI as for my xml it was in Unicode.