Note: 
All scripts using registry keys to determine location of A2 and A2:OA
No files are moved, copied or removed by these scripts

------

for ARMA 2: Combined Operations
solution to enable ingameUI modification manager
(when -mod are used the modification manager is disabled)

Windows Seven, Vista users using inbuilt mklink


[code]
mklink /j ".\Addons" "..\ARMA 2\Addons"
mklink /j ".\Dta" "..\ARMA 2\Dta"
mklink /j ".\Keys" "..\ARMA 2\Keys"
mklink /j ".\userconfig" "..\ARMA 2\userconfig"
[/code]


Windows XP and Server 2003 users with NTFS drives needs use this from SysInternals
http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx


[Code]
junction  ".\Addons" "..\ARMA 2\Addons"
junction  ".\Dta" "..\ARMA 2\Dta"
junction  ".\Keys" "..\ARMA 2\Keys"
junction  ".\userconfig" "..\ARMA 2\userconfig"
[/code]

this will automatically enable your game to load ARMA 2 content w/o need to use -mod switch 

now you can add / remove mods in the UI interface

there are 3 problematic

1. you cannot enable/disable ARMA 2 off the list and it looks disabled
* yet it works, so no issue

2. all servers with retail A2:CO will show as Red with question mark
* yet You can join and play, yet it works so no issue

+ there is 1 downside of this

3.
if you host you will be shown as w/o the CA and thus A2:CO users can't play with You 
* can't be resolved w/o data wise changes, no big issue if you not hosting


-----

for ARMA 2: Combined Operations
solution to make visible mods located in ARMA 2 directory for your OA ingameUI modification manager

if you have @ACE in ARMA 2

[Code]
_junctionTHISmod4me.cmd modfoldername 
[/code]

example
 _junctionTHISmod4me_Vista&Seven.cmd @ACE

note: again WindowsXP and Server 2003 users need use Junction from sysinternals
http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx

_junctionTHISmod4me_windowsXP.cmd @ACE