Alanoll Posted May 16, 2004 Posted May 16, 2004 i see wraith was getting annoyed with it as well.@mukeshnunawe dun lik por enlish. I not unter stand u wen u typ lik dis.
Wraith Posted May 16, 2004 Posted May 16, 2004 Yeah, I don't particularly like it when people apparently can't make that step from being an idiotic AOL script kiddie, to someone who can talk like a human.For anyone that hasn't made the transition, here's a translation:YEAH I DONT PARTICULARLY LIEK IT WH3N PEOPLA APAERNTLY CANT MAEK TAHT ST3P FROM BNG AN IDIOTIC AOL SCRIPT KIDEI 2 SOMAONA WHO CAN TOK LIEK A HUMAN!11!!1! WTF LOL
mukeshnuna Posted May 16, 2004 Author Posted May 16, 2004 @mukeshnuna:Speak english in future.@everyone else:Thinking of replying? Don't.Not until he starts using english.ok......so sory about that...!@everyone else:Thinking of replying? Don't.Not until he starts using english.how was it??Discouraging , right?? You said it to me for others....don't do it for others who ask here for help....hope you understand ....!but yeah i would suggest you to not to tell everyone to not to reply for this post...........you could tell me for that also.....i would have changed it...!don't do this for other ones.....thank you...!now please, would you give me a step by step procedure how to run it....?it's not running through cmdlines.txt!!!so should i run it through winnt.sif.....[setupParams]?????
Alanoll Posted May 16, 2004 Posted May 16, 2004 in case you failed to noticed, but EVERYTIME i've posted, I've given you alink to a post that could help you.It's in the signature. (below this)
mukeshnuna Posted May 16, 2004 Author Posted May 16, 2004 but Alanoll.......do you think that i would be doing something wrong???I got all your links read, and did the exact as it was specified...so why it isn't running???OK....now Alanoll what do you think if i switch to winnt.sif [setupParams].........it might work!!!Cmdlines.txt might now be working for me....!thanks..!
mukeshnuna Posted May 20, 2004 Author Posted May 20, 2004 no........none log file is created in the drive??so how should i go now my friend???
mukeshnuna Posted May 20, 2004 Author Posted May 20, 2004 this is my winnt.sif file now........in XP SP2[setupParams] "%SOURCEPATH%\Xplode\XPlode.exe /log:#SYSTEMDRIVE#\xplode.log"my xplode directory is in the root dir of my CD.....!
Alanoll Posted May 20, 2004 Posted May 20, 2004 well, in your last post, I can tell you EXACTLY whats wrong.XPLODE does NOT work with SP2 yet.
mukeshnuna Posted May 20, 2004 Author Posted May 20, 2004 ok....i would switch it to Sp1.......with the same configuration??Is everything right then??Or Wrong??
Alanoll Posted May 20, 2004 Posted May 20, 2004 how many times must I say this.....%SOURCEPATH% is not defined EXCEPT THROUGH XPLODE. So your line won't work.SetupParams requires XPlode to be on HDD. READ the linked post in my signature about getting it started, FOLLOW IT EXACTLY.
mukeshnuna Posted May 20, 2004 Author Posted May 20, 2004 but then my frnd....i want everything to run from cd....then wht path should i use ??.....!
Alanoll Posted May 20, 2004 Posted May 20, 2004 you should use CMDLINES.TXTLike the linked document tells you to do.b.) Method 2 (Comepletly from CD)The only difference between CD-ROM and harddrive is that the path to XPinstall and variables are different, and XPInstall.exe is located on the CD instead of the HDD.Say for example that your Application folder is located at %CDROOT%\Unattend with %CDROOT% being the base of your XP CD, and Unattended being the location of XPInstall.Now in the cmdlines.txt, you have to reference to XPinstall but using simple DOS style paths.So in this example the lines would be:"..\Unattend\XPinstall.exe"The ".." reference the folder ONE level up from where cmdlines.txt is located (%CDROOT%\$OEM$), and so ".." equates to %CDROOT% as that is the next level up from $OEM$.As an example of "..", lets so you're currently in C:\Windows\System32. A command "..\explorer.exe" will open the program "C:\Windows\Explorer.exe". Get it?To use an alternate script, use the referencing principle, but instead of #Systemdrive#, use either #Sourcedrive# like in the above section of #XPinstall# as that equates to the location of XPinstall.exe, and that is currently on the CD.So as an example using test.xml again"..\Unattend\Xpinstall.exe /x:#XPinstall#\test.xml" OR "..\Xpinstall.exe /x:#Sourcedrive#\Unattend\test.xml"Notice that with #Sourcedrive# that it only equates to the drive letter and : like C: or D:
mukeshnuna Posted May 20, 2004 Author Posted May 20, 2004 and the method u described, if i use it, then DOES IT MEANS THAT I DON'T HAVE TO USE [setupParams] METHOD??....this confuses me!....so accord to your method, i modified my files like this......removed [setupParams] option from winnt.sif file in I386[setupParams] "%SOURCEPATH%\Xplode\XPlode.exe /log:#SYSTEMDRIVE#\xplode.log"cmdlines.txt[COMMANDS]"..\Xplode\Xplode.exe"xplode.cmdcmdow @ /HID%SOURCEPATH%\Xplode\XPlode.exe /xml:"#XPLODE#\XPlode.xml" /log:"#SYSTEMDRIVE#\Xplode.log"exitand this is my dir structure...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now