tetrarch

F) other - the desktop is never visible long enough to see any icons And although it's not directly relevant, with coLinux and cygwin there's a free alternative to VMware if you want to get Windows / Linux LV sessions running side-by-side. Best of both worlds: all the ease-of-use that Linux provides, combined with the legendary stability of Windows!

Okay, looks like you may be missing some of the development packages. Try this: dpkg-query -s libc6-dev and if you don't get something like this: Package: libc6-devStatus: install ok installed then you're missing the C library development package, which means you need to install it using this: apt-get install libc6-dev If that doesn't fix it, let me know.

That's usually caused by not having a dev package installed - ld (the linker) is being called without a path set correctly, or with a missing file (crti.o, one of the basic C runtime object files). To properly help, it'd be useful to know the following details: * Labview version * Linux distribution (Redhat, Debian, Slackware, etc) * Command you use to make the LSB file * The output of the "uname -a" command since Linux can come in many different shapes and forms. cheers, Tom

The wait function will normally happen in parallel with the rest of the code, so if you have something that takes more than the 10ms, there won't be a problem, and if it takes less than 10ms, it'll free up some time for the rest of the system to do its thing. Putting a wait in the main loop is generally a good idea.

Standard Linux distributions come with the GNU compiler, which can handle C, C++, Java and a few other options as well. Usually something like: g++ -Wall -olibrary.o -c library.cpp will create an object file from a C++ source file. C is a "subset" of C++, much of the basic syntax is similar however C has no support for classes, overloading or the OO side of the code, so rewriting good C++ code in C is usually very timeconsuming, and in this case, there's no need. Make sure any functions that need to be called from LabView are exported with: extern "C" {...function prototypes...} and you should then be able to use CINs to access C++ functions. The guide in the Labview bookshelf has more details on compiling - where it talks about C, C++ works just as well. As a last resort, you could consider copying and pasting the code into a formula node...

No, the Linux and Windows versions are very different. You'd need to buy the Linux edition separately or contact NI directly about it. NI Linux page Installation under Linux is straightforward enough (run one of the programs on the CD).

Dependency Walker might be useful here. It'll help you find most, if not all, the DLLs required. You may also need to run regsvr.exe XXX.dll for each one, depending on whether it's COM or just a library.

or if you have event support, create an event structure to handle "mouse down" or "mouse up" events for the existing LED.

Plenty of links here. Some of them might even still work... you might want to read up about OO design methodologies and UML notation, if any of it is unfamiliar.

NtQuerySystemInformation used to be the popular way of getting the right information. MS now recommend using other functions though (linked on the same page). Not sure how easier it's going to be to get LabView to handle the datatypes... This CodeProject page might also be of some assistance. Another approach which may or may not be better is to use the PDH.DLL (Performance Data Helper) functions. Can't remember what the general availability is (might need to distribute the DLL with your app?). They query the performance counters, which are sorta designed for this task, so they might be the best bet. cheers, Tom

Here's an "all-round general" VI for CRC calculation. The polynomial needs to be translated from equation form into numeric representation - one bit per power of X. In your case: x^16 + x^15 + x^2 + 1 so that's something like 1 1000 0000 0000 0101 in binary (or 18005 hex). No guarantees that this works (I put it together a while ago for a quick data check, and didn't need it to conform exactly to the CRC standards), but it should give you a starting point. Search for "CRC polynomial" and you should be able to get more information about how things are calculated. PS. Many CRC implementations also have a starting value (often 0xFFFF for 16-bit, or 0xFFFFFFFF for 32-bit) and a final XOR value (again, 0xFFFF is common). Download File:post-607-1103278851.vi