Windows SDK SetTimer() and Runtime Engine

Does anybody knows what happens in the CVI RTE when you call the WIN32 SDK
function SetTimer and start the LW RTE with RunUserInterface. We have
In our application we use the SDK function SetTimer to create a timer with
an intervall of 10ms. Even if the Timer callback function is empty the CPU
usage climbs up to about 55% when starting the CVI user interface. Other
processes and threads have about 40% longer runtimes as before starting the
user interface.
For testing we wrote the following short code.
SetSleepPolicy (VAL_SLEEP_MORE);
TimeIdent=SetTimer(NULL,0,10,TimerProc);
RunUserInterface ();
Has anybody experienced a similar problem.
IVM Automotive
Michael Koch & Stefan Urich

I'll go see you in a minute..

Similar Messages

Make the installer for my executable run the DAqcarddriver and runtime engine installer automatically

*Hi
I would like to know how to make the installer for my executable run the DAqcarddriver and runtime engine installer automatically
I would like to include run time engine and the drivers of my daqcard(AI16XE50),( and maybe Ni daq or anything else needed?) in order to make my application portable for other computers on OS win98 and winXP .
How can I do that
thank you in advance
Olivier

Olivier,
What version of LabVIEW are you using to build your application? On a remote computer you should only need the drivers you are using and the Run-Time Engine. You can attach installers to LabVIEW 8 installers, but for previous versions you will have to add it by opening the installer configuration page, configuring your installer and then configure the Advanced properties. This will allow you to attach a EXE to the installer which you can run. Also depending on the version of LabVIEW will affect the OS version that you will be able to install the RTE on. LabVIEW 7.0 is the last version that can be installed on Windows 98.
Please let me know if you have any further questions and please include the version of LabVIEW you are using. Thanks!
Andy F.
National Instruments

I went to download the latest i Tunes update but somehow it went wrong and I ended up removing i Tunes from my system and re installing it but I can't get it to reinstall. I keep getting error massages Error 7(windows error 1114) and runtime error R6034,

I attempted to download the latest i Tunes update but somehow it all went wrong and I have ended up trying to reinstall iTunes but it does not work. I keep getting error messages-Error 7 (windows error 1114) and Runtime error-" R6034 an application has attempted to to load the runtime library incorrectly". Help what do I do now?

Hello there, tulchan.
The following Knowledge Base article addresses the very issue you're describing:
iTunes 11.1.4 for Windows: Unable to install or open
http://support.apple.com/kb/TS5376
Check for .dll files
Go to C:\Program Files (x86)\iTunes and C:\Program Files\iTunes and look for .dll files.
If you find QTMovie.DLL, or any other .dll files, move them to the desktop.
Reboot your computer.
Note: Depending on your operating system, you may only have one of the listed paths.
Uninstall and reinstall iTunes
Uninstall iTunes and all of its related components.
Reboot your computer. If you can't uninstall a piece of Apple software, try using the Microsoft Program Install and Uninstall Utility.
Re-download and reinstall iTunes 11.1.4.
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

Exe in french and runtime engine in english can it run?

exe in french and runtime engine in english
also max version is english
can it run successfully?

Hello,
You can build your executable with the french version of LabVIEW and run your executable with the english Run-Time Engine. However, note that strings in menus (such as File, Edit, Project, Help, and so on) and pop-up menus depend upon the version of the LabVIEW Run-Time Engine you are using with the executable. If you use the english Run-Time Engine, the menus always appear in english, regardless of the language of your operating system.
Also, note that for standard dialog boxes, LabVIEW uses strings (such as Open, Close, Save, and so on) that are specific to the operating system. Some dialogs contain LabVIEW specific strings (for example, Select Cur Dir), which LabVIEW displays in french, german, or japanese, according to the operating system's regional settings.
So if you need french menus and LabVIEW resources in your executable, use the french version of the Run-Time Engine available here.
Good luck and have a nice day!
Shakhina P.
Applications Engineer
National Instruments

Simple: dll and runtime engine

Do I need the LV runtime engine to be installed on the machine to access the functions from the .dll file built out from the LV project?
Solved!
Go to Solution.

Simple: Yes. And you will need the "correct" version!
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Just tried to install update to iTunes and keep getting error statements. The errors statements read: "iTunes was not installed correctly. Please reinstall iTunes. Error 7 (Windows error 1114) and Runtime error - Program: C\Program files (x86)\iTunes\iTun

I just tried to install the iTunes update 11.4.1 and keep getting error messages. I have never had this issue before over many years of using iTunes and getting updates to the software. I have removed the iTunes from my computer and reinstalled it but keep getting the errors. Here are the error statements: "Runtime error: Program: C:\Program Files(x86)\iTunes\iTunes.exe; R6034; An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team. iTunes was not installed correctly. Please reinstall iTunes. Error 7 (Windows error 1114)

Follow the instructions of tt2 in https://discussions.apple.com/thread/5822086 and note to run as admin

Windows Media Player and audio engine behavior

I have made one LFX and one GFX module both residing in the same dll.
I have noticed some strange behavior with windows media player which I don't understand.
When playing back audio with WMP there are always two processes (image names) that loads my dll with APOs. One process called audiodg.exe and one called svchost.exe. My understanding is that my APOs would be loaded only by the audio engine which I belief
is found in audiodg.exe.
Is there any explanation of why WMP causes my APO dll to be loaded by two different modules (image names) at the same time?
One of the reasons I'm asking is that I have problems getting my APOs working correctly with the tidal web player (tidal.com). I'm not sure what the problem is but I can see that my APO dll is loaded by two different modules (image names) at the same time,
just like WMP.
Thomas BE

The "Windows Audio service" svchost.exe process is always running; you can check its current state via the "sc query audiosrv" command.
>sc query audiosrv
SERVICE_NAME: audiosrv
        TYPE               : 20 WIN32_SHARE_PROCESS
        STATE              : 4 RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
When someone calls IAudioClient::IsFormatSupported(...), your SFX is loaded into audiosrv to answer the query. Some media players call this, and some don't.
When audio actually plays, audiosrv launches audiodg.exe. audiodg.exe builds the full audio pipeline from app to driver, including all of your APOs.
Some time after audio stops playing, audiodg.exe shuts itself down.
Matthew van Eerde

"runtime engine" crash

I have a problem with a LabView executable compiled for LV 6.1: it works without problem on a PC which has just LV Runtime Engine 6.1 installed, but it crashes (without error message) on a different machine that has a full installation of LV 8.5 and Runtime Engines 8.5, 8.2, 8.0, 7.1, 7.0 and 6.1. On this 2nd machine I installed Runtime Engine 6.1 last, because I got the error message about the missing engine when I tried to run the executable in question. After having installed the Runtime Engine, I no longer get the error message, but after a brief moment (before the first GUI opens) the executable crashes quietly. Any suggestions on how to solve this issue (rebooting the PC didn't solve it BTW)? According to the information I found so far on the NI website, Runtime Engines of different LV versions are supposed to run in parallel without problem.
As for my config: MS Windows 2003, Standard Edition, SP2
Solved!
Go to Solution.

Matthias,
then i fear that you are running into compatibility issues with the OS. Windows Server 2003 was never tested with any LV Version.
Reading the ReadMe from LV 8.6 it states:
LabVIEW supports Windows Vista/XP/2000. LabVIEW does not support Windows NT/Me/98/95, any of the Windows Server editions, or Windows XP x64. LabVIEW does support Windows Vista x64.
Since your system runs on Windows Server 2003 (since you didn't answer my questionmark in the last post, i think that is a fact) you are lucky that the newer application runs.
Please note that "not supported" means: it was never tested and therefore it might work, but if not, NI does not supply any support.
So the only solution to your issue is to switch to an OS which LV RTE 6.1 was tested on; the newest OS i think was tested (although not sure) is Windows XP.
hope this helps,
Norbert
Message Edited by Norbert B on 03-05-2009 06:48 AM
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Runtime Engine 6 and Windows XP

Hi all,
Ok, I created a vi in Labview 6.0i and compliled it. Installed Runtime
Engine 6 on an XP machine where I want to run the VI. The problme I'm
having is that the VI starts, but doesn;t seem to communicate with my
instruments on the GPIB bus. This vi runs fine on a Windows 2000
machine. Any Ideas?
Thanks
Andrew

I'll go see you in a minute..

Several question s about runtime Engine, application builder and labview player

I am a little confused by all the options to distribute a program.
Please help bij answering (one of) the following questions:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
3. What is the advantage of the labview player above the runtime Engine?
All questions refer to the latest software versions of NI software
Thanks in advance,
Regards,
Ferry

ferry1979 wrote:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
(In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
(Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
No. See above.
3. What is the advantage of the labview player above the runtime Engine?
The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
Message Edited by altenbach on 08-21-2005 10:05 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
runtime.png ‏24 KB

Installing LabView 8.2 runtime engine on Windows 7 64-bit

We have a product built on LabView 8.2
For a couple of years, we have been distributing this product on Windows 7 64-bit systems with no trouble at all.
Today, we received a customer complaint indicating that the LabView 8.2 runtime engine cannot be installed on Windows 7 64-bit.
Our verification team has confirmed this to be true.
Interestingly, we have several Windows 7 64-bit computers with the LabView 8.2 runtime engine already installed.
How is this possible?
Has something changed in Windows that no longer allows the LabView 8.2 runtime engine?
We are confused by the fact that this appears to be a new problem and the runtime engine did, at some point, install correctly on multiple Windows 7 64-bti computers.
Any thoughts would be extremely appreciated.
Attachments:
lv_install_error.jpg ‏22 KB

No, i dont think the 8.2 installer is corrupt, but it uses the Windows Installer service, which according the image has some problems. Maybe it recently updated? It's incompatible with that old installer so you need to downgrade it? It's corrupted and needs some fix?
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

LabVIEW Runtime engine on Windows Embedded Standard 7 P 32/64 bit?

Did anyone ever try to install and run LabVIEW Runtime engine (2011 or later) on Windows Embedded Standard 7 P 32/64 bit?
I am trying to figure out if this will work, for example on a Beckhoff CX5120 embedded PC. I will need to have some simple TCP/IP communication in order to exchange information with another PC, but nothing else, i.e. drivers, etc...
I hope someone tried to do this already. I just don't have the right hardware right now to check it out.
Solved!
Go to Solution.

As NI sells touch panels with WES7 installed here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/210551 it's pretty safe to assume they've used the RTE on WES7.
But yes, it's been done.

Cannot load Runtime engine verion 7.0, only 8.0 and later versions are supported

Hi,
I am new to using third party labview drivers. I have a labview driver for Chroma 63600 loads that I want to use in TestStand 2012.
However when I load the vi. I get an error 'cannot load Runtime engine verion 7.0, only 8.0 and later versions are supported'
I have Labview Runtime Engine version 7.0 Installed on my Windows 7 machine.
Could anyone please let me know, How I could resolve this issue?
Please see attached driver for Chroma Loads
Solved!
Go to Solution.
Attachments:
chr63600_LabView_V11.zip ‏866 KB

To avoid more confuison,Here is the scenario,
The version that was on the driver attached is from the driver manufacturer.
I do not have any version of labview INSTALLED on my system. I am using the driver in Test Stand 2012 using a labview adapter.
I make sure I match the VI version and the run time engine version on TestStand 2012 to load the VI.
But for this specific driver, I was not successful in loading the VI at all.
As I understood that only 8.0 OR LATER are supported on TS 2012, I have asked to upconvert the driver to work with 8.2.1 Labview runtime engine.
I have now got a.LLB file of the driver mass compiled in Labview 2012 from discussion boards( and also attached here). I have tried the mass compiled LLB file on TS2012 but still have issues loading the VI as it moans about different version of SUB VIs.
However I am still trying to fix this version incomaptibilies. Any help would be much appreciated

USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

Hello all,
I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
What has happened is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
I've installed on different computers (without previous labview installs) with the installer. They all worked.
The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
They say the COM ports aren't even showing up when they run the installed application.
So, I'm not sure where to start. Is this a driver issue? Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
Thank you in advance,
cayenne

The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Windows Runtime Engine

Hi,
running a job using Windows Runtime Engine and a script in VBScript will cause no action, in job log and system log no entry. It seems this runtime is not working.
The dispatcher is configured and running. All jobs with java runtime engine are running properly.
Any ideas what needs to be configured?
Thanks for replies

Hi Ralf,
could you please provide more information: Do you try to test-run the job?
I remember having had this problem, too.
I think I solved it by reading the error messages in the DOS prompt when starting a test.

Windows SDK SetTimer() and Runtime Engine

Similar Messages

Maybe you are looking for