MHz

A *.cmd file will not execute on a 9x operating system. Commands in a *.cmd file may not work for a 9x system. This difference ensures that scripts made for one type of system are not functional on another type of system. This is a major issue if they are treated the same.

Create your shortcut and put your shortcut into $OEM$\$DOCS\All Users\Start Menu\Programs\Games.

That is an awesome laptop. High res and refresh.

I may have made error in judgement OemFilesPath = ".\SETUP\XP\HOME"winnt.exe is the interpreter for winnt.sif? So that would be the working directory. If this is the case then maybe ..\Dir1and ,,\Dir2Along with example above.

@battleangel3222 Your post is very inhuman for a fellow member who has only posted once or twice. Trying to force Autoit onto fellow members is not very polite either. Please show some respect and understanding. Welcome Protoss.

Or UltraISO and use save as. Most ISO editors have this function.

OemFilesPath is the path to your $OEM$ folder. That would mean? OemFilesPath = ".\SETUP\XP\HOME"If this is the case. The you cannot have 2 $OEM$ in the same directory. So you could put 2 directories into that directory, then put each $OEM$ directory into each new directory that you just created. -I386 -Dir1\$OEM$ -Dir2\$OEM$ Winnt.sif entries would be OemFilesPath = ".\SETUP\XP\HOME\Dir1"and the second winnt.sif OemFilesPath = ".\SETUP\XP\HOME\Dir2" This may work? But you have 1 I386 Directory? Where is the 2nd winnt.sif? Edit: And why did you not post in the Multi-Boot CD/DVDs forum?

You can simply disabled Administrator account logon. example: [GuiUnattended] AutoLogon = No AdminPassword = *Then you can do what maxXPsoft states for logon.

If you want to autologon as Administrator once. Yes, you need a password. You can use AutoLogonCount=(a number) , if you want to logon more then once as Administrator.

No password, no autologon into administrator account that you chose as in winnt.sif.[GuiUnattended] AutoLogon = Yes AdminPassword = *

How are you autologging on? Looks like you are trying to autologon to the administator account but perhaps without a correct password.

Press Alt+Space, then resize the window. Then close it.

Embedded is like a live cd. OS and programs do not write any data, to allow it to run from cd's, flashdrives etc. Only clear guide I know of is at Microsoft for Windows XP embedded.

I believe unattended cd's, by design, will lose the repair option. All you need to do is make a 2nd cd with Windows XP Slipstreamed without winnt.sif etc. And use it as your repair option etc. cd.

Is Cmdlines.txt still in $OEM$, to create Adiel from a batch file?

Perhaps oobeinfo.ini could be adopted as the method for adding users. I have not tried this method yet. But seems to be success with it from users. Many more options seem to available via this method. The autologon could still be in a *.reg file, or even added in the regtweaks *.reg file? It is a logon tweak. Thanks. B)

With wpi etc. you may have to sacrifice create user setup? I have done installations with the inverted comma's " ". Except for strings with spaces. No issues come from not having them.

I f you have OEMPreinstall=no. I believe you can still have $oem$ on your cd. Files will not get copied over. But Cmdlines.txt does still get processed, if I remember correctly. With that, files that you would normally insert into $Docs etc. Would go into archives, and extracted from runonceex, guirunonce or whatever else.Testing will give you your answers and options. Hope this is helping you in some way.

@xper That is great advertising for msfn and unattended cd's. But my point is the links to the unattended guide itself? Even have a link positioned right under that banner to the guide. Or a button or something on the home page for the guide? So it will be go un-noticed? Just throwing up some idea's.

Agree UnattendSwitch="yes" Specifies whether Setup skips Windows Welcome or Mini-Setup when preinstalling Windows XP Home Edition or Windows XP Professional using the CD Boot method. Set this to yes to skip the "Setting Up Internet Connection" and "Create User Accounts" screens.UnattendSwitch="no" should be the answer. OemSkipWelcome=0 or 1 This option should be set to 0 if you have OemPreinstall from above on No, If OemPreinstall is on Yes then this option should be set to 1, not doing so will halt the OEM process! When set to 0 this tells Setup not to display the welcome screen during the GUI-mode of Windows Setup (Note: This is not the same as "Windows Welcome" where you set a username for your new account when Setup finishes) OemSkipWelcome=1 for this setting to stop any halt in process. But is any other related to UnattendSwitch that may cause create user accounts not showing? UnattendSwitch was mentioned earlier in the thread? OEMPreInstall = yes may force no show of create user accounts?

Switches look fine. You could even add the -x switch, which does the autocrc. Cdimagegui just extracts the dos version of cdimage into a temp directory and the gui sends the commands to it. So it is exactly the same as using commandline. Some people prefer mkisofs only because it is opensource. But cdimage has proven itself to me over and over to perform, so is my favorite.

-> Firstly, would like to see any progressing changes that may happen tabled in the first post. -> I would ike to see more separation between RunOnceEx and GuiRunOnce methods. Noobs accidently mix these 2 together. PDF's are great. One for each type of methods as above. -> Clear warning that only All Users and Default User accounts only!!! exist in $Docs folder. -> Mention of application switches forum and other forums for help involved by need and expertise. -> The msfn unattended cd guide needs more, clearer advertising. Most noobs do not know of it's existence, even til the end of their project. Same with deployment tools. This is a important to save commonly known basic questions and let the level of knowledge rise.

@bmn Yes. AutoLogon = Yes This for autologon for Administrator account. Take it out of your Winnt.sif, so you will get the user setup screen. And you can give your Administrator account a password, so it will not ask you for it later. @darksith88 Let us know how it is going with your user setup screen problem.

2 users accounts you can use in $Docs. All Users or Default User. No other account is able to exist as they are not created until the end of setup. "Bob.Bobscomp." is created as a safe guard, as windows will not overwrite an existing profile directory.

Sorry, previous post related to bmn post. But you have no [Data] section, in your answer file? Example [Data] AutoPartition=0 MsDosInitiated=0 UnattendedInstall=YesTry this. You may also want to try a test install with OemPreinstall=No. This key maybe disallowing the user setup screen. Although, I cannot find any references to state that it does have that effect.