LabVIEW annoyance. help( not a hater thread)

[Alan Anderson]

Originally Posted by Alan Anderson

I have no idea how long a Build takes on our new Windows Vista laptop -- it fails to build, giving an Error 8 (possible file permission error), and I haven't finished troubleshooting it.

I resolved the Error 8. I had copied a project from our Windows XP laptop to the Vista laptop. and the output file directory in the project's build specification wasn't compatible with Vista's filesystem structure.

Now it only takes nine minutes -- a noticeable speedup, but still unreasonably slow. It shows the "Initializing build. This could take several minutes..." message for more than Eric's two minutes, and a totally new Basic Robot project runs the build for another two minutes. This is on a 2 GHz AMD Turion 64 with 3 Gigabytes of 800MHz SDRAM. What the heck is going on here?

[Greg McKaskle]

I wasn't able to look into this today, day jog kept getting in the way. I hope to gain some insight, and hopefully a solution tomorrow. I currently can't explain or justify the time it takes. I looked into the one issue with the analysis libs and the checkbox and can pretty much explain that one. I'll certainly post as soon as I understand it.

Greg McKaskle

[Alan Anderson]

I turned off the virus scanner on our nice new Vista machine, and build time for our full project dropped drastically to just over three minutes. Mystery solved, I guess.

I checked the old XP laptop with 10-15 minute builds, and it only has 256 MB of RAM. Might that explain the extreme slowness?

[Greg McKaskle]

That is helpful in more ways than one. The virus checker is concerned anytime disk activity is taking place, so this also points in the direction of overly disk bound activity.

The LV build used to be so simple. LV VIs are already compiled and the .o is bound inside of them. The files were aggregated into a primitive zip called an LLB, that was attached as data to the end of a tiny EXE wrapper that knew how to load the LV runtime engine, and we were off to the races. If you wanted it smaller, the other parts of the VI were stripped of diagram and some panel info.

With libaries, lots of things changed while I wasn't looking, so let me investigate. I'd like it to take less than a minute. I don't see why the build should be slower than the download.

By the way, noticed in my other post that I had a typo

day jog kept getting in the way

Hah, day job is what was getting in the way, I haven't jogged in years.

Greg McKaskle

[Uberbots]

Originally Posted by Greg McKaskle

The LV build used to be so simple. LV VIs are already compiled and the .o is bound inside of them. The files were aggregated into a primitive zip called an LLB, that was attached as data to the end of a tiny EXE wrapper that knew how to load the LV runtime engine, and we were off to the races. If you wanted it smaller, the other parts of the VI were stripped of diagram and some panel info.

but im guessing the code compiled in these .o and exe wrapper segments are for an x86 processor, not for the processor contained in the rio? is this why it takes so long?

[Stuart]

no I would expect that these .o files are for the power PC( its a power PC right?), although I do reserve the right to be wrong. Im curious to see if any one still has update 1 or update 2 on their computers, see if the change in the libs too place during that time.