RT Startup does not disable!

[sth]

I have an RT project that should run "forever", it is set as startup.  And runs as startup as well.

However during development, I want to run it in the Development environment for debugging.  However, if the startup routine is still running, asking it to run the VI causes Error 666 and the RT system has crashed and restarted. Ok, then I try to run my VI but network ports are not released and things won't run.

So, I turn off the "Set as Startup" characteristic of my VI build and ask the system to deploy and reboot.  Deploy is sketchy since there is a running startup.  When it reboots the same dang startup runs again since it DID NOT DISABLE.

So I have to log in through SSH, manually delete the startup.rtexe file and reboot.  Then I can run my VI in the Development environment.  This is way too much hacking around for something that should be a standard operation.  Kill the startup VI should close all asynchronous VI launches, all network port opens, all VISA references etc.  It should reset the RT execution environment back to pristine.  However it only seems to do it in a half-assed way by crashing the RT system.  I tried reporting this bug, but only got a hint that sometime someone would look into it.

This is not a show stopper but I would put it under "Major Inconvenience" for a developer.  Have others had these issues or am I pushing the RT envelope by asking it to do a lot of things, (asynchronous launching, network port listening and server response, FPGA data fetching and caching etc.)

[Jacobson-ni]

I haven't seen this myself. I've definitely had a startup executable running and tried running a project from the IDE but I only remember some dialog telling me that there is already code running and do I want to stop that application before deploying my own code and if I continue past that it seems to work as expected.

I only did a quick search through our bugs but can't find a single reference to an error 666 or -666, so I guess I would want to make sure it wasn't just a typo (I was assuming it's a LV error but maybe that's not the case).

[sth]

Freudian typo:

LabVIEW: (Hex 0x661) The LabVIEW Real-Time process encountered an unexpected error and restarted automatically.