`Felix`

1. :: set the default packer if you do not use the command line option. :: WinRAR or 7-Zip set packName=7-Zip Change set packName=WinRAR or !makeit.cmd /rar 2. "NeroVision" is correct. For the shortcut, add the following to your post_config.cmd file. search for: if /i exist "%basetarget%\Nero ShowTime\ShowTime.exe" ( shortcut /a:c /f:"%shortcutFolder%\Nero ShowTime.lnk" /t:"%basetarget%\Nero ShowTime\ShowTime.exe" /d:"Watch your favorite DVD-Video movies and turn your computer into a home cinema.">NUL 2>&1 ) on a new line under this entry add: if /i exist "%basetarget%\NeroVision\NeroVision.exe" ( shortcut /a:c /f:"%shortcutFolder%\NeroVision.lnk" /t:"%basetarget%\NeroVision\NeroVision.exe" /d:"Make great looking VCDs, SVCDs and DVDs with spectacular menus. Capture video from your DV camera, video card or TV tuner card. Create amazing slideshows. Cut and edit your own movies with spectacular effects.">NUL 2>&1 )

LOL *tries to make list* EDIT: on another note, new version isnt quite working for me when i 7-zip it it just stops after "Registering DLL's" gonna try winrar now <{POST_SNAPBACK}> hi pplz, 1.2.2 is now available See change log on first post for details... Enjoy!

Is in the manual that i am finishing... full complete instructions. stay tuned... Will all be available in the 1.2.2 release.

What "manual" tasks are you referring to?

well firstly have you tested the installer manually to make sure it is working? then we can eliminate that the installer is faulty and sort out your run once coding. <{POST_SNAPBACK}> i hav tried it .. it works.. so i put it in my UACD & reinstall clean windows & no signs of nero on my newly installed windows all.. even if i try to install again the same thing happens.. <{POST_SNAPBACK}> Ok then well then we know it is a problem with your RunOnceEx.cmd configuration. Attached is a copy of one of mine, have a look at that and make sure you are using the same syntax for running from CD. RunOnceEx.cmd

Hi Neanderthal, Thanks for the good news. We can use that reg tweak because that is specific to your machine SID. There are ways of doing it but, we would need to add an extra tool to the kit called getsid.exe and the amount of coding and the time to process this during the post_config.cmd processing would be not worth the benefit. But keep those ideas, suggestions and tweaks coming

well firstly have you tested the installer manually to make sure it is working? then we can eliminate that the installer is faulty and sort out your run once coding.

because 1.2.2 will be available in the next 24 hours. currently only 1.2.1 is available.

Ok have corrected that too

Actually my scripts work with nero-* and nve-* (package1 and package2) I have not had any requests for features from pack3 and 4 - are these features you would like to have - from pack 3 and 4 i mean? or if you are only after 1 and 2 - then the scripts do that right now... simply have the scripts in the same directory/folder as your nero-* and nve-* and run it... make sure you list all the features you want in the "Start User Configuration Preferences" section of the !makeit.cmd file and thats it... The possible features to add the the "tlist" line are as follows: CoverDesigner, ImageDrive, Nero BackItUp, Nero MediaHome, Nero PhotoSnap, Nero Recode, Nero ShowTime, nero soundtrax, Nero StartSmart, Nero Toolkit, Nero Wave Editor, NeroVision, WMPBurn Hope this answers your question.

well as you can see in the script the compression being used is "-t7z" - according the 7zip helpfile is the best. I have just done a test here (!makeit.cmd /7zip) using the default settings and here are the results.custom_nero (WinRAR): 28,367Kb - using best compression available WinRAR v3.41 custom_nero (7-zip): 27,614Kb - using normal compression 7-Zip v4.15b custom_nero (7-zip): 22,787Kb - using ultra compression 7-Zip v4.15b Basically after some more experimentation and reading i found another additional switch to add the the 7-zip commmand line to switch on ultra (i thought that it was the best compression just by selecting 7z format) anyway i have updated the command line for the next build. You can make the change to your current !makeit.cmd script now to take advantage of the extra compression (NB takes 4-5 times longer to compress) Look for the following command line in the !makeit.cmd file (towards the bottom) "%zipPath%" a -t7z "%installerName%" %TmpPath%\* -r -y >NUL 2>&1 Change the line to: "%zipPath%" a -t7z -mx9 "%installerName%" %TmpPath%\* -r -y >NUL 2>&1 The important part here is -mx9 - Thats it! Hope this answers your query

Hi Albert, Can you tell me what updates you are referring to? Please give me as much information (URL's are handy) and i will look into it.

So you have it sorted now?

Yeah well i have been testing on many type of configurations and i forgot to change it back to %programfiles% when i packed it up.. sorry! slimzky - what are you refering to with "ahead"?

We don't we simply use the nero burning rom

yes - so please send me the latest version an i will include it for future builds... and of course you can update it at your source... Not with the 1.2.1 update coming in the next couple of hours... will on build the shortcut if the exe is present. Only the essentials. Full documentation will be complete in the next 24 hours. I was getting some pressure for the updates so i have made them available to fix a number of problems in 1.1 release. True, but that is part of making the product better...

The SOE's i have built for a number of Enterprise's i have worked for over the years have used many methods including the scripts and floppy approach you mention. Basically what is the best solution for the organisation, may and will vary based on the infrastructure available and business requirements they have. 1. Floppy/script approaches often are used in a Novell server environment when you have an unattended source available that you boot to the network from a floppy and then automatically run the unattended installation. This method can be time consuming to deploy to a large organisation - but it works! 2. CD Unattended installations are great and faster as you can have multiple copies of CD's and have a number of machines building at once without real impacts on the network, however it can be time consuming again in big organisations and people intensive. 3. Build a master machine image using a unattended installation and then "ghost" (or equivalent) the machine image. This is very handy as you can then multicast the image to numbers of machines at once... Down side is network traffic impacts, and if you don't have a fleet of like machine configurations (don't need to be exactly the same, but similar) you can have some issues with the single common image. Microsoft also have similar process for doing similar things and this is essentially what they do in-house. 4. Part build images - this is when you load the TEXT based component of the installation onto a machine and then image it... this can often be very good if the organisation has many different machine configurations - then you can deploy a common "base" image and then let the machines build themselves... down side - can be slower than method 3, but best all round approach. This is also the idea of the method behind longhorn installations in the future to speed up the installation process. I have used all these methods and a few variations on these - but as i said you need to base the solution based on the infrastructure and requirements of the business. Hope this information helps. If you want to speak about specific issues, feel free to PM me.

will add as a command line switch to next build good idea...

thanks for your help Ice

did you change the path in makeit!.cmd? as for the cmd boxes, i'm not talking about that, im talking about the part where it says registering dlls and stuff like that but i think i just thought of how to do it edit the post_config.cmd right? <{POST_SNAPBACK}> yep thats right you will find statements like the following cls echo. echo Loading registry settings... You can safely remove these statements and this will then eliminate the dialogue boxes. Hope this information helps

hi there just rem line 60 for now... i need sleep will look at it tomorrow. have also updated the archive with the rem version.

Hi lilweirddude, Good to hear it all went well 1. Yep there is in (i am guessing you are speaking about the self extractor?) if you use winrar then in the comment file you can change the silent=0 to either silent=1 for total silent install or silent=2 for a progress bar dialogue. 2. New uninstaller option in version 1.2.0 now available... as for the version you have installed - simply delete the files added and remove the registry settings and shortcuts.. or grab the uninstaller.exe file from the latest archive and then run the following: [path_to_uninstall_file\uninstall.exe /remove I put the "/remove" in the as a safety feature in case a user just double clicks it... try it if you like it will notify you that you need to run the correct command line for it to work. Hope this answers your questions.

Ok people - finally v1.2.0 is available.... please test and let me know if you find any problems. I have done alot of testing on a range of machines already but can't test every possible choice. There are some major changes to the !makeit.cmd file - instructions within and you should find it easier to setup now I will be updating the first post with Q&A and instructions tomorrow as it is 2.10am here and i need some sleep.... Enjoy!

Please i could help... as for the inf files - good idea... as a secondry project later a simply little application that will allow the generation of these inf files would be handy... in the meantime over the next couple of weeks i will begin building some english inf files that can be made available here for users. Look forward to the next build

Ice you are right we will have to stop meeting this way The code works well - couple of questions... 1. If i want to add as a default say "sub0" but i don't want to have it in tlist var (want to have it in the code as default) where and how would i put it? 2. I have been playing with this code below? Do you think that would be a better "cleaner" option and if so, any idea on how i would incorporate the list? DIR "%TmpPath%" /AD /B | FINDSTR /R /V /I /C:"Common Files" /C:"sub0" /c:"sub1" /c:"sub2" /c:"sub 5" /c:"sub 8" /c:"sub 9" So in this i have "common files" and "sub0" that will always been there and the rest will be variable based on the contents of %tlist% Thanks very much for all you help - it has been invaluable!