Michael Aivaliotis

QUOTE(gmart @ May 23 2007, 01:17 PM) I did not clock the 8.2 startup time when I had it before the upgrade. Sorry. I'm not about to downgrade. It felt like 30s.As far as everyone else. That's great, I'm happy for you (I really am) but how do I debug this? Any suggestions?

My stats: LabVIEW 7.1.1: 30s LabVIEW 8.0.1: 2m45s LabVIEW 8.2.1: 1m30s So, unless you can launch in 30s you're too slow for me, sorry. I'm talking LabVIEW startup time without loading any VI's.

QUOTE(LV Punk @ May 23 2007, 09:19 AM) Ok, now I see it too. Thanks. I'll move this to the bug forum.

QUOTE(Tomi Maila @ May 23 2007, 11:31 AM) Thank you Tomi for supporting LAVA with this challenge.

QUOTE(LV Punk @ May 23 2007, 03:57 AM) Outline works fine for me. Anyone else?QUOTE(Gary Rubin @ May 23 2007, 05:38 AM) Clicking on the "Last Post" link brings me to the top of the page on which the last post is located, rather than right to the last post. Sorry, fixed now.

I just finished performing some speed optimization changes on the forums and other areas of the site. Please let me know if everything feels a little faster.

QUOTE(Jacemdom @ May 22 2007, 05:50 PM) Sorry, the conversation started off with 8.2 and you switched it to 8.0.1 so I missed that. In 8.2 however NI decided to make both extractable. Here are the 8.2 contents: Web Browser Version: http://forums.lavag.org/index.php?act=attach&type=post&id=5923 Full Version: http://forums.lavag.org/index.php?act=attach&type=post&id=5925 I don't think this changed much from 801. So as you can see, even the

QUOTE(Jacemdom @ May 22 2007, 03:35 PM) I could spend the time and figure it out, but you can also do this yourself. Just download both run-times. Extract them and look at the folder contents. You will see several clearly labeled msi install files for the full runtime which are related to various add-on features.

I just want to revive this thread and say a big Booo! to NI for slowing LabVIEW down agian. After applying the new 8.2.1 patch my launch time sucks. Back to 8.0 startup speed.

QUOTE(crelf @ May 21 2007, 06:50 AM) Sometimes I have to remind myself that there is a real person writing these posts...

Can you attach a new VI with your graph on the panel and a constant with data fed to it? I want to try a few things.

QUOTE(tcplomp @ May 21 2007, 06:46 AM) That works too.

QUOTE(chrisdavis @ May 21 2007, 06:14 PM) I agree. Since the LabVIEW 8.0 release, NI decide to add a little confusion by creating two run-time engines. The old run-time is now called the "web browser only" runtime: QUOTE There are two downloads that are available. You only need to install one of them. LabVIEW 8.2.1 Run-Time Engine (Web Browser Only) (24MB) is a smaller download intended for viewing Remote Front Panels in web pages. It does not contain the full run-time engine, but will allow some executables to run. This version can not be deployed. Download LVRunTimeEng.exe to install this version. LabVIEW 8.2.1 Run-Time Engine (Standard) (91MB) gives full support for executables. This version will support all executables built with LabVIEW as well as allow viewing of Remote Front Panels in web browsers. It includes support for DataSocket, Variable Engine and NI-USI. This version can be deployed using an installer created with Application Builder. Download LabVIEW_8.2.1_Runtime_Engine.exe to install this version. So really, you may be able to get by with the web browser only version which is "only" 24MB.

QUOTE(chrisdavis @ May 16 2007, 06:44 PM) Question for you. How are the additional msi files included? Are they a post or pre install task? Also, upon an upgrade, what happens when the additional msi gets called again? Do you get the repair, or uninstall dialog for the msi?

Maybe we should start a new group called XNI? Thanks Jason for all your hard work and contributions to the LabVIEW legacy.

QUOTE(Eugen Graf @ May 18 2007, 08:42 AM) Again, many ways to skin a cat. Your approach will work fine but there is no way to control the timing of the reads. They will happen asap which may or may not be desirable. I suggest you add a shift register with a timer value to control this better. Since the reads happen independantly from external commands, you need to put something that will trigger them. Some code in the timeout case of the bottom loop that sends a read command with a timer should do it.Another issue I see is you don't have an associated Write before the Read. What Write command will tell the instrument to return data? Unless the instrument is always returning data then I guess it's fine. In that case my timer solution in the previous paragraph is not valid. You need to do a check bytes at port in order to see if a Read is necessary.

QUOTE(Darren @ May 18 2007, 08:00 AM) The idea behind this is that viewing the results will probably bias your decision thus you give up your right to vote. You can vote then view the results or you can view the results only and not vote.

QUOTE(NI Support) So it turns out that the best way to resolve this is to uninstall ALL drivers and install the one I want before the build. Does anyone else see problems with this methodology? I mean, let's say for instance that you are supporting multiple projects with differnet driver version requirements. What then? If anyone's gone down this path, do you have any suggestions?

When building an NI installer, you can specify additional installers. How does this list get populated? Does it depend upon what you have installed already? How do you specify a different version? Must you install that specific version in order for it to show in the list and include it in your installer build? I have a specific issue: I see in my list that I have NI-Serial 3.2 installed and available. When I do the build, it prompts me for the driver CD which I provide. Even though the version of NI-Serial on the CD is the same as the one shown, it does not accept it. I'm giving it Feb 2007 - Disk2 but it asks for Nov. 2006 - Desk2. I even tried to uninstall NI-Serial and re-install the one from my CD but no-joy. I even tried copying the source NI-Serial folder from the CD to my hard drive and pointing to it but it still did not like it. It complained about not locating {GUID}. Question: Why can't we just point to the #$%$@&! NI *.msi files we need? Note: NI support has been contacted.

This is somehow related to this post: Autosync a project folder with a folder on disk I'm trying to build an installer. I want to add a Help folder using my installer. I would really like to use NI's installer but, yet again, I have found a limitation which causes me to look for other solutions (when will NI "get it"?). In any case, perhaps I'm being too quick to judge . I would like to specify a folder in my installer that will be copied to my destination. It seems the only way to do this is to create it first in your project file then specify to copy this folder in the installer. This is an acceptable option. There is a limitation however. My Help folder contents change dynamically. Anyone who's generated an html help understands this. This means I would have to do an add folder contents, remove folder contents, over and over again (or before the install build). This is very tedious and prone to me forgetting to do this. This is just one example of dynamic folders. Does anyone have a solution or workaround?

ya, the "--" don't work. Just enter a fictitious date instead.

No idea. Just remove the subscription.

Interpreting web standards isn't my job, thank god, but I think it depends on what version of the standard the browser chose to recognize and how much of it.

btw, those are warnings not errors. All web pages generate warnings, even on ni.com. This is a way of life on the web. Some declarations only work for certain web browsers. If a browser does not recognize something, it generates a warning like the one's you indicate. Sometimes however I have noticed that the Google ads cause pages to pause for a while before they load. Haven't investigated this yet but I will soon.

QUOTE(crelf @ May 12 2007, 02:25 PM) Yes, and on that Wiki page, you could group the icons based on how they are laid out in the functions palette.