Including the RunTime Engine in a build

[wiebe@CARYA]

---

@Coryman wrote:

I think I have it!  I am sending the entire 'volume' folder over and it is 492 MBytes.  How's that?  The volume folder has the support files.  Didn't know that was part of what needs to be sent to run the installer. 

---

Yes, you'll need the entire folder.

492 MBi is expectable. You might try to turn off some support installer that are not needed (a trail and error process) to get it to maybe 250 MBi... Note that you need to do a full uninstall before testing the new install, or the application might still work, because the old installer already installed the dependencies.

Note that once the installer installed the RTE, you can run any\all LabVIEW executables (for that LV version, if all dependencies, DAQ etc., are also installed). So the installer can be used as a vessel to get the RTE on a system. Downloading and installing the RTE would do more or less the same, except the custom installer will also add shortcuts and such to the OS.

[Coryman]

Well, my shop ran the installer and his computer STILL says there is no RunTime Engine.  I saw it listed as part of the additional files for the build, so what is going on now?

[RavensFan]

Don't know.  It's impossible to help without any screenshots of what the installer build looks like.  Also, what NI-MAX looks like in the software part of the tree.

[crossrulz]

Run the installer as an administrator?  I have seen a few other programs mess up when the installer is not ran as an admin.

Otherwise, I think you need a screen shot of the error coming up.  It might be a VI that is broken on deployment and not a RTE issue.

[Coryman]

My client manually installed the run time engine and the application now comes up on the screen, but there is no communication with the front end.  They are using a PCI 6221 card for the interface.  Here is a screen dump of the installer build.  I am assuming the drivers for that card are included in the build.

[Coryman]

Yes, he is the administrator for that computer.

[RavensFan]

Do you have any error message with a specific error number? ("no communication on front end" is not that specific to tell us what is going on)

Is it possible that the VI is looking for the device under a specific name, but the device has a different name when installed on the target PC?

Show us the NI-MAX screen,  software branch AND devices and interfaces

[crossrulz]

---

@Coryman wrote:

Yes, he is the administrator for that computer.

---

As of Window 7, that does not matter anymore.  You have to right-click on the installer and choose "Run As Administrator".  If you are an admin, it just does not ask for an admin password.

But we've moved on from that now.  I am with RavensFan.  It sounds like the device is just not configured the same (or at all) on the customer's machine.  You will probably want to uncheck the "Automatically select additional installers" and add the "NI-DAQmx Runtime with Configuration Support".  This will add MAX to the installer and allow the customer to configure and test the DAQ before trying your application.

[wiebe@CARYA]

---

@Coryman wrote:

Yes, he is the administrator for that computer.

---

With UAC that doesn't mean the installer is run with full administrator rights.

https://www.google.com/search&q=administrator+account+vs+run+as+administrator

Explicitly right click the installer and select "run as administrator" is not the same as installing it as a administrator...

Maybe the system is spoiled now (installer thinks it's installed, Windows thinks it's not). Might try an uninstall first (as administrator).

EDIT: That crossed (12 min later? not sure what happened)

[wiebe@CARYA]

I try to avoid hardware, but adding DAQmx to the installer will not automatically add all the MAX tasks to the installed application.

I think there's an option somewhere that installs the DAQmx setup with the installer. Not sure if you use tasks (or other things configured in MAX), but that's the first thing that comes up.