LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview Detailed Help not working after 64-bit to 32-bit change

My Detailed Help stopped working after removing Labview2014 (64-bit) and installing Labview(32-bit).

 

All of the help files were correctly installed in the 32-bit help location here:

      C:\Program Files (x86)\National Instruments\LabVIEW 2014\help

 

The original help directory is here:

      C:\Program Files\National Instruments\LabVIEW 2014\help

A single file remained in this directory (lvivi.chm) after removing the 64-bit version. The detailed helps works fine for the ivi pallete.

 

My question is, how do I make Labview look for the chm files in the correctly populated (32-bit) path?

 

 

 

 

 

 

 

0 Kudos
Message 1 of 10
(2,965 Views)

I suppose it's a little late to tell you that LV 32-bit and LV 64-bit can exist happily side-by-side as long as you remember that a driver must be explicitly installed for the LV flavor that you are using if you want to use it.  (And also realize that LV 64-bit isn't supported by tool kits as well as with LV 32-bit.)

 

Unfortunately, I cannot explain, nor can I help you, with the issue you're having.  😞

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 2 of 10
(2,945 Views)

There is a reason we don't want both 32 and 64-bit versions co-existing on the same system. Seems like after removing the 64-bit version via Add/Remove programs and a installing a fresh 32-bit version I should not be seeing this problem. The new help files were installed correctly but some reference to the new help directory did not get updated. This like this should be a simple registry change or something. 

0 Kudos
Message 3 of 10
(2,942 Views)

@todd123 wrote:

There is a reason we don't want both 32 and 64-bit versions co-existing on the same system. Seems like after removing the 64-bit version via Add/Remove programs and a installing a fresh 32-bit version I should not be seeing this problem. The new help files were installed correctly but some reference to the new help directory did not get updated. This like this should be a simple registry change or something. 


Yes, this is exactly why I can't explain it, either.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 4 of 10
(2,935 Views)

Not helpful

0 Kudos
Message 5 of 10
(2,924 Views)

I just wanted to let you know that I don't have anything else to offer that you haven't already tried.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 6 of 10
(2,919 Views)

@todd123 wrote:

There is a reason we don't want both 32 and 64-bit versions co-existing on the same system. Seems like after removing the 64-bit version via Add/Remove programs and a installing a fresh 32-bit version I should not be seeing this problem. The new help files were installed correctly but some reference to the new help directory did not get updated. This like this should be a simple registry change or something. 


So, you can show what?  Snips,  screen shots, Hkeys, Max nce files, NIER dumps? Really, 

 

what can you show volunteers like those responding to your "flailed" attempts except attitude?.. nothing you have shown caused me trouble!  Then again.. you have shown nothing.   

 

You don't even stare your reasons why you don't want side by side 32, 64 bit installations. 

 

Really, did you want experienced advice or a corner to whine in?


"Should be" isn't "Is" -Jay
0 Kudos
Message 7 of 10
(2,908 Views)

And you seriously talking to an NI customer like that? Do you work for ni? Or, are you sitting in your moms basement trying to collect bitcoins. If you’ve never seen the problem then sit back and shut up. It’s no concern of yours why we don’t want 64 and 32 bit coexisting. You’re right on one point. After days of reinstalling drivers, trying to get other various issues resolved, and listening to you and your shallow knowledge, it gives me attitude. 

0 Kudos
Message 8 of 10
(2,884 Views)

One last post from me.  This isn't the official NI tech support hotline.  It's a forum where knowledgeable people try to help others on their own time.  They don't have to help, and now they probably won't.

 

If you have concerns, then act like an NI customer and use the 800 help number to get official support.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 9 of 10
(2,878 Views)

Hi Todd,

 

I'm not sure why LabVIEW help is still looking in the old help folder. I don't believe there's a way to change where detailed help looks for .chm files, but if you just move the new .chm files into the old folder, you should be good to go.

 

I really apologize that you haven't had a positive forum experience on NI.com. If you have a a service package with us, you are always welcome to visit http://www.ni.com/support or call us at 866-275-6964 to create a service request with an Applications Engineer here at NI and we'd be happy to help you out.

 

Lindsey Nestor
Program Manager, Hardware Services
National Instruments
0 Kudos
Message 10 of 10
(2,860 Views)