topic LabVIEW 2009 f2 Patch in BreakPoint

LabVIEW 2009 f2 Patch

Todd S. — Thu, 15 Oct 2009 16:06:44 GMT

LabVIEW 2009 f2 provides several significant fixes to LabVIEW 2009. We are providing these fixes sooner via this patch, rather than wait for the still planned maintenance release (2009 SP1) which will be provided later. You can learn about the individual fixes in this knowledge base (KB) document, LabVIEW 2009 f2 Patch Details.. National Instruments strongly recommends that all customers download and install this patch in order to benefit from several critical fixes.

We're using the new notification mechanism built into our installers to make users aware of the availability of this patch, hopefully closing the loop between National Instruments providing a patch and our users becoming aware of the patch and subsequently downloading and installing the patch. Our goal in this effort is to improve the support experience for our users.

Please use this forum thread to provide feedback on the patch notification and overall patch experience. We'll create separate threads for specific issues corrected in this patch as needed.

Regards,

Todd

Re: LabVIEW 2009 f2 Patch

RayFarmer — Fri, 16 Oct 2009 06:15:11 GMT

Great, but it should have been posted in the LabVIEW forum.

Regards

Ray

Re: LabVIEW 2009 f2 Patch

muks — Fri, 16 Oct 2009 07:03:28 GMT

Ray,

It is posted

Re: LabVIEW 2009 f2 Patch

RayFarmer — Fri, 16 Oct 2009 07:56:55 GMT

Ok, so what is it doing in this forum, especially as the post is locked to the top. This is not the place!!!

Those that use LabVIEW would have seen the post in the LabVIEW forum and those that dont use it , do not careless.

Ray

Re: LabVIEW 2009 f2 Patch

muks — Fri, 16 Oct 2009 08:07:16 GMT

Ok, so what is it doing in this forum, especially as the post is locked to the top. This is not the place!!!

Those that use LabVIEW would have seen the post in the LabVIEW forum and those that dont use it , do not careless.

Ray,

Did you see this?

(This is a duplicate post. To comment and ask questions please post on this identical post on the BreakPoint board)

So that is an info (A forced one to stay for some time like the pilot one) this is for discussing it.

Re: LabVIEW 2009 f2 Patch

RayFarmer — Fri, 16 Oct 2009 09:45:40 GMT

Hi muks,

not sure what is your point is as your link sends you back to the same point

Ray

Re: LabVIEW 2009 f2 Patch

LandyRover — Fri, 16 Oct 2009 12:23:37 GMT

What was the reason for advertising it as available on the 14th of October, but downloads were not available (error 404) untill the following day? Someone take a nap?

Dave B.

Re: LabVIEW 2009 f2 Patch

Ben — Fri, 16 Oct 2009 13:04:28 GMT

Hi Ray,

Todd is just trying to get the word out and there are some LV users that may only check the Breakpoint (looking for a LabTOON updates etc). There some ugly bugs that neede fixed and users may not have noticed there were problems lurking under the hood.

I do like getting the "heads-up" (even though I got it three times LV BP and Champions forum). I would rather get duplicate that no heads-up.

Re: some errors when trying to get the updates...

I believe that was the result of "race condition" in the web-site mechanisms that I am afraid an Action Engine will not fix.

Ben

Re: LabVIEW 2009 f2 Patch

smercurio_fc — Sat, 17 Oct 2009 04:13:45 GMT

LandyRover wrote:
What was the reason for advertising it as available on the 14th of October, but downloads were not available (error 404) untill the following day? Someone take a nap?

Dave B.

Taken up here.

Re: LabVIEW 2009 f2 Patch

Roy_F — Mon, 19 Oct 2009 15:16:56 GMT

Broken Links and Date of Availability

This was our first use of the install notification function for LabVIEW and we are still learning how best to enable this function. There's quite a few things that need to happen with a preferred sequence. We needed to make the documents with information available at the same time that notifications would be seen and we didn't want to delay the notifications waiting on the code. There is some amount of variance in the time a document is published and the time it ripples through our servers. This resulted in the notification link apparently not working for some number of minutes.

The call to put the links in the document before the code was available was mine. We turned on notifications before the image was available so people installing LabVIEW would be aware of the patch and when it would be available. I wanted the links added so they would work as soon as the patch was pushed live without having to wait on an update to the document pointing to the patch. I thought adding the red text with an available date would avoid confusion, but I was wrong. And, as soon as someone from Japan asked why the link was not working yet, we realized we should have added a time with U.S. Central indicated as well.

So, the fault lies clearly with my requests, not with those that implemented them. Please accept my apologies for the time, trouble and confusion these decisions had on all. We're using this thread to capture the issues associated with the patch process, such as how it was communicated and delivered. I'll use this information to update our processes and procedures to avoid these problems in the future. So, keep your comments coming and I will endeavor to make good use of them.

Why is discussion in Breakpoint instead of LabVIEW?

Not that Todd can't take a few hits (he's pretty thick skinned), but the decision to have the discussion here was also my call, so move your aim to the right two feet and focus on me.
My thought was to keep non-technical and non-LabVIEW specific discussion in breakpoint and technical discussions (i.e. specific LabVIEW issues) in the LabVIEW board. Things like how the patch was communicated or delivered would belong here, specific LabVIEW technical issues (e.g. what are user defined refnums, are VIs binary compatible, etc.) would be discussed in LabVIEW.

Sincerely,

Roy Faltesek

Senior Group Manager

LabVIEW R&D

Re: LabVIEW 2009 f2 Patch

LandyRover — Mon, 19 Oct 2009 15:51:08 GMT

No worries, but sadly I find that sort of thing (as do many others from a "True Hardware" background) to be rather irksome, to say the least. Perhaps in the near future, something can be automated, so that when a file finally filters down to the point where it is distributed to users from, THEN the notification goes live?

I also do the support thing for our customers, so I know only too well the onslaught you get when you say something, and for whatever reason, there is a delay in what you said you'd do, actually happening! 🙂

Cheers n beers.

Dave B.

Re: LabVIEW 2009 f2 Patch

RayFarmer — Mon, 19 Oct 2009 20:01:43 GMT

ok, taking aim two feet to the right

"Things like how the patch was communicated or delivered would belong here....."

Actually I believe the Feedback might have been a better alternative.

But from the final words from the original post;

"..Please use this forum thread to provide feedback on the patch notification and overall patch experience. We'll create separate threads for specific issues corrected in this patch as needed."

The only place should have been the LabVIEW forum as this would have ensured that any spawned threads would have been in the correct forum to start with to obtain the larger participants

Regards

Ray

Re: LabVIEW 2009 f2 Patch

Roy_F — Tue, 20 Oct 2009 01:05:25 GMT

Hit - good aim. 🙂

Ray Farmer wrote:
...Actually I believe the Feedback might have been a better alternative.

Do you mean the "Feedback on NI Discussion Forums", which has description "This is an area to provide feedback on the functionality of the NI Discussion Forums." That would obviously not be appropriate for discussion on our patch process. The description for Breakpoint is "The community area focused on off-topic discussions! " Perhaps I was being too literal (and possibly even wrong) for considering a discussion on the patch process itself as off-topic of LabVIEW. I doubt that it would have really bothered anyone monitoring the LabVIEW board to see these posts, but the patch process we're using (notification mechanism, downloader, KBs, Drivers and Updates) is NI wide and that seems off-topic of LabVIEW.

Ray Farmer wrote:
The only place should have been the LabVIEW forum as this would have ensured that any spawned threads would have been in the correct forum to start with to obtain the larger participants

So far, we don't have any spawned threads on LabVIEW technical issues, but if any are created in Breakpoint, we are prepared to redirect (nudge) those to the LabVIEW board.

I'll assess how this worked out when done and see if we should do it differently next time. This being our first time to do a LabVIEW install Notification, I expected more problems with the process than with the patch itself or the issues it addressed. The broken links and timing issues, for example, are something I've learned and will want to correct in the future. My expectations for the next Notification we do will obviously be higher, so perhaps we'll just deal with it entirely in the LabVIEW board and if we happen to get some off-topic feedback on the process there, no harm done.

Thanks for the comments; keep them coming. I hope I'm not coming across as too defensive - we are listening and there are others within the company that watch my every move (i.e. this is not a dictatorship - well, maybe it is, but I'm not him ).

Roy

Re: LabVIEW 2009 f2 Patch

RayFarmer — Tue, 20 Oct 2009 06:00:04 GMT

Hi Roy,

You are probably right about "Feedback on NI Discussion Forums".

Regards

Ray

Re: LabVIEW 2009 f2 Patch

abdel2 — Thu, 29 Oct 2009 06:26:59 GMT

Great patch! Before I tried to convert my 8.6 VIs into 2009 but the program kept crashing on one vi as soon as I opened it for editing. Now I have successfully converted to Labview 2009 without any hassle.