Leaderboard

How about this?

&x is the address of x (type *) is a coercion to pointer to type * is dereferencing value at x treated as type.

Of course if you append the checksum to the string and run it through the same code you'll see it's purpose. To save the trouble in this case you only have to figure out what x XOR x is.

LabVIEW is known to be a little greedy when it comes to file locks. For example: Cannot move or delete folder while LabVIEW is open. I use the utility Unlocker for deal with locking issues in general. As usual, the wise rolfk presents a Windows API-based solution using SetCurrentDirectory(), if you're up for it.

http://www.eaipatterns.com/docs/IEEE_Software_Design_2PC.pdf

I hate it when mom and dad fight...

OK - I tried both solutions - the Unlocker is ok but its not a solution for a program which i develope to someone else use.. the other solution is nice - I implemented it and the only disadvantage of this solution is that for unlocking one folder you need to lock other and in this case i choose c:\windows - but it means that each time you use a common dialog file box in you program - the deafaut location will be c:\windows... Thanks again! LabVIEW Folder Unlocker.vi

I'm not sure why you'd do that, but it makes sense. Think of the difference between the integer word length and the word length as the power of 2 that a single bit represents. If your word length and your integer word length are both the same, that difference is 0, and a single bit represents 2^0=1 (a fixed-point value with an integer length equal to word length has no fractional portion). If the integer word length is 6 and the word length is 8, a single bit is 2^(6-8) = 2^(-2) = 0.25. In your case, you have an integer word length of 2 and a word length of 1, so a single bit represents 2^(2-1) = 2^1 = 2, which matches what LabVIEW is telling you: the number has 1 bit, which represents either 0 or 2.

Change the calling convention to stdcall (WINAPI).