LV 8.0.1 is out!

[syrus]

My primary workstation did the mass compile in about 1 hour. On my new laptop, the mass compile crashes. I have not found a reason for this, and my configuration does not match any of problems NI listed in the download instructions. Oh well...

[Ed Dickens]

It almost sounds like every upgrade is unique!

Talk about personalizing settings!

Has anyone done two updates yet where both seem to be correct?

Ben

I've got two identical desktops that I'm applying the patch to this week. There's nothing on them except WinXP, Office, LabVIEW and the needed drivers. We'll see how that goes.

Ed

[Grampa_of_Oliva_n_Eden]

I've got two identical desktops that I'm applying the patch to this week. There's nothing on them except WinXP, Office, LabVIEW and the needed drivers. We'll see how that goes.

Ed

Please keep us updated Ed.

I am looking for at least one positive report re: LV 8.0.1.

When it comes to computers in general, predictability is highly desirable.

Ben

[Ed Dickens]

Please keep us updated Ed.

I am looking for at least one positive report re: LV 8.0.1.

When it comes to computers in general, predictability is highly desirable.

Ben

Well, so far I've seen no major issues on the first of these PC's.

My 1000+ VI test application on the first station ran all day yesterday without a hitch.

I'm just starting to build the second application for the second one, so I won't know for a while. OpenG Commander installed OK if that means anything to any one.

I forgot about the "No bold text on required subVI inputs" problem yesterday and didn't look to see if the first PC had this problem. It's at a different location so I can't check right now, but the second one has lost it's bold text.

Ed

[AutoMeasure]

NI support says it'll be a few weeks before an RTE installer will be available... However, building an app installer from an updated system should install the updated RTE, right?

Also, 8.0.1 built apps are supposed to run with the 8.0.0 RTE.

No word on what actually changes in the 8.0.1 RTE.

I just noticed that there's a file in the FTP folder named 'LabVIEW_8.0.1_Runtime_Engine.exe' and dated March 9.

I've adopted the style of not including the RTE in my installers so that the installer ZIP file is a reasonable size for e-mailing or downloading, especially helpful when sending frequent updates. I give the user a link to NI's FTP site to download the RTE.

[tleibner]

Download Here:

ftp://ftp.ni.com/support/labview/updates/...bview_8.0.1.exe

Docs:

ftp://ftp.ni.com/support/labview/updates/...adme_8_0_1.html

Again (as with the 8.0 download), I'd love to have a http access to the files. That's because I am stuck behind a proxy with disabled ftp. Pleeeeeease, NI!

Thanks

Thomas

[Rolf Kalbermatter]

Please keep us updated Ed.

I am looking for at least one positive report re: LV 8.0.1.

When it comes to computers in general, predictability is highly desirable.

Ben

I have been upgrading to 8.0.1 about three weeks ago and haven't noticed anything strange in LabVIEW 8 yet. The mass compile did take about 3 hours despite Jim's accelarted tool, but that is probably the price for having a Centrino notbook with a 1.6 GHz Mobile Pentium. Considering that after more than one year I still can work almost 4 hours offline on one battery I guess that is not to bad.

Rolf Kalbermatter

[Dave Graybeal]

Ok, some more patch wierdness...

What the hell happened to my icons on my splash?

Michael, just Yesterday I updated another computer from 8.0 to 8.0.1 and ran into this same issue with the 'd' graphic. I remembered seeing this post a while back and was finally able to find it, but was bummed to see that there was no solution for it. Is this issue something that you were able to fix?

I'm not sure exactly what caused the problem, but I tried running the JKI mass compile tool and it crashed on me about half way thru, so i tried running the labview version which crashed as well ( this one actually showed me the vi it had trouble with, but i didnt get it written down and have not seen the error since). I ended up having to check out all my code from my SC software to get the JKI compiler to finally go thru. Not sure what part of this process caused the 'd' graphic, but it's a bit odd to look at!

Thanks,

Dave Graybeal