Loading vi from newer LabVIEW version

I can't seem to start LabVIEW 8.2 with a vi from 8.5. Please see the attachment.
Attachments:
labview error.doc ‏34 KB

That is by design. You cannot open newer versions of VI in an earlier version of LabVIEW. You can have whoever created the VI resave it in 8.2 format.

Similar Messages

Trying to load efax from new hp emachine. you get this; You can't open the application "eFax Messenger" because PowerPC applications are no longer supported.

trying to load efax from new hp emachine. you get this
;You can’t open the application “eFax Messenger” because PowerPC applications are no longer supported.
when is hp, efax, or apple getting their act together to fix the issue?

Hi,
The eFax service provided with the HP device is a remote cloud feature and have nothing to do with installing any software on your computer.
Any software named eFax you may trying to install is not affilated with HP in any way, as well I doubt if it is affilated with the eFax service in any manner.
In order to enable and use the eFax feature please follow the steps below:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02970945&tmp_task=useCatego ry&cc=us&dlc=en&lang=en&lc=en&product=5070121
Regards,
Shlomi

Small runtime engine for newer labview versions?

A few times in the past I have created simple LabVIEW standalone executibles. I did this in 8.6 and used the runtime engine minimal installer instead of the full version. This resulted in an installation package size of 30-35 Meg.
I agin need to create a simple executible but have not seen a minimum runtime installer for any LabVIEW version since 8.6
Are there any minimal runtimes for other versions?
The default 2014 runtime is 264 Meg!!! It is hard to explain to a customer why a simple "Hello World" program requires a 200+ Meg download.
Solved!
Go to Solution.

Jack Dunaway has documented a way of segmenting the run time engine, basically only including the pieces of it you need.
https://connect.wirebirdlabs.com/knowledgebase/articles/172999-segmenting-the-run-time-engine
And here is an idea exchange item on it.
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Segment-the-LabVIEW-Run-Time-Engine-RTE-to-ONLY-Necess...
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Load repository from newer version

Is it possible to load the contents of a Designer 6i 4.4 Repository into a 6i 4.1 Repository?

Wim,
For me, this was also an interesting question, but I read on Metalink that it isn't possible.
regards,
Harm

Screen saver lag in loading photos from new folder

I use my screen saver to display the family photos in a side show. I have several thousand photos in several folders. I have noticed that whenever I want to change the folder used as the side show source, it takes the Screen Saver Preference pane a very long time to respond. It is as if it is scanning all the photos in the currently assigned folder in order to display them in the preview window provided, and it gets so dogged down doing that it can't respond to my clicks on the Choose Folder option. This is puzzling because when I move my mouse cursor to the upper left corner of my screen to activate the screen saver, it only takes a few seconds to begin displaying photos, even with iTunes and other apps running. But when I open the Screen Saver Preference Pane just to change the source folder or to make any other simple change in options (pan and zoom, time to activate screen saver, etc.) it bogs down completely for 2-3 minutes. This makes no sense to me -- if the OS can get the screen saver side show going on a folder with several thousand photos in just seconds when the hot corner is used to activate it, why does it take the Preference Pane version so long to load the very same photos in a preview window? The problem is so bad, that I rarely bother to change source folders now. Which is a shame, because the side show program does a stellar job displaying photos -- at least once it gets around to it! A possible solution would be to give the user the option to suppress previewing of images. I have suggested this to Apple in several emails, and with each update to the OS I hope to find the problem corrected. So far, no cigar.
As long as I'm at it, I'd like to make my annual request that Apple to make the Screen Saver side show a stand-alone application. My reasons, partly taken from an earlier post, are as follows. The built-in side show provided by Apple via the Screen Saver Preference Pane does a fantastic job of displaying even low-resolution photos in full-screen mode (especially with pan and zoom activated) without the photo appearing excessively blurry or pixelized. I don't know how the Apple programmers do it, but the photos displayed by the screen saver seem crisper and sharper than the same photos displayed by Preview or Photoshop. This may partly be due to an illusion created by the pan and zoom -- the expansion and shifting of the image on the screen causes the mind to focus on the signal, which is consistent from frame to frame, as opposed to the noise (pixelization) which varies somewhat randomly. I think there is some kind of perceptual averaging process that allows the mind to perceive the underlying true image, despite the low resolution.
Be that as it may, I love the iMac screen saver. But I can't get control of it because it is not a stand-alone app. If the side show were available as stand-alone application it would probably have other features such as the ability to pause, go backward or forward, set the duration of each photo, select background music, etc. These would be in addition to the pan and zoom options already offered by the Screen Saver Preference Pane. And unlike the Preference Pane, selecting a new folder for the side show would (hopefully) not dog the machine completely down.
I am aware that side show capability is available within iPhoto and also at the FINDER level when using Spotlight to search for images. But again, none of these are stand alone apps, they all work a little differently, and no one of them does everything you need. How about just having an app called Slideshow (or iSlideshow)?
Does anyone else see a need for this?

I have several thousand photos in several folders. I have noticed that whenever I want to change the folder used as the side show source, it takes the Screen Saver Preference pane a very long time to respond. It is as if it is scanning all the photos in the currently assigned folder in order to display them in the preview window provided, and it gets so dogged down doing that it can't respond to my clicks on the Choose Folder option.
Assuming you don't want to redistribute your photos into a greater number of folders or subfolders so there would be fewer in each folder to process, you could try a workaround. Try moving your currently-assigned folder to your desktop temporarily, before opening the Screen Saver preference pane. If the preference pane can't find the old folder, it may immediately ask you to choose a new one. You could hopefully then do so, close the preference pane, and then put back the old folder.
It's my understanding that there will be no future updates to Tiger, only security fixes.

AE CS5 can't load projects from an earlier version

Hi!
I have several AE projects created back in 2006. I've tried to open them in AE CS5 but I get an error:
(Translated from spanish) After Effects error: this file was created in an earlier version of After Effects [5.5.1 (Windows)] and can't be opened. You can convert this file using an earlier version of After Effects and saving it again.
What a solution! I can't even remember what AE version was used to create the file back in 2006!
Is this normal? new versions of AE can't load earlier version projects or what?
What can I do? I don't have an earlier version of AE at hand right now...
OK, Let's suppose I did that project in After Effects 6 (I'm not sure, but maybe). Let's suppose I can install and run AE6 in my Windows 7 x64 machine (I'm not going to downgrade to Windows XP x32). OK, I load the project, And save it again? What's the point on doing this? I can't save it in AE-CS5 format from AE6. If it was created in AE6 I can only save it in AE6 format (the format that it already has) or older, but not newer!
Just imagine if MS Word 2010 could not load docs created in MS Word 2003...

Yes, this is normal and it's documented in the help. The rest is beside the point - even Microsoft could have decided to cease support on their old formats and it was actually under discussion for Office 2007 to avoid the various security issues associated with those old formats. You know, programs evolve and it's simply not possible to always guarantee 100% legacy compatibility....
Mylenium

Firefox very slow when first loading pages from new domains.

I've noticed that when starting the browser or opening up a new site it takes a considerably longer amount of time to load all the JS and assets compared to Chrome. Typically an extra 10 to 20 seconds, which is seriously annoying and nontrivial. After I've loaded the first page from the site Firefox is usually pretty fast on loading new pages from the same domain.
Firefox also sometimes fails to render CSS, resulting in a white page in Times New Roman and misplaced images.
I've tried setting up a new installation of Firefox and it hasn't solved the problem. Also tried Firefox portable with no addons and I got the problem straight out of the gate. It seems to be a problem with the code as Chrome and my internet connection work just fine. I've tried using Google as my primary DNS (8.8.8.8) which hasn't changed much.

You can try to disable hardware acceleration in Firefox.
*Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
You need close and restart Firefox after toggling this setting.
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
*https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration
Create a new profile as a test to check if your current profile is causing the problem.
See "Creating a profile":
*https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
*http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
*http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox

Loading songs from new computer

Old laptop screen broke. Bought new computer. Bought new songs on new computer. Once shuffle connects, Store wants to wipe off all songs on shuffle before loading new songs. Is it at all possible to transfer songs from old LT, through external drive, on to new LT, then load on to shuffle. Have I lost all of my $$$?

This forum is for troubleshooting compatibility issues between Mac OS and Windows, not iPods. You should probably post your question in the iPod and/or iTunes forums:
http://discussions.apple.com/category.jspa?categoryID=149
http://discussions.apple.com/category.jspa?categoryID=151

What is the eaisest way to convert an LLB to new labview version?

I have an insturment driver LLB that is a total mess now.
It started out as a LV 5.11 LLB
I am working in LV 8.5 now and LV 8.5 will not open code written in LV 5.11 (Too old)
I have tried to mass compile it in LV 8.2 but I still am running in to VI's in the LLB that are too old for LV 8.5 to open.
That means they are still in LV 5.11.
Do I really have to open each and save every single VI in the LLB in LV 8.2 to be able to use it in LV 8.5?

Dennis Knutson wrote:
I was able to mass compile it. I did notice that you did not include the hp34970u.llb. Did you point to this during the mass compile. Also, this llb is long obsolete. There is a nice, modern 8.5 project style driver available as well as a plug and play driver. Why do you even need to convert this?
I have mass compiled it with out errors too, but it seems like it was not really compiled as I still keep running into vi's in it that were still in 5.11.
I have a decade (or more) of 5.11 code that I am maintaining and upgrading when I have a chance.
Production test is still coding and deploying LV 5.11
I have tried the newer version of the 34970A driver but it is missing some of the vi's that many of our 5.11 codebase uses so is is not a drop in replacement for upgrading code.
Here is the "u" llb too, I forgot to attach last time
Message Edited by RTSLVU on 03-10-2009 01:12 PM
Attachments:
hp34970u.llb ‏21 KB

Update iWork from newer AppStore version

I just bought a new iMac 27" and purchased Pages,Numbers and Keynotes 09 from the AppStore
How do I update these same applications from iWork 08 on my older iMac 24" without having to buy them again.
On my old iMac the AppStore icon default to Install but when I click on it
I get the following popup.

brunelleda wrote:
Sorry, I taught that my screen capture would show up.
You do no drag the screensnap into the post, you need to navigate to the file on your mac using the camera icon and insert it.
Peter

What are developers' opinions on how best to handle upgrading large code libraries with multiple apps to new a labview version?

I have a large set of code that I've painstakingly migrated from one labview version to another over the years. I have lots of deployed applications that I need to continue to support. From experience and interaction with other developers, I don't think I can continue to migrate every application to a new labview version when I upgrade going forward. Every application seems to break in one way or another, the builds don't work right and need to be re-done, and its too much time to get all my applications working and tested again. That opinion is solidified by NI's policies that make it impossible to install old toolkit versions on new labview versions, for example. Compatibility is often being sacrificed so NI can develop labview in the direction they choose. So I have to take the position that whatever version I write an application in will probably need to be maintained in that labview version throughout it's life.
In light of this, how are other developers managing older applicatiosn written in older versions of labview. Right now I have a virtual PC on my system with 7.1, 8.0, 8.2, and 8.5 all running on different virtual PC's so I can keep each installation separate. I strongly recommend this approach. But keeping my large libraries of code separate is tough. They are many GB, they all link to each other, and I always get worried even when I separate them in different directories that somehow labview will search in the wrong place and find the wrong version of a sub-vi. Are other people also trying to maintain separate copies of all their code in different labview versions? How are other people managing this problem?
-Devin
I got 99 problems but 8.6 ain't one.
Solved!
Go to Solution.

Hi,
The following directory hierarchy, coupled with a "hierarchical" VI naming strategy, have been effective (for me) at preventing "cross-linking" across projects and LV versions. The storage hierarchy was designed for use within an SCC environment, but works fine independently. Hierarchical-naming insures unique names for application-specific files. Use of Project Libraries (in LabVIEW 8.x) addresses the problem of having different VIs with the same name, still, it gives me warm-fuzzies to have app-specific files named uniquely, and I can't imagine not using Hierarchical-naming anymore - it's described at-length in section 2.1 of attached .doc..
Note: It's been my experience that companies identify resources as supporting specific "Programs", where a Program is related to a product or "family" of products, so, under <Programs> (below) each "Program" subdirectory encapsulates product-specific (or product-family-specific) applications. Also, assuming no SCC tool is being employed the <Production> directory (below) exists as a repository for distributables. All distributables required to reproduce a test-station should be located under <Production>.
<Software_Root>
<Development>
| <Common>
| | <LabVIEW_61>
| | | <Drivers>
| | | | <DMM>
| | | | <OS>
| | | | <PS>
| | | <Utilities>
| | | <File>
| | | <Error>
| | | <String>
| | <LabVIEW_711>
| | <LabVIEW_82>
| | <LabVIEW_851>
<Programs>
* Program-specific applications that (probably) have distributables
| <Program_#1>
| | <Application_#1>
| | <Docs>
| | <Source>
*       Individual, application-specific, VIs go here
| | <Application_#2>
| | <Application_#3>
| <Program_2>
| | <Program_3>
| <Tools>
* Tools are NOT "program"-specific, and, may have distributables
| <SomeTool>
| <SomeOtherTool>
<Production>
| <COTS&Freeware>
| <Programs>
| | <Program_1>
| | | <Application_#1>
| | | | <Application_#1_Rev#1>
| | | | Application_#1.bld>
| | | | <EXE>
| | | | <Installer>
| | | | <Source>
| | | |    Application_#1.llb>
*           Distributable is created from LLB "snapshot", not directly from development tree
| | | <Application_#2>
| | | | <Application_#2_Rev#1>
| | | | Application_#2.lvproj>
| | | | <EXE>
| | | | <Installer>
| | | | <Source>
| | | |    Application_#2.llb>
| <Tools>
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
StyleGuide.doc ‏941 KB

Installing old VIs in newer LabVIEW folder: how to avoid conversion warnings?

We are offering a set of VIs to our users. We build our own installer which installs them into the LabVIEW program folder under vi.lib. A menu file is installed in the menus tor which collects the VIs in a palette.
For providing compatibility with LV 8.2 and up the VIs are in v8.2 format. When they are installed in a higher LV version and a LV program that contains some of the VIs is closed, LV issues the warning that the VIs have been recompiled and converted from an older format. How can we install the VIs so that LV ignores the format version?

smercurio_fc wrote:
I did not mean to imply that setting the read-only flag would fix your problem. Only that it would prevent the file from being saved, if that's what you were intending to be done. You cannot change the behavior, as it is by design. You can deal with it by compiling the VIs when you install the software, as has been mentioned. Or, you can distribute pre-compiled versions in the LabVIEW versions of your choice.
You mean it is definitely not possible to have VIs in one, relatively old LabVIEW format and install them for newer LabVIEW versions without getting this (completely useless) warning? This is hard to believe. How do other companies distribute their LabVIEW programming interfaces? Do they really maintain a VI versions for every LV version (and possible sub-version) just to guarantee a good user experience?
Since the recompiled changes are dumped anyway, I would expect a VI or library flag I could set or a special way of installing the VIs that tells LabVIEW: ignore the changes when the VI is closed.
Recompiling everything during installation is not what we want since it would make the installation process too complicated, in which our LabVIEW API is just a small part. If nothing else works I would rather install the VIs writable so the user could just hit "save all" when he closes his program and get rid of the warnings, but this is not optimal.
Olf

I am trying to load LR on my new macbook pro. It asks for the serial number. I enter the digits, but it says, quote, " This is an upgrade serial number. The serial number from your previous version of Lightroom is also required."

I am trying to load LR on my new macbook pro. It asks for the serial number. I enter the digits, but it says, quote, " This is an upgrade serial number. The serial number from your previous version of Lightroom is also required."

If you still have the old computer and it is a MAC, the Lightroom 5 serial numbers are in a text file.
users/"username"/Library/Application Support/Adobe/Lightroom/Lightroom 5.0 Registration
More info here
Preference and other file locations in Lightroom 5

IPhoto doesn´t work after trying to load photos from iphone with newer version. Help!!!!!

First, I do not have a recent back-up of my iPhoto Library. (But, I learned my lesson for next time). When I tried to load photos from my super duper up to date software I-phone to my outdated iPhoto on the computer (only version 8.1.2), a message came that I cannot open your Mediateck with this version of iPhoto,. You have changed your mediathek with a newer version of iPhoto.
(in German, because I am writing from Germany "Sie konnen ihre aktuelle Mediathek nicht mit dieser Version von iPhoto öffnen. Sie haben Ihre Mediathek mit einer neueren version von iPhoto geändert").
How can I save all the baby pictures of my 3 kids??Help

Did you update iPhoto?
If not:
Try these in order - from best option on down...
1. Do you have an up-to-date back up? If so, try copy the library6.iphoto file from the back up to the iPhoto Library (Right Click -> Show Package Contents) allowing it to overwrite the damaged file.
2. Download iPhoto Library Manager and use its rebuild function. (In early versions of Library Manager it's the File -> Rebuild command. In later versions it's under the Library menu.)
This will create an entirely new library. It will then copy (or try to) your photos and all the associated metadata and versions to this new Library, and arrange it as close as it can to what you had in the damaged Library. It does this based on information it finds in the iPhoto sharing mechanism - but that means that things not shared won't be there, so no slideshows, books or calendars, for instance - but it should get all your events, albums and keywords, faces and places back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
3. If neither of these work then you'll need to create and populate a new library.
To create and populate a new iPhoto 08 library:
Note this will give you a working library with the same Events and pictures as before, however, you will lose your albums, keywords, modified versions, books, calendars etc.
In the iPhoto Preferences -> Events Uncheck the box at 'Imported Items from the Finder'
Move the iPhoto Library to the desktop
Launch iPhoto. It will ask if you wish to create a new Library. Say Yes.
Go into the iPhoto Library (Right Click -> Show Package Contents) on your desktop and find the Originals folder. From the Originals folder drag the individual Event Folders to the iPhoto Window and it will recreate them in the new library.
When you're sure all is well you can delete the iPhoto Library on your desktop.
In the future, in addition to your usual back up routine, you might like to make a copy of the library6.iPhoto file whenever you have made changes to the library as protection against database corruption.

Load error code 9: VI version (8.2) is newer than the LabVIEW version (8.2b23).

I am getting the error...
VI version is later than the current LabVIEW version. An error occurred loading VI 'CleanupCallback.vi'. LabVIEW load error code 9: VI version (8.2) is newer than the LabVIEW version (8.2b23).

This is true. the 'b' indicates that it is a beta version of labview 8 (.2 in this case). I am surprised your beta version is still working. You need to upgrade to 8.2 or have the vi downgraded to 8.0
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?

Loading vi from newer LabVIEW version

Similar Messages

Maybe you are looking for