hooovahh

What I was trying to say is hackers adapt every 6 months or so to crack the latest LabVIEW, which makes me think that the same effort could be put into cracking LabVIEW passwords. Well put.

You say that because new executables are released every 6 months, that this would deter the hackers. But then you mention the license generating hacks. And these surely change with every version of LabVIEW released (likely every 6 months). I would be surprised if there didn't exist a license generator for all versions of LabVIEW. I also don't know what techniques the hackers use to create license generators, but from your explanation it sounds like alot of work went into figuring out how to modify this one version of LabVIEW to open VIs with passwords. I guess the point of this post is that I believe someone out there has the ability to open VIs with passwords, in all versions of LabVIEW. I haven't seen it, but this post leads me to believe that. If I did find some page on the internet that explains how to hack all versions of LabVIEW, I'm not sure I would post it. Even this thread makes me nervous. Are we spreading the word on hacking LabVIEW, by just talking about it? However not talking about it may give the false sense of security, thinking that LabVIEW is secure when protecting source code. EDIT: It seems rightfully so, that the page at StackOverflow has been removed.

I'm not a cryptology at all, zero experience what so ever, but I've often mentioned how not secure the password protection method is (despite a few NI employees telling me otherwise). But I'm starting to understand now why it is done the way it is. I thought that the whole VI should be encrypted, making it impossible to find the MD5 of the password in the file. I now know why NI can't do that. Using a few graphics cards you can get above 3 Billion hashes/second (if you are going the MD5 route). Which would still be pretty secure for passwords 10 characters or greater (which aren't susceptible to dictionary attacks). But as already mentioned there is the LabVIEW.exe modifications that can take place as well (which are against NI's agreement).

Theres an example that ships with LabVIEW that is called Basic Input Demo or something that interfaces with mice keyboards and gamepads if they are supported. Search the palette for Joystick and you'll find some VIs.

I'm a little surprised the native Remove White space doesn't work. I also tried the OpenG remove white space and it didn't remove it. There's alot of over head but I think a simple solution would be to use the String to Byte Array, then use the OpenG Filter Array to remove any zeros, then use the byte array to string. EDIT: Sorry thought of an easier solution. Use the Search and Replace string, where you search for the 00 and replace with nothing. There is a boolean input to remove all, that needs to be set to true.

I'm sure there is a DLL call you can use but a simply hacky way of doing it is if SpeedFan supports logging the temperature. I know CPUtemp can be configured to log to a CSV file every minute or so. If SpeedFan supports this you could then re open that log in LabVIEW.

I really wish NI would be less "official". Like for instance I was wondering, why are there VI's in my vi.lib with passworded block diagrams? Before I was told it was because these VIs had scripting and NI didn't want to expose people to that. But now I can't seem to think of a good reason to hide any source code, other than the code may not be very professional looking.

I saw the random multiple untitled VIs as well. One thing I noticed is this doesn't seem to work with arrays, but if it did I could see some issues with it. What I mean is I have an array of a cluster, and in that cluster is a 1-D array of strings labeled "ArrayString". When I use the Xnode on this data type it recognizes that I have an item named "ArrayString" but according to its output the data type is a Void. In a perfect world I would expect it to output a 2-D array of String where each row is the 1D array found in the cluster. To be fair it isn't often that I have an array of string, inside a cluster inside an array, this was just a test to see how well the Xnode did what I expected. It of course did work with a 1-D array of string, inside a cluster, inside a cluster, inside an array. Here the output was an array of a cluster with one item which was the 1-D array of a string.

So I built an application that I had built many times before, and when it finished there was an error. I turned on error logging and when I built it again it worked just fine. Figured I'd share. I'd just never seen a blank error before. This was LabVIEW 2010 SP1 Windows 7 32-bit.

Correct me if I'm wrong but I think this is native in LabVIEW. Make a new MCLB and right click then go to Drag and Drop, choose to allow dragging and dropping, and you can choose to drag and drop to outside controls if you'd like. Then in Drag Mode, select Move Only (I think this is what you want). EDIT: sorry re-read your post and it is about Columns my answer was to re-arrange rows.

I'm also wondering what controls you're talking about. There are a bunch of things I don't like about Windows 7 (removal of up button, highlight whole row in explorer, unintuitive search, sorting windows constantly) but I didn't find anything wrong with the new controls.

If there is no pop-up asking for a password when you press "CTRL + E" then my guess is they removed the block diagram. In some versions of LabVIEW you could choose to save without block diagrams, but later I think you have to do it through scripting, or a Build Specification in a project. Try opening the VI in another version of LabVIEW. I think you won't be able to open it if there is no block diagram. If this is the case then there is no hope in getting source code out of that file. You'll need to get an original copy or recreate the functionality.

Wow thanks, there are some really neat examples in there. I think alot of engineers struggle with UI design (myself included). This is probably why it is so easy to spot a LabVIEW program from other programs, the controls and indicators tend to look all the same without much effort going into the UI.

Okay a couple things. Regarding your error, I usually see that error when I have MAX running an forgot to stop the task, then run LabVIEW and it can't get a hold of that resource. Not sure if you're familiar with MAX (Measurement & Automation Explorer) but if it's not running then this isn't your problem. Secondly I'm not a big fan of the Express VIs and am not sure how they work. But I believe you can simply get rid of the two express VIs on the left, and replace their output with a string constant (wiring into the DAQmx read), with the name of the virtual channel, or task you want to sample. Obviously the two string constants will need to be different, or else you will try to run the same task twice, and you will get the resource error you have. Also you may want to add a DAQmx Clear operation after each of your Stop operations. Another minor issue I see is you have 2 indicators for each output. You can right click the POT 1 Reading dial and go to Visible Items and choose Digital Display. With this I believe you can get rid of the extra indicators. Have you ran a NI example on your channels? If you go to the Help menu then Find Examples. I'd recommend searching for DAQmx and finding a Continuous Read example then use your virtual channel name (made in MAX) and see if the NI example reads your AI.

Personally I would send the reference to the sub VI and manipulate it there, but there are many ways to do what you want, and I'm not sure what is the most efficient way.

I might be wrong but I think 8.2 was the first to take advantage of multicore PCs and only up to 4 cores. Then in the next major release of LabVIEW they supported more cores, I think 16 or 32, some number much greater than I was concerned with.

I remember someone mentioning a similar problem, where their code was running fine, but a broken arrow in the build. They said the issue was that during the build process it looks at all the VIs that are dependencies and determines if the code is broken. He had a test VI that was broken in a disabled diagram structure, so the code would run just fine in development, but the VI was still a dependency. I hope I'm not re-telling his story wrong but I would suggest searching for the disabled diagram structure and see if there is any broken code in any of them. Just a thought.

Not sure how I missed this thread for so long but yeah I was going to say that with Windows 7, Virtual PC is installed and you can run in XP mode, which is basically a free XP environment that doesn't have any licensing issues. This is convienient because you can copy your virtual hard drive make a new virtual machine, and not have to deal with licensing or network naming conflics as long as you only start one at a time. Don't get me wrong I think I like VMWare more but it's not the standard at my company. Also you should know that there is a free version of VMWare that allows you to create virtual machines, it is VMWare Player. Despite the name you can make virtual machines as well but the motherboard it emulates might not meet all your needs. (ie no USB booting support) The other thing I was going to mention was licensing issues with Windows 7. For that reason I don't know many people here that run a virtual machine of Windows 7 but I know some do. I think we get away with it because of our site license of Windows. Again I'm not in IT but they make it work for us. A good percentage of our customers still prefer XP, so for us it makes sense to have a virtual machine in the same environment.

You know that the Office didn't invent that right? Also when I read the title of the post I imagined someone dying trying to get to lava.

One option is to just have a image constant of your text. Very hack job I know. I did also find this post that shows how to rotate an image, but again I don't think that's what you are going for either but it seemed related to what crelf said about rotating images. http://forums.ni.com/ni/board/message?board.id=170&message.id=491856#M491856

Okay I found a site that helped me kill some time while I was stuck in the airport due to weather yesterday. http://clientsfromhell.net/ It's kinda hit and miss for me some are funny some are lame, and some seem fake but even so I made it through about 30 pages of them. Most are website design, or photoshop related but I think programmers can appreciate them too. Here's a few of my favorites.

I may get excited easily, but that is the coolest thing I've seen today...okay maybe even this week. I want to ask you a bunch more questions but I guess I'll just wait until something is announced or released by NI.

I'm not one to question wikipedia, but I don't believe a Wiimote can detect depth by any means other than looking at how far away the two points are. Maybe that's what they meant. The Wiimote is just an IR camera that can track up to 4 points. I think what it meant by saying it can detect depth, is that if you have two points of light, and you know they are 2 feet, and you know that 2 feet is approximately X number of pixels in the IR camera, then you can calculate how far away you are from the two points of light, by how close the two points of light are away from each other. (hope that makes sense it is kinda wordy) I know that some people use this technique to adjust for their projector which may have the sensor bar farther away than most TVs. The problem is that the two points of light are too close to each other and it has a tough time detecting them independently, so people will make their own sensor bar where the points of light are farther apart, there by allowing them to be farther away from them.

Thanks, I did searching before posting but couldn't find that thread for some reason. I tested it on Windows 7 32 and 64 and it worked as expected.

I did some searching and I couldn't find the function I needed. I wanted to know if my EXE (which was built on 32-bit LabVIEW) is running in a 64 Bit operating system. The Conditional Disabled structure has Bitness, but that reffers to the bitness of the code (is this being built on LabVIEW 32 or 64 bit), not what operating system am I running in. There is also a property node that is Application.TargetOS, but this also only returns the OS it was designed to run on. So I wrote a VI to do this, but I wanted to know if there was a better way, a more native way to tell if the operating system I am running in is 64 bit or 32 bit. Right now it reads the registry, and looks at environment variables which seems cheap to me. I'd like the solution to be universal among all operating systems, but my VI only works on Windows. It has been tested on Windows 7 32-bit, and 64-bit, and Windows XP 32-bit. I'd like to know if there are any issues with it running in XP 64-bit, and Vista 32 and 64. Is OS 64 Bit.vi