For some reason it just WON'T work... - RELOADED

[Bâshrat the Sneaky]

Hiya all

Now that I've completely fallen in love with this magnificent program, (Again, congratz Wraith ) I also wanted to use it at the presetup stage (i.e. just before setup starts). It's being executed from presetup.cmd, with these commands:

REM Find CDROM driveletter        
SET TAGFILE=\OEM
FOR %%i in (c 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:%TAGFILE%" set CDDRIVE=%%i:

REM Start XPLode
START /WAIT %CDDRIVE%\$OEM$\XPlode\XPlode.exe /xml:"#XPLODE#\presetup_xplode.xml" /log:"C:\XPlode_presetup.log"
START /WAIT CMD.EXE
EXIT

(I thought I'd post it, it might be useful for somebody.)

And my directory structure, so you can agree that the paths used are correct.

So I added the "START /WAIT CMD.exe" for testing purposes. This is the result of my test (screenshot taken from VMware):

So if anyone could help me solving this problem..?

P.S.: the .xml files are ok this time (I tested them with Firefox and they are valid... )

Edited August 15, 2005 by Wraith

[Wraith]

Do you get any sort of output from XPlode if you run it with /console ?

[Bâshrat the Sneaky]

Do you get any sort of output from XPlode if you run it with /console ?

<{POST_SNAPBACK}>

Well... since XPlode.exe cannot be found, I cannot run it at all... That's the problem!

[Wraith]

When the file can't be found, you get:

D:\Profiles\Wraith>start /wait aslkjhf.exe
The system cannot find the file aslkjhf.exe.

NOT the error you're experiencing.

To be quite honest, I've never seen the same problem you're experiencing.

[Alanoll]

so....i would have thought this would be obvious to you Bashrat since you deal with this part of setup....

You do remember "Windows" or rather the shell for windows isn't fully loaded and so very LITTLE will actually work. Let alone a program that uses Windows API calls and such.

[Bâshrat the Sneaky]

so....i would have thought this would be obvious to you Bashrat since you deal with this part of setup....

You do remember "Windows" or rather the shell for windows isn't fully loaded and so very LITTLE will actually work. Let alone a program that uses Windows API calls and such.

<{POST_SNAPBACK}>

lol

Indeed... If I only had read the error code correctly: it doesn't say 'file cannot be found' but 'file cannot be executed'... stupid me....

Thanks for your support, guys ^^