Leaderboard

The likely reason why it's not working is that you're probably using 32-bit LabVIEW, but running on a 64-bit OS. Windows is not allowing you to call the osk.exe that it comes with since it's 64-bit. When you copied the osk.exe from Windows XP you copied the 32-bit version, and that's why it worked. If you were running LabVIEW 64-bit you wouldn't have an issue. You could try to use the Wow64DisableWow64FsRedirection function (http://msdn.microsof...v=vs.85%29.aspx) but I've never done this myself. Follow-up: Attached is a LV2009 VI that you can try. Note that the VI is configured to run in the UI thread. I have the 32-bit version of LV2009 and am running Win 7 64-bit and this VI launched the on-screen keyboard. EDIT: I made a wiring error on my previous upload. run osk.vi

Dear OpenG and LAVA Communities, I’m happy to announce that the OpenG 4.0 release is now available for download. OpenG 4.0 is a synchronised release of all packages that form the OpenG Library: The release includes the following features: Fix to all outstanding bugs (at design time). Package sources upgraded to, and tested in, LabVIEW 2009. Packages now built using VIPM 2010. I will be posting more about this release in the near future. On behalf of Jim Kring and OpenG.org, thank you. Jonathon Green OpenG Developer Installation Open up VIPM 2010 and if not configured to do so press Check All Package Repositories for Available Packages, then choose one of the two options below: Install the OpenG Toolkit package - this package will configure your system to install all the latest packages as well as remove any non-Library packages no longer required (don’t worry it won’t remove any VIs you are using). This is recommended for new or basic users. Manual installation - upgrade required packages on a package-per-package basis. Note: OpenG Builder is not part of the OpenG Toolkit and therefore will need to be manually upgraded (if required).