midiboy

Hi guys, once again, a problem with cmd commands :-) If anyone has a solution, I would very much appreciate it ... Here´s the problem: I need to dynamically create an xml file with a commandline script so I was thinking of using the ECHO command to create that script something like: ECHO This text goes to the new file >C:\Test.xml ECHO Next line >>C:\Test.xml Only problem is ... the xml file has symbols in the text that ECHO interprets as commands. Example: this line should go into the xml: <?xml version="1.0" encoding="utf-8"?> Now, how do I do that ? Iif I wrap the whole code into double quotes like this: ECHO "<?xml version="1.0" encoding="utf-8"?>" >C:\Test.xml the quotes get written into the xml like this: "<?xml version="1.0" encoding="utf-8"?>" If I don´t do that, ECHO interprets the "<" and ">" symbols as commands and throws an error message. If I use single quotes instead of double quotes, the whole code gets messed up even more. I also tried adding a "\" before the double quotes but this does not help either. Since the whole thing is part of a bigger cmd script, it should not be vbscript or anything else. Does anyone have an idea ?? Thanks for your help! Alex

Hi ! A new WAIK was released to support the new OS: WAIK Beta Bye, Alex

Hi fizban, thanks for that. However, I was not looking for that information, instead I was trying to find a way to set the default update mode to Microsoft Update instead of just WIndows Update which is the default for each XP or Vista installation. With Windows XP one had to register some activeX components (see the "Download Everything Microsoft thread in the Unattended XP forum). However, with Windows Vista, things are different. I did not find any value in the registry that controls if Microsoft or Windows Update are used, instead the information seems to be stored in the SoftwareDistribution directory. Copying that over (actually the AuthCabs, SelfUpdate and WuRedir directories are all one needs) to an unattended installation works. Not a very "neat" solution but unless you or someone else comes up with another solution it seems to be the only way. Bye, Alex

Hi Mara, thanks !

Hi mara, In my case, WPI just starts cmd files that are in the relevant program directory. Those cmds then start the programs. That way I am more flexible in the choice of the tool installing my programs. The cmd that starts Nero light simply calls the program like this: cd /D %~dp0 start "" /wait ".\nero_lite_installer_9.2.6.0.exe" /unattended /serial=xxxxxxxxxxxxxxxxxxxxxxxx I think this is correct, no ? Bye, Alex

Hi ! Thanks for the light version of Nero 9. The silent install works fine, however, shortly afterwards, the program compatability assistent pops up saying that the program may not be installed correctly. I usually click on "the program was installed correctly". Is there any way to prevent this assistent from popping up ? This is the only program where this happens. This is on a German Vista Ultimate, x32 and/or x64. Thanks, Alex

Hi Maverick, I am sorry. In no way did I mean to offend spoof or anyone else. I just found it hard to believe that this is the only way. Maybe my choice of words were not that good, english is not my mothers tongue, you know .... Anyway, spoof´s solution to the problem works. Bye, Alex

Hi spoof, Sorry for the late reply (vacation). you are kidding me, there has to be another way to do that. Where is the information stored. After all it is just a different url no ?? Bye, Alex

Hi again, just found out that it works fine if the Administrator created during setup is named Administrator2 instead of Administrator. Installation is still running but it seems to work fine now. Any idea why this is happening ? bug or feature ? Bye, Alex

Hi guys, I have not found any threads on Windows7 unattended problems so I am starting one myself. I have just tried to create an unattended Windows 7 beta1 installation DVD by copying the autounattend.xml over from my Vista installation dvd and it ran quite well. The only thing I had to remove was the <ProductKey> value. However, there is a problem with the Administrator user. In my autounattend.xml I have the following code: <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <AutoLogon> <Enabled>true</Enabled> <LogonCount>4</LogonCount> <Username>Administrator</Username> <Password> <Value>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</Value> <PlainText>false</PlainText> </Password> </AutoLogon> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</Value> <PlainText>false</PlainText> </Password> <Description>Administrator</Description> <DisplayName>Administrator</DisplayName> <Group>Administrators</Group> <Name>Administrator</Name> </LocalAccount> </LocalAccounts> </UserAccounts> </component> This works fine in Windows Vista. In Windows 7 however, the unattended setup will stop with a wrong user/password message. Thats because Windows 7 created an Administrator_ploc (strange name, hah ?) user instead of just activating the Administrator user and setting the proper password to that user. Anyone else has this ? Happens all the time, even with plain passwords. All the other stuff like setupcomplete.cmd, WPI etc. seem to work fine. (limited testing so far). Have a happy new Year ! Alex

Hi ! Thanks guys for your help ! :-) Happy X-mas ! Alex

Hi Guys, does anyone know how to set the Microsoft Update switch automatically during an unattended setup ? (see screenshot please). I have tried with the muweb dlls similar to the way it was done with Windows XP but this does not seem to be the right way in Vista because this dll is not found when I manually enable Microsoft Update. There also does not seem to be any registry entry related to this so I am wondering what is changed when a user enables Microsoft update. Any ideas ? Thanks, Alex

Hi Yzöwl, unfortunately it does not work just yet the way it is now. The script now starts itself over and over and never comes around to starting any of the scripts in the subfolders. Thats probably because the script that contains your code is also called install.cmd and it calls itself over and over ... any easy way around that except renaming that script in the top dir ? Also, I had troubles with your call command. It did not really work. As soon as I changed it to this: @for /f "delims=" %%i in ('dir/b/s/a-d install.cmd') do start "" /wait "%%~i" ... it worked. Anyway, I have this working now. If you want to spend some time on the first issue above, I would be very thankful. If not, don´t bother Bye, Alex

Hi Yzöwl, I was sure you would answer ! Thanks for the code, will try it soon, have a nice evening/day, Alex

Hi guys, if anyone has an idea, please let me know ! :-) I would like to start a cmd that recursively searches through subfolders and starts each cmd called install.cmd it finds in those subfolders. I do have this code to start the cmd inside the current folder but how do I make it go through each subfolder inside this folder and start all files called "install.cmd" instead ? set p=%~dp0 for %%i in ("%p%install.cmd") do start "" /wait %%i Any ideas ? Thanks a lot ! Alex

Hi Kel, good to hear that you can confirm that those regkeys really work :-) As for this "RunWPI_Embedded.exe" you posted. What does it do ? Start WPI or simply set the options ? If it starts WPI, you do know that this will never work on a 64bit OS ? Thats because the exe ist 32bit and on a 64bit OS you will need the 64bit mshta.exe (see my thread on WPI on a 64bit OS). Bye, Alex

Hi Kel, are you sure ? I have no problem with IE7 when the reg keys are set manually before WPI starts. Bye, Alex

Hi Mark, unfortunately, the newest build you sent me which sets the two debug regkeys itself did not do the trick or something else went wrong. During the Office 2007 installation while the updates were applied, WPI suddenly started the next installation in the list, Visio while the Office setup was still installing updates. Of course Visio quit with a setup error (only one instance of setup can be run at any one time -> translated error message). So unless you have other ideas, one probably has to set those keys before starting WPI but I will try again tomorrow. It is late now, so maybe I did something wrong ... Bye, Alex

Guys, this really works ! Unbelievable ! I just installed Office 2007, Visio 2007, Project 2007, Office Communicator and Live Meeting client including all the available updates in each of the Updates folder with WPI on Vista x64. Mark has already sent me an updated WPI build that changes those two reg keys on its own so, will test this next ! I am SOOOOO happy that this is finally solved ! YUPPPEEEE !! Bye, Alex

Hi mark, yeah, totally strange but I am sooo glad I found this by accident! I have just compiled my new unattended Vista x64 DVD where I will test this with the following changes: To start WPI I have added this code to the script that starts WPI: REG ADD "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main" /V "Disable Script Debugger" /T "REG_SZ" /D "no" /F REG ADD "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main" /V "DisableScriptDebuggerIE" /T "REG_SZ" /D "no" /F Then, WPI is starting using the line: start "" /wait "%windir%\system32\mshta.exe" "%WPIfolderDVD%\WPI.hta" And then, when WPI exits, I have this code in the script: REG ADD "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main" /V "Disable Script Debugger" /T "REG_SZ" /D "yes" /F REG ADD "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main" /V "DisableScriptDebuggerIE" /T "REG_SZ" /D "yes" /F exit I will keep you updated if this works in Vista and during an unattended installation as well. I have tested XP again before and it worked even on the second time but I did not test it during an unattended installation yet so the next few hours will show if this is really the solution to that old problem Till then, Alex

UNBELIEVABLE !!!!! Turning Script debugging ON in IE 7 solves the problem ! I need to do some more tests, so far I only tried it on WinXP: I did this in IE7 according to the link, mritter posted: Then, I started WPI and installed Office 2007 and Livemeeting. This has crashed all the time in the past. Now, suddenly it worked fine. Fortunately, I had made a snapshot of the virtual machine before doing the above so I reverted the machine to the snapshot, turned script debugging OFF again and started WPI again. This time it crashed again. So obviously, turning script debugging ON will cure the problem. This is with the WPI 7.2 beta, don´t know about earlier versions. I will now test this with Vista as well. Also I will try to find out the regkeys that those two settings change so we can turn script debugging on before WPI starts and turn it off again when WPI is finished. edit: here´s the reg key: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main] "Disable Script Debugger"="no" "DisableScriptDebuggerIE"="no" Can you guys confirm my findings ? Bye, Alex PS: If this is really it, I am more than happy !

Hi guys, the problem seems to be as follows (from my point of view): I used to have the problem when installing Office 2007 alone. Back then, the updates folder was filled with all SP1 updates + all the Office Updates that were release since. Since back then the idea was that one of the Office Updates was the cause of the problem, I removed all updates from that Updates folder and voila, Office 2007 installed fine in WPI since. However, that is no reason to rejoice because now, everytime I install any kind of Microsoft application in addition to Office (Office first, then for instance Visio or the LiveMeeting client or Project 2007 etc.), WPI will always crash during the last phases of that second Microsoft application. The problem seems to be unrelated to OS version (tried with Vista and XP), and it happens during an unattended install and during a manual install when the desktop is loaded. Since I am always getting a "illegal character" (translated from German) error message, I am wondering if this is something to do with language versions or codetables etc. Also, I am wondering ... I am getting this "Do you want to debug" "Yes/no script error message". If I click YES, nothing happens. Would it make sense to install a debug application before installing Office and then debugging when the error happens ? What application would I have to install in order to do that ? (I am no programmer so I have no idea, sorry) Bye, Alex

Hi Nanaki, thanks for your help but unfortunately, this does not help. Now, with this new version, the script that started cdswitch will proceed to the next step after 30 min. when you restart or try to restart CDSwitch. So after 30 minutes WPI will start (this is the next step) but since the wrong DVD is still inserted, it won´t work correctly). I may be wrong but restarting CDswitch does not seem to be the solution for this problem or something else goes wrong. Any other ideas ? Bye, Alex

Hi guys, alright, accepted. I hope you do find a workaround for the Microsoft apps issues though. Would really love it :-) Thanks for taking your time to answer ! Bye, Alex

Hi again, Nanaki, sorry to say but the problem also appears on 32bit Vista. Do you maybe have a debug version that will tell what goes wrong/happens ? I could try that and post back ! Bye, Alex