1) Prepare a batch with unattended switch to install
![;)](http://reboot.pro/public/style_emoticons/default/wink.png)
For Visual C++ 200X support: "vcredist_x86 Install.cmd":
vcredist_x86.exe /Q"winpcap Install.cmd":
winpcap-nmap-4.02.exe /Salso winpcap script available here
"ghostwall Install.cmd"
ghostwall_setup.exe /silent
ps: we will have a set of ready batches in time.
1b) One can use junction when available. Check here post 13.
1c) If there is an unattended switch to install other than %programfiles% , with some little batch tricks one can find nice ways for big sized applications
![:cheers:](http://reboot.pro/public/style_emoticons/default/cheers.gif)
Method is I hope explaining itsself.
Idea is having setups of these applications on a removable media Ready for usage with a batch (.cmd) file, like amalux's marvelous collection of portable application.
Also when available it maybe preferred to have junctions with especially big sized applications or 1c).
Advantages/Disadvantages of the mentioned method exists , it is up to users, however I guess most of you like the Advantages part
![:cheers:](http://reboot.pro/public/style_emoticons/default/cheers.gif)
LiveXP Notes:
For a general easy to use:
*
I strongly advice to use this method with BootSDI (you can use wimpack) + some free space.
![:cheers:](http://reboot.pro/public/style_emoticons/default/cheers.gif)
ps: When you use wimpack, keep default settings for "Pack 'Program Files' folder + Individuallly" to have junction when available.
*
Besides well known scripts that are used on most builds like mmc, penetwork, ....,
Enabling Windows Installer (msi.script), ScriptingCore.script, ScriptingSup.Script (Basic-->Shells-->Addons) and LODR-loader.script, LODR-Thinstall_Support.script (Apps--->Supplementary) will help many installers work without problem.
**
As usual script selection is about your aim, list here only to point the available scripts in the project. Further is up to user.
***
Out-of-the-box LiveXP even with selecting additional LODR-script you may miss some dependancies, We hope user support will lead us some new LODR-Script(s) to provide dependencies in future
![:(](http://reboot.pro/public/style_emoticons/default/sad.png)
*
For vc2005 applications, here is the trick, ready & packed. (Thanks to Colin Finck's BartPE plugin for old days
![;)](http://reboot.pro/public/style_emoticons/default/wink.png)
http://lancelot.winb...Colin_Finck.rar
example: after booting LiveXP, use vc2005rt_install.cmd. Than use "vcredist_x86 Install.cmd" you prepared before.
![:)](http://reboot.pro/public/style_emoticons/default/smile.png)
VistaPE Notes:
So far i only know, joakim's lodr packages work on VistaPE
![:angry:](http://reboot.pro/public/style_emoticons/default/mad.gif)
I will be glad to add any notes to post#1 here from VistaPE users.
![:cheers:](http://reboot.pro/public/style_emoticons/default/cheers.gif)
Historical Notes:
sanbarrow is THE man behind the whole LODR idea.
I am sure he have lots of tricks in his pockets since he is the man who has a wide set of LODR ready packages.
I hope he share his wisdom for LODR-U idea too.
Thanks to sanbarrow, providing this switches through topics reminding other users there is another way naturally exists.
Lancelot (I) asked for "General LODR" packages many times to sanbarrow in past......
Than one day, a LODR hero came from the west when sun was just going down , joakim.
joakim is our LODR-U man who made first "special" LODR-U packs. He prefered Universal than General and why not.
-U refers universal meaning (preferably) project independant.
Comparing with sanbarrow's LODR packages (some of which are already LODR-U), joakim's LODR-U packages aim to work on moa, LiveXP, VistaPE, xxxPE.......
And Story goes on with current section, with the voice of a cowboy song behind the scene.
CU
![:cheers:](http://reboot.pro/public/style_emoticons/default/cheers.gif)
Edit:
lodr virtual-box code that can be converted to lodr-u easly to use on livexp, thanks to sanbarrow
http://sanbarrow.com...php?p=6095#6095