Ronin7

Yes- that did fix the issue. I moved "Create control.vi" out of the C:\Program Files (x86)\National Instruments\LabVIEW 2018\project\UI Tools\Control Generator directory, opened LabVIEW 2018 SP1 (which now launches without crash), moved "Create Control.vi" back into the original directory and mass compiled the directory and now everything works. I appreciate your assistance and I apologize for digging up an issue with an outdated version of LabVIEW but some of us are stuck on older versions. Again- Thanks!

Hello, I recently installed the UI Tools Addon Package and now LabVIEW 2018 crashes immediately on start. I saw a similar topic with the same package where Jim Kring was able to give some instructions privately to help resolve the issue- I would appreciate the same assistance as I have tried to uninstall all packages and reinstall LabVIEW 2018 and LabVIEW still crashes immediately. Appreciate any assistance, Thanks!

Maybe This is what they mean?

I don't see a way to change the border color programatically (even with scripting). The only way to change the border color is with the paintbrush tool in the dev environment- so maybe create a dedicated control for each of the above types with the coloring applied in the dev environment and then programatically show/hide each themed control. Not elegant and would require some extra logic to show and hide the themed control but is doable. If you get really desperate you might be able to do what you need with the .net versions of the controls you want to use but that is a whole new can of worms.

Rolf Because some companies display sociopathic behavior toward their customers NI should do the same? While that may be a reality that is an unconvincing argument. The point in all of this is that the infrastructure is already there for a customer who has already paid for a lifetime product. If they are so hard-up for money they could charge some sort of re-access fee, say $100, for the effort to keep the content available and the bandwidth used to provide the download. As far as accusing someone of not doing all of their job if they did not predict that NI would totally shift paradigms as far as LabVIEW licensing and marketing, well then 99% of their user base is guilty of the same...

No way to enlarge anything on the LabVIEW tree controls. Best Bet for what you need is to use a .net Treeview control. You can have custom sized images etc. but there is a somewhat steep learning curve and using .net in labview results in messy block diagrams with all of the references that have to be opened and closed etc. There are examples on LAVA and ni.com.

Thanks for the assistance Gents- apparently it is the cvirt.dll causing the issue (CVI Runtime cvirt.dll was deprecated in 2017) KB article in case it helps anyone else in the future CVIRT.dll Is Missing From LabWindows™/CVI™ - NI. Copying cvirt.dll to c:\windows\system32 AND c:\windows\sysWOW64 fixed the issue.

ShaunR- thank you for your response. I'm using LV2018 32bit to attempt to get this old stuff working so the bitness should be OK. I used "Depenency Walker" as you suggested and while I'm sure I don't understand everything it shows it appears that there are a bunch of missing dependencies so it looks like there is an issue with the driver installer. Appreciate the help-

All, I need to get a VI with some Old Tabor Drivers working. I have installed the particular drivers from NI.com but I am getting an error stating a .dll cannot be loaded. If I open the Call Library Function Node it is expecting the .dll to be at C:\VXIPNP\WinNT\Bin\ww257x_32.dll . Since this location does not exist for Windows 10, I tried creating that folder and putting the .dll there and that did not work. I tried pointing to other locations as well and still no luck. Does anyone more familiar with how .dlls should work have an pointers (no pun intended) for how to get this garbage working? a

Good luck Sir- you are one of the shining lights of LabVIEW and your willingness to share deep insights on this and the NI forums was of immeasurable value. I hope that there are others at NI with a comparable understanding and skillset but that is probably unlikely.