LabVIEW fails on startup

[easchwarz]

I have installed the lv-7.1 using the install script.  I chose only the defaults.
When I launch LabVIEW, it displays the startup screen (splash) and at the lower right-hand corner, reads :LabVIEW 7.1 -- Init tmp res files
it hangs there and closes.  The program does not show any activity and the bottom right corner doesn't change.

The splash if it loses focus, will not redraw.

I checked the /tmp/ directory and found a log file (since this is the default location for my temp files)
This is current file "labview_7.1_eric2_cur.txt"
This is repeated (without the "**" headers) some 60+ times

####
#Date: Thu, Jul 21, 2005 10:14:13 AM
#OSName: Linux
#OSVers: 2.6.11-1.35_FC3
#AppName: labview
#Version: 7.1
#AppKind: FDS



filemgr.cpp(6010) : DWarn: path name exceeds maximum length of 4095 characters
$Id: //labview/branches/Mercury/dev/source/manager/filemgr.cpp#13 $
0x081D9DB3 - <unknown> + 0
0x081D974C - _Z9FListDir2PP6Path_tPP5CPStrPP10FMFileTypei + 26C
0x086A5996 - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0
0x086A5A8E - <unknown> + 0

[EdDickens]

The first thing I'd try would be to reboot, then delete everything in your system 'temp' directory and try again.

It's kind of a long shot but worth a try.

Ed

[vix]

Hi,
I found the same problem after installation of LabVIEW 6.1 on Fedora Core 5-
I used LV 6.1 under Fedore Core 3 for a long time without any problem.
Unfortunately Ed's suggestion hasn't been helpful.

This is my LabVIEW_Failure_log.root.txt

####
#Date: mar, ott 02, 2007 06:09:23
#Desc: Failure : "filemgr.cpp", line 4145
LabVIEW version 6.1
For assistance in resolving this problem, please record the preceding information and navigate to www.ni.com/failure, or contact National Instruments.
#RCS: $Id: //labview/dev/mgsource/filemgr.cpp#80 $
#OSName: Linux
#OSVers: 2.6.18-1.2798.fc6
#AppName: labview
#AppKind: FDS
0x0815E31A - <unknown> + 0
0x0815DDDE - FListDir2 + 252
0x083D07D2 - SyncDirectory__19EditablePaletteMenuP8BaseMenuPP6 + 162
0x083CC71F - MarkSyncSubmenu__19EditablePaletteMenuP8BaseMenui + 263
0x083CB437 - LinkToDirectory__19EditablePaletteMenuP8BaseMenui + D7
0x083D0D98 - SyncDirectory__19EditablePaletteMenuP8BaseMenuPP6 + 728
0x083CC71F - MarkSyncSubmenu__19EditablePaletteMenuP8BaseMenui + 263
0x083CB437 - LinkToDirectory__19EditablePaletteMenuP8BaseMenui + D7
0x083D0D98 - SyncDirectory__19EditablePaletteMenuP8BaseMenuPP6 + 728
0x083CC71F - MarkSyncSubmenu__19EditablePaletteMenuP8BaseMenui + 263
0x083CB437 - LinkToDirectory__19EditablePaletteMenuP8BaseMenui + D7
0x083D0D98 - SyncDirectory__19EditablePaletteMenuP8BaseMenuPP6 + 728
0x083CC71F - MarkSyncSubmenu__19EditablePaletteMenuP8BaseMenui + 263
0x083CB437 - LinkToDirectory__19EditablePaletteMenuP8BaseMenui + D7
0x083D0D98 - SyncDirectory__19EditablePaletteMenuP8BaseMenuPP6 + 728

In /tmp/ folder there are also a series of lvtlXXXX.rsc files (XXXX are numbers). If I try to open these files I saw the message that they are binary files

Could someone help me?

[Jason_Whaylen]

Vix,

In looking into what is going on here, the problem seems to arise purely from the upgrade from Fedora Core 3 to Fedora Core 5.  Due to the fact that these are open source operating systems, there is no way for us to continually monitor compatibility and functionality.  Unfortunately, this is unsupported by NI, and the only suggestions I can provide on this situation is to revert back to the working configuration or to reference another source where there are Linux experts.  Sorry for the lack of specific suggestions.

Regards,

Jason W.

[vix]

Hi Jason.

I've done other tests and I found the same problem with SUSE 10.2 and labview 6.1. And Suse is one of the NI supported distros.. I think

I've successfully been able to run labview 6.1 in SUSE 10.1 on an old PC; on my old PC I tested Fedora Core 3, and labview 6.1 worked fine.
But the motherboard of my PC has broken fortunately I saved the hard disk, but now I have a new machine (Pentium 4 HT).
I tried to install Suse 10.0 but It has been impossible (wrong processor recognition). I searched on the web and I found I had to use Suse 10.2.
The OS and LabVIEW installation were OK, but when I launch LabVIEW 6.1 the splah screen hangs with the message "Init menus"
If I launch LV from terminal I can see the error in filemgr.cpp line 4145

Could you help me?

[Jason_Whaylen]

Hey Vix!

I see why you are going about this in this way.  It's never fun to deal with losing your motherboard, but hopefully we can get this working for you.  I am not particularly familiar with using these versions of LabVIEW with your OS.  What I have found is an article from within our documentation that explains which versions of LabVIEW are compatible with various Linux Distributions.  This can be referenced here. 

This table does not reference the LabVIEW versions as far back as in this situation, but the trend would appear that this version is not directly compatible.  The suggestion I can provide is to refer to the installations that are mentioned at the bottom.  If I am reading it correctly, one of the bottom two would refer to what is being used in this application.  These files can be referenced by going to Drivers and Updates. 

I hope this helps.  If not be sure to let me know!

Thanks,

Jason W.

[vix]

I've successfully installed NI-KAL 1.6 following the instructions, but unfortunately labVIEW still doesn't start....
There's still the same internal error during startup

[vix]

At last I solved my problem!!!!

Thanks to Duffey's suggestion in this thread,

---

Mandrake (and Fedora Core 2, FC2) are using a new directory indexing feature on filesystems. This causes "." and ".." not always to be listed first, and LabVIEW currently relies on this behaviour (you can see this by doing ls -af in a directory).

Fortunately, you can turn it off for the time being (there is no loss in features). On all of your ext3 partitions, you'll want to run (as root):

tune2fs -O ^dir_index /dev/yourpartition

---

also for SUSE is the same!

I hope this can help other guys...