ShaunR

No. As Phillip states. It is not a modem and therefore does not use Modem hardware signalling.

Not even a week and there's a patch?

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.

Use the VISA property node.

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.

Woah. Cats resurfaced. That's worth a "like" in itself

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.

So. Whats the verdict?. Likey, likey?

Why Do I Get Windows Error 1303 When Installing NI Software?

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.

The maximum is 8 per execution system, per priority. You can get your twenty by spreading them over 3 execution systems (for normal priority)

+1 for JSON.(strings) Strict typing is for wimps.

Some pragmatic info here. This is a bit outdated but still a good base reference.

Nope. Why do you need a cache for prefs? (let the OS do that) Kind of defeats the object.

No. I use a database (SQLite) nowadays for preferences.

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

A bit of lateral thinking?

I'd forgotten about that. You can even give it a script filename with all your commands and upload entire directories with the GLOB command.

You will need the LabVIEW Internet Toolkit if you are going to do it from LabVIEW. e.g.

Can't wait to see the screenshots. Congrats.

Well. For me anything that doesn't use 3rd party products is preferred But generally when we are talking about this sort of thing we are also talking about convergence on a solution for the final optimisation step. As was indicated with the "Fast Trim"; using LabVIEW parallelism will always converge faster since the worst case is a solution is in the middle (if split over 2 for loops) rather than at the end. This however comes with the caveat for this case in how do you tell one loop that the other has found it without introducing complexity that mitigates the benefit. I haven't tried your example (I don't have the JKI toolkit) but in theory enabling parallelism of the for loop should also yield benefits although I have yet to see a real world scenario where it actually does.