LabVIEW 2012 used to hang at shutdown, now hangs at launch ("Initializing menus")

Hello,
I'm running Windows 8 64-bit, and have LabVIEW 2012 32-bit (12.0f3). I started using it a few days ago, and was never able to shut down LabVIEW properly. I could close my projects, but when I then tried to exit LabVIEW from the home screen, the GUI simply stop responding, and I'd have to forcibly kill it. Then, I installed the latest VIPM, and noticed that I can't shut that down properly either (I believe VIPM is implemented in LabVIEW?). None of my non-LabVIEW-based programs have this issue.
Then, I tried to install OpenG from within VIPM, which launched LabVIEW itself. However, that hung at "Initializing menus".
I'm not sure if VIPM had anything to do with it, but now, I'm unable to start LabVIEW altogether. Even after restarting my machine (using the Restart option, not Windows 8's Hybrid Boot), LabVIEW would hang at "Initializing menus". Task Manager shows 0% CPU activity, and LabVIEW had only taken ~20MB of memory.
What could be the cause, and how can I fix it?
Thanks
Solved!
Go to Solution.

Ok, I:
Uninstalled ALL National Instruments, JKI, and IVI software.
Rebooted
Manually deleted residual NI, JKI, and IVI files/folders
Cleaned the Windows registry of NI, JKI, and IVI entries
Rebooted
Checked Task Manager to ensure that no NI service eluded deletion
Installed LabVIEW 2012 from the NI Developer Suite DVD (LabVIEW only -- no other components)
Rebooted
Launched LabVIEW
LabVIEW launches now, but I'm still unable to shut it down properly... One day it will probably refuse to launch too.
Some help please?

Similar Messages

PowerMac G4 Hanging on Shutdown, now won't accept 10.2.4 patch

I have a dual 1.ghz G4 silver door PowerMac. I've been running OS X 10.2.8. Suddenly, my system quit shutting down properly. It would start the shutdown, then hang up at the stage where the screen had the blue desktop background and the clock looking icon was "spinning". The only way to get the system to go past this point was to press and hold the start button.
I tried the disk utitlity and Disk Warrior, but none of those fixes changed the shutdown behavior. So, I reinstalled the OS X 10.2 operating system, using the "archive and replace" option. Then I began patching the 10.2.0 OS to bring it back to 10.2.8. The "combo" 10.2.8 patch wouldn't run. It would start prepping, then abort with the cryptic message that there was an error, please try again.
After a couple of tries, I gave up and started applying the patches one at a time. I got as far as trying to apply the 10.2.4 patch. For that patch, the installer tells me it cannot apply the patch to my system because it doesn't meet the requirements for this patch.
I can't tell whether the shutdown problem I had earlier is related to the inability to upgrade my OS to the most recent patch, but I am wondering whether there might be some hardware issue at the bottom of this series of events.
Any help, hints or clues would be appreciated.
Nikki
PowerMac G4 Dual 1 GHz Mac OS X (10.2.x)

Hi, biosmell -
I am considering pulling the internal battery in hopes it will kill the boot memory and perhaps default back to the OSX disks again.
That should work to reset PRAM, which contains the boot volume selection. Be sure to also pull the power cord, and to wait long enough; about a half hour should be fine.
After replacing the battery and reconnecting the power cord, wait another couple of minutes and then boot it - by default it should boot to the first OS it finds on a local (i.e., internal) hard drive.

LabVIEW 2012: compareTimestamps using "Comparison Express VI"

Hi,
I am using LabVIEW 2012 try to compare two timestamps data using "Comparison Express VI"
When set "Items to Compare" to Timestamps and try to connect timestamp to the input of the VI, I got a broken wire.
How to use the "Comparison Express VI" to compare Timestamps?
Best regards
Amr

This question brings up an interesting point. NI has said that internally a timestamp value carries time data (the number do seconds since the "beginning of time") in two forms: A DBL floating point version and a U32 integer version. Now if you use the equals comparison operator to compare two values, which version gets compared, float or integer?
Or to put it another way, is it safe to test equality between two timestamps?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

HT201272 I purchased an audiobook in Nov 2012 using iPhone 4S and then upgraded to iPhone 5 in Dec. Now I am not seeing the audio book in purchase history in iTunes. This means I am not able to get the book in my new iPhone. Please help

I purchased an audiobook in Nov 2012 using iPhone 4S and then upgraded to iPhone 5 in Dec. Now I am not seeing the audio book in purchase history in iTunes. This means I am not able to get the book in my new iPhone. Please help.

Audiobooks are currently a one-time only download from the store. If you don't have it on your computer (audiobooks go into the Books part of your iTunes library) nor on a backup, then if it's still in the store you can try contacting iTunes support and see if they will grant you a re-download : http://www.apple.com/support/itunes/contact/ - click on Contact iTunes Store Support on the right-hand side of the page

LabView 2012 hangs when opening a file from LabView 8.5

I have a program originally built in LabView 8.5. I am attempting to migrate it to a new machine running LabView 2012. I can open the program for the first time and make the adjustments needed to clear a few errors having to do with updated VI's and controls. I can then run the VI but after this I close out of LabView and when I attempt to reopen the file LabView hangs on the splash screen while loading the VI.
Any help would be appriciated. Thank you.
-Sam

Please post your original VI and the converted one so we can take a look.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Exe created with labview 2012 won't run using LVRTE2013

I created an exe using Labview 2012. I had the user install the latest rte (lvrte2013). The exe would not run and told the user it needed 2012 rte. Do users have to have the same rte for each exe?
Solved!
Go to Solution.

Yes. But the various RTEs can coexist on the same PC.

Cannot enter correct values in the SQL server express 2012 using labview

Hi everyone,
I am trying to enter the 2D array I get from DAQ into the SQL server express 2012 using Labview. When I am run the software, it connects with the table but doesn't enter the correct values. It only enters the "0" for each column of the table. I have attached the VI as well as the screenshot from the database server.
I am also writing the same 2D array data into the text file and I get the correct readins there.
Is there something I am doing wrong here.
Attachments:
test.png ‏251 KB
test3.vi ‏96 KB

If you had read the QL manuals or reference books, you would be aware SQL Server doesn't do multidimensional arrays.
I prefer BLOBs or VARCHAR(MAXCHAR) as an alternative. I enter the values in formatted string values delimiter separated.
But how to deal with multidimensional arrays. Well up to 3-5 you can use simple value for each "dimension". So the lowest dimension
would be comma delimit. The next set of values and each succeeding set for each 2nd dimension values would have the "set" of values separated
by a ":" or semicolon. For the third I use the ":" or colon to separate each 2D block of the 3rd dimension. This can all be easily reparsed
with a multidimensional parser for the application. Should be simple to build. (e.g.. Use string arrays to parse the higher dimensions
and numeric array for the lowest dimension). The VARCHAR(MAXCHAR) has an upper data bound of 2GB! If you have to save more
than 3 dimensions for most all applications, you don't understand how best to analyze the test data and may want to give it more
thought to optimize the operation as well as the design, so it doesn't get too complex. By the way I use Data Clusters built in the
data order and type as for SQL Server Data Table. This makes the design of the SQL Server interface easy as pie .

Spartan 3E with Labview 2012 (32 bit) on WIndows 7 64-bit - Error Code: -310602 NI-COBS: Unable to communicate with device over communication cable.

Thanks for the info, Kyle. I will probably try to find an older 32-bit XP machine. VM is just not an option for me right now.

Hello everybody,
I am trying to use the DIgilent Spartan 3E board with Labvew 2012 SP1 32 bit. I am able to compile the example code for LED shift. I am however unable to transfer code to the FPGA. I get the following error message:
Error Code: -310602
NI-COBS: Unable to communicate with device over communication cable.
Please verify that the cable is connected to a supported device and that the appropriate drivers are installed.
My system configuration is as follows:
Windows 7 (64 bit) on Dell XPS laptop.
Labview 2012 SP1 (32 bit)
Labview FPGA 2012 SP1
Labview 2012 FPGA support for Spartan3E
Xilinx 13.4 tools
DEFB LV FPGA 2012sp1 support installer
Xilinx USB cable driver v1.3 installed.
I took all the precautions mentioned by others on this forum and others, mainly that the cable must be disconnected before installing the Xilinx cable driver. All software and drivers were installed correctly. I even uninstalled and reinstalled the entire Labview software set I had. I still get the same error.
A few other questions:
1. Is the Xilinx cable different from a regular USB cable of the same configuration ?
2. When I program the FPGA I only have the USB cable connected between my computer and the Spartan 3e board. Should any other cable be connected ?
3. What should be the correct jumper settings for J1 - JP30 (especially J30, J11, JP9, JP6, JP7, etc) ?
I have been at this or over 3 days trying to figure it out. Any help will be greatly appreciated.

What files do I send to be upgraded from LabVIEW 5.1.1 to LabVIEW 2012?

OK. Just to be clear. I am a complete newb to ANYTHING LabVIEW or LabWindows related. I am a programmer, but I have never used any version ever. That said, I am responsible for the upgrade process of getting our old LabVIEW 5.1.1 system up to date. The old system (still running and doing it's job everyday), is an old Windows NT v4.0 SP6 system running LabVIEW 5.1.1. You can just imagine how ancient this is by today's standard.
Have I set the stage properly? I hope so. Newb, Ancient LabVIEW version 5.1.1, Windows NT 4.0, upgrading from 5.1.1 to 2012.
Now here is what I "think" I know about what is required. Because LabVIEW 2012 will not directly read in, process and /or compile LabVIEW 5.1.1 files, I must first open and save the files using an intermediate version of LabVIEW (specifically 8.2.1) to bring the files up to a version that 2012 can handle. I have noticed in reading the Version Conversion forum, that I can attach a zip file of my LabVIEW files and one of the resident Gurus will convert it for me and give them back - quite nice I think.
Now, I have what I think are all of the required LabVIEW vi and llb files that make up this system we have in place, but I want to be sure before I just post a bunch of stuff.
What exactly do I need to zip up and what can I leave out?
Are there LabVIEW vi and llb files in a "project" that are not needed?
Are there any setup/configuration/project specific files I need to include?
Are there any limitatations to this conversion process that I need to be concerned with - such as various toolkits/suites/modules that may have been used but are no longer supported?
Secondly, I am not really comfortable with posting my vi and llb files for the world to see (and possibly use) as I am not the owner of said modules, just the user/future developer who will be responsible for insuring they stay up to date. Is there any way I can send my files to a specific NI guru via email instead of just posting them?
Solved!
Go to Solution.

So if I understand you correctly, all I really need to do is to get LabVIEW 8.2.1, and update my .vi, .lib, and any .ctl files to that version.
Is it a simple matter of just opening the files and hitting something like SAVE AS, or just SAVE and it will do this? Once done, LabVIEW 2012 will then allow me to open them and do what I need to do? Do I have to save them into LabVIEW 2012 first, or is that automatic when I try to recompile them?
When I get a copy of LabVIEW 8.2.1 (eval version), do I have to get all of the pieces (modules, toolkits, etc.) in order to update the 5.1.1 files? Based on what is installed on that NT v4.0 system, we have the following items installed:
NI VISA
NI ComponentWorks 3D Graph
NI DataSocket
NI LabVIEW 5.1.1 Advanced Analysis Library
NI LabVIEW RTE 5.1.1
NI LabVIEW v5.1.1
NI Measurement and Auto Explorer 1.1
NI-488 2.1.60
NI-DAQ 6.6
NI-PAL 1.3.110
NI-Reports
NI-VXI/VISA
You mention DAQ. Our program uses NI DAQ v6.6 now. I have LabVIEW Developer 2012, so I just download the DAQ files for it and it will replace the NI DAQ v6.6 library files we use now?
Thanks for your help so far. If we had a support contract in place, this wouldn't be an issue. However, as I stated, I am not the owner of the files, just the currently assigned caretaker, and part of my task is to get from where we are now on this ancient hardware/software platform, to the latest and greatest. However, I am specifically not allowed to just place the files on a public forum for all to see. It just isn't done. We can send them to a known location and a known entity, but not to just anyone/anywhere as a public forum is by its very nature.
I know there is nothing you guys can do if I cannot give you the files, but thanks for helping me to do it myself. Getting an eval copy of 8.2.1, et. al is probably what I have to do here.

Missing vi.lib files in Run-Time LabVIEW 2012

Hi
I've got a problem executing VI's under RT in LabVIEW 2012.
Our system consist of multiple independent modules which are opened and run from a Manager VI. VI paths to the modules are read from an .ini file by the Manager VI.
We have build a single executable (RT Launcher) that takes the path of the Manager VI as argument (Attachment : RT Launcher.png).
The RT Launcher is placed in the ..\National Instruments\LabVIEW 2012 folder as the LabVIEW.exe.
The RT Launcher is called from the CLI.
"C:\Program Files\National Instruments\LabVIEW 2012\RT Launcher.exe" "C:\Workspace\Labview\Manager.vi"
This will run the Manager.vi in the RunTime Environment and the Manager.vi will open the .ini file and execute the Module VI's one by one.
By calling the RT Launcher.exe from the same folder as the LabVIEW.exe, the search paths should be the same.
The system worked fine in LabVIEW 2010.
The Manager VI is opened with broken arrow and the errors indicate that vi.lib sub VIs are missing (attachment : Manager VI errors.png)
I know there are issues regarding object cache and separated compiled code from LV2010 -> LV2011 -> LV2012, but simply can't figure out how to come around this problem.
Can anyone explain the difference and how to solve the problem ?
Thanks
Regards Kahr
Certified LabVIEW Architect
CIM A/S
Solved!
Go to Solution.
Attachments:
RT Launcher.png ‏68 KB
Manager VI errors.png ‏35 KB

Hi Kahr.
It sounds like you are making some dynamic calls to VI's, eg. by using 'Open VI Reference'. My answer is based on that assumption.
You are absolutely right. In LabVIEW2010 we introduced a function called 'Separating Compiled Code from VI'. At that time none of the VIs from VI.lib had that option enabled. In LabVIEW2011, many VI's in VI.lib have, by default, a separation of compiled code and VI. This option cannot be changed (greyed out) for these VI's as well. This feature was introduced in order to simplify source code control.
Separating Compiled Code from VIs and Other File Types
The drawback is, that it is no longer possible to call VI's dynamically from an application (executable), when this option in enabled, since the compiled code no longer exists. The method of calling a VI dynamically from an application has been (and still is) used to make some kind of a plug-and-play architecture, meaning we have one EXE-file that only gets distributed once and a set of subVI's that gets redistributed according to new versions (new features added to the subVI), meaning we can make changes in the subVI without having to redistribute the EXE-file.
With the release of LabVIEW2011 and LabVIEW2012 we can no longer distribute VI's that uses functions from vi.lib, this also include DAQmx calls even though the DAQmx driver is installed.
The simple explaining is, that it has never been intended that VI's got distributed. Eg, when Microsoft is making a new software update for Windows7, they don't send out the source code to all the users.
The solution is therefore to wrap up the source code into 'something' that includes all the compiled files. In LabVIEW we do that in a couple of different ways.
1) Include the VI's in the EXE-file.
When building the application, we have the option to include files, that normally is not included in builds. If we call a SubVI dynamically this will not automatically be included! However, the drawback of this method is, that if you need to change something in one of your SubVI's, you would need to build and distribute the entire application. Thereby, we are not making use of the plug-and-play architecture that we originally wanted. However, this method will fix the error.
Error 1003 When Using VI Server in a LabVIEW Application
2) Now, if we still want the plug-and-play architecture in LabVIEW2011+2012 (and this will properly be the same for the next many released of LabVIEW), this can still easily be achieved by making a Source Distribution. When we make a Source Distribution, we can include the VI's from VI.lib and thereby the compiled code. When using this method, two important things should be remembered:
a) Make the files into a LLB file. This will pack all the VI's into one single file, that is easy to distribute.
Go to Destinations ==> Destination Type ==> LLB.
b) Make sure not to 'Exclude files from vi.lib', as this method will then simply not work.
Go to Additional Exclusions ==> Remove checker mark in 'Exclude files from vi.lib'.
How Can I Call a VI Dynamically from an Executable Without Including Those VIs in the Build?
I have made a small example to demonstrate this:
Example: Using vi.lib
This example has two mainVIs and two EXE-applications. Build the two EXE-files, but do NOT build the source distribution yet.
1) Main(IncludeSubInExE). This version has included the subVI in the build distribution for the EXE-file. When running this EXE everything works fine, even when calling the subVI dynamically. However, since the subVI is build into the exe, we would have to redistribute the exe for every new version of the subVI. This breaks the hole idea.
2) Main. The subVI is no longer included in the build. When running and trying to call the subVI, you will get this error (on both your developer and run-time machine):
Now, build the Source Distribution and run this EXE again. The exe is running perfectly with no errors.
I hope this answers your question.
Best Regards
Alex E. Petersen
Certified LabVIEW Developer (CLD)
Application Engineer
Image House PantoInspect
Attachments:
Using vi.lib.zip ‏83 KB

Mac Pro 5,1 hangs on shutdown

I use a 2012 3.33 GHz 6-core Mac Pro 5,1 in my recording studio, running OS 10.9.2 with 16 GB RAM. I use all of the PCIe slots: slot #1 is the ATI Radeon HD 5770 graphics card, #2 is a Universal Audio UAD-2 Quad card for my powered-plugin library, #3 is the Avid Pro Tools HD-Native card and #4 is an OWC Accelsior 120GB 6G SSD which I use as my primary Pro Tools production drive.
Ever since I upgraded to Mavericks and added the Accelsior SSD (this January) the computer hangs on shutdown and occasionally on startup. With shutdown it's the same every time - when I shut it down I get a blank gray screen with only the cursor arrow showing, and I can still move the arrow around. After a few minutes I hit the power button to force it to shut off.
The machine also runs very sluggishly and takes forever to boot up. It almost as if there are a ton of hidden processes bogging it down.
I've checked and re-checked for viruses, I've reset the SMC and PRAM, I use Disk Utility to verify all my drives and repair all the disk permissions about 3 times per week, and I do daily diagnostics with Tech Tool Pro 7. I'm about to pull all the PCIe cards except the graphics card and disconnect all peripherals except keyboard and mouse and then reconnect everything in steps but before I do all that I was wondering if any forum participants have dealt with a similar problem ?
- Lang Doogie

You could try a different SSD than the Mercury model from OWC.
Also, any and even the ones from OWC should have TRIM enabled and you do not.
I have a number of Samsung SSD and just noticed one $110 250GB
http://www.amazon.com/Samsung-Electronics-EVO-Series-2-5-Inch-MZ-7TE250BW/dp/B00 E3W1726/
Different firmware can matter.
http://www.amazon.com/Samsung-Electronics-EVO-Series-2-5-Inch-MZ-7TE250BW/dp/B00 E3W1726/ref=sr_1_1?ie=UTF8&qid=1410381741&sr=8-1&keywords=250GB+SSD

LabVIEW 2012 and LegoNXT

Hi,
Will my EV3 Lego mindstorm brick work with LabVIEW 2012 and LabVIEW Lego MindstormNXT 2012? Because when I'm installing LabVIEW module for Lego 2012, it'sprompting me to install LV2012 SP1. I already have LV2012 but NOT SP1.
Regards.

NapDynamite wrote:
The system in my lab has no SP1, probably the guy over here never bothered to install that update. Now when I checked those updates to install SP1, the update service is locked for this patch and is asking for renewal of subscription.
My boss, who is not very cognizant of software stuff, is now asking me to use the EV3 software which comes along with LEGO pack becuase he's not ready to spend much to renew.
And my dream of teaching LabVIEW to school kids is now in vain.
Regards.
In vain?
A bit dramatic isn't it?
One license is $99.
Site license is $570.
http://sine.ni.com/nips/cds/view/p/lang/en/nid/210666

Installing NI-USRP for LabVIEW 2012

It's been a few months since LabVIEW 2012 was released. Is there a supported way to install NI-USRP support for LabVIEW 2012 or does a new installer of NI-USRP need to be released? As of right now, NI-USRP 1.1 is available and installs support up to LabVIEW 2011 but not LabVIEW 2012.
Thank you!
Dr. Spaceman
"Really? I think you mean radio."

Dr Spaceman,
Generally we recommend that most people use the 32 bit version of LabVIEW unless they are planning on using our vision software. Many of our toolkits and modules only work with LabVIEW 32 bit. This article talks more about the difference between 32 bit and 64 bit. http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
Regards,
Leah
"All right, now that the popsicle's melted we've got ourselves a tongue depressor."
Regards,
Leah
National Instruments
Applications Engineer

Nokia C7 frequent hanging, sudden shutdown, wont o...

I am Ismael Viloria. I have just received my prize on Pier Roxas' promo on Facebook last Friday, December 10, 2010. For the past 3 days of using it, I have encountered frequent hanging, sudden shutdown, and now December 13, 2010, it shudown and now it wont open anymore. I just want to know what should I do regarding this problem. I hope Nokia will help me with this problem because the phone that they have just gave me is defective.

i am giving solution to C7 USER
TO
SOLVE UR PROBLEM. C7
PROBLEM: 1. Phone hangs then
restarts after a
few seconds 2.phone hangs, shuts
down, then cannot be started up
again for a while, like 30
minutes. C7 SOLUTION OF
PROBLEM: Mine also has defect in
it and i rectify in following way.
~back up ur
msg,contact,videos,image
to PC.
~then format ur mmc and remove
it. ~remove 3rd party app,games
from ur phone.
~do hard reset by pressing
*#7370#
then
~reinstall C7 FIRMWARE from nokia
care and after that
~then update ur phone with
latest firmware v012.004
RM-675 file
size-274 MB (release on 30dec) in INDIA from ovi suite or
from
nokia care and PR 1.0 UPDATE(jan
1ä),then
~transfer ur
back up msg,contacts,photos. now it
will work fine and flawlessly
without
any
problem and now ur problem will
be solved. IMROVEMENTS IN
FIRMWARE v012.004:
~fix all restarting,hanging
bugs that have in older
Firmware
~Updated version is very quick for
video sharing. ~It has all new
updated Facebook
application.
~Improved browser speed and
also the
search speed also.
~It also provided updated
country and
region maps plus in-device user
guide. ~Improved search. Performance
improvements. PR 1.0 IMPROVEMENTS
~camera now starts faster
~more smooth animation during
sweep
~gallery open faster
~browser speed increases. THANK YOU.

Upgrade to LabVIEW 2012 caused Additional Installers issue

Hello again all you helpful forum-goers!
I have been using LabVIEW 2010 (SP1) for a while on my Windows XP computer, but I recently purchased and installed LabVIEW 2012 for a future project. In the meantime, my previous projects must still use LabVIEW 2010 until I use my company's formal change tracking system to upgrade them. However, when I recently opened one of my older projects in 2010 to update it and rebuild the installer, I saw in the Additional Installers tab a bunch of blank lines at the end of the list (see attached screenshot). This doesn't directly hurt me, but I have to think it is a symptom of the root problem.
More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked. That seems like an upgrade oops on National Instruments' part to me. I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk. "FADEC_Emulator" is the name of my software. Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3. Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked. However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3). Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3? Confusing! And if it did that, why didn't it have that version handy already? And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
I'm afraid that since installing LabVIEW 2012 my system has gotten into an unstable state, and I now have possibly corrupted my project's LV project file. I need to have both 2010 and 2012 on my computer for the time being.
Does anyone have any idea what is going on with my system, and/or how to fix it?
Thank you very much in advance for your suggestions and time!
-Joe
Solved!
Go to Solution.
Attachments:
Additional Installers Blank Lines.png ‏45 KB

Hi Joe,
I tried to reproduce your issues, and encountered mixed results. Please verify with what I've provided below that we are testing under the same conditions
jmorris wrote:
More directly relevant, the NI VISA Run-Time 5.0.3 that had been checked previously was now missing, and the NI VISA Run-Time 5.2 that had replaced it was NOT checked. That seems like an upgrade oops on National Instruments' part to me. I decided it was just a quirk, and that the 2012 installer had replaced my 5.0.3 version with the 5.2 version (deleting the old version), so I checked the 5.2 version to build my installer, and after requiring my DVD to copy the software to my computer, that seemed to work ok.
In this scenario, I built a test project with VISA RT 5.0.3 and LabVIEW 2010 configuration. I then installed LabVIEW 2012 and VISA 5.2.0 on top of the aforementioned setup. When I opened the 2010 project in 2012, VISA Run-Time 5.2 was checked (as expected, dissimilar to your configuration). As I mentioned earlier, this may have been because VISA 5.2.0 did not install properly.
jmorris wrote:
Now the immediate problem: when I distributed the project file to a colleague who only has LabVIEW 2010, she was not able to build my software's installer, because it asked her for the "FADEC_Emulator" disk. "FADEC_Emulator" is the name of my software. Expanding the error dialog showed that it wanted that disk in order to get access to NI VISA Run-Time 5.0.3. Opening the properties of the installer in the project file within LabVIEW showed NI VISA Run-Time 5.0.3 checked. However, opening the project file with Wordpad showed that NI VISA Run-Time 5.2 was listed as an additional installer (and NOT 5.0.3). Maybe her system saw that I wanted NI VISA Run-Time 5.2, and automatically replaced it with the latest version it had, 5.0.3? Confusing! And if it did that, why didn't it have that version handy already? And switching versions like that seems like it would be a bad idea to do silently, in case I was relying on a feature specific to the new version.
For this case, I built the installer on LabVIEW 2012 with VISA RT 5.2.0 then saved it for LabVIEW 2010 compatiblity. When I opened the installer in a LabVIEW 2010 with VISA 5.0.3 environment, VISA 5.0.3 was checked (as expected since LabVIEW will default to the latest version of VISA on the PC regardless of what the original installer referenced). I did, however, see three extra blank lines in the additional installers tab (more on this below) . I also tried to build the installer as you indicated, but did not get any prompts for disks and was able to build successfully.
One thing to keep in mind is that LabVIEW by default will use the version of the driver that is installed on the build PC, regardless of whether it is newer or older than the installer references. If you feel this negatively impacts your successes as a developer, please feel free to post a feature request (e.g. for a prompt when the driver version changes) in our idea exchange forum (http://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas ).
Lastly, regarding the empty lines in the additional installer specifications, this problem appears to be fixed in LabVIEW 2012 and only manifests itself in 2010. During my course of testing, this did not affect building the installers and is a minor inconvenience which has been fixed in subsequent versions.
Please let me know if you have any additional questions/comments regarding these issues.
Regards
Doug W
Applications Engineer
National Instruments

LabVIEW 2012 used to hang at shutdown, now hangs at launch ("Initializing menus")

Similar Messages

Maybe you are looking for