CVI 8.1 Distribution BUG

Similar Questions

• CVI 8.1 Distribution Edit Panel installer problem.

  I have a marked RED of Fulcrum OR reports on the CVI 8.1 Distribution Edit Panel. When I ignore it, the distribution kit is produced, installed and the program works correctly.

  But what is the cause of this error? I've attached a picture in a word doc.

  Mert, I got the NIReports.msm from a WIN98 CVI 6.0 computer used by our supplier. Good thing I stored his old computer. I copied on my development machine and the construction/Panel is now happy. Thanks for the answers! Scott Youngren

• CVI 2009 Build Distribution: create shortcuts

  When I change the settings for Distribution to build, I want to install my application under C:\Program Files\myFactoryDir\myAppDir, so in the "Edit" window, I use the tab "Files" to change "Installation of files and directories" as I need.

  So, I want to create the following shortcut:

  [Start>>Programs]\myFactoryDir\myAppDir\myApp.exe

  but I'm not able to specify "[start > programs] \myFactoryDir\myAppDir" as the Destination Directory (in the menu ring, only [start > programs] \myAppDir is available).

  Is it possible to do in CVI 2009 (as I am used to doing with LabVIEW)?

  In fact, please ignore the previous screenshot. Looks like I misunderstood where you want to place your shortcut. But it's even easier, then, since all you need to do is to rename the folder shortcut in the files tab:

  

• Distribution with CVI 8.0.1 construction kit fails after installation of CVI 2010

  Update out of the newspaper:

  Adding files to install
  
  **************
  
  Internal error: A tool or the library returned an error. (Error code - 21)
  
  **************
  
  Error details:
  
  Error to the MDF API function: _MDFBuildDevPartMerger_Load
  
  returned nmdkLoadMergeModule code error 26152
  
  Final report of the error
  
  **************

  This happened earlier. CVI 7.1.1 and earlier versions than 8.0.1 (i.e. + 8.1.1) work.

  Any help would be appreciated.

  It turns out there are two different problems that arise in the CVI 8.0 distribution builds when you CVI 2009 or newer installed:

  1. Support for ActiveX container will not be included if you install the runtime in the application directory, or if you're not going under the grouping of LabWindows/CVI Run-Time Engine. In these cases, the ActiveX container merge module should be used and ICB 8.0 won't be able to find it.
  
  
  2. The merge module Instrument Driver Run-Time (instrsup.msm) and the Mesa merge module (NIMesaDLL.msm) cannot be moved to the application directory (which is the option on the Advanced tab that I mentioned in the previous post). This will result in the construction of distribution fails with the error you reported.

  To solve the first problem, I recommend the copy of C:\Program Files\Common Files\Merge Modules\ActiveX_Container.msm and rename the copy with a space instead of a line of underscore ("ActiveX Container.msm").

  The second question has no easy workaround. If acceptable for your use case, I would say either making the performance overall installation (by unchecking the option in the Advanced tab) or removing the CVI build runtime of your distribution. In the latter case, your application would be based on an already mounted overall CVI runtime engine.

  If any of those who will work for you, I can get you copies of pre-2009 instrsup.msm and NIMesaDLL.msm that you would have to manually exchange and out with versions in your common Files\Merge Modules directory whenever you have need to build this distribution in CVI 8.0.

  I am sorry for these questions. Let me know if you need these older modules.

  A. Mert

  National Instruments

• Executable built with CVI 8.1 error-5093, the analysis library is not found

  Upgraded to 8.1 Labwindows/CVI of Labwindows/CVI 7.0 development machines. An earlier application was built using the ICB 7.0 and installed on a test computer. The same code built with CVI 8.1 is any error during execution of the function stdev, 5093 error code has been generated. (From analysis.h: LibraryNotFoundAnlysErr =-5093, / / the analysis library was not found.) Tried to build a facility with 8.1 and installation on the test computer and application errors still executing the stdev function. Back to the same application, but built with CVI 7.0, it works fine. Am I missing something with the build in 8.1 options? Or is it something in the workspace or project? Please notify. Thanks in advance

  Hi Tommy,.

  In CVI 8.0, the implementation of the analysis library has changed a static library that is linked to your .exe in a DLL that must be loaded when running. If you rebuild your source code and you want to deploy to another machine where the CVI environment is not installed, then you must re-create an installer in CVI 8.1 distribution, so that he can pack the analysis as well as your program library.

  You can confirm whether the analysis library is installed by searching for C:\Program NIUninstaller Instruments\Shared\Analysis\nianlys.dll in your target machine (although it is not enough to simply copy this file manually).

  When you create an installer in the CVI, be sure that, in the tab drivers & components in the dialog box change Installer , support of analysis element under the Group of LabWindows/CVI Run-Time Engine is checked.

  Luis

• Please update omp_cvi_internal.h

  Hello

  When compiling with the warning level extended I get the following messages from files provided with CVI:

  "omp_cvi_internal.h" (71,26) WARNING: function declaration is not a prototype. "."

  "omp_cvi_internal.h" (72,26) WARNING: function declaration is not a prototype. "."

  "omp_cvi_internal.h" (94,35) WARNING: function declaration is not a prototype. "."

  "WARNING winnt.h" (8780,19): cast by "LONG64" (aka "long") function of type call without correspondence type 'PVOID' (aka ' Sub *') ".

  "WARNING winnt.h" (8791,19): cast by "LONG64" (aka "long") function of type call without correspondence type 'PVOID' (aka ' Sub *') ".

  "WARNING winnt.h" (8802,19): cast by "LONG64" (aka "long") function of type call without correspondence type 'PVOID' (aka ' Sub *') ".

  I suggest you update both files include accordingly ;-)

  Hi all

  This issue was addressed by the patch of f1 2015 LabWindows/CVI. Information on bug fixes in this update can be found here: http://digital.ni.com/public.nsf/allkb/E2DAF5E18C487A8886257F7D006353EA . The patch is available through the Update Service OR or related kb download.

  Thank you

• Can I use an XControl reference in a class?

  LabVIEW help stipulates that "a private data control cannot contain an XControl or an XControl refnum", while previous reviews have shown that the problems occur in a built application, but not in the development environment: http://forums.ni.com/t5/LabVIEW/X-Control-Distribution-Bug/td-p/1132058 this question seems to have been given the CAR #210033 http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-X-Control-X-Control-Reference-as-a-Class-Data-Me... with the note that it only covers the XControl reference , not the XControl himself, as a member of class private data.

  I just tried a simple application with a XControl reference in the private data of the class, and it seems to work without error in the application built in development (2012 f3 (12.0.1f3) SP1 32-bit LabVIEW).  I have looked through the last few lists of bug fixes and cannot find this CAR in one (2011 or 2012), even if the documents say they list only a "subset".

  Can anyone confirm if the #210033 CAR has been fixed?  I don't want to go too far down this path if she will introduce problems at some unknown point.

  According to the database of the CAR, this CAR has been corrected in LabVIEW 2010.

• ICB is unable to paint child panels

  I have a problem with the panels child fault to paint in the following circumstances:

  I created a very simple application to illustrate the problem (attached).  It consists of two panels in one. File of the IUR.  I generated the default code of this and simply added the loading of the second round table as a child of the main panel and the display of this child Panel.

  If I optimize the main panel, and then reduce by using the button "_" in the title bar, when the application is changed afterwards (by clicking on its button on the toolbar of the tasks or by Alt - Tab), the child window is not repainted correctly (I see my office through a hole in the main window when the child window should be).  It is only after that I put a control on the Panel of the child; If the child Panel had no control, he painted OK.

  Sounds pretty basic, but I've been unable to influence this behavior with all the most obvious attributes of Panel (floating / important / furniture / style of the title bar / etc) and it doesn't seem to be a round table in which I can plug a fix because no case seems to be generated when the Panel is re-best.  Oddly enough if I minimize the application by clicking its button on the taskbar when it is already enabled, or by using the 'show desktop' he painted correctly when re-maximized.

  I'm with LabWindows/CVi version 8.5.1 (356) - which I note is also the version of cvirte.dll

  and MS Windows XP version 2002 Service pack 2.

  Is there a patch to do this, because it has all the features of the engine performance missing the paint event of the window for the child Panel or get confused about the cutting areas - which reminds me; by dragging the application window on the child causes to be redrawn and clicking on invisible group of child controls (if he is lucky enough to hit) works the usual Panel.

  Any ideas anyone?

  (Edit = I forgot attachment!)

  James & Brian,

  It's probably the same question that has been discussed here. If so, it was fixed CVI 9.0. (Bug ID: 112287)

  It's still not clear to us why it happens to some PC, but not others. At one point, it seems clear that the bug occurred with Vista Aero active, but we have now 3 instances of cases where Vista was not the culprit. So we do not know.

  In all cases, the fix 9.0 should have supported the problem. To confirm this, you can download the CVI 9.0 runtime and try.

  Luis

• How to force the compilation released executable before running the distribution of LabWindows/CVI kit?

  I am new in 2015 of the CVI. I used CVI 7 and when I chose "Create the Kit of Distribution", when I was still in debug mode, Labwindows asked me to build the executable of setting before creating the Distribution Kit. This does not happen to CVI2015, and the Distribution Kit is created with the latest built executable version, although I made a few changes in my code! This is a problem since I work in debug mode and I usually forget to build the executable of liberation before calling the distribution kit, so I need CVI to do it automatically like CVI 7 did. I suppose that there is an option to do this, but I can't find. Can someone tell me please how to resolve this problem and force CVI to build the exe version before building the distribution kit? Thank you.

  Today, I've solved quite simply create a new distribution. The previous like unsing was automatically imported by CVI7 project. By creating a new distribution, now when I change something, CVI ask me if I want to build the release. So I did not understand the problem but I solved it by editing a new distribution kit.

• Bug CVI research dialogue...

  I, again, don't find not the bug overview page. so, I'll post here:

  using CVI 8.5, during a search (CTRL + F). by selecting the check box "Multiple files" but NOT the checkbox "search folders", if the specified directory in the "search in files" options is not valid, the search will complain and not run. Note that this specific option is disabled since "Find in files" is unchecked, then the search does not have to worry about what's written there...

  (also: is there a page to track bugs submitted to OR?)

  You're right, it is a bug. I entered a bug for her report (#130204).

  As far as I know is not a publicly available database that you can use to check the status of a bug report. Each version of the CVI includes a list of all bugs that have been resolved for this release in its readme file, and you can also see this list online (for example, here is the list for the 8.5.1 release). If a fix is not yet released publicly, I recommend that you post a question here or send a mail DIRECTLY, ask questions about the status of the bug report.

  Luis

• CVI 2013 Legacy Formatting options not saved at exit. (Bug control)

  Bug control: when I choose the legacy formatting options to change the styles of support and then save and close the program, the information is reset to default to reopening the project.

  CVI Version 13.0.0

  Hi blakney,.

  I actually filed a request for Corrective Action on this issue yesterday. What a coincidence! Good work it is. If you want to track the status of the correction, the identification number of the CAR is 449864.

  Thank you and my apologies if this caused you inconvenience.

• CVI Distribution needs 2 versions of CVI device drivers

  I have an app that I'm building a distribution, it is in the CVI 9.0.1 and several versions before that.

  When I build it, he asks the device drivers of CVI (CVI 9.0.1) of February 2009 and drivers of CVI (CVI 8.5.1) since March 2008.

  Is it possible that I can do this using all the stuff from the latest driver disks (the disk of the Feb 2009)?

  It is an application that runs on a box of PXI, so there a lot of drivers for that and some map on the (I think)!

  Hi Ken,

  The components included from this source "Cache" will find when you go to manage Distribution, click on your distribution and click on modify. Access the driver and Components tab, then go down to each active boxes and on the right pane, you will see a check box in the component Source. Check this and it will always ask you to insert the disc of the first generation, but after that, you won't have to.

  I hope this helps!

• Is there a bug in CVI 2010 SetTableCellRangeVals and SetTableCellRangeAttribute for strings - particularly in 64-bit mode?

  It seems that I can't get SetTableCellRangeVals to publish string data to a table in 32-bit mode, I can't SetTableCellRangeAttribute to work for arrays of strings and now it seems numbers either. I just get garbage - it could be my code, however.

  Worse in 64-bit mode, I can't seem to post anything (for strings at least), but get a GP fault instead.

  I played with the size of the pointer in the array of strings (from 4 to 8 bytes

  The heart of the test code is here but the files are attached as well.

  int CVICALLBACK Test_callback (int, int int event, control panel,
  void * callbackData, int eventData1, int eventData2)
  {
  int i, numrows = 10, byattrib;
  int bit32 = 1;
  Double * dbl_array;
  char * string_array, * string;
  Rect a_rect;
   
  switch (event)
  {
  case EVENT_COMMIT:
  GetCtrlVal (main_handle, PANEL_BYATTRIB, & byattrib);
  String = malloc (50 * sizeof (char));
  If (bit32)
  string_array = malloc (4 * numrows * sizeof (char));
  on the other
  string_array = malloc (8 * numrows * sizeof (char));
  for (i = 0; i< numrows;="">
  string_array [i] = malloc (50 * sizeof (char));
  dbl_array = malloc (numrows * sizeof (double));
     
  for (i = 0; i< numrows;="">
  {
  dbl_array [i] = i * I * 3.1416.
  FMT (string, "The value is %f", dbl_array [i]);
  strcpy ([i] string_array, string);
  }
     
  a_rect. Top = 1;
  a_rect. Left = 1;
  a_rect. Height = numrows;
  a_rect. Width = 1;
     
  status = DeleteTableRows (main_handle, PANEL_TABLE, 1, -1);
     
  status = InsertTableRows (main_handle, PANEL_TABLE,-1, numrows, VAL_USE_MASTER_CELL_TYPE);
     
  If (byattrib)
  {
  status = SetTableCellRangeAttribute (main_handle, PANEL_TABLE, a_rect, ATTR_CTRL_VAL, dbl_array);
     
  a_rect. Left = 2;
  status = SetTableCellRangeAttribute (main_handle, PANEL_TABLE, a_rect, ATTR_CTRL_VAL, string_array);
  }
     
  on the other
  {
  status = SetTableCellRangeVals (main_handle, PANEL_TABLE, a_rect, dbl_array, VAL_ROW_MAJOR);
     
  a_rect. Left = 2;
  status = SetTableCellRangeVals (main_handle, PANEL_TABLE, a_rect, string_array, VAL_ROW_MAJOR);
  }
     
  free (string);
  for (i = 0; i< numrows;="">
  free (string_array [i]);
  free (string_array);
  free (dbl_array);
  break;
  }
  return 0;
  }

  Thanks for any help,

  Greg

  Greg-

  Certainly, you have found a bug.  However, I think that the issues that you run in a SetTableCellRangeAttribute are the result of a misunderstanding of the function.  This function, when you use it to set the value, sets the values of all the cells in the range to the same value.  Therefore, the var_args parameter must be the value that you want to set all cells to and not a pointer to an array of values.  In your code, you would need dereference the berries, and then, you would see that all the cells are the same value, which is the expected behavior.

  I created a bug report for the accident which follows from the definition of values on string cell types in 64 - bit with ID 284842.  This bug will be fixed in the next version of maintenace of the CVI.  In the meantime, you should be able to use SetTableCellVal to set the value of each cell individually in 64-bit.

  I'm sorry for the inconvenience-

  NickB

  National Instruments

• Generator of CVI 2012 Distribution always asks for disc

  I have CVI 2012 and drivers installed on my Windows 7 computer. It is the only version of the CVI and drivers that I have installed on my computer.

  However, whenever I try to build a distribution, I wonder to insert the CVI installation disc. It's very annoying. Why is this happening?

  Okay, I think I found what I was doing wrong.

  Apparently, the option to cache the current installed software is not an option until you have been presented with the need to install from the disc.

  (At this point I took no notes, so this may be inaccurate or misinterpreted)

  On this Panel you ask something like "you have the installation discs. If you say no, they ask where to install from. Here, I have indicated to the DVD disc with the installation disc and on this Panel was the cache option. (At least this is how I remember it.)

  What was confusing, it was that I had selected cache on the drivers... Tab that I wasn't expecting to have the option or need to do later.

• Distribution Kit for the CVI 8.0 missing files...

  We have a set of pre-built TestStand custom steps which consist of a DLL, ICO, couple of INI files of the IUR.

  A Kit of Distribution CVI 8.0 was created to install these files in the right places so that the development suite TestStand 3.5 can see IE:

  C:\Program NIUninstaller Instruments\TestStand 3.5\Components\User\StepTypes\Bin

  C:\Program NIUninstaller Instruments\TestStand 3.5\Components\User\Icons

  C:\Program NIUninstaller Instruments\TestStand 3.5\Components\User\Language\English

  C:\Program NIUninstaller Instruments\TestStand 3.5\Components\User\StepTypes\Uir

  C:\Program NIUninstaller Instruments\TestStand 3.5\Components\User\TypePalettes

  However, when the installation program is running (Administrator) some files never reach their destinations.  For example the ICO files do not appear in

  C:\Program NIUninstaller Instruments\TestStand 3.5\Components\User\Icons and language INI files are not in the

  Folder C:\Program NIUninstaller Instruments\TestStand 3.5\Components\User\Language\English.  It is on a PC Windows XP Pro SP2.

  Although custom steps work correctly a TestStand test Executive, when the sequence files that use are open in TestStand their icons are missing and made a right click put errors in the menu: "Resource File Missing", (or similar).

  Is this a permissions problem?  I know that in Vista and Win7 that the "Program Files" folder is locked close enough wise access, even if the account is administrator.  I don't think that it was a problem under Win XP!

  Any thoughts?

  Your .ico and .ini files are installed in the StepTypes directory. For example, C:\Program NIUninstaller Instruments\TestStand 3.5\Components\User\StepTypes\Language\English\CS_OpDisplay.ini. I would check your installation tree structure in the files tab when editing your distribution. My guess is that the problem lies there.

  Let me know if you still have problems.

  A. Mert

  National Instruments