Labview 7.0 will not start in Win XP Professional

[Joe W B]

I get the message that it wants to send a message to microsoft. My temp directory was corrupted, but I fixed it. Is there something I can do? I seem unable to delete the corrupted temp directory, but I renamed it and made a new temp directory. Labview does write files to that directory before crashing.

[EdDickens]

Can you give some more details? Does the splash screen show at all? If it does, watch in the lower right corner for the process that's loading. This can give you a clue as to what's causing the problem. The last thing listed there could be the problem.

One common thing that causes LabVIEW to not start is corrupted menu files. If you are using a custom menu setup, try deleting the menuSetup="yourmenuname" key from the .ini file and then start LabVIEW. This will load the default menu and will at least show if that's the problem.

Ed

[Joe W B]

Even the vi will load. Then there is a loooooong pause and it apologises that it has to close labview and will I let it send a report to microsoft. When I look at the report it is essentially a stack dump, but the appname is labview.exe, with an offset of 0004e413. however that might help.

Some of the time I can start my DAQ vi before it aborts, and at least once the vi continued to run and let me record data. Just now it recorded for about a minute then aborted. very frustrating

[EdDickens]

These are the most frustrating to figure out.

If you can get to the diagram without it crashing, start disabling bits of code (put it in a case structure so it won't run). See if you can narrow it down that way. Or make a copy of the app and start deleting sections of code. Sometimes getting rid of the offending code, then re-adding it will fix the problem.

You might try uninstalling and reinstalling NI-DAQ and any other driver sets you have installed one at a time. (reboot after each uninst and reinst) This might take care of it.

If none of that helps, your best bet will be to call NI support and see if they have any suggestions. But they'll probably tell you to uninstall everything related NI and reinstall if it's not a know problem
.

I've been running LabVIEW 7 on XP almost since it was released and have had no real problems.

Good luck and let us know how it goes.

Ed

[Joe W B]

Thanks Ed. I used Labview 6.x (all versions) all the way back to 3. This code has been pretty good through most of those versions (probably since 4). I think the issue is going to turn out to be the crosslinked files on the hard drive. Weird that Labview won't run if it cannot write to the temp directory, doesn't even attempt to write to a different temp directory, just stops. I suspect anyway that the labview errors are mostly unrelated to labview itself. When we get the drive replaced I will know for sure. Thanks again.

Joe

[Peter]

Joe W B wrote in message news:<5065000000080000004FAC0000-1066448259000@exchange.ni.com>...
> I get the message that it wants to send a message to microsoft. My
> temp directory was corrupted, but I fixed it. Is there something I
> can do? I seem unable to delete the corrupted temp directory, but I
> renamed it and made a new temp directory. Labview does write files to
> that directory before crashing.

If you have corruption of your C: drive in XP (or 2000) then you need
to do a "proper" disc repair.

go to start->run and enter "CMD"
In the console window that appears enter
"chkdsk /r"
press "y" to schedule on restart.
now reboot your PC, do NOT press any keys, and wait for the 5 stage
disk check + fix to start.
Go to lunch, it will take a while to c
omplete.

😉

[Joe W B]

We tried to do this repeatedly, but it just crashed over and over during the chkdsk operation. Finally,our guy put in a new 80gig hard drive, I reinstalled everything and fixed the entire problem. Kind of an annoying problem, that Labview seemed to be crashing just because it couldn't write to the default temp directory. Maybe there was more to it than that, but that was how it looked to my eyes. Anyhow, it is over with now.