LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

What's the deal with xuser.lib and xvi.lib?

Tried to examine some old LV2021 code in LV2021 and the screen blew up with missing library notifications.  Subsequent investigation revealed that user.lib and vi.lib had been renamed xuser.lib and xvi.lib.

 

I renamed the folders back to their original names and everything loaded as expected.  Further investigation revealed that all my older versions of LabView, except LV7.1, had the same renamed files issue.  This included LV2021,2020, 2019, 2018, 2017, 2016 & 2010.  My latest version, 2022Q3 had the correctly named files...

 

Can anyone explain what is going on?   I can't find anything out there on xuser.lib and xvi.lib

 

0 Kudos
Message 1 of 6
(853 Views)

Never seen that… did someone else use your computer recently ? 😅

0 Kudos
Message 2 of 6
(837 Views)

@Spaz wrote:

Tried to examine some old LV2021 code in LV2021 and the screen blew up with missing library notifications.


In my experience, screen explosions are somewhat uncommon.

0 Kudos
Message 3 of 6
(809 Views)

@tavias wrote:

xuser.lib and xvi.lib are libraries commonly used in Unix-based systems for handling user-related functions and X Window System interactions, respectively. They play crucial roles in enabling various software to run smoothly on Unix-like operating systems.


How kind of you to create an account just so you can answer this one question with a generic answer that doesn't even pertain to the topic.

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 6
(774 Views)

My initial assumption was that for, some reason, LV2022Q3 renamed user.lib and vi.lib with a prepended 'x' on all old versions in the 'C:\Program Files (x86)\National Instruments' folder that followed the LabView 20xx naming format (hence LabView 7.1 was untouched)...

 

I thought there would be some valid explanation for why this happened and I was to dense to find any documentation of that behavior or a reason for it.

 

No one's used my computer.  In, fact very few are of sufficient fortitude to spend more than a few seconds in my office...😧.

 

 

0 Kudos
Message 5 of 6
(737 Views)

@Spaz wrote:

My initial assumption was that for, some reason, LV2022Q3 renamed user.lib and vi.lib with a prepended 'x' on all old versions in the 'C:\Program Files (x86)\National Instruments' folder that followed the LabView 20xx naming format (hence LabView 7.1 was untouched)...

 

I thought there would be some valid explanation for why this happened and I was to dense to find any documentation of that behavior or a reason for it.

 

No one's used my computer.  In, fact very few are of sufficient fortitude to spend more than a few seconds in my office...😧.

 

 


On a more serious note than my last post, I'll check on my computer at home to see if this has happened to me as well.  I remember hearing something about no longer having to install the same drivers every time you install a new LV version, and maybe this is part of it?  Or I could be hallucinating ChatGPT-style.

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 6
(732 Views)