midiboy

Hi Benjamin, hello and thanks for still adding the format feature The shell folder bug: in the current last version, everything works fine if you leave the location of the Windows Desktop at the default position in C:\Dokumente und Einstellungen\NewUser\Desktop. All the content of C:\Dokumente und Einstellungen\DEFAULT USER\Desktop is copied over to the new users Desktop. However, if you choose to move the location of the Windows Desktop to any other place in Wihu (during creation of a new user), lets say to D:\Alexander\Desktop, then nothings gets copied to the new Desktop folder on D:\Alexander\Desktop although Wihu properly created that folder. Thanks for your help, Bye, Alex

Hi ! I have not found any mention of this on the forum yet. Has anyone noticed that Benjamin seemingly decided to discontinue work on Wihu ? I just read about this on his homepage. What a pity ! While I understand that Benjamin should probably direct more of his time to his studies I don´t think that completely discontinuing Wihu should be the only solution. Maybe it could be at least possible to update version 2.1.x from time to time, fix bugs etc. instead of completely abandoning Wihu or make a complete rewrite. Mhh, actually the only tool I found during a quick look on MSFN that seems to do a similar thing as Wihu is Xplode. However, this tool seems EXTREMELY complicated to use/setup from my point of view, not only because it relies on XML. Other than that, I could not find a similar thing to Wihu anywhere. I can´t talk about other people here obviously, but I use Wihu regularily. Actually I wouldn´t even know what to do with my precious unattended installation DVD without Wihu ! Just so you know how important Wihu is to some of us .... A small request at the end ... Could you maybe fix this bug in the current version that prevents the desktop symbols/other files to be copied over from the default user\Desktop folder to the Desktop folder of a newly created user if the Desktop location is moved from the original location to any other location like D:\Desktop ? You said you would fix this in the upcoming rewrite but seemingly this won´t happen so ... Anyway, even if you are really discontinuing Wihu ... thanks for your work over the last months and good luck for your studies (at least finish quickly and THEN sell a new Wihu to us ) Bye, Alex

Hi everyone ! I have been successfully running a Multiboot DVD consisting of 2 Windows installations and a few tools. I have closely followed the MultibootDVD guide from this site. However, recently I have been wondering about something, maybe you guys can explain this. Now, in the MultibootDVD guide it is described how to seperate the actual boot files from the rest of the Windows XP installation. In the end you wind up with the folder PRO1 that consists of the Windows XP bootfiles and the rest of the installation in the Setup\Pro1\i386 folder. The "link" between those two folders seems to be the txtsetup.sif file that specifies the folder where the rest of the installation is supposed to be found at: SetupSourcePath = "\SETUP\XP\Professional\" Now, what I wanted was to start the installation as usual from the bootDVD but continue the installation from the Windows setup files on my harddisc. I thought that if you have to tell Windows where the i386 folder is, why not direct it to my installation base on my second harddisc. So I changed the above entry in txtsetup.sif to SetupSourcePath = "D:\Installation\Windows\XP\" where my i386 folder resides. Everything went fine at first. The text setup of Windows XP started, then Windows presented me with the "partition manager" where I had to decided where to install Windows. At that point, Windows detected my second harddisc as drive D: already. However, instead of formating and copying files afterwards, setup ended with an error message. I do´n´t understand why this does not work as expected. I have not changed anything except tell Windows to continue installation from a harddisc instead of the DVD. NTFS drivers have already loaded so Windows should be able to read from an NTFS drive. Also, it had correctly detected the second drive as D: before the error occured so where is the problem in doing this ? Can anyone explain that ? Thanks for your help, Alex

Hi ! Installing Google Desktop search silently is fairly easy, the switch is "/silent" However, there are plugins available which cause Google Desktop search to pop up a message during installation asking to acknowledge that plugin installation. Is there any way to get rid of that or to temporarily disable that warning message on plugin installation by a registry tweak or something ? Thanks, Alex

I think the switch is the same for all language versions, at least the German version install perfectly silent with this switch: setup.exe -ms And contrary to the old 1.0 version, it even works in 1.0.1 !!

Hi Benjamin, great to see you work on a new version ! What "unnecessary features" did you think about ? Hope it is not something someone finds necessary ;-) I have added two things to the wishlist which came to mind. I just hope the new version will not be completely different so we can keep using our ini files or at least the changes should be posted in a very detailed mannor so that changes can be done easily. Maybe one small add on: While you are redesigning Wihu ... here are two critical comments I got from numerous "newbies" who used my unattended DVD: The first comment was about the two user creation dialogs. It was not clear to them why the first user got a dedicated page and all the other users should be created on a different, not similar looking page. Maybe it would be easier if all users would be created on 1 page and the default user would simply be marked by some option (which could default to the first created user ) The second comment I got was very consistent in that no user who operated Wihu got the idea that he could be changing the default shell folders or any other option simply because no one would right click on a user and look into the detailed settings dialog. Maybe it would be easier if there was a more prominent button next to each created user labeled SETTINGS or change settings or something that people would actually notice. The above comments are of course just suggestions. If someone knows Wihu, he will certainly find his way but newbies operating it sometimes need a different approach but it is up to you ... Everyone was very happy with the installation part of Wihu by the way ! :-) Bye, Alex

Thanks, Benjamin ! I appreciate your continuing work and support for us Wihu users ! Looking forward to test your next version ! Bye, Alex

Thanks a lot for the explanation, Dahi ! Bye, Alex

Yeah, that did it, soulin ! Thanks alot !!! Bye, Alex

Hi again, Dahi, I guess I was too early with my assumption. It is not working correctly yet. Or I am too stupid FOR /F "TOKENS=3*" %%i in ('reg query "HKCU\Software\VirtuaMedia\ZoomPlayer" /v InstallDirectory ^| FINDSTR "REG_SZ" ') do set MYINSTALLPATH = "%%i %%j" ECHO ZoomPlayer was found in %MYINSTALLPATH% The outcome of this was: ZoomPlayer was found in No matter, what name I choose for the variable, be it WHERE or MYINSTALLPATH or anything else ... it does not get echoed correctly. Does the name of this variable really matter ?? I checked by using "set" before echoing the variable and the variable MYINSTALLPATH was set correctly but I still cannot "use" it ?? Probably just a minor thing but .... Thanks for your help ! Alex

Hi Dahi, as usual, your tip works great, thanks ! If you don´t mind ... could you give me some theory as to why it works that way ? I understand the reason behind the "*" after tokens but I have no idea why a second variable "%%j" would be necessary .... thanks, you helped a lot ! Bye, Alex

Hi guys, I am sorry to bother you with this but I cannot find the solution to this so I hope someone might have an idea or even a solution to this problem. I am trying to query a string from the registry and put the result in a variable from inside a batch file. The information I want to retrieve out of the registry is the installation path of ZoomPlayer. It is stored like this in the registry: [HKEY_CURRENT_USER\Software\VirtuaMedia\ZoomPlayer] "InstallDirectory"="C:\\Programme\\Zoom Player" Now, I am querying the registry with this command: FOR /F "TOKENS=3" %%i in ('reg query "HKCU\Software\VirtuaMedia\ZoomPlayer" /v InstallDirectory ^| FINDSTR "REG_SZ" ') do set INSTALLPATH = "%%i" This works fine except for one small problem. It will always retrieve this result: "C:\Programme\Zoom" This means, it will stop at the first blank instead of retrieving the whole path. Of course this is useless ! I have tried all kinds of things to get around this but found no working solution. Any ideas ? Thanks for your help ! Bye, Alex

Hi again, as it turns out, I had a small cosmetic problem during installation now because a cmd window would now open during the installation of the hotfixes and display (echo) the installation of every hotfix and firefox extension. CMD /C was not enough if "for" was used. But I managed to solve that one on my own I just added this: @echo off & cmdow @ /HID & to the command, before start /wait and it works now without any cmd window opening. So the final commands are like this: REG ADD %KEY%\007 /VE /D "Windows XP PostSP2 Updates" /f REG ADD %KEY%\001 /V 2 /D "CMD /C for %%i in (%CDROM%\Setup\Updates\*.exe) do @echo off & cmdow @ /HID & start /wait %%i /passive /norestart /quiet" /f REG ADD %KEY%\008 /VE /D "Mozilla Firefox 1.0 inkl. Extensions" /f .... REG ADD %KEY%\008 /V 6 /D "CMD /C for /R %CDROM%\SETUP\Firefox\xpi %%i in (*.xpi) do @echo off & cmdow @ /HID & start \"\" /wait \"%PROGRAMFILES%\Mozilla Firefox\firefox.exe\" -install-global-extension %CDROM%\SETUP\Firefox\xpi\%%~ni.xpi" /f

Dahi, you know what ? YOU ARE A GENIUS ! Thanks a lot, it works perfectly ! Bye, Alex

Hi guys ! THANKS ! Both asbsamsf´s and Dahi´s version work fine now. The problem was that I had my test files on the Desktop and SET CDROM was containing the path to it. Seemingly there are no spaces allowed in there so thats where the error was. HOWEVER, I now have a problem with the execution of the commands. The Hotfixes install fine, but the Firefox extension installation has a problem. As you can see on the picture (although in german) Windows wants to find a file named "-install-global-extension if this command is run ... Of course it cannot find it and causes an error message to appear. I have no idea how to correct this, the installation works fine if I use this command (without any "for"): REG ADD %KEY%\009 /V 1 /D "\"%PROGRAMFILES%\Mozilla Firefox\firefox.exe\" -install-global-extension %CDROM%\SETUP\Firefox\xpi\disable_targets_for_downloads-0.8-fx.xpi" /f But the same command using the "for" command causes the error message. Thanks for your help, Alex

Hi Dahi, thanks ! But unfortunately, I still get the message "Too many command line parameters" .... Bye, Alex

Hi guys, I have been playing around with this and I have been looking for a solution but cannot find it ... I would like to use the "for" command in runonceex. But it won´t work. I cannot even get the command to transer properly to the registry ... Here are two commands from batch files I would like to use in the runonceex instead: 1. 1. for %%i in (%CDROM%\Setup\Updates\*.exe) do start /wait %%i /passive /norestart /quiet" 2. for %%j in (%CDROM%\SETUP\Firefox\xpi\*.xpi) do start /wait "%PROGRAMFILES%\Mozilla Firefox\firefox.exe" -install-global-extension %%j So, I tried this in my runonceex: REG ADD %KEY%\007 /VE /D "Windows XP PostSP2 Updates" /f REG ADD %KEY%\007 /V 1 /D "CMD /C for %%i in (%CDROM%\Setup\Updates\*.exe) do start /wait %%i /passive /norestart /quiet" /f REG ADD %KEY%\009 /VE /D "Mozilla Firefox Extensions" /f REG ADD %KEY%\009 /V 1 /D "CMD /C for %%j in (%CDROM%\SETUP\Firefox\xpi\*.xpi) do start /wait \"%PROGRAMFILES%\Mozilla Firefox\firefox.exe\" -install-global-extension %%j" /f This gives me the error message: too many arguments (translated from German) So I tried with %i instead of %%i. This does not give an error message, however, the command for the Windows Updates in they registry key now looks like this: CMD /C for CDROMi /passive /norestart I then tried all sorts of things like add a "\" before each bracket etc. but nothing seems to work .... Mhh ... could need some help here if you have any ideas ... Thanks, Alex

Hi ! Just a question from a non Nforce board user. I wanted to make my unattended DVD work on all chipsets so I added Nforce, Via, Intel and SIS chipset drivers to my OEM folder and adapted the drivers path in winnt.sif. That works fine. However, NVIDIA released the Nforce Standalone kit drivers for Nforce 4 boards that look similar to the Nforce all in one drivers but only work for Nforce 4 boards. Can I add the folders from that standalone kit to my OEM folders for Nforce 4 support without causing troubles with Nforce 2/3 users using my DVD ? I know that Windows will only install the needed drivers from the drivers path but the inf /cat files from the Nforce 4 drivers look very similar to the ones from the Nforce All in one kit and I don´t want Nforce 2 board users installing the wrong driver .... I wish Nvdia would just release an updated all in 1 driver instead of this ... Thanks, Alex

Hi Benjamin, thanks, yes, it works now. Seemingly one has to add a command at the top group position (command.1 in your example), otherwise it does not work. I added a dummy command now and it works. Good luck then ! Bye Alex

Hi XPect, thanks for your help. However, I don´t get it ... I tried this: [Diverses] Description.0=Programm 1 command.0=CMD /C "%WIHU%\..\Test\silent_install.cmd" workdir.0="%WIHU%\..\Test" selected.0=0 group.1=1 Description.1.0=Option 1 command.1.0=CMD /C "%WIHU%\..\Option1\silent_install.cmd" workdir.1.0="%WIHU%\..\Option1" selected.1.0=0 Description.1.1=Option 2 group.1=1 command1.1=CMD /C "%WIHU%\..\Option2\silent_install.cmd" workdir.1.1="%WIHU%\..\Option2" selected.1.1=1 Description.2=Programm 3 command.2=CMD /C "%WIHU%\..\Test2\silent_install.cmd" workdir.2="%WIHU%\..\Test2" selected.2=1 The result is that only program 1 is displayed. I am tired ... Bye, Alex

Hi Benjamin, I hope I am not disturbing your studying for exams too much ... Just came across a situation where I would want an option in Wihu to toggle between two programs to be installed. The reason is this: I want to give the user an option to choose between two versions of a program to install. Version 1 and 2 for instance. He can choose to install version 1 or versions 2 or no version at all but he should not be allowed to check both versions since that would lead to conflicts during installation. I am not sure if there is a command for this yet in Wihu. Or is there ? It should be that if the user selects version 1, he should not be able to check version 2 anymore and vice versa. Anyway, would be nice to have something like that ... Thanks , Bye, Alex

Hi ! It´s still not working unfortunately. But thanks for your help anyway ! Bye, Alex

Hi ! Sure, I have attached it to my post. If it is not too much work could you highlight any changes you make so I could learn something from it ? Thanks anyway ! :-) BYe, Alex

Hi ACEOFNOS! Thanks for your help ! Well I tried your file but it behaves similar to a modified inf I tried some time ago. If I try to update the driver choosing the option shown in the pic, Windows will tell me that it cannot find a matching driver at that location. I have to choose the option " Don´t search, choose the driver myself" in order to install the new driver. This however will not work during unattended installation. Windows would not use the driver in that case. Thanks, Alex

Hi ! Maybe someone can help me with this ... I have a NIC, a Surecom model based on the Realtek 8139 chip. Installing the latest Realtek drivers works fine, I am sure of that, however the Surecom model does not appear in the drivers inf file so I have to force Windows to take this driver and acknowledge quite a few warnings doing so. I would like to add the driver to my unattended installation but obviously, Windows will not use that driver for my NIC. Is there any way I can make Windows take that driver ? Obviously I will have to adapt the inf file somehow. I even tried this before, I placed the Hardware ID of my card in a few places inside the inf but it did not change much. I probably did not do it the right way. Also there are quite a few ID`s available to choose from in the cards properties. Hardware ID´s, compatible ID´s and a few others. I don´t really know which one to choose. I have attached the Realtek drivers inf file to this post and the ID`s of my card are as follows: PCI\VEN_10EC&DEV_8139&SUBSYS_032010BD&REV_10\4&2E98101C&0&50F0 PCI\VEN_10EC&DEV_8139&SUBSYS_032010BD&REV_10 PCI\VEN_10EC&DEV_8139&SUBSYS_032010BD PCI\VEN_10EC&DEV_8139&CC_020000 PCI\VEN_10EC&DEV_8139&CC_0200 PCI\VEN_10EC&DEV_8139&REV_10 PCI\VEN_10EC&DEV_8139 PCI\VEN_10EC&CC_020000 PCI\VEN_10EC&CC_0200 PCI\VEN_10EC PCI\CC_020000 PCI\CC_0200 pci\ven_10ec&dev_8139&subsys_813910ec&rev_10 Any ideas ? Thanks in advance ! Bye, Alex