Are you trying to open the port on the LabVIEW side twice? You can only open a port once or, more specifically, you can only bind one socket. If you are trying to "multicast" then you must use a multicast address, however, you will still open only one socket.
This is quite common so I wouldn't feel too left behind. Moving to a newer version represents a significant project risk and if/when you upgrade (which should be for a very good reason rather than there is just a new one) it's better to let other people find all the bugs/issues and any work-arounds for them. I'm still on 2009 which is far more stable and performant than than 8.6 (and, anecdotally/arguably, more performant than everything to date) and I'm waiting for a feature list or bug list that warrants an upgrade.
However. Back to toolbars. The change was made in 2011. 2009 and 2010 both have the (much better IMHO) standard 3D button bar.
Unbundle the error cluster after the Error Message Dialogue VI and "OR" it with the stop button to terminate the loop. The loop will then stop if there is an error or if you press the stop button.
Hmmm. In 2009 and 2010 it was max 8 per exec, per priority irrespective of the number of cores. Max 200+1 in total.
I've just looked in 2011 (I rarely use it) and indeed you seem to be right; you can set 20. However, it can be set to 20 on both my Quad core (8) and my dual core (4) so I think they just bumped up the limit rather than made it scalable in accordance with number of cores.
You can still use a Get method. Just you have to make it a singleton (which is the default for a VI, but you have to program it for classes-e.g use a DVR).
Wiring through error clusters (if they exist) is recommended since if someone wires them up it will clear any errors on the wire from previous operations which is unexpected bahaviour.
Thats because I cut and pasted your seed, method so it's not surprising (i.e you were trying to fit 1,0000,0000 x 1,000,0000 chars in memory)
There's no pleasing some people