Jump to content

Recommended Posts


Posted

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)

Posted (edited)

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.

Edited by Bi0haZarD
Posted

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 ;)

Posted (edited)

I did what alanoll said, but I'm still getting the same error:

Warning:
Setup was unable to invoke external program .\XPlode\XPlode.exe /log:C:\XPlode.log because of the following error:
CreateProcess returned error 2 (2).


***

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

***

Edited by Jeroeneke
Posted

have been trying some times this afternoon, but it never worked that way.

looks like cmdlines.txt can't install from another folder than "$1\Install". Looks strange to me! Anyone has some idea's ?

thx!

Posted

only suggestion is to install with my method then.. won't get any log files though.

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

and have XPLode directly inside your $OEM$ folder.

i'll try to see if i can make a cmd file which will work as well and allow logging.

Posted

Hehe, actually I'm doing this for school, this is my eh, big work I need to work on the whole year (how do you say that in english :P )

I wanted it to look as good as possible (also, I need some good points as this is my last year and it isn't going verry well atm :P, so taking a more "professional" way should make those teachers happy :D )

after all, I'm happy I've choosed for XPlode as it gives a nice result :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...