Val Brown

Right, no shooting allowed... I do what I've always done. It is a path control with the full path name of the VI that is to be included in the tab of the subpanel. So don't shoot me if something else should be done to support the 9.x file format. val

OK, this is a real mystery to me. Probably I just don't understand the implications of the setting but here's the scenario. I have a project with a top-level VI that has a subpanel that call two different VIs, each in a separate page of the control. So, shift to page 2 and one of the VIs is visible, switch to Page 3 the other is and the other tabs access controls that are internal to the top-level VI. The called VIs are included in the Always Included list in the Source Files page of the App Builder. Inclusion Type is set to Include if Referenced with the Application EXE as the destination. When i use the 8.X file layout in the Advanced page, the build succeeds and the app works correctly, loading and running appropriate VIs as each page is selected; however, if I deselect using the 8.x file layout, the pages are blank when called unless the flat VIs are included on the hard drive of the target system, in the correct location per the development file layout. Obviously I'm not setting up the inclusion process correctly but I really don't get what to do to make it work correctly when not using the 8.x file layout. Any help would be appreciated including pointing me to relevant KBs that I've overlooked in trying to resolve this.

Ton, Thanks for the beta URL. I started that process yesterday but I guess I'll have to wait until Monday (or so) for it to be "authorized" by NI and that's disappointing because I was hoping the involved AE would be able to expedite that process.

I've got a bit of a problem here. I'm scheduling a meeting with NI R&D for the week of April 12, which is coming up fast, because of a problem I've had with completing a build in LV 2009. The build works perfectly in 8.6.1 and the code works perfectly in LV 2009 as a development environment; however, the build "works" (with a request for a file location) but then the built app says it's "...not a valid Windows resource". In any event it's a real "stump the panel" thing and thus the reason for possibly going down to Austin in about 10 days. Here's my dilemma and a request for some help -- if possible. The suggestion was made to download 2010 beta to see if the build problem "just goes away". I'm happy to do that but was only able to apply for the beta program NOW. I have no URL for the download of 2010 beta and, if things work as expected, I won't have access to it until Monday some time at the earliest, through official channels. That puts a real crimp in the schedule for me as I really need to book tickets, etc IF I'm going to have to go down to Austin. So here's the request (and apologies for the long story). Can anyone here give me a URL so that I can download and install the 2010 beta? If I can run a test build with my code and it WORKS!!!! (chorus of angels singing) then I don't have to go down to Austin. No, don't get me wrong. I really do LOVE Austin -- and I enjoy hanging with the NI crew. I mean who doesn't really LOVE 6th street? But, if I can avoid HAVING to go down there, esp at this time when I've got multiple pending releases, it would REALLY make my life easier. Back channel me if that's better for you but I really would appreciate getting a way to download, install and then test my code with 2010 beta over the weekend.

OK, so here's a comment and an example of system that works and, at worst, works far better than any of the US systems. I live in British Columbia, Canada and, because I'm a "Landed Immigrant", have complete access tot he health care system. I just got my free vaccine for H1N1 yesterday -- the whole process took maybe 15 mins. No matter what you may believe -- because of what you've been told by US media, the Canadian health care system works.

I'm seeing curious results in some of my recent build attempts. I have the Auto Increment option set for version numbering and yet, despite that being set, I have now build three different EXE from the same build script and they all share the same version number. So, instead of being: 12.0.1.0 12.0.1.1 12.0.1.2 They are all 12.0.1.0. Now I've been using the Auto Increment versioning option for quite a while, with the same project, even on the same physical computer so this one REALLY confuses me. Anybody seen this kind of behavior or have any good ideas?

I see this very differently in many ways FWIW. 1. I was originally in a somewhat similar situation (viz working for a company developing software for it) so I had my contract stipulate that the licenses for LV would be purchased for me personally with full right of ownership in the event that I left that company. 2. If you don't do something like #1 when you work for a company then you are using the tools of that company and the tools remain with the company when you leave. This would be the same for a hammer or aircraft carrier. If LV belonged to the company then it stays with them and you would need to purchased the full development system to use/update code. 3. re: #2, the same holds true regardless of the language used, it's just that getting various versions of other languages like C++, JAVA, etc appear to be far less expensive than LV; but the principle remains the same. 4. Did you release the code under your own copyright or as a product of the company? If that later then it remains their property and you could only extend/correct/distribute it with their consent -- regardless of the tools used. I wouldn't say that this is a LV or NI problem per se -- it is not their responsibility that you set up your business relationship the way you did. It is unfortunate but it is also, as far as I can tell, just the way it is and you, quite understandably, don't like it.

Right, I didn't mean to imply that there had been intentional highjacking just that my original question -- as completely framed -- has still not been resolved.

I don't want to be JUST a curmudgeon but, as the OP, I'd like to remind everyone that we began this thread with the following problem, after a "successful build". Try to run the EXE and the following appears" "LabVIEW: File is not a resource file. The file 'BuiltAPP.EXE' could not be loaded" This project and build spec worked fine, built fine under 8.6.1 but there has been NO success with a useable build under LV 2009. A CAR has been filled in re: to one aspect of this that involves the SPT, but that in and of itself really doesn't seem to be the problem. So, can I ask for this to revert to the original question and have another thread to pursue the various offshoots that have emerged? I'm still here unable to successfully build under LV 2009 a build spec that has successfully built all the way back to LV5 (in various smaller and earlier incarnations of the VIs used of course). Any help with this aspect would be greatly appreciated.

FWIW you couldn't pay me to use Dell, HP or Compaq let alone give me one of have me buy them. Don't get me wrong -- all of them are fine if you don't mind: 1. bloatware 2. proprietary blotware 3. challenges if you go off their spec at all I have used Acer for years without any problems with the computer. I also use a MacBook Pro with XP installed, Boot Camp and VMWare Fusion. I can't do without my Mac at this point -- all internet is done via it including email, web browsing (using Safari), etc. All of my LV work is in Windows so I run LV within XP on my MBP both in Fusion (so virtualization) as well as in Boot Camp when I need real throughput for my USB-accessed hardware. FWIW you couldn't pay me to use Dell, HP or Compaq let alone give me one of have me buy them. Don't get me wrong -- all of them are fine if you don't mind: 1. bloatware 2. proprietary blotware 3. challenges if you go off their spec at all I have used Acer for years without any problems with the computer. I also use a MacBook Pro with XP installed, Boot Camp and VMWare Fusion. I can't do without my Mac at this point -- all internet is done via it including email, web browsing (using Safari), etc. All of my LV work is in Windows so I run LV within XP on my MBP both in Fusion (so virtualization) as well as in Boot Camp when I need real throughput for my USB-accessed hardware.

I'm still having my original problem: using SPT and even the Obsolete SPT. The build "succeeds" (whether or not I check "Advanced/Use 8.x..." option) but then I get "...not a Resource" when trying to run the "successfully" built EXE.

I hadn't noticed this behavior in the past but now I'm encountering something very similar in LV2009. I have a project that looks for a VI during a build but that VI can't be found anywhere in the VIs OF the project. It's very, very curious and I have NI working with me on it.

To my mind this is correct behavior: ie a "Value Change" has occurred programmatically because the value was set (programmatically) to a value that is newly set, whether that value is the same as before. It is really the value set operation that is being tested not the value of the value. I though you "by ref" folks would really get that.... Seriously I think that this is correct behavior and should be maintained. If someone wants a "test to see if the value is still the same after reint to default" then that functionality could be implemented for individual controls.

OK, so has anyone else had problems with transferring projects from 8.6.1 to LV 2009? I have one major project that originally had large problems even running in 2009 but that was solved by uninstalling 8.6.1 and 2009 then reinstalling 2009 alone. It seems that there has been some significant reorganization done in the SPT, esp in the Wavelet Analysis subs. Ok so that DID get sorted out (essentially by the "virgin" install of 2009) but now when I do my build -- of a project that builds perfectly well in 2009 -- I can get the project to build BUT, i get the following error message when trying to run the built EXE: "LabVIEW: File is not a resource file. The file 'BuiltAPP.EXE' could not be loaded" Any good ideas, besides backing down to 8.6.1?

I discovered a problem with legacy 8.6.1 code when I upgraded to LV 2009. The code involved the Easy Discrete Gabor Transform.VI. Regardless of parameter set used, the VI returned error -42619. After some investigation it was determined that the source of the error was Fast Dual.VI and the reason for the error turned out to be that the configuration of the Call LIbrary Function Node had been changed in LV 2009. The AE created a new Call Library Function Node, configuring it the same as in 8.6.1, and voila, no more error. CAR #182427 was filed to address the change in the Easy Discrete Gabor Transform so R&D will investigate it further.

OK, so I have a build spec for an EXE that builds without any problem in 8.6.1 but, in LV 2009, the build "completes" but then I get a "...not a resource..." error when trying to start the built EXE. I've tried both the legacy 8.6.1 "flat file" setup as well as the LV 2009. Nothing else has changed in the buildspec but, interestingly enough, while performing the build, LV asks me -- repeatedly -- to browse for several VIs, all from SPT. Any good ideas?

Excellent! BTW, Jim, do either the RCF plugin or State Machine require OpenG?

Kind of a "retro-occurrence"....with an attitude! AQ, am I hearing that byval has an inherent "advantage" in that it enforces dataflow and precludes (more or less) race conditions whereas the byref option ALLOWS for race conditions, unless otherwise handled in the architecture?

" Jim Kring found one just last week, and thought he was looking at a bug in LabVIEW, but it wasn't. When you use references, you open up a whole new world of race conditions, recursive deadlock, and on and on. " Has this been posted somewhere so that we can see what happened? This is an important tip because I'm sure some would understand DVR as meaning "unlimited by-ref" had come to LVOOP.

OK, so I had to do the restart of WIndows THEN the next startup of LV worked like a charm.

Doing the install for LV 2009 I was asked to point the installer to NI Device Drivers...Should I just use my current Device Drivers DVD or is there another download to do?

It is for me as well. And AQ, I like the CTL+SHIFT+R idea....a lot!

I'm looking for someone in Canada, preferably BC, who has experience in LVOOP and who is available to provide consultation services. I am also interested in those who are not based in Canada but prefer someone in Canada for business-related reasons. I can be reached back channel as well (val@zengar.com) and/or via PM here.

I had the same question but want to ask you where you saw the preliminary schedule? All I can find is a listing of some of the events.

Do you have URL for the prior presentation? If I could review that I'd probably have some direct questions.