Installing LabView 6.1 Runtime on Win 7 64 bit

[hants1984]

LV 6.1 and LV 8.5 both have "Simple Error handler" and "General Error Handler" but those are not same. "Simple Error handler" calls "General Error Handler" where lies the problem.

If I load a LV6.1 based program on LV8.5 and then try to go to the root of broken arrow, I come to a point where "General Error Handler" source show another vi used inside it Error Database.vi (or, somthing like that, I don't have exact information right now, the icon is pink and blue). whereas if I start a fresh LV8.5 program and call "General Error Handler" the icon inside the source looks same as "General Error Handler" with black background (instead of error database). I am not talking about custom vi. Frankly speaking NI should use different named function at the first palce when introduced something different.

I came to this forum just to know, whether I can install LabView 6.1 Runtime Engine(not program) in Win 7 64 bit (let forget about my application). If the official answer is yes then there might be other problem with PC setting or, something else. Perhaps you could direct me some official answer. By searching vast information I can't get any absolute answer yet.

[hants1984]

"For the sake of the post, this information is available here.  You can open LV 6.1 VIs in LV 2011."

Thanks Oli.P, the compatibility information is clear enough. I shall try to make my application compatible to LV8.5.1 first (which is the latest I have) then see whether It run in Win 7 (64 bit). 

Regards

[smercurio_fc]

---

hants1984 wrote:If I load a LV6.1 based program on LV8.5 and then try to go to the root of broken arrow, I come to a point where "General Error Handler" source show another vi used inside it Error Database.vi (or, somthing like that, I don't have exact information right now, the icon is pink and blue). whereas if I start a fresh LV8.5 program and call "General Error Handler" the icon inside the source looks same as "General Error Handler" with black background (instead of error database). I am not talking about custom vi. Frankly speaking NI should use different named function at the first palce when introduced something different.

---

I don't have access to LabVIEW 6.1, as it is on my work machine, so I can't verify what you are saying. However, I can say that I have never seen the issue you are referring to, and I've upgraded many VIs from old versions of LabVIEW to newer versions. Note: I am NOT saying you're lying, and I'm sure you have the problem - I just can't give you a reason for it since I cannot access my installation of LabVIEW 6.1.

---

I came to this forum just to know, whether I can install LabView 6.1 Runtime Engine(not program) in Win 7 64 bit (let forget about my application). If the official answer is yes then there might be other problem with PC setting or, something else. Perhaps you could direct me some official answer. By searching vast information I can't get any absolute answer yet.

---

The only "official" answer you will find is that it is not supported. Any methods of installations are things that people have tried (and have been discussed many times before in this forum). Some work, some don't. And those that do work sometimes don't work under other conditions (such as specific hardware drivers, or video, or mouse, or something else). NI cannot and will not "officially" support any kind of installation of LabVIEW 6.1 under Windows 7, 64-bit. This would mean that they would have to expend the resources to test it under many different conditions, and they simply are not going to spend the effort on something so obsolete.

Bottom line: there is no official method for installng LabVIEW 6.1 (either the development, or the run-time engine) on Windows 7 64-bit. I don't know how it can be said any more clear than that.

[hnats1984]

"However, I can say that I have never seen the issue you are referring to, and I've upgraded many VIs from old versions of LabVIEW to newer versions. Note: I am NOT saying you're lying, and I'm sure you have the problem - I just can't give you a reason for it"

I must admit the way you are talking (mainly previous response) is not seems right to me. Software Knight should be more sensible, not buldoze with a sword and horse.

Attached are the two snap shots of General Error Handler.vi. One used Error Code Database.vi and other used General Error Handler Core.vi. BTW, I uderstand the issue now and solved it. My application is now LV8.5 compatible. I just made the installer and will try in Win 7 64 bit sometime today. I included 8.5 runtime engine with the installer.

Thanks for all your time.

[smercurio_fc]

---

@hnats1984 wrote:

"However, I can say that I have never seen the issue you are referring to, and I've upgraded many VIs from old versions of LabVIEW to newer versions. Note: I am NOT saying you're lying, and I'm sure you have the problem - I just can't give you a reason for it"

I must admit the way you are talking (mainly previous response) is not seems right to me. Software Knight should be more sensible, not buldoze with a sword and horse.

---

More sensible than repeating what has already been repeated countless times? You keep asking about how to run older versions of LabVIEW on Windows 7 64-bit. I point out several times that this question has been asked numerous times and answered numerous times. And yet you come back asking whether there's an "official" method to install LabVIEW 6.1 on Windows 7 64-bit. There is NO official method. Is that sensible enough?

And I will repeat what I said: Unless someone else can replicate what you are saying regarding the general error handler, then the sensible conclusion to draw is that the problem is at your end. I can create (and did so) a VI in LabVIEW 6.1 that uses the GEH and I can load it just fine, without broken arrows, in LabVIEW 8.2, 8.6, 2009, 2010, and 2011. QED.

You claim that you understand what the issue is. I don't suppose you'd mind sharing it with the class?

[hnats1984]

Thanks, but you havn't commented on the snap shot of GEH.vi I posted. I found another forum post have same problem as me, "Vi not running when using NI´s SiimpleErr​orHandler.​vi (TS2010/LV​2011) in runtime - Windows 7"

I sorted the problem after realizing all our application is in LLB and it's keeping a copy of Old GEH.vi, SEH.vi. I deleted those from LLB and picked GEH.vi from Controls Palette and solves the issue.

Now, I have problem creating a installer in LV8.5, it was created but when I tried to run it pop up with lot of error messages related to NI LV and says it can't find it. During creation of Installer I select to add LV RTE. I attached 3 pictures, total 9 error messages. To send to customer I need to understand it and create it.

For the time being I decided to install LVRTE 8.5 from web and create an Application.exe. But after I press build, it starts working, then a message pop-up, "GOOP Object Repository.vi is password protected. Enter the password to access block diagram". Any idea about this. I don't know any password.

[smercurio_fc]

---

@hnats1984 wrote:

Thanks, but you havn't commented on the snap shot of GEH.vi I posted. I found another forum post have same problem as me, "Vi not running when using NI´s SiimpleErr​orHandler.​vi (TS2010/LV​2011) in runtime - Windows 7"

I sorted the problem after realizing all our application is in LLB and it's keeping a copy of Old GEH.vi, SEH.vi. I deleted those from LLB and picked GEH.vi from Controls Palette and solves the issue.

---

What exactly did you want me to comment on? It's irrelevant what was in the old code vs what's in the newer version. Obviously, the code is likely to be different as better ways are found to do certain things. In your case, though, you broke a cardinal rule: never include VIs from LabVIEW's <vi.lib> directory in LLBs.

---

Now, I have problem creating a installer in LV8.5, it was created but when I tried to run it pop up with lot of error messages related to NI LV and says it can't find it. During creation of Installer I select to add LV RTE. I attached 3 pictures, total 9 error messages. To send to customer I need to understand it and create it.

For the time being I decided to install LVRTE 8.5 from web and create an Application.exe. But after I press build, it starts working, then a message pop-up, "GOOP Object Repository.vi is password protected. Enter the password to access block diagram". Any idea about this. I don't know any password.

---

Can't help you with this. LabVIEW 8.5 is also not supported on Windows 7.

[RavensFan]

---

@hnats1984 wrote:

Thanks, but you havn't commented on the snap shot of GEH.vi I posted. I found another forum post have same problem as me, "Vi not running when using NI´s SiimpleErr​orHandler.​vi (TS2010/LV​2011) in runtime - Windows 7"

---

The screenshot you posted called General Error Handler in LV6.1 is not the General Error Handler at all.  It is called "Error Code Database" as it shows in the screenshot.  You seem to be confusing names of VI's.

The screenshot you posted called General Error Handler in LV8.5 is the actual General Error Handler.

[hants1984]

in 6.1, GEH.vi (block diagram) and "Err Code DB.v"i both are there, I tried to show one "GEH.vi" uses "Err Code DB.vi" and the other use GEH Core.vi

 I found loaction of the vi's were the problem, I copied all vi's to root of the project ignoring LLB. After resolving all conflict of vi location (C:\... \NI....) the Application.exe and Installer can be created.

Application.exe: I installed LVRTE8.5 in Win7 (64 bit) pc and then run App.exe. It is working fine now.

Installer: Installer works in XP pc but show the err messages I shared before and ultimately failed. I think it could be due to Win 7pc have 2 program files directory. I will try Installer excluding LVRTE8.5. As all error msg related to NI files not being found.

[Zar666]

hi guys taking the 6.1 runtime from an old installation and copying it to the folder containing the labview runtimes and it works fine, at least running an exe that required the 6.1 runtime.

Hello.