SystemExec.vi Out of Memory Issue

[||||||]

I have a vi where I'm trying to call a .exe to open.  I have tried entering both "cmd \c fploader.exe" as well as just fploader (the .exe is called fploader.exe and is included in the project file as a source file for deployment).  When I try to run it with just fploader in the command, it opens, but when I close it I get the "Error 2: LabView out of memory error I have attached.  If I use the "cmd \c fploader.exe" then I get Error 1: not a valid batch, program or command.  Can anyone help?

[A.Thomas]

1. You need to either pass the executable’s path to SystemExec or the executable’s path must be added to the default path.
2. You need to add a string “cmd /c “ before the name of your executable. For example “cmd /c fploader.exe”.

What would you type in the Windows Command Prompt if you were to run the fploader.exe? Do you need to pass any arguments?

[||||||]

I've tried "cmd /c fploader.exe" which results in the attachment that I have attached with Error 1 on it.  Also, again as I said, the .exe is included in the projects path since it's included as a source file (gives Error 2 AFTER the exe is open and closed).  So for some reason the open is working, I just can't close.  Also, this installer goes out into the field, so hardcoding in a patch isn't a good idea (hince why I did it the way I did).  Any other ideas?

[A.Thomas]

It’s better to add a control to the front panel and use it to wire in the path rather than hardcoding it as you mentioned. Then the other users in the field can copy the executable anywhere they want and just pass the correct path.

In regards to the issue for closing, can you elaborate a bit more? What is it that you are trying to close? The fploader.exe that you just opened?

[||||||]

So I can't let the user select a path to it, the installer needs to just allow them to hit a button and the program open.  A lot of our customers aren't computer saavy, which is why we do it this way. And yes, I am able to open the fploader.exe, but when it closes, the LabVIEW crashes with the out of memory error.