LabVIEW 8.6 Runtime and MAX installation

Can I install the LabVIEW 8.6 runtime engine and MAX on any computer without violating the license agreement for a single seat developer package? When I install this on a lab machine running XP and I go to launch MAX from the installed desktop icon, it does nothing... What am I doing wrong? Thanks, Keith

KC
You can try installing MAX from a download, MAX is included in many NI drivers, of which the smallest of which is the NI VISA driver. You can download and install VISA and it will automatically install the most update version of MAX as well. The VISA driver, MAX, and the runtime engine are total free and you can install them on any computer without any licenses.
Hunter
Message Edited by Huter on 02-23-2009 01:03 PM

Similar Messages

Silent install Air Runtime and Air App with custom installer?

I want to use a custom installer that will perform some actions, and then silently install air runtime and an air application. The goal here is to be able to perform a customized install for an Air application (for a user that might not have Air installed) without confusing the user with multiple install screens. Can I use a custom installer to silently install Air (if the user doesn't have it installed) and the Air app? If so, are there any restrictions on the custom installer? If there are any examples of this, please provide the links.

Since you applied for the distribution from Adobe you should
have received a link to a page where you can download what they
call the "side-car" installer. It's basically an installation
system they are making available to developers that can be easily
configured to deliver a bundled runtime and application
installation for Mac and Windows.
Check your email again and see if you can't find a link in
there pointing you to a download page for the AIR runtime as well
as the aforementioned side-car installer. For those who don't know,
here
is where you can apply for a redistribution permit for AIR.
I have a small tutorial posted that might be of help to you
on my blog:
http://blog.arnimaack.com/flex-air-series-4-air-all-in-one-installers-on-CD-DVD

Need how to install Air Runtime and App from CD Rom

I am looking for some direction on how to bundle the Air
runtime and my app together in a single executable file from a CD
rom, for MAC and WIN. I already have applied for and received
licensing necessary form Adobe and I have the dmg and exe of the
Air runtime.
I have the seamless install working where internet access is
available however the initial group who will receive the app won't
have internet access at the time of distribution so the bundled
install will be from CD rom.

Since you applied for the distribution from Adobe you should
have received a link to a page where you can download what they
call the "side-car" installer. It's basically an installation
system they are making available to developers that can be easily
configured to deliver a bundled runtime and application
installation for Mac and Windows.
Check your email again and see if you can't find a link in
there pointing you to a download page for the AIR runtime as well
as the aforementioned side-car installer. For those who don't know,
here
is where you can apply for a redistribution permit for AIR.
I have a small tutorial posted that might be of help to you
on my blog:
http://blog.arnimaack.com/flex-air-series-4-air-all-in-one-installers-on-CD-DVD

Labview 8 Application Builder and VISA Runtime Engine

Hi,
I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
Is this possible?
Ken

Hi,
this How-To explains about making those selections and including the different drivers :
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
and this tutorial covers the screenshots a little more step by step.
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Installation of Microsoft Visual C++ 2005 C Runtime and its impact

Dear All,
I am working with a client, and as a prerequisite, Microsoft Visual C++ 2005 C Runtime has to be installed on the client's servers in order for one of our products to work.
Since at the moment the client do not have this installed on their servers, and the fact that their servers have not been rebooted in a long time, they feel that there is a risk in installing Microsoft Visual C++ 2005 C Runtime if rebooting the server
is required.
Could anyone provide me with some insight into the following:
1. If there is any impact on the OS (Windows 2003 R2) or the IIS (version 6.0) or any other MS products or applications by installing Microsoft Visual C++ 2005 C Runtime
2. If any common library will be written into during the installation and what is the impact
3. If the server has to be rebooted after the installation
4. What is an appropriate procedure for rollback (is it simply uninstalling “Microsoft Visual C++ 2005 C Runtime” and would a reboot of the server be required after the uninstall, etc.)
Would anyone be able to provide any insight on the above?
Many thanks in advance.

1. Use reliable backup and preserve return path.
2. Do pilot test on computer that is not part of your enterprise.
3. Consider applications that may have different versions of MSC libraries. Here I can se the possible problem.
Regards
Milos

Installing LabView 8.2 runtime engine on Windows 7 64-bit

We have a product built on LabView 8.2
For a couple of years, we have been distributing this product on Windows 7 64-bit systems with no trouble at all.
Today, we received a customer complaint indicating that the LabView 8.2 runtime engine cannot be installed on Windows 7 64-bit.
Our verification team has confirmed this to be true.
Interestingly, we have several Windows 7 64-bit computers with the LabView 8.2 runtime engine already installed.
How is this possible?
Has something changed in Windows that no longer allows the LabView 8.2 runtime engine?
We are confused by the fact that this appears to be a new problem and the runtime engine did, at some point, install correctly on multiple Windows 7 64-bti computers.
Any thoughts would be extremely appreciated.
Attachments:
lv_install_error.jpg ‏22 KB

No, i dont think the 8.2 installer is corrupt, but it uses the Windows Installer service, which according the image has some problems. Maybe it recently updated? It's incompatible with that old installer so you need to downgrade it? It's corrupted and needs some fix?
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Labview 8.2 application builder - installer deletes previously installed programs

Problem Description :
I've been developing with LabView for 8+ years and recently had to upgrade from 6.1 to 8.2 because of compatibility issues with LabView, MAX, DAQ and SERIAL. LabView had always been so intuitive and efficient, but that has changed to some degree sometime after 6.1 IMO. I won't get further into that, but I am having several problems with Application Builder and particularly, with creating an Installer and installing test programs. I haven't seen many posts on this subject so I assume I am doing something wrong.
In 6.1, I could build a program and create an installer in minutes, and all in the same step - Click on Build and the installer was created. I could also locate my files anywhere I wanted. Unfortunately the process in 8.2 is no where as simple as one has to create a build and installer separately. So far, I haven't been able to distribute my installer files where I want them according to our internal procedures. The build portion works fine and I can locate my files as needed, but not so for the installer (at least I haven't figured it out yet). The main problem is that I have some common DLLs that I'd like to locate in a common directory for all of my programs, but it seems like I'm stuck putting them in the installation directory of every program that I write. Again, it is fine in build. There doesn't seem to be any flexibility in changing the location of the files in the installer. I did see a post somewhere that mentioned that DLL files must be located in the system directory if you don't want them included in the build or installation. I would just like to install the dlls to a common directory and not include them in every installation directory. Just like I did in LV 6.1!
This is a relatively minor problem compared to what happens when I try to install the programs.
I have five separate programs for which I have recently built and created installers with the limitations that I've described above. I can install one program on my machine and it runs properly. If I try to install any of the
other four, they will delete the previous installation - all the files are deleted (they all have different names). What I think is going on is that the installer thinks that these five programs are the same and simply overwrites the previous installation. One reason I believe this, is because I tried an installation and it failed with the error message that there was already a higher version installed. The higher version it was referring to was almost certainly the one program I could install, but certainly not a higher version of the one I was trying to install (it didn't exist yet). After I uninstalled the one program, I could install any other four. It doesn't matter if I install on the build computer or the target computer (ATE).
What am I doing wrong? Please help me to resolve this problem.
I wan't the build and install files in the same exact location:
Example of my five programs and the locations of build and install:
C:\KIK2-LabView\Customer Name\Base Part Number1\Program1.exe.......
C:\KIK2-LabView\Customer Name\Base Part Number2\Program2.exe.......
C:\KIK2-LabView\Customer Name\Base Part Number3\Program3.exe.......
C:\KIK2-LabView\Customer Name\Base Part Number4\Program4.exe.......
C:\KIK2-LabView\Customer Name\Base Part Number5\Program5.exe.......
The support files will also be put in the corresponding directories. The common files were supposed to go in the KIK2-LabView directory instead of copies in every installation directory.
Is there something I have to do with the registry? In 6.1 it was all automatic.
I hope there are simple answers to my problems, but I have yet to find them out. I have been able to find very little info on Application Builder, and nothing that is comprehensive.
Thanks!

Thank for the reply, Andy
I have scoured the Help files and this forum which helped me to create the build and installer, but they didn't address any of the problems that I described in my post. I tried to make sure that I exhausted numerous resources before posting and requesting help.
I appreciate the response, but you didn't quite get to my most important problem - that when I try to install a program from the created installer, it overwrites my previously installed program. Actually I have found the answer in a different thread. --->  http://forums.ni.com/ni/board/message?board.id=140&message.id=16146. My problem is that I cut and pasted all of my project files and made the appropriate changes specific to each new project. If you don't create brand new builds and installers in these projects, you will create duplicate registry keys, even though all of the names, numbers, files, etc. were changed to be completely unique. I opened the .lvproj file in notepad and found several registry keys to be the same; here is an example:
<Property Name="UpgradeCode" Type="Str">{831013BF-9112-45AA-BF13-A13F08098841}</Property>
All of the projects that I created by cut and paste (and edit) method had this same exact key (as well as other keys) which was causing the previous install to be deleted/overwritten or gave me the message that a higher version already existed.  Again, this happened even though all of the project data was completely unique after it was edited, including the project filename (of course). Finally, I completely rebuilt my projects from scratch starting with "New Project" and voila, they now all install properly. Obviously, none shared any of the same registry keys.
I don't know if this is something that was overlooked, but it is so much easier to cut, paste and edit projects when they are very similar.   Unfortunately I have found out the hard way that new build and install spec's must be created. Is there a change that can be made to the Project File in LabView so that when certain information changes (like the executable file name) that new registry keys will be generated? It is obvious that you don't want someone to accidentally install a lower version of the project over a newer one, but it would have prevented my work time loss (several days) and will prevent time loss for others in the future as well. Could you at least consider allowing the developer to generate new keys like was available in LabView 6.1?
Also concerning the location of files, I previously had done all of what you said and can locate the build files where I want. However, in the Installer (Source Files Tab), when I create the folders in [Windows Volume], all of the files from the build spec are put into the SAME directory, regardless of where they were located in the build spec. If I try to delete one file, all will be removed. I can't place individual files where I want them to go in the installer (if they are a part of the build). Example: In the installer, I created the subfolders KIK2-LabView\Customer\UUT Base Part Number on the [Windows Volume] directory and set the UUT Base Part Number as default. I want most of the files to go into the default directory, but a few of the dependent dll's should go into the KIK2-LabView folder as they are common to many other programs/projects. In short, I don't need or desire 50 copies of these dlls on my ATE. I was able to locate the installer files anywhere in LabView Pro 6.1, but so far I can't figure out if this is possible in 8.2. It would appear that it is not.
Thanks,
John W.

Labview 8.6 sound and measurement suite not installed properly under Vista 32 or 64 bit

I apologize if this isn't the correct place for this post but I'm in need of a solution. I recently purchased LabVIEW 8.6 Developer Suite with the Sound and Measurement Suite to create a NVH testing program at my company. I'm a newbe at Labview but I've been a programmer/computer hardware geek since the days of the TRS-80 model1. Here's my problem. I installed the package from the developers suite DVD's on my Windows XP professional desktop and everything is fine. I see the Sound and Vibration Measurement Suite listed under LabVIEW 8.6 in Measurement & Automation Explorer and the toolkit examples work in LabVIEW. When the laptop I purchased to do my actual work arrived with has Vista Business Edition 32 bit version installed I found the following problem. On that machine and two other Vista machines(one 64 bit and one 32 bit) that I tried, the installation doesn't register the Souind and Vibration Suite under LabVIEW 8.6 and they show the Sound and Vibration toolkit as not installed in the examples section. In the Windows control panel under National Instruments, all 4 machines show the Sound and Vibration Suite 6.0 as installed. I've tried to uninstall, reinstall, modify, from the control panel, and reinstall from the DVD's with no change in the outcome. I really need to get the laptop working as this is my actual development and test machine. Installing XP is not an option as the machine is newly purchased with a high end sound system and XP downgrade wasn't available. I'm out of ideas.
Solved!
Go to Solution.

I wanted to let close this as I got it working finally. This time I un-installed the Sound and Vibration entries from the LabVIEW control in Vista's uninstaller. Then re-installed and now it works. Before there were three entries, one for the suite, one for the runtime, and one for the toolkit. After removing all three and re-installing from the DVD, only the suite shows up, and all seems to be good.

Has anyone used a touch screen monitor with scxi.I am having video lock ups while using LV and MAX

I have a PCI-MIO-16XE-50 daq card (dev1) connected to a scxi-1000 chassis address 0 ID 1, with a scxi-1102,1163,1163,1162 slots 1,2,3,4 respectively.Cable is connected to daq card to 1102 card .Micro touch screen is used on com2. Have tried other serial ports 1,5. Touch screen works fine with windows until LabView and max is installed .Video lockups,Max failures occur.MAX seems to confict with touch screen.

Max is the NI interface for all the drivers. It may be a specific driver that is causing problems, perhaps NI-VISA. I would try installing things one piece at a time. Might want to start by uninstalling everything so that you start with a clean system. First install LabVIEW with no drivers at all. See if the Micro touch screen still works. Then try installing NI-DAQ. Install each of the drivers you need one at a time. If you don't need something, leave it out.

SharePoint - Error_1_Error occurred in deployment step 'Add Solution': Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was rea

Hi,
I am Shanmugavel, SharePoint developer,
I am facing the below SharePoint 2013 deployment issue while deploying using VS2012.
If i will deploy the same wsp or existing wsp
(last build) using direct powershell deployment, the solution adding properly, but the same timeout exception coming while activation the features. Please find the below error.
I tried the below activists:
1. Restarted my dev server, DB server.
2. tried the same solution id different server
3. tried existing wsp file (last build version)
4. Deactivated all the features, including project Active deployment configuration.... but still i am facing the same issue.
I hope this is not coding level issue, because still my code is not start running, before that some problem coming.
Please help me any one..... Last two days i am struck because of this...

What you need to understand is the installation of a WSP does not do much. It just makes sure that you relevant solution files are deployed to the SharePoint farm.
Next comes the point when you activate the features. It is when the code which you have written to "Activate" certain features for your custom solution.
Regarding the error you are getting, it typically means that you have more connections (default is I guess 100) open for a SQL database then you are allowed to.
If you have a custom database and you are opening a connection, make sure you close it as well.
Look at the similar discussion here:
The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool
size was reached[^]
I would suggest further to look at the
ULS logs[^] to get better insight.
Manas Bhardwaj's Stream : www.manasbhardwaj.net

6/10/14 - Release - AIR 14 Runtime and SDK

Today we're pleased to announce that the next version of AIR is available for immediate download.
This update includes the following fixes and security updates:
Security update details can be found here: Security Bulletin (APSB14-14)
New Features:
Anisotropic Filtering
This new texture sampling filter can enhance the image quality of textures on surfaces that are at oblique viewing angles. There are two ways to enable this feature:
In AGAL, set one of the values – "anisotropic2x", "anisotropic4x", "anisotropic8x", or "anisotropic16x" to the filter option in the sampling instructions.
Call Context3D::setSamplerStateAt with the 3rd parameter "filter" being one of the values defined in Context3DTextureFilter - "ANISOTROPIC2X", "ANISOTROPIC4X", "ANISOTROPIC8X", or "ANISOTROPIC16X"
New Stage3D "Standard" Profile
Developers can now request this high level profile when creating Context3D. Three new features are available in this profile:
Multiple render target allows to you to draw geometry to multiple outputs (up to 4) during one drawing
Floating point texture allows you to create Texture, RectangleTexture and CubeTuxture with the RGBA16F folder.
AGAL v2 contains these improvements:
Increased register size
Partial derivative instructions
Fragment depth output
Conditional forward jump
Intel x86 Android Support
As announced in our Flash Runtime blog, we're adding support for Intel x86 Android to AIR. An ADT command line option (-arch) has been added to allow packaging apps with Android x86 support. Please note that currently only captive runtime packaging is allowed for x86 architecture. This means all APK targets (apk, apk-debug and apk-captive-runtime) will forcibly be packaged with captive runtime. Feedback on this approach is encouraged.
Sample APK packaging command for x86 devices:
adt -package -target ( apk | apk-captive-runtime ) -arch x86 -storetype pkcs12 -keystore abc.p12 HelloWorld.apk HelloWorld-app.xml HelloWorld.swf
adt -package -target apk-debug -arch x86 -storetype pkcs12 -keystore abc.p12 HelloWorld.apk HelloWorld-app.xml HelloWorld.swf
Note that -arch is optional. If not specified, armv7 is assumed.
Packaging for x86 architecture in Flash Builder:
Open the debug/run configurations of the project in Flash Builder and click on "Customize launch.." button. Add a new parameter "-arch" with value "x86" and place it before "-storetype". Click "OK" to apply changes.
Except for RTMPE and DRM, all other features and capabilities are completely functional and supported. Native extensions written for x86 platforms can also be packaged and used by an app for x86 devices. To support this, a new ANE platform 'Android-x86' is now available.
The following example highlights the usage of the same -
<extension xmlns="http://ns.adobe.com/air/extension/14.0>
<id>com.adobe.sample.ane</id>
<versionNumber>1.0</versionNumber>
<platforms>
<platform name="Android-ARM">
<applicationDeployment>
<nativeLibrary>sample.jar</nativeLibrary>
<initializer>com.example.ane.Extension</initializer>
<finalizer>com.example.ane.Extension</finalizer>
</applicationDeployment>
</platform>
<platform name="Android-x86">
<applicationDeployment>
<nativeLibrary>sample.jar</nativeLibrary>
<initializer>com.example.ane.Extension</initializer>
<finalizer>com.example.ane.Extension</finalizer>
</applicationDeployment>
</platform>
</platforms>
</extension>
New packaging command for ANE:
adt -package -target ane Sample.ane extension.xml -swc Sample.swc -platform Android-ARM -C Android-ARM/ . -platform Android-x86 -C Android-x86/ .
Improved Packaging Engine - iOS
Based on the feedback received from the developer community, tons of improvements and bug fixes have been made in the new packaging engine for iOS. We encourage developers to report issues to http://bugbase.adobe.com, to ensure that we are able to continue to improve the packager in future releases.
To enable this feature, please use "-useLegacyAOT no" in the ADT command, before the signing options. As of now, this feature is not available within Flash Pro but it can still be used with Flash builder by adding the parameter -useLegacyAOT under the "Customize launch" option.
Here is an example ADT command for compiling an applications using “-useLegacyAOT no":
adt -package -target ( ipa-test | ipa-debug | ipa-app-store | ipa-ad-hoc) -useLegacyAOT no -provisioning-profile -keystore -storetype pkcs12 -storepass xxxx HelloWorld.ipa Helloworld-app.xml HelloWorld.swf
For more information, please visit Faster compiling with AIR for iOS
AIR Gamepad
AIR Gamepad feature enables the app developers to provide a second screen on Android mobile devices for the Flash based browser games. AIR Gamepad API enables Flash based browser apps to connect to a paired Android device running the AIR Runtime app and therefore allowing the Android devices to be used as game controllers or second-screen interfaces.
Key functionality of this feature:
Gesture eventsTouch events
Accelerometer events
Vibration
Customize the AIR gamepad screen by applying your own skins
To learn more about the AIR Gamepad APIs, please refer to the documentation found here.
To try out the Wand.swc which can be downloaded from here.
Live samples of AIR Gamepad can be tested using the following links:
ModelViewer
HungryHero
For more information, please visit Android devices with AIR as gamepads
Fixed Issues:
[IOS] Resolves an issue introduced in AIR 4.0.0.1390 where DatagramSocket was not receiving packets (3747382)
[IOS] Values are now set correctly when assigning Vector3D.Y_AXIS to a Vector3D object with -useLegacyAOT=no[Android] Browse file dialog called by FileReference.browse() is correctly displayed on the Nexus 7 and Xoom 4.1.2 (3721032)
[Android] is ignored for all but one extension when multiple extensions are used (3761458)
[x86][Android] Workers get terminated even without calling terminate function (3755006)
[Android] Setting the restrict property on a StageText instance and adding or removing text incorrectly add extra characters. (3749699)
[iOS] Values are now set correctly when assigning Vector3D.Y_AXIS to a Vector3D object with useLegacyAOT=no (3744595)
[iOS] ANE doesn't include libraries through platform.xml and throws error on packaging the IPA (3743946)
[iOS] DatagramSocket not receiving packets on iOS (3742982)
[iOS] Not able to debug/launch iPad iOS Simulator from Flash Builder. Note: One needs to set a environment variable using the command: launchctl setenv AIR_IOS_SIMULATOR_DEVICE "iPad Retina” Then restart the process and run the application on simulator device of his/her choice. By default iPhone is launched. (3728052)
[iOS] Not able to debug AIR app in iOS Simulator from Flash Builder when Xcode below 5.x is installed (3727760)
[iOS7] StageText fontWeight/fontPosture API does not work (3724627)
[Android] R$Styleable.class goes missing from the final AIR app APK though is included in ANE. (3723876)
[Android] Starling throws Buffer creation failed. Internal error while createVertexBuffer (3756123)
[Win] Ctrl+A, Ctrl+C and Ctrl+V now work correctly in StageText fields (3708480)
Multiple security and stability fixes
Known Issues:
[Android] Missing support for XXXHDPI icon on Android 4.4 (3730948)
[x86][Android] Export Release Build from Flash Builder fails to run app on Android device when -arch parameter is used. (3759405)
[Android]Captive packaging fails for APK using multiple ANEs, throws OutOfMemoryError. (Workaround: run export _JAVA_OPTIONS='-Xms4096m -Xmx4096m' and then run the packaging command). (3766280)
[iOS8] A notification dialog is coming after launching any AIR applications. (3771162)
[Android] ADT Does not pass required heap space to dx.jar (3771118)
[Android] StageText restrict = "A-Z" not blocked lowercase letters input. (3769801)
[iOS] Package IPA file with ipa-app-store or ipa-ad-hoc type will case logic judgment with incorrect (3768506)
[Android] StageText displayAsPassword displays text without mask in landscape on Android (3768443)
Download Locations:
AIR 14 runtime for Windows: 14.0.0.110 Runtime Download
AIR 14 runtime for Macintosh: 14.0.0.110 Runtime Download
AIR 14 SDK & Compiler for Windows: 14.0.0.110 SDK & Compiler Download
AIR 14 SDK & Compiler for Macintosh: 14.0.0.110 SDK & Compiler Download
Note: To provide all the all the necessary tools for our developers in one place and avoid having to download multiple components, we are packaging Adobe AIR 13 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 13 SDK & Compiler”.
AIR SDK 14 (Compatible with Flex) for Windows: 14.0.0.110 SDK Windows Download
AIR SDK 14 (Compatible with Flex) for Macintosh: 14.0.0.110 SDK Macintosh Download
Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page

OK! Let's take 7 steps ... an easy answer to a focus problem not a machine problem. (MAC!)
1.1. Download the Adobe Flash Player file version 14 at Adobe - Install Adobe Flash Player
1.2 or dowonload the above link: http://download.macromedia.com/pub/flashplayer/current/support/install_flash_player_osx.dm g
2.1 Double-click the AdobeFlashPlayerInstaller_14_ltrosxd_aaa_aih.dmg in your download folder
4. Do not double-click the red face (png file) - Installer "Install Adobe Flash Player".
5. Right click the face to perform a precise selection: Show Package Contents.
6.1 Select - Contents and double click; Select - Resources and double click; Select - Adobe Flash Player.pkg and double click.
6.2 Warning!! Select - Contents and double click; Select - Resources and double click; Select - app.bundle and copy it to your internet plugin folder (more work!!)
7. Select: Continue and complete your installation.
R. Alexander

9/3/2013 - AIR 3.9.0.720 Runtime and SDK Beta

Adobe AIR Beta Channel Update
This beta release provides access to the latest AIR runtime and SDK (with compiler) for Windows, Mac OS, iOS and Android.
Below are some of the key features and benefits of AIR 3.9. Please see our release notes for full details.
Mobile Workers (concurrency) for Android - BETA – Our hugely popular desktop feature, AIR Workers, is now making its debut on mobile! We have added support on Android devices so that you will be able to execute code in the background without interrupting your application’s main code. Your UI will remain responsive, enhancing the user experience. We haven’t forgotten about iOS! Look for news on iOS workers in an upcoming release (NOTE: this feature will undergo an extended beta period).
Mobile Support for Background Execution in “Direct” Render Mode – AIR now supports background execution of code on iOS and Android when render mode is set to “direct”. This will allow your applications to perform tasks such as audio playback even when invisible to the user. Due to power and CPU considerations, we recommend reviewing our release notes for additional details and guidance.
Mac OS 10.9 Support – We have tested against the latest developer releases of OS X 10.9 and are making sure that your applications support the latest technologies such as “App Nap”.
XXHDPI Icon Support – With this feature we have added support for beautiful, high resolution icons on devices such as the Nexus 10.
Known Issues:
The following behaviors will be modified in Safari 6.1 and higher in Safe Mode:
AIR Badge Installs - AIR Badge Installer will not launch an installer when running Safari 7 in Safe Mode. Users will instead see a dialog with a link to more details and workarounds on an Adobe website.
LocalConnection - When a LocalConnection is constructed from a SWF hosted in Safe Mode, it may only establish a connection with other SWFs also hosted in Safe Mode. If a LocalConnection is constructed from a tab with Safe Mode disabled, it will not be able to communicate with a SWF in a Safe Mode tab.
Developers can detect whether or not a SWF is running in Safe Mode by checking the Boolean ProductManager.isAllowed(). (This is currently unofficial, and it's possible that we may alter it during the API review process.)
3622405: [iOS7] iOS7 specific icons are not yet supported.
3621111: [Android] Cannot load files asynchronously in StageWebView.
3616999: [iOS7] On changing AudioPlayback mode from Media to voice dialog comes up asking permission for accessing Microphone.
3616981: [iOS] Sound gets stop on clicking Power button even when UIBackground tag value set to Audio in application.xml
AIR SDK build compiled with iOS 7 Beta SDK is coming soon.
Fixed Issues:
3613819: [iOS7] On using Sound.play app asks permission for accessing the Microphone even when microphone API is not used in the app.
About the Beta Channel
If you would like real-time notification for announcements related to the AIR Beta Channel, please subscribe to our Twitter feed @FlashPlayerBeta, or follow the Flash Runtime Announcements forums by choosing "Follow this forum" from the right-hand menu on the Forums page.
You can find instructions for getting started with this release here: AIR Labs Page
We encourage you to let us know what you think on our AIR Labs Forum

AIR runtime and AIR applications built using Captive Runtime still need Admin Privilege to Install

I am working on a small project to install AIR application(native .exe & .dmg) with AIR runtime without needing the Administrator privilege so I used Captive runtime but the installation is still asking for admin privilege
I bundled AIR application with AIR runtime using Captive runtime from flash builder 4.6, then I packaged this into a .MSI using Advanced Installer. Now when I install it for a user without admin privilege it prompts me for Admin credentials.
Can you please tell me if
1. I need AIR distribution license to install AIR runtime without Admin privilege
2. Do I need a different installer
3. Am I missing any step here
Thank you

If you're installing to a location where Windows requires elevated privileges, like Program Files, you'll need to have admin privileges to continue. Are you using an AIR based native installer or have you taken the application with the captive runtime and rolled this up in your own installer?
Here's a section from the Installation and deployment options in Adobe AIR 3 article that might help:
Installation privileges
When designing an installer, one has the option to choose from approaches that may or may not require administrative privilege. For example, a drag-and-drop install on Mac OS X requires no special privilege; users can always copy the application into their own application folders, for which they have the necessary permissions. On the other hand, if registry keys must be written to the machine-specific portion of the registry on Windows, installation of that application will require administrative privilege to do so.
The two installer formats directly supported by AIR, AIR files and native installers, have always required administrative privilege. This was a design decision made in part to simplify the implementation of the AIR installers: If administrative privilege is assumed to be available, implementation is possible if the registry can be written to, and so on. It was also selected because, in many enterprises, this is the desired behavior: administrators can use the privilege requirement to gate software installation.
All the same, there are scenarios where supporting installation without requiring administrative privileges is desirable, or even necessary. This can now be achieved using custom installers; you simply need to author an installer that operates correctly with only standard user privilege. In practice this can be easy to achieve; a simple install-by-copy to a writable location (that is, in the user's own folder) will suffice. Should you author a more complex installer, you should keep in mind that the addition of certain operations during the install process will in turn reintroduce the requirement for administrative privileges.

After installing Version 5 I get an error message about incompatibility and min and max versions.

I shutdown Zone Alarm, and deleted the contents of the file, which contained the "exe" file, then reinstalled Firefox version 5.0. I still get the XUL Runner error message about incompatibility of Version 5.0 with min and max 5.0.1. What next?

The updater wasn't able to update all the files and some were left as older versions.<br />
You need to do a clean reinstall.
Download a fresh Firefox copy and save the file to the desktop.
* Firefox 5.0.x: http://www.mozilla.com/en-US/firefox/all.html
* Uninstall your current Firefox version.
* Do not remove personal data when you uninstall the current version.
Remove the Firefox program folder before installing that newly downloaded copy of the Firefox installer.
* It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
Your bookmarks and other profile data are stored elsewhere in the Firefox Profile Folder and won't be affected by a reinstall, but make sure that you do not select to remove personal data if you uninstall Firefox.
* http://kb.mozillazine.org/Profile_folder_-_Firefox
* http://kb.mozillazine.org/Profile_backup

7/16/2012 - AIR 3.4 Runtime and SDK Beta 1

The beta 1 release provides access to the AIR 3.4 runtime and SDK for Windows, Mac OS, iOS and Android. The key features and benefits of AIR 3.4 are:
iOS 5.1 SDK Support — Build your AIR on iOS applications by default with iOS 5.1 SDK (without using the --platformsdk switch) and leverage the enhancements available in iOS 5.1 SDK.
Exception Support in Native Extensions for iOS — A native extension for iOS can now use both C++ and Objective-C exceptions.
iOS Push Notifications — This feature will use APNS (Apple Push Notification Service) and a provider (third-party server which will communicate with the APN) to generate notifications.
AIR direct deployment (without iTunes) — Deploy an AIR application on iOS devices without having to use iTunes or the iPhone configuration utility.
You can find instructions for getting started with this release here: AIR 3.4 Labs Page
We encourage you to let us know what you think over on our AIR 3.4 Labs Forum

Excellent, glad you were able to get this to work! Had you tried right clicking the installer and doing a "run as administrator"?

LabVIEW 8.6 Runtime and MAX installation

Similar Messages

Maybe you are looking for