08-10-2009 01:23 PM
Solved! Go to Solution.
08-10-2009 02:09 PM
08-10-2009 02:40 PM
08-10-2009 03:09 PM
Thank, I will take care of this details. But, unfortunly, this not working.
uint32_t SystemParametersInfoA(uint32_t SPI, uint32_t 0, uint32_t *value, uint32_t False);
SPI = 114 = SPI_GETSCREENSAVERRUNNING
If *value != 0, screensaver ON, else scresaver OFF
Still have the fatal Windows error.
Thank
08-10-2009 05:00 PM
08-11-2009 01:52 AM
CFiset wrote:Thank, I will take care of this details. But, unfortunly, this not working.
uint32_t SystemParametersInfoA(uint32_t SPI, uint32_t 0, uint32_t *value, uint32_t False);
SPI = 114 = SPI_GETSCREENSAVERRUNNING
If *value != 0, screensaver ON, else scresaver OFF
Still have the fatal Windows error.
Thank
I noticed the Call Library Node having a rather strange path to user32.dll on the initial load. Do you happen to have copied that DLL somewhere and referencing it with full path in your VI?
That is a very big NO-NO! user32.dll and many other Windows system DLLs do weird things to the system and are utterly bad behavioured if you try to load another copy from somewhere else on disk than the system directory. Just change the library name to user32.dll only and let Windows pick the right DLL from its system directory.
Another problem with specifying the full path to a copy of such a DLL is that LabVIEW will think you need to have this specific DLL in a built application and will include it in the build. However your user32.dll is almost 200% VERY incompatible to just about any other Windows system out there, because of Windows version, Service Pack, and bug fix upgrades as well as different language versions of Windows.
Rolf Kalbermatter
08-11-2009 06:09 AM - edited 08-11-2009 06:12 AM
Thank rolfk,
I just change the path from C:\Windows\System32\user32.dll to user32.dll. This work great.
Problem solved
Thank rolfk and smercurio_fc
08-11-2009 08:45 AM
rolfk wrote:I noticed the Call Library Node having a rather strange path to user32.dll on the initial load. Do you happen to have copied that DLL somewhere and referencing it with full path in your VI?
You know, I had seen the same thing but didn't think twice about it. I had thought it might have occurred when the VI was saved, or if the user was running a different OS, like Vista, or 7. Should've remembered we're talking about Windows here.
06-25-2015 07:26 PM
Hi.
I am kinda new to Labview and I had this problem while changing from version 2012 in my laptop to another PC with 2014. I attached the VI.
My problem relays on the access violation related to the user32.dll. I can't find where to change the path to user32.dll or %windir%\System32\user32.dll as this knowledgebase (http://digital.ni.com/public.nsf/allkb/CE69D2C55480900486257B6A0037C327) sugests since I am not using a call library function node directly.
I use the modules Mathscript RT and Control Design & Simulation. I also use VISA to comunicate with an Arduino via simple protocol I made.
My program runs flawlessly on my laptop but when I try to use it in the other computer it crashes 10 sec after it starts.
Some of the debugging I´ve made is to deattach my "Power Interface Circuit" to control a DC motor from the Arduino and this doesn´t seem to change anything.
I would appreciate your help. Many thanks.