.exe Build from LabWindow/CVI 7.1 run exception under RTE 8.0.1

Below is the source file  of test1.exe, which was built using LabWindow/CVI 7.1 environment, OS is Windows XP SP3
Due to some reason(install TestStand, or LabView, or ...), the Runtime  Engine  cvirte.dll, cvirt.dll (exists in c:\windows\system32\ )is 8.0.1
Executing this file, the GenericMessagePopup() will generate window's exception.  But if executing GenericMessagePopup() before LoadLibrary(), it will be ok.
By the way, "cp3245mt.dll" is Borland's DLL. If load other DLL, everything is OK.
Is there any suggestion to solve the conflict between NI and Borland? Thanks!
// test1.c  sourcefile
#include <windows.h> 
#include <userint.h>
#include <stdio.h>
main()
// If execute the below line first. it will be ok.
//    GenericMessagePopup("Info", "Test","Yes","No",0,0,0,0, 
//   VAL_GENERIC_POPUP_BTN1,VAL_GENERIC_POPUP_NO_CTRL,VAL_GENERIC_POPUP_BTN2);
   LoadLibrary("cp3245mt.dll"); 
   GenericMessagePopup("Info", "Test","Yes","No",0,0,0,0, VAL_GENERIC_POPUP_BTN1,VAL_GENERIC_POPUP_NO_CTRL,VAL_GENERIC_POPUP_BTN2);

Did you ever figure this out. I've set classpaths, the APPCPATH variable several
times with many variations and its not working for me, though the jsp thing is working.

Similar Messages

  • Announcement: LabWindows/CVI 2010 SP1 Run-Time Engine Updated

    A new version of the LabWindows/CVI 2010 SP1 Run-Time Engine (10.0.1.434) is now available for download. The new version includes Security Update 5Q5FJ4QW which resolves security vulnerabilities in components installed with LabWindows/CVI 2010 SP1 and earlier and LabVIEW 2011 and earlier. Further details can be found at KnowledgeBase Article 5Q5FJ4QW: How Does National Instruments Security Update 5Q5FJ4QW Affect Me? Installing the security update will have the same effect as installing the new version of the Run-Time Engine.
    The update can be downloaded from the Drivers and Updates page. The LabWindows/CVIRun-Time Engine is a free download.
    National Instruments
    Product Support Engineer

    The correct link should be this one
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

  • Permission Denied Error when calling Matlab script from LabWindows​/CVI

    Hello,
    I am reading in data from a DAQ and am writing it to a .csv file in LabWindows/CVI.  I am then sending this data to Matlab to be filtered.  I would like the filtered data to be accessed by LabWindows/CVI so that I can display it as a strip chart.  I have gotten everything to work except the writing to a file in a Matlab script that is called from LabWindows/CVI.  I am basically using the shipped example in found in the activex demo. (http://zone.ni.com/devzone/cda/epd/p/id/2994). I select the script that I want to run and each time it tries to open a file with write permissions I get a "Permission Denied" error.  This occurs when using fopen() in Matlab.  I have also tried using csvwrite() as well as dlmwrite().  Each one gives me a similar error.  The script currently does not try to do any data processing.  It just opens the file, if it is successful it then prints "hello" and then closes it.  The script works well when it is run in Matlab, just not when it is called in LabWindows/CVI.  Below is the script.  Any thoughts, comments or suggestions are greatly appreciated.  I am also open to using other approaches for sending data between Matlab and LabWindows/CVI.  Thanks in advance!!
    fclose('all');
    [file, errmsg] = fopen('out.txt', 'w');
    if(file<0)
        disp(errmsg)
    else
        fprintf(file, 'hello');
        fclose('all');
    end;
    [file, errmsg] = fopen('out.txt', 'w');
    if(file<0)    
    disp(errmsg)
    else  
     fprintf(file, 'hello');    
    fclose('all');
    end;

    I am using Windows 7.  I am running CVI as an administrator and was able to get rid of the "Permission Denied" error by going into the User Account Controls in windows and changing it to "Never Notify".  However, this did not fix the problem of Matlab not being able to write to a file when the script is run from CVI.  In the Matlab code below, It now gets in to the "else", suggesting that fopen() returns a good file handle.  After getting in to the else statement, it will not actually write to the file, nor does it create it.  However, I can make changes to the plot settings and those appear.  Everything is functional when run from Matlab but when run from CVI, things get screwy with opening the file for writing.  It handles the read well.  It seems like there would have to be some file permission errors but, in the CVI program, I open and write to the file "in.csv".  Any help is greatly appreciated.
    clear;
    fclose('all');
    t = zeros(1000);
    t = csvread('in.csv');
    for i=1:1000
        t(i) = t(i)*4;
    end;
    [file, errmsg] = fopen('out.txt', 'w');
    if(file<0)
        disp(errmsg)
    else
        fprintf(file, 'goodbye');
        for i=1:1000
            %t(i) = t(i)*3;
            fprintf(file, '%f,', t(i));
        end;
        fclose(file);
        plot(t/3, t);
        ylabel('t');
        xlabel('Time (s)');
        title('Is this really working?!?');
    end;
    Thanks,
    Chris

  • Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW

    Hello All,
    Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW
    http://zone.ni.com/devzone/conceptd.nsf/webmain/9A93316BEBEDB17786256FA300675A0A 
    But I can not find any hyperlinkt to download
    "LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers"
    Is there any evaluation version for downloading?
    Thanks,
    nonomiya

    So strange,
    I go through three pages but does not find any entry for download,
    hmm...,
    1. After press the hyperlink,
    See Also:
    LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
    2. and for a resuest info. form.
    3. press download..
    ====
    LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
    System Requirements
    NI LabVIEW 7.1 or later
    Windows 2000/NT/XP
    Use the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers to create LabVIEW VIs for VXIplug&play and IVI-C instrument drivers from function panel (.fp) files.
    Instrument Driver Network
    Before using the conversion utility to create a new instrument driver wrapper, please visit ni.com/idnet to see if a LabVIEW Plug and Play instrument driver is available for your device. The Instrument Driver Network (IDNET) provides support for more than 3,000 different instrument models from over 170 different instrument vendors.
    Recommendations
    This utility was created for developers of C-based instrument drivers who wish to provide a LabVIEW interface, but do not develop a LabVIEW Plug and Play driver. By developing the C and LabVIEW interfaces together, it keeps the components synchronized, and eliminates the need for customers to create their own LabVIEW interfaces. Vendors should distribute the LabVIEW wrapper files with the associated VXIplug&play or IVI instrument driver, so that end users do not have to visit multiple web sites to download the complete driver.
    If you are not an instrument vendor, we recommend that you use this utility only if you have instrument driver expertise. Access to the instrument driver source code is preferred, in case you need to edit the C instrument driver in LabWindows/CVI.
    After generation, the wrapper VIs should be tested with the instrument.
    Instructions
    Once you install the software, simply access the utility from the Tools>>Instrumentation>>Import CVI Instrument Driver...menu in LabVIEW. This software replaces the built-in tool and provides feature enhancements.
    For additional information on this utility, view the resources below.
    Readme for the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
    Submit your Driver
    Visit the Instrument Driver Network
    nonomiya

  • Update Station Globals from LAbWindows/CVI user interface

    Hi,
    I am having a requirement such that i need to update a station global variable to true or false based on the click on a button present in User Interface.
    My Setup:
    Labwindows/CVI 8.5
    TestStand 4.2.1
    Please advice me.
    Solved!
    Go to Solution.

    Hi,
    first thing, why have you posted this query twice, http://forums.ni.com/t5/NI-TestStand/Update-Station-Globals-from-CVI-UI/m-p/1317023
    to be able to update a StationGlobal, you first need to get a reference to the Engine, this can be done using ApplicationMgr.GetEngine()
    Once you have that reference you can then get a reference to the StationGlobals by the use of Engine.Globals(). this returns a PropertyObject.
    So now you can use the SetVal methods to set your boolean, eg PropertyObject.SetValBoolean("MyBoolean",  0,  True)
    hope this helps
    Regards
    Ray Farmer

  • Importing Instruments Driver from LabWindows/CVI

    Does anybody have got wintools_32.dll library ?
    I need it to convert LabWindowc/CVI Wintools Instrument Driver to Labview.
    Could you send it to me?
    Romek.
    [email protected]

    Hi!
    Thanks for your answer.
    Exactly, I've tried to import LabWindows/CVI instrument driver to Labview.
    This Instrument driver I've found here:
    http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3F04956A4E034080020E74861&p_node=DZ52176&p_submitted=N&p_rank=&p_answer=&p_source=External
    During import procedure i was asked about wintools_32.dll library.
    Personally I am interested in System Tray icons functionality of this driver.
    I'm not sure that wintools_32.dll is Labwindows/CVI library, but i've searched Microsoft Windows pages with no results.
    Regards.
    Romek.

  • How can I convert a project from LabWindows/CVI 2010 to a Visual Studio 2011 project?

    I have a good sized project, 12 source files, 14 headers, 1 uir, that I want to be able to edit and compile in MS Visual Studio 2011, MSVC++.
    I remember being told that LabWindows dropped support for C++ in 2008 and no longer had a wizard for converting projects. I know I can go the DLL route, but I have never created a DLL before and wouldn't know where to begin with it. What would be the best way to go about this conversion?
    Solved!
    Go to Solution.

    CVI 2010 still supports the Visual Studio Conversion Wizard for Visual Studio 2005/2008. We do plan to add support for VS 2010 in a future release.
    If you need a VS 2010 project now, you can use the Visual Studio 2008 conversion wizard, then upgrade the VS 2008 project to VS 2010.
    National Instruments
    Product Support Engineer

  • LabWindows/CVI for Linux 2010 support under glibc-2.3

    Our target Linux platform has glibc-2.3 (compatible with version 8.0) .  Our hope was to implement version 2010 which fixes some serious shorcomings in version 8.0, however it requires glibc-2.5.  This library is integral to the Linux OS and can't be updated alone.  Because our CVI application is a wrapper on a third party software product, upgrading the OS is not an option.
    What we desire is release of 2010 that is compatible with glibc-2.3, even if there are limitations.
    One serious problem in version 8.0 for which we have no work-around:
    On some Linux systems, FileSelectPopup
    doesn't show all the files in a directory.
    Others for which we begrudgingly deal with:
    Displaying a panel can take a long time
    when other threads are processing system events. While the panel is trying to
    display, the contents of the panel might be entirely black. (Limiting all GUI calls to a single thread avoids this)
    On some Linux systems, FileSelectPopup
    doesn't show all the files in a directory.
    Panels can behave erratically when their
    size is modified from within the panel callback as a result of a size event.
    (The size returned is different than what is programmatically set).

    This isn't even worth responding to, but I can't help it.
    From someone who has great experience with many OSs and not swayed by marketing hype, lemming herding, or other cult issues. I can confidently say the following:
    A simple analytic approach to OS determination reveals that Linux (& other Unix), Win-x, VxWorks, RTE, OSx, etc. each have specific application targets. Determine if your application requires mass market appeal for gaming & other toys, or be it industrial, or mission critical applications. Always choose the right tool. If you only have a hammer...step aside.
    As for where the questioned services are provided...study the conceptual origin of DDE, Active X, etc. Unix has it, and much more. Don't get me started on the interprocess limitations of Windows! The
    re's more to be held for those who have seen the possibilities.
    Any comparison among OSs for 'the best' is like comparing apples, oranges, etc. Even a fruit stand attendent is more intelligent then to attempt such a feat! If you want a mango, buy a mango. But don't try to prove that it's better than any other.

  • The applicatio​n uninstalle​r ,created with Labwindows CVI, doesn´t work after upgrading to 2010 version

    Hi,
    I have been working with Labwindows CVI 2009 with no problem but after upgrading to 2010 version I have the following problem:
    When i´m going to execute the unistaller, either from Windows Control Panel or directly from the uninst.exe icon, it doesn´t work. The PC thinks a few seconds and does nothing, and it happens with all the applications I build with Labwindows CVi 2010.
    Thanks,
    Asier
    Solved!
    Go to Solution.

    Hello -
    Are you installing these distributions on a non-English operating system?  If so, the first thing to try would be the workaround listed on this known issue. 
    The known issue only lists Italian OSs as the troublesome OS, but it could actually happen on many different non-English OSs. I will update the text accordingly the next time I update the known issues list.
    NickB
    National Instruments

  • Mysql database connection with Labwindows/CVI 2009 sql toolkit

    Dear experienced users,
    I am using the following software/hardware:
    Windows 7/ Mysql database 5.6.15 64-bit with MySql ODBC 5.2 Ansi driver installed
    Labwindows/CVI 2009 with sql toolkit
    The user DSN of ODBC Data source administrator have been confiugred to one of mysql database. The test MYSQL Connector/ODBC is succesful.
    The Labwindows/CVI build setting is configure to debug64 after trying debug (32)
    The source code is from the example readtab.c with changes to the dsn I am testing
        hdbc = DBConnect ("DSN=dvd_collection");   
    The error message I have is confusing me.
    (it is in the attachd png)
    I thought it was due to the 64 bit mysql database. That's why I tried the 64 bit build from Labwiondws/CVI. I alsow tried Labview DB tools open connect.vi. It shows me the same error.
    Any suggestion is appreciated.
    Thanks,
    Jimmy
    Attachments:
    Capture.PNG ‏24 KB

    Jimmy
    I always use connection strings of the form "DSN=datasourcename;UID=database_user_id; PWD=database_user_password".
    Where:
    datasourcename = The name of the connection defined in the ODBC connection.
    database_user_id = One of the user identities created by the database administrator. Obviously the administrator will lock down the permissions appropriate to the task in hand.
    database_user_password = The password that identifies database_user_id, again set by the database administrator.
    Note that while it is obviously desireable to lock the permissions down as far as possible on the MySQL server, the more you do so, the slower the database will run, because of the way mySQL searches the permissions tables.

  • How to access the result list in teststand after execution using labwindows​/cvi

    I am developing a user interface in labwindows/cvi that runs multiple teststand sequence files and would like to combine their reports (generated in teststand) into a single file at the end of a UUT. What is the best way to do this? At the moment, I'm trying to access the result list local variable after the execution has ended using API calls from labwindows/cvi and an end-of-execution callback event but those run-time variables do not exist anymore. How do I get a hold of the result list array at the end of an execution? I would like to grab this variable and pass it along from sequence to sequence using labwindows/cvi and not teststand itself. Is this possible? Any help would be great.
    Thanks in advance,
    Luis

    Hey Luis,
    Check out the response to this thread at the NI TestStand board here!

  • Yokogawa UT driver for LabWindows/CVI 6.0 won't translate to LabVIEW 8.6?

    The device driver for the Yokogawa UT series furnace controllers is in LabWindows/CVI 6.0 and I would like to use it in LabVIEW. I tried to use the utility to convert from LabWindows/CVI to LabVIEW, but it said it couldn't and that the device driver is from before LabWindows/CVI 5.01.
    In any case, here is the series of events.
    I downloaded the LabWindows/CVI to LabVIEW Converter, from
    the page on LabVIEW's developer's connection that had the driver for the
    Yokogawa UT controller.
    From an empty LabVIEW Block Diagram, I click
    Tools>>Instrumentation>>Create LabVIEW Interface to LabWindows/CVI
    Instrument Driver...
    This takes a little while to load. During loading an
    FC_Interface_Main.vi runs, apparently trying to find a file.
    Once that is done, the two options are Basic and Advanced. I leave
    basic selected. I click next. browse to find the ykut.fp file from the
    driver I downloaded.
    I then click next. The error window that is seen in the screen shot is
    then shown.
    I called a tech support guy at NI about this, and I e-mailed him with all the above, but there was no reply, though the conversion utility is no longer available on the same web page as this specific device driver.
    In any case, if anybody could give a little guidance, it would be appreciated.

    Hello Screamingzebras,
    I converted the .fp file to be version 5.5 and ran the utility that was mentioned.  I have attached two files to this post.  "ykut.zip" is the converted .fp file (version 5.5).  "yut.zip" is the converted instrument driver.
    Regards,
    Jon S.
    National Instruments
    LabVIEW R&D
    Attachments:
    yut.zip ‏174 KB
    ykut.zip ‏25 KB

  • Using DLLs created with LabWindows/CVI 8.0.0 in LabWindows/CVI 8.0.1

    Hi,
    I have created a project containing some methods with LabWindows/CVI 8.0.0 and then build the project and generated the DLL and LIB files. These DLL and LIB files are working fine in another projects created in LabWindows/CVI 8.0.0 (even on another machines).
    But when I use these DLL and LIB files in a project created with LabWindows/CVI 8.0.1 on another machine and try to call the methods of these files, the following error occurs: -
    "The program has caused a 'Unknown' fault at 001B:7C812AFB"
    Is this error occurs due to ther version mismatch or there is some other problem?
    Please help me to resolve this issue.
    Thanks,
    Sarabjit Singh

    Judging from this, I don't think NI has a newer version of this tool:
    http://forums.ni.com/t5/Measurement-Studio-for-VC/Convert-project-from-LabWindows-CVI-to-Visual-Stud...

  • CVI applications can run in Linux ?

    Hello
    Ask: 1 in Windows to write CVI applications can run in Linux? And Linux must have the LabWindows/CVI 2010 Linux Run-Time module??
     The 2.Linux can support the CVI development environment?

    There is some sort of support for running applications on Linunx, even though you cannot directly run the IDE on it.
    Shortly, you will need to develop on Windows and then compile and run on Linux system. I don't know how easy is all this process as I only develop for Windows systems.
    A lot of informations can be found in this White Paper.
    The Linux Run-Time Engine is a module to be purchased separately.
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

  • Avoid MathScipt Comments in EXE, Build & Run Problems - NI Please Fix these Bugs!

    Hello,
    After 4 days of intensive work, I have finally found the solution for two major MathScript Problems:
    1) Mathscript Comments are included in your EXE File !!
        - Yes, if you do not watch your steps, the EXE will include all your % Mathscript Comments!
    2) Problems building, but even worse: An app that builds with NO Error and NO Warnings will not RUN and creates the following misleading Erro Message:
        "The VI is not Executable. The full development version of LabView is required to fix the errors"
        With absolutely NO hint to what VI have the problem.
    I have made myself an internal note how to avoid this problem. I am using LabView 2009, 2010 DS1 Release (I think this is 9.01) under WInXP SP2.
    Rather than retyping everything, I will post the full text of my Notes below. I also mention several other LV BUG in this note, so pleae read carefully.
    One is the TagSrv Error that occurs in LabView 2009 if I programatically deploy Shared Variables under the WinXP Development Environment. After this problem has occured, it will occur every time I restart XP, and in essense I have to restore to before I did this (thanks Nortong Ghost !!!).
    Below you can find the full unabridged version of my Build, Run and Bug Notes for LV 2009 / 2010 DS1 (9.01). Hope they can be helpful to my fellow LabView programmers!
    2010-07-03:
    Building under LabView 2009 / 2010 DS1 Release (version 9.01)
    Follow the steps below:
    a) To successfully build an EXE that also runs
    b) Avoid that MathScript Comments are included in the EXE !!!!!!!!!!!!!!!!
    Before Building:
    I) Recompile All  by pressing Ctrl+Shift and pressing the RUN button on the Application_References.vi
       Then Save All (about 1200 Vis are saved)
    II) Make Sure that NO User Defined Mathscript (and Mathscript Nodes?) define Empty Functions:
        This seemed to cause the following problem with the built EXE: The main VI will be broken, and a dialog reports:
        "The VI is not Executable. The full development version of LabView is required to fix the errors"
        MathScitp BUG: Empty Functions causes no Build Errorm but RUN Error:
        The following User Defined MathScript .m files are candidates:
        log_write() and log_clear() whith do_log_write() and do_log_clear() commented out, these functions are empty.
        When calls to log_write() and log_clear() where removed, the problem above vanished !
    Building the EXE:
    1) Additional Exclusions:
     -"Disconnect type definitions": YES
     - "Remove unused polymorphic VI instantces": YES
     - "Remove unused members of project libraries": NO (do not know if this is important)
    2) Advanced:
     - Enable Debugging: "NO"
    3) Mathscript BUG: The Application Builder Includes ALL MathScript Comments in the EXE if you use the New Build File Layout:
       IMPORTANT !!!!!!!!!!!!!
       Advanced:
       "Use LabView 8.x file layout": YES !!!!!!!
       Using the new layout, causes ALL COMMENTS FROM USER DEFINED MATHSCRIPT .M FILES TO BE INCLUDED IN THE .EXE !!!!!!!
    4) BUG: DSC Reference Problem in LabView 2010 DS1 release:
       In VI Deploy_Shared_Variables.vi we deploy alle Shared Variables using the "Deploy Libraries.vi" which is a part of the DSC option.
       As long as only deploying of Variables is used, using this VI should NOT require any DSC Runtime license.
       We have used this before with no compilation problems.
       However, starting with LV 2009 SP1 (or was it the DS1 2010 upgrade) LV will start nagging us to resolve references to tens of VIs
       in the DSC lib file ! Solution: Used press "Stop" on the dialog, and the Build will succeed and the EXE will work !
       Optionally, we could use the following Invoke node for the deployment:
       (see: http://digital.ni.com/public.nsf/allkb/04D9A85B6967EE87862571140065EEC6). Excerpt from this description:
      <<Right-click the block diagram to bring up the programming palette and go to Programming»Application Control and place the
        Invoke Node on the block diagram. Using the hand tool, click Method and select Library»Deploy Library>>
    5) LabView BUG: Do NOT RUn the Application under the WIn XP SP2 Development Environment if the APP Deploys Shared Vars:
       This will cause the Dreaded TagSrv Error:  "TagSrv.exe: This application has requested the runtime to terminate in an unusual way".
       After this Error has occured, it will reoccur each time WinXP SP2 is restarted, and (Network) Shared Variables will NOT work any more!
    Geir Ove
    Attachments:
    LabView_Tagsrv_Error.jpg ‏26 KB

    Hello Geir,
    I have tried to reproduce the behavior you are seeing where .m file comments appear in the final built executable.  However, I am unable to do so using LabVIEW 2009 SP1.  I have a caller VI with a MathScript node that calls the adder function in adder.m.  The contents of adder.m are as follows:
    % ADDER This function adds 3 to its input variable
    %   y = adder(x)
    %   INPUT: x
    %   OUTPUT: y, equal to x + 3
    function y = adder(x)
    y = x + 3;
    I have configured the build specification as you mention in steps (1) and (2):
    Additional Exclusions
     - "Disconnect type definitions" Yes
     - "Remove unused polymorphic VI instances" Yes
     - "Remove unused members of project libraries" No
    Advanced
     - "Enable Debugging" No
    At first, I did not include the adder.m file in the project.  I built the application and was not able to find the text "adder" anywhere in the EXE.  Then, I added the .m file to the project and put it in the "Always Included" section in "Source Files."  Again, I was not able to find the search text in the built EXE.  In step 3, you mention
    geirove wrote:    
       "Use LabView 8.x file layout": YES !!!!!!!
    but in the 5th post in this thread, you state
    geirove wrote:
    Compile using the new compile method ( Use LabView 8.x file layout": NO),
    I have tried both settings in the Advanced section, but again, I am not able to find any comments in the EXE.  I even added a call to the "path" function in adder.m.  This puts a warning glyph on the caller MathScript node and generates different code.  The EXE will return an unknown symbol error for adder (any VI with a warning glyph will not work in a built app), but I am not able to find any comments in the EXE.  This project is attached below.
    As for your other item with a broken EXE if you call empty functions, I am unable to reproduce this as well.  I have taken the last attachment to your third post in this thread (the log_write function) and called it from the caller VI as well.  The EXE runs just fine and I do not find any comments in this EXE either.
    Unfortunately, there was a rather serious issue in the LabVIEW 2009 MathScript RT Module, where some internal MathScript VIs could become corrupted when building executables.  Have you tried running the "Find Bad Instantiations" tool from this Knowledge Base article?  Simply installing the SP1 version on top may not have corrected any VIs that may be corrupted.
    Due to our difficulty in reproducing the issues you mention, could you modify the attached project or else attach a new project, appropriately configured, that builds an EXE with .m comments embedded in it?  This way, we can uncover any minute details that we're overlooking.
    Grant M.
    Senior Software Engineer | LabVIEW MathScript | National Instruments
    Attachments:
    MComments.zip ‏186 KB

Maybe you are looking for