Ulrich

Hello crelf, sorry for the late response but on friday I wasn't online anymore. You're right, there are many possible reasons for that. We use some dlls in Sub VIs (e.g. Hostname.dll to get the PC name). Communication and data acquiring goes over the GPIB Bus (with VISA). The code is very large (300 VIs). When we get the blue screen only the main VI was running. This is not more than a main menu, waiting which Sub VI the user is choosing. The block diagram of that is posted. We are doing more tests to figure out the problem. Over the weekend the PC was logged on "local" and there was no blue screen. But normally we need to log on to our network domain. Right at the moment it looks like the problem is home-made. Many Thanks Ulrich

Hello, at work we have a mysterious but big problem. We have measurement devices (=prober) controlled by a PC. On this PC we also have our LV executables. With Win 2000 an Win NT everthing's fine. With Win XP the PC hangs up with a "blue screen". We already get a second PC, also with "blue screen". We tried LV executables Version 7.1 and 8.01, both with "blue screen". We started the prober control SW and our LV exe. Both running but doing nothing (just in a idle state). We get the "blue screen". It looks like a combination of LV exe, prober software and XP. We never had this problem with Win NT or Win 2000 and the same prober software and LV exe. Have anyone out there similar problems and can give us a hint? :headbang: many thanks in advance and have a nice weekend Ulrich

Hello, When I run this VI, I get one hour difference, from 1:00:00 AM 1/1/1970 to 2:00:00 AM 1/1/1970. My PC has the GMT+1 timezone (I've tried other timezones with the same result) Have a nice day Ulrich

Hi, If you chance the value of the element from the initialize array it starts from the begining. Change the Indicator "initialized array" into a control instead of the initialize array the VI will work fine. very strange. Uli

My favorite is a file dialog where the user can only search in specified directories. So he can't do anything wrong. See you Ulrich Download File:post-3940-1143805352.zip

Hello, I have the same problem, but unfortunately no idea. have a nice day Ulrich

Hello, I've seen many errors in Labview. But this one is new to me. See you Ulrich

Hello all, a colleague of mine found a solution for the problem. He took the lvanlys.dll from LV6.1 and everything is working fine again. have a nice day Ulrich :thumbup:

Hello all together, With LV 7.1 I didn't had this problem. There it was enough to copy the LV run time files to the PC. Actually I have 4 programs as LV8.0 EXE files. 3 of them are running (they don't use this dll) with only copying the run time files. NI recommended to make an installer. With this installer also the program with the dll is running. Unfortunately I have to install everything (also programs I'm not using). LV runtime, MAX, NI488.2, NI Visa, NI Spy. (I need the lvanlys.dll also for linear fit, so I have to use this dll) thanks for your help Ulrich

Hello, I made an .exe file in LV8.0 (PDS). On the PC where LV is installed the programm is running. On another PC without LV, the .exe file will not start because of "lvanlys.dll is an forbidden Labview file" (needed in mean.vi). The lvanlys.dll is in the same directory as on my "Labview" PC. Can anyone help me with this??? Many thanks in advance Ulrich