Edmundo Valle Neto wrote:
Hi.
I saw some messages about this problem posted before, but I couldn't find an answer.
What do the contents of your cmdlines.txt llok like? It's amazing what a second pair of eyes sees (sometimes).
You did put the section header [COMMANDS] in, and you did remember to put double quotes around your actual lines? Are you sure the files you want to run are accessible? (i.e. you have put them into the $oem$ folder too?)
I have the same question posted at http://www.mail-archive.com/[email protected]/msg01866.html, of get rid of all the extra and needless XP things.
For who doesn't know exactly why someone would need to use this file "cmdlines.txt", this file is parsed at the end of installation when there is no user logged-on, so changes made to the registry at this point goes to the default profile.
I've put the cmdlines.txt at z:\os\winxpsp2\I386\$OEM$ as I had sucefully made with some CDs, but I couldn't get it parsed, the file is simply ignored.
There can sometimes be problems with your use of uppercase directory and or filenames. I suggest you lowercase all your files under %z%:\os\
Hope maybe one of these will help you to the next stage.
Regards,
Urs Rau
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ unattended-info mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-info
