Help me plese (i'm thai user)

[tash]

I can't run Xplode in Winxp Setup

I Put Xplode in "$OEM$/$1/Install" on my cd

//////////////////////////////////////////////////

and in Install Folder contain this

[msn]

[NetFramework]

[notepad2]

[PowerToys]

[winrar342]

[WMP10]

XPlode.exe

XPlode.xml

XPlodeAdduser.x4e

XPlodeExecute.x4e

XPlodeGFXInstall.x4d

XPlodeMisc.x4e

XPlodeOriginalInstall.x4d

XPlodeRegistry.x4e

XPlodeSelectInstall.x4d

XPlodeSilentInstall.x4d

//////////////////////////////////////////////////

I use cmdlines.txt to run, this is code of cmdlines.txt

[COMMANDS]

"xplode.cmd"

"%SYSTEMDRIVE%\Install\XPlode.exe"

xplode.cmd code is

ECHO OFF

ECHO.

ECHO.

ECHO Now Copy Files Need For Update

ECHO Please wait...

ECHO OFF

xcopy $1 /s /r /y /q C:\

exit

After I copy [install] and xplode program to my drive Use xplode.cmd Why Xplode not run ,help me please (I test xplode it can run but not run in winxp setup)

[Nanaki]

Delete "xplode.cmd". It's useless.

[Afterdawn]

Offtopic:

What's does it matter if your Thai or not?

Do you practise Muay Thai? I do!

[tash]

95% of Thai can do Muaythai it basic in my country,

but now i want help for Xplode

If you can tel me Step by Step from Beginer tel me please Thank you

[Nanaki]

"XPlode.cmd" is useless, as an OEM disk already copies everything to drive.

Second, try executing "run_with_logging.cmd" and post your log it generates.

[minos197]

I have and easiest way to run it.you just put all the xplode files in the $OEM$folder you have the cmdlines.txt and only add to the cmdlines this

[COMMANDS]

"xplode.exe"

Make sure it runs at all before testing the cd.Try running the exe or the cmd it has for logging in the pc you are working..IF it appears you are reasy to go.If not check the logs

[tash]

Why it not run!!!!!!!!!!

I have read All Topic in this topic

Agian this is my folder structure

-----------------------------------------------------------------------

[$OEM$]

......[$1]

..............[install]

......[$$]

......[$Docs]

......[$Progs]

[cmpnents]

[Docs]

[i386]

[support]

[Valueadd]

-------------------------------------------------------------------------

i386\winnt.sif

Please tell me why it not run and no log file create, thank you

now i tried becluase i do other way agian agian for 15 times but it still not run

Edited February 7, 2005 by xper

[Nanaki]

Well, I don't use that method, so I can't see any errors in it (which I'm sure there are ).

Try using the following:

ROOT

- $OEM$

- cmdlines.txt

- i368

- XPlode

- XPlode.exe

- XPlode.xml

- The various plugins

And then in cmdlines.txt:

[COMMANDS]
..\XPlode\XPlode.exe

But we need a log. =p

[tash]

Ok I Can do it thank you everyone for help me

i hope you wil happy better....

[xper]

@tash

12. Very often we see meaningless subjects in topic title. They give no clue of what the posts are all about. For example:

- Oh no!

- Help

- I'm mad

- Please help

- Question

- I need your help

- Hmmmm ....

This should be avoided. Users should enter something more specific in topic title so that it is easier for others to help.

Also put your .sif, .inf, whatever in file and attach it to your post.

Thanks

[tash]

Sorry, for this topic title

next time i must carfully than

[Wraith]

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

[parithon]

I like to have my $OEM$ folder have the least amount of files possible to get passed the text based portion of the install quicker, and allows you to install the applications on other machines without a lot of navigation.

My $OEM$ folder looks like so:

\$OEM$\

CMDLINES.TXT

XPlode.exe

XPlode.xml

XPlodeAddUser.x4e

XplodeExecute.x4e

XplodeGFXInstall.x4e

XplodeMisc.x4e

XplodeOriginalInstall.x4d

XplodeRegistry.x4d

\$OEM$\$1\Drivers\001_chipset

\$OEM$\$1\Drivers\002_graphics

\$OEM$\$1\Drivers\003_audio

\$OEM$\$1\Drivers\004_usb

\$OEM$\$$\Resources\Themes

\$OEM$\$$\System32\

OEMINFO.INI

OEMLOGO.BMP

[CMDLINES.TXT]

XPlode.exe /log:%windir%\XPlode.log <--- allows for troubleshooting

Then I setup the XML file to link to the applications on the CD itself, instead of running everything off the HDD and then deleting them after the installation is complete... unless you like to waist space on your hard drive, then continue to use your method.

~parithon