midiboy

Thanks, SiMoNsAyS ! I adapted the cmd and posted it in my previous post ! Bye, Alex

Hi! Thanks, Alanoll for your quick help ! It took me a while to test this but it does indeed work !!! You are a genius !! Is this a universal variable or only available for your msi ? Because I searched for something like this and could not find anything like it, the set command does not reveal that variable either. If that were a universal variable available systemwide that would be wonderful ! Thanks, Alex

Hi Benjamin, thanks, implementing this would be great ! Also if you have time some day, redesigning the first dialog to make use of added space would be nice ! Thanks, Alex

Hi guys, thank you very much for your help everyone ! @ckitching: thanks, using your idea made me realize that I had set the same workdir for all commands, stupid me ! Everything works now, the way I posted it ! @ tjhart85: I prefer to use batch files so I can have the same command in Wihu for everything and can also install silently without Wihu (should I ever need that)

Hi a06lp, in what way does this use relative paths ? Bye, Alex

Hi Alanoll (or others) I am trying desperately to use a relativ path for the winamp.ini but it does not work not matter what I try. The msi and the winamp.ini are in the same directory and my batch file should look something like this: start /wait .\Winamp.msi /qb ini=".\winamp.ini" Winamp.msi is found but the winamp.ini file isn´t found by the msi. I tried all kinds of combinations like ini =winamp.ini, ini=\winamp.ini, ini=.\winamp.ini, etc. etc. but nothing works. Why do we have to use absolute paths here ? The problem with absolute paths is that I have to adapt the batch file calling it depending on where the folder is ( my harddisk, CD etc.) and I would really like to avoid this. I did a search for "relative paths" on this forum but nothing really useful came up. I did come up with a post from you where you used a variable called %SETUPDIR% but it did not work here. There must be a solution to tell the msi where the ini is using relativ paths, no ? Please help ! Thanks, Alex

HI ! Sorry for this (probably newbie) question but I have been playing around with this for 2 hours now but cannot find the solution ... so I need some help here ... I am trying to call a cmd from Wihu. That cmd is one directory up from the Wihu directory and then one directory down: Setup --| |-- Wihu |-- Dscaler5 (with cmd and Dscaler5005.exe inside) So inside Wihu (install.ini) I call the cmd like this: Description.1=DScaler 5 command.1=CMD /C "%WIHU%\..\Dscaler5\silent_install.cmd" workdir.1=%WIHU%\..\Dscaler5\ The cmd itself looks like this and works if I double click on it inside the DScaler5 directory: start /wait DScaler5005.exe /VERYSILENT However, if I let Wihu call this cmd, then DScaler5005.exe cannot be found ! Could you please tell me how I should set the work directory or anything else in install.ini to make this cmd call the exe from Wihu ? I would like to leave the paths relative so I can call the cmd from the directory and from Wihu no matter if I am installing from CD or from harddisc. This should be possible, no ? I am sorry if this has been covered before, I looked through all the helpfiles ... Thanks, Alex

Hi ckitching! Thanks, thats what I was looking for ! Cool ! Alex

Hi again, as for point 1 ... after some thinking, this helppanel is not as bad as I first thought. Might need it after all ... but .... Could you make it remember it´s position and size or influence the width of the helparea in another way ? Because, if I do not use the help area it is too big and if I intend to use it, then I would need more space Also, something about the resizing of Wihu ... If I resize Wihu and make it remember the size, which works fine by the way, the first screen will not make use of the added space at all ! It looks very bad that way. This is not the case with all other screens, just the first screen keeps using the default space. Could you maybe change that ? (see pic) Thanks, Alex

Hi Benjamin, starting to use Wihu for software installation purposes now ... I know, I am late Could you tell me two things .... ? 1. I would like to disable the help panel completely ( should not be shown at all or remain invisible if moved completely to the right .... 2. I don´t need section names actually because I will just install a few apps. Currently this is not possible. And last but not least, not related to software installation purposes ... 3. Is it possible to add a switch to the [users] section to make all users that are created in Wihu Administrators using unlimited passwords ? Something like Group.0=1 Status.0=0x10028 but for all users ? Thanks, Alex

HI again, it also works on my second PC, I just did a new installation there. I also compiled a cmd file for you that sets all file associations Isobuster offers in the interactive installer. (thanks, SiMoNsAyS for your help on this ! ) fileassociations.cmd : @echo off cmdow @ /HID M Short %PF% Variable FOR %%A IN ("%PROGRAMFILES%") DO SET SHORTPF=%%~sA REG ADD "HKLM\SOFTWARE\Classes\.iso" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.bin" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.cif" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.vcd" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.vc4" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.fcd" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.gcd" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.img" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.dmg" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.c2d" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.cdi" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.dao" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.tao" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.ccd" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.cue" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.bwt" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.cdi" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.b5t" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.b5i" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.mds" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.mdf" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.nrg" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.pdi" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.pxi" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.P01" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.gi" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\.cd" /VE /D "IsoBuster" /F REG ADD "HKLM\SOFTWARE\Classes\IsoBuster\DefaultIcon" /VE /D "%SHORTPF%\Smart Projects\IsoBuster\IsoBuster.exe" /F REG ADD "HKLM\SOFTWARE\Classes\IsoBuster\shell\Öffnen\command" /VE /D "%SHORTPF%\Smart Projects\IsoBuster\IsoBuster.exe \"%%1\"" /F Bye, Alex

Ok, I verified that this method is working by installing in a fresh new virtual machine. No problem whatsover. The only problem that appeared was with VMWare. Somehow, the ALT-F4 command in my vbs script used to close isobuster.exe triggered an error in VMWare. (see pic) After recognizing the message, everything worked normal.

OK Guys, here it is ... my solution ! I am glad I can finally come up with a real working solution for this problem altough I am sure there are much more elegant ways to do this. But I am no programmer, I just collected info from various threads on MSFN and sort of pieced it all together. I have not tried this on a fresh unattended installation yet but I tried on my local machine and it worked there so it SHOULD work. I will test on a virtual machine soon but I see no reason why it should not work so here it is: As I said a few posts before the problem with IsoBuster registration is, that it is machine specific AND installs the reg info into the HKCU part of the registry so the only solution I can think of that would work on every machine and for all users would be to register Isobuster interactively using a script and then somehow copy the registry information from the current user to the default user. Since I have no idea how to inject data into the default user branch once Windows is past the T12 stage ( I tried various ways like using the .Default branch in the registry, but nothing worked) I came up with a workaround. What we will do is install Isobuster silently during unattended installation, then run a script to register Isobuster. Then, right after that, a batch file will read the 7 ID numbers generated during registration and add them to a file called "isobuster.reg" in the default user directory. Of course the file is generated in a way that makes it a valid reg file. Then, all one has to do is make sure that this regfile gets processed whenever a new user is created. That is easy, one simply has to add an entry to the runonce entry in the HKCU\Software\Microsoft\Windows\Current Version branch. Since I am doing this anyway for registry entries that I want processed when a new user is created I just have to add the isobuster.reg file to the batch. OK, here is what I do step by step: 1. In cmdlines.txt add this entry: "REGEDIT /S RunOnceUser.reg" "REGEDIT /S isobuster.reg" The second one is just a small reg file that will make sure that IsoBuster won´t pop up the "connect to check for Upgraded dialog" after registration is finished. It contains these lines: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Smart Projects\IsoBuster] "VersionCheckCriteria"=dword:00000000 Make sure this is in the same directory as cmdlines.txt also. 2. Add a file called RunOnceUser.cmd in the same directory as cmdlines.txt containing this code: cmdow @ /HID @echo off SET KEY=HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce REG ADD %KEY% /V 1 /D "%USERPROFILE%\startup.cmd" /f 3. In the ...\$OEM$\$Docs\Default User folder of my installation DVD I add a file named "startup.cmd" and this contains these lines: @echo off cmdow @ /HID REGEDIT /S "%USERPROFILE%\isobuster.reg" attrib -R "%USERPROFILE%\isobuster.reg" DEL "%USERPROFILE%\isobuster.reg" DEL /F /S /Q "%USERPROFILE%\startup.cmd" exit This will make sure that the isobuster.reg file gets loaded into the registry when a new user is created. 4. Now for the ISOBUster installation itself using my runonceex.cmd: REG ADD %KEY%\029 /VE /D "ISO Buster 1.7" /f REG ADD %KEY%\029 /V 1 /D "%CDROM%\Setup\IsoBuster\IsoBusterSetup.exe /VERYSILENT /SP-" /f REG ADD %KEY%\029 /V 2 /D "taskkill.exe /F /IM isobuster.exe" /f REG ADD %KEY%\029 /V 3 /D "WScript.exe %CDROM%\Setup\IsoBuster\register.vbs" /f REG ADD %KEY%\029 /V 4 /D "CMD /C %CDROM%\Setup\IsoBuster\reg4defaultuser.cmd" /f The first line installs Isobuster silently. The second kills the isobuster registration dialog The third one calls a script that will start the registration dialog again ( a bit complicated to do it that way, I know but I didn´t know how to make a script that would use the open registration dialog the moment it appears ) The fourth line calls the batch file that will read from the registry and write the isobuster.reg file in the default user directory. 5. Create a file named register.vbs and place it into the Isobuster installation directory on the DVD: Set WshShell = CreateObject("WScript.Shell") Set FileSysObj = CreateObject("Scripting.FileSystemObject") ScriptPath = FileSysObj.GetFile(WScript.ScriptFullName).ParentFolder Cmd = Chr(34) & "%PROGRAMFILES%\Smart Projects\IsoBuster\isobuster.exe" & Chr(34) WshShell.Run Cmd WScript.Sleep(1500) WshShell.SendKeys ("FILL REGISTRATION ID IN HERE !!!") WScript.Sleep(300) WshShell.SendKeys ("{TAB}") WScript.Sleep(300) WshShell.SendKeys ("FILL SERIAL IN HERE !!!!") WScript.Sleep(300) WshShell.SendKeys ("{TAB}") WScript.Sleep(300) WshShell.SendKeys ("{ENTER}") WScript.Sleep(300) WshShell.SendKeys ("%{F4}") WScript.quit 6. Create a file named reg4defaultuser.cmd and place it also into that directory: @echo off echo Windows Registry Editor Version 5.00 > "%Allusersprofile%\..\Default User\isobuster.reg" echo. >> "%Allusersprofile%\..\Default User\isobuster.reg" echo [HKEY_CURRENT_USER\Software\Smart Projects] >> "%Allusersprofile%\..\Default User\isobuster.reg" echo. >> "%Allusersprofile%\..\Default User\isobuster.reg" echo [HKEY_CURRENT_USER\Software\Smart Projects\IsoBuster] >> "%Allusersprofile%\..\Default User\isobuster.reg" echo "VersionCheckCriteria"=dword:00000000 >> "%Allusersprofile%\..\Default User\isobuster.reg" FOR /F "TOKENS=3" %%i in ('reg query "HKCU\Software\Smart Projects\Isobuster" /v ID ^| FINDSTR "REG_SZ"') do echo "ID"="%%i" >> "%Allusersprofile%\..\Default User\isobuster.reg" FOR /F "TOKENS=3" %%j in ('reg query "HKCU\Software\Smart Projects\Isobuster" /v ID1 ^| FINDSTR "REG_SZ"') do echo "ID1"="%%j" >> "%Allusersprofile%\..\Default User\isobuster.reg" FOR /F "TOKENS=3" %%k in ('reg query "HKCU\Software\Smart Projects\Isobuster" /v ID2 ^| FINDSTR "REG_SZ"') do echo "ID2"="%%k" >> "%Allusersprofile%\..\Default User\isobuster.reg" FOR /F "TOKENS=3" %%l in ('reg query "HKCU\Software\Smart Projects\Isobuster" /v ID3 ^| FINDSTR "REG_SZ"') do echo "ID3"="%%l" >> "%Allusersprofile%\..\Default User\isobuster.reg" FOR /F "TOKENS=3" %%m in ('reg query "HKCU\Software\Smart Projects\Isobuster" /v ID4 ^| FINDSTR "REG_SZ"') do echo "ID4"="%%m" >> "%Allusersprofile%\..\Default User\isobuster.reg" FOR /F "TOKENS=3" %%n in ('reg query "HKCU\Software\Smart Projects\Isobuster" /v ID5 ^| FINDSTR "REG_SZ"') do echo "ID5"="%%n" >> "%Allusersprofile%\..\Default User\isobuster.reg" FOR /F "TOKENS=3" %%o in ('reg query "HKCU\Software\Smart Projects\Isobuster" /v ID6 ^| FINDSTR "REG_SZ"') do echo "ID6"="%%o" >> "%Allusersprofile%\..\Default User\isobuster.reg" exit Thats it ! A bit complicated the whole process but I don´t think it will get much easier with machine specific registration. Of course injecting the Registration data into default user part of the registry would be way cooler but I don´t know how to do that ! Hopefully the above works for you too ! Bye, Alex

Canar. This is ridiculous ! Don´t be so anal about all of this ! Aren´t there more important things to worry about than a silent installer of a free program ? Actually, you and Peter and the whole Foobar community should thank 1chaoticadult for spreading foobar and making this program more widely available. Until I read about this silent installer here, I had never used Foobar before and I have installed it on quite a few systems since, using 1chaoticadult´s installer. You should not only thank him for spreading foobar, you should also thank him for making a silent installer which your community did not provide yet. So even if 1chaoticadult has acted in an inmoral way (I can see where that accusation comes from ) you guys should not bash each other over some minor legal issue. Help each other with the bugs and make peace over this ! Just my 2 cents ... BYe, Alex

Well, I guess the solution would theoretically be to register Isobuster interactively during unattended installation using a vb or autoit script. This way, the machine specific ID´s get written to the HKCU part of the registry but of course only for the user that does the install. Then, one would have to read those 6 ID numbers from the registry (reg query ?) and somehow inject them to the HKCU part of the DEFAULT USER so every future user will get them. Doing this automatically is beyond my knowledge however. I know there are ways but I am not up to it. Maybe someone else can ? I just wonder why noone seems to have found a working solution for this yet, after all IsoBuster has been around for a while ... Bye, Alex

Hi again, I guess the problem with the long file names comes from the switches you used for the BootIso. I changed them like this: -h -n -o -m I hope this does not cause any harm except that the iso will probably not be readable under DOS or NT 3.51. Another thing I noticed, those context menu entries also appear on the Recycling bin now. Any idea how to get rid of those ? Thanks, Alex

Hi Yzöwl using your script gave me an error message when trying to create a Boot ISO of my AIO DVD folder. It says some file created by BartPE is longer than 110 characters. I integrated BARTPE into my MultibootDVD as described in the MultiBootDVD guide on MSFN and has always worked fine so I guess your script does not need to stop on files larger than 110 characters ... ?? Bye, Alex

No, it returns 0 if the string is found and 1 if it is not found. That is not the problem. I can see the errorlevel when I echo it. That works properly. The problem lies within the if command. If I check for errorlevel 0 instead of 1 then it will always jump to the same branch regardless of the errorlevel. If I check for errorlevel 1 it works. Bye, Alex

HI again, Shotgun, took me a while to answer because I had to test this on a "non SSE2 capable" system first and I didn´t have one around ... Anyway, it did not work as expected on an old Athlon PC. This is because the script checks for "SSE2" and "No" but strangely enough, CHKCPU will not mention SSE2 at all if the processor does not even support SSE. So I had to change the script to make it look for SSE2 and Yes. That worked but only like this: @echo off FOR %%d IN (c: d: e: f: g: h: i: j: k: l: m: n: o: p: q: r: s: t: u: v: w: x: y: z:) DO IF EXIST %%d\AIO SET CDROM=%%d %CDROM%\SETUP\CHKCPU\CHKCPU.EXE /v | %CDROM%\SETUP\CHKCPU\findstr.exe "SSE2" | %CDROM%\SETUP\CHKCPU\findstr.exe "Yes" > NUL rem echo %errorlevel% if not errorlevel 1 goto SSE2 if errorlevel 1 goto NoSSE2 :NoSSE2 start %CDROM%\SETUP\ffdshow\ffdshow-20041012.exe /S goto end :SSE2 start %CDROM%\SETUP\ffdshow\SSE2\ffdshow-20041012-sse2.exe /S goto end :end exit It does NOT work if I check for errorlevel 0 instead of 1. Any idea why ?? I was also able to complete a working script for checking the Chipset. To be more exact I had to make sure that the Intel Chipset uses one of the 6 ICH Southbridges because the INTEL IDE driver only works for those chipsets. Older chipsets are not supported anymore with the latest Intel Chipset driver so my script which uses CPU-Z goes liike this: @echo off %SYSTEMDRIVE%\CPU-Z\cpuz -file=%SYSTEMDRIVE%\chipsatz findstr /I Southbridge %SYSTEMDRIVE%\chipsatz.txt | findstr /I ich > NUL echo %errorlevel% >> %SYSTEMDRIVE%\chipsatz.txt rem echo %errorlevel% if not errorlevel 1 goto ich if errorlevel 1 goto end :ich start %SYSTEMDRIVE%\install\Intel\Setup.exe -INTELIDE -s goto end :end exit This has to be run from harddisc as CPU-Z needs to write a file. Of course I am in big trouble if findstr.exe suddenly outputs other errorlevels except 0 and 1 ! This won´t happen though, right ??? As for your last message, yes, I didn´t copy findstr.exe. Back then I didn´t even realize that this was a program I thought it was some kind of command like copy. Thanks for all your help ! Couldn´t have done it without you ! Bye, Alex

Hi ! Actually registering for all users does not seem to be that easy after all ... First I tried to load the registry settings (ID 0 to ID 7 or so ) from commands.txt during T12 stage so that the default user gets them and all future users will be registered properly. This did not work in the virtual machine because seemingly those ID`s are computer specific so they only work on one machine. I then gave up on that idea and wrote myself a little vb script that calls the isobuster.exe after silent installation and fills in the keys through sendkeys. This works obviously but since this happens during the unattended installation those keys only work for the Administrator account so if a new user logs on and tries to use IsoBuster it is not registered. Any ideas how to register IsoBuster for all users on more than one machine (should at least work in the virtual machine and on my main PC ) ? Thanks, Alex

Hi again, Shotgun, yeah well, in the meantime I found out that the problem is that CHCKCPU will not run from CDROM, at least that "findstring" code part won´t work there. I guess thats because it needs to write to a file to check for that string ?? Anyway, if I copy it to C: and run the script from there, it works so thats fine with me. I did add something similar to your code to my runonceex but thats not what I meant actually. I was asking if it is possible to add the whole code from the cmd to the runonceex, not just call the external cmd from the runonceex. But it is working now so thats not a big problem :-) I will try something similar for the Intel Chipset now .... Bye, Alex

PS: @ prathapml: I did read up on the links you gave me but turning off the "Import Wizard" using the code in one of those links seems to be either not working or there is another problem somewhere. I even asked this on the official Mozilla forum but no answer yet. I tried all kinds of combinations in all kinds of js files with all kinds of editors and formats, but the Import Wizard pops up each and every time Firefox runs for the first time and no profile for that user is present. So the only way, I see currently is to trick Firefox with that dummy profile. Ah, and sorry for the worng forum, I did give it some thought though. In my opinion, this thread is more about problems with an unattended installation than about switches Bye, Alex

Hi again, yeah, I know, Astalavista ... don´t be offended if I am reluctant to switch to your method of doing things, the same goes for SimonSays and others ... I have spent more than 30 hours on this and I need this to work now, otherwise I would need to call it a failure and I don´t wanna do that And I guess I found the solution to my problem. If I let Winrar copy the profile to the APPDATA folder by unpacking the dummy profile from an SFX into that folder, everything works fine. I have no idea why manually copying it with xcopy will not work but that may be some sort of Windows problem, how knows ... What I don´t quite understand is, why you guys here seem to concentrate on making default installation packages for users instead of finding ways to use as much ressources offered by the original installers as possible. I have read SimonSays´guide and to be honest, my head was spinning afterwards. This is sooo complicated. Less complicated but unneccessary in my humble opinion are installations where a preinstalled firefox folder and profile is being copied and then adapted to a new PC. This is no good practice with other apps and I don´t see a good enough reason for falling back to that "preWindowsNT habit" as I would call it. Anyway ... I think my installation is at least as easy as all the other methods used in this forum if not easier, while having the advantage to be very flexible if a new firefox version comes out or new extension are being used. IN addition to that, uninstalling Firefox is possible and Firefox manages profile creation on its own, without the need for any special VBS script or other tools to adapt an existing profile ... This is what I do: 1. Download any Firefox distribution in any language. 2. Unpack, replace Setup.exe with Setup.exe from Mozilla package. 3. Adapt config.ini to run in silent mode. 4. OPTIONAL: Copy Plugins folder from an existing firefox installation ( for Flash/shockwave plugins for instance) to a new location 5. OPTIONAL: Adapt default profile (prefs.js, bookmark.html etc.) in Firefox default/profile folder and copy that to a new location 6. Create a dummy profile that is just going to be used to install extensions without Firefox popping up the Import Wizard and copy it to a new location. 7. Pack the dummy profile (Mozilla folder in APPDATA) using Winrar, making an SFX (Mozilla.exe) using that code: Path=%APPDATA% Overwrite=1 8. Add this to a default.cmd to make Firefox the default browser: <<---- THIS PART IS FROM SIMONSAYS GUIDE ! THANKS !!! (I just took out 4 lines concerning MS IE that I am running during T12 stage so it affects the default user profile ) @echo off cmdow @ /HID REM Variables FOR %%A IN ("%PROGRAMFILES%") DO SET SHORTPF=%%~sA REM FIREFOX REG ADD "HKLM\SOFTWARE\Classes\.htm" /VE /D "FirefoxHTML" /F REG ADD "HKLM\SOFTWARE\Classes\.html" /VE /D "FirefoxHTML" /F REG ADD "HKLM\SOFTWARE\Classes\FirefoxHTML\DefaultIcon" /VE /D "%SHORTPF%\MOZILL~1\FIREFOX.EXE,1" /F REG ADD "HKLM\SOFTWARE\Classes\FirefoxHTML\shell\open\command" /VE /D "%SHORTPF%\MOZILL~1\FIREFOX.EXE -url \"%%1\"" /F REG ADD "HKLM\SOFTWARE\Classes\ftp\DefaultIcon" /VE /D "%SHORTPF%\MOZILL~1\FIREFOX.EXE,1" /F REG ADD "HKLM\SOFTWARE\Classes\ftp\shell\open\command" /VE /D "%SHORTPF%\MOZILL~1\FIREFOX.EXE -url \"%%1\"" /F REG DELETE "HKLM\SOFTWARE\Classes\ftp\shell\open\ddeexec" /F REG ADD "HKLM\SOFTWARE\Classes\gopher\DefaultIcon" /VE /D "%SHORTPF%\MOZILL~1\FIREFOX.EXE,1" /F REG ADD "HKLM\SOFTWARE\Classes\gopher\shell\open\command" /VE /D "%SHORTPF%\MOZILL~1\FIREFOX.EXE -url \"%%1\"" /F REG DELETE "HKLM\SOFTWARE\Classes\gopher\shell\open\ddeexec" /F REG ADD "HKLM\SOFTWARE\Classes\http\DefaultIcon" /VE /D "%SHORTPF%\MOZILL~1\FIREFOX.EXE,1" /F REG ADD "HKLM\SOFTWARE\Classes\http\shell\open\command" /VE /D "%SHORTPF%\MOZILL~1\FIREFOX.EXE -url \"%%1\"" /F REG DELETE "HKLM\SOFTWARE\Classes\http\shell\open\ddeexec" /F REG ADD "HKLM\SOFTWARE\Classes\https\DefaultIcon" /VE /D "%SHORTPF%\MOZILL~1\FIREFOX.EXE,1" /F REG ADD "HKLM\SOFTWARE\Classes\https\shell\open\command" /VE /D "%SHORTPF%\MOZILL~1\FIREFOX.EXE -url \"%%1\"" /F REG DELETE "HKLM\SOFTWARE\Classes\https\shell\open\ddeexec" /F 9. Add this to your runonceex.cmd ( of course adapting to your needs/paths etc. ) REG ADD %KEY%\008 /VE /D "Mozilla Firefox 1.0" /f REG ADD %KEY%\008 /V 1 /D "%CDROM%\Setup\Firefox\dummy\Mozilla.exe /S" /f REG ADD %KEY%\008 /V 2 /D "%CDROM%\Setup\Firefox\setup.exe -ira" /f REG ADD %KEY%\008 /V 3 /D "CMD /C xcopy /S /E /H /Y %CDROM%\SETUP\Firefox\plugins\*.* \"%PROGRAMFILES%\Mozilla Firefox\plugins\\"" /f REG ADD %KEY%\008 /V 4 /D "CMD /C xcopy /S /E /H /Y %CDROM%\SETUP\Firefox\profile\*.* \"%PROGRAMFILES%\Mozilla Firefox\defaults\profile\\"" /f REG ADD %KEY%\008 /V 5 /D "CMD /C %CDROM%\SETUP\Firefox\default.cmd" /f REG ADD %KEY%\009 /VE /D "Mozilla Firefox Extensions" /f REG ADD %KEY%\009 /V 1 /D "\"%PROGRAMFILES%\Mozilla Firefox\firefox.exe\" -install-global-extension %CDROM%\SETUP\Firefox\xpi\auto_copy-0.3-fx.xpi" /f REG ADD %KEY%\009 /V 2 /D "\"%PROGRAMFILES%\Mozilla Firefox\firefox.exe\" -install-global-extension %CDROM%\SETUP\Firefox\xpi\disable_targets_for_downloads-0.8-fx.xpi" /f REG ADD %KEY%\009 /V 3 /D "\"%PROGRAMFILES%\Mozilla Firefox\firefox.exe\" -install-global-extension %CDROM%\SETUP\Firefox\xpi\favorites_converter_(export)-1.0.1-fx.xpi" /f REG ADD %KEY%\009 /V 4 /D "\"%PROGRAMFILES%\Mozilla Firefox\firefox.exe\" -install-global-extension %CDROM%\SETUP\Firefox\xpi\flashgot-0.5.5-fx+mz.xpi" /f REG ADD %KEY%\009 /V 5 /D "\"%PROGRAMFILES%\Mozilla Firefox\firefox.exe\" -install-global-extension %CDROM%\SETUP\Firefox\xpi\ieview-0.84-fx-windows.xpi" /f REG ADD %KEY%\009 /V 6 /D "\"%PROGRAMFILES%\Mozilla Firefox\firefox.exe\" -install-global-extension %CDROM%\SETUP\Firefox\xpi\TargetAlert.xpi" /f 10. IN the cleanup phase I delete the dummy profile in %APPDATA% again, so that next time, when installation is finished and the Administrator (who runs the silent installation) needs to use the browser, a new profile is being created and THEN the Import Wizard is running (which is fine then for me). Thats it ! For my needs this is enough. The Import Wizard does not pop up while extensions are installed and I stay as close to what Firefox brings with it to install itself and extensions so I am more flexible in the long run. Just tested it and for the first time in all those long hours, this worked perfectly ! Bye, Alex

Thanks, Benjamin ! It works again ! Byebye, Alex

Guys, I really appreciate your chiming in here and I really appreciate all you different Firefox installation guides but instead of suggesting totally different ways of installing firefox it would help much more if someone would help me find the problem with my way of doing things ! I don´t want to sound rude or unthankful but I did read up on most of the common installation methods used in this forum (by SimonSays or Astalavista to name just a few) but they don´t fit my needs because I DON`T want 20 extensions included that I don´t need + all the themes and extras. Also the extensions I would need were mostly not included so this does not help me. Also, as I said in my initial post, I am using a German installation. I see nothing wrong the way I do this. This, to me, seems like a very clean way of doing this. The application and all extensions are installed on that machine, nothing is dragged over (and possibly not initiated properly) from a previous installation and only the things I need are installed. The ONLY (!!) problem I am having is, that when the first extension is being installed, the import wizard pops up. This is the thing I have to get rid of, either by finding a working switch or by succeeding in copying a dummy profile that will ONLY be used while the extensions are installed (it will get deleted later on ). DigeratiPrime, what are you talking about ? Could you please explain ? THANKS ! Thanks, Alex