Maximize Compatibility option to save for earlier versions?

1. Where is the Maximize Compatibility option in CS6 to save to earlier versions?
2. Does this option still exist in CC? If so, how is it enabled?
Thanks.

Ctrl or Cmd k to open your Preferences, go to File Handling, then right at the bottom of this section:

Similar Messages

  • Labview 7.1 crashes windows XP when using VI's saved with the 'Save for Previous Version' option available in Labview 8

    I am trying to work with a series of vi's developed in Labview 8 in Labview 7.1.  The code was saved with the 'Save for Previous Version' option available in Labview 8.  When trying to use the code in LV7.1 my entire Windows XP system locks up (cursor freezes).  Are there any ideas what's going on and how to fix this?
    Thanks for your help!
    Mike

    I have seen some problems with the save for previous option in the past. Instead of saving the entire hierarchy, try seperating the code into several different pieces and saving each piece individually. Then, see if you can open the different pieces in 7.1.
    If that doesn't help, you should post some more details, like when exactly does it lock up, does it have things like DLL calls, and maybe attach the code.
    Try to take over the world!

  • ITunes Store option to search for "other versions" of songs?

    When searching for music, there used to be an option to search for "other versions" of the same song -- and it seems to have disappeared.  I found so many other great artists doing covers of songs!  Writing to Apple Support did not produce a response.  Wondering if anyone here knows?

    It's too bad they took away this feature.  I used it all the time to find other good versions of a song by different artists.
    I previously took multiple painful steps to go back to an earlier iTunes version when I discovered that iTunes 11 dropped the "sort" feature.  When I heard that the recent version allowed sorting, I downloaded it.  However, when they reinstated the sort feature, they apparently did not include the "other versions" feature.

  • Source Distribution for Earlier Versions

    I have a large project built in 8.6 that i'm trying to create a source distribution for. Is it possible to make the source dist. for an earlier version of labview (say 8.2)? Thanks

    Hello Paul,
    Since source distribution is a collection of all VIs that are needed for your project, you would not be able to use the VIs in 8.6 for an earlier version of LabVIEW. However, you can use Save for Previous Version of your project to save ALL VIs in an earlier version of LabVIEW which then you can create the source distribution for that particular version of LabVIEW.
    Andy Chang
    National Instruments
    LabVIEW Control Design and Simulation

  • How do I continue to save for previous version?

    Hello. I am currently using LabView 9.0 32-bit, Windows 7. Unfortunately, my university uses Labview 8.6.1 32-bit, Windows Vista Business. First, I tried to open my VI's which I started at the University and modified on my machine back on a university machine. I received an error stating that the files were saved with a newer version of LabView and could not be opened. I went home, and opened the VI's again and used File > Save for Previous Version. This is okay, except it forces me to create a new destination folder. When I close LabView and open the VI's from this destination folder, they open up automatically with an asterisk to indicate the files have changed and require saving. Obviously this is automatically converting my 8.6 files to 9.0. This is very frustrating.
    How can I force LabView to stick with the version that the files were created or saved as? If I attempt to save the "asterisked" files for previous version, it refuses to let me. Thank you for your time and consideration.

    You must be doing something wrong, or perhaps Windows 7 is interfering. Here's the step-by-step process:
    Launch LabVIEW 2009.
    Open an 8.6 VI. It should show up with an asterisk in the title bar.
    Make some changes.
    Select File -> Save for Previous Version.
    Verify that "8.6" is selected in the dropdown.
    Click "Save...".
    In the dialog click the "Save" button to accept the default of saving the VI into a new folder called "<VI Name> Folder".
    Close the VI. When asked if you want to save changes click "Don't Save".
    Check the timestamp on the newly created file in that folder.
    Open the same 8.6 VI again.
    Make some changes. 
    Select File -> Save for Previous Version.
    Verify that "8.6" is selected in the dropdown.
    Click "Save...".
    The "File name" textbox should have the same default name as previously. If you click "Save" Windows should move you into that folder, and the save dialog should remain open. The file listing should contain the VI.
    Click on the "Current Folder" button. You should get a dialog warning you that the operation will save over existing files. Click "OK" to continue. The VI will be saved as the previous version over the previous save that was done. To verify this, check the timestamp on the file.
    I just did the above on LV2009 running under XP just so I could get the button names correct.
    You can repeat steps 10-16 as many times as you want without needing to create a new folder.

  • 8.2.1 save for previous version

    I have a few problems with Labview 8.2.1 "Save for Previous Version" for use with a computer with Labview 8.0.
    1-Labview 8.0 does not see the VI (created by 8.2.1 that was saved for previous version 8.0) as an 8.0 VI.
    it complains:
    "The VI, last saved with LabVIEW 8.0, has been converted to version 8.0.  After a VI has been saved with LabVIEW 8.0 it can only be loaded by LabVIEW 8.0 or later.  Use Save for Previous Version... to save VIs for older versions of LabVIEW."
    2-I can't Reset the History to zero.  The history resets only down to 1.
    3-Save for Previous Version will not save only the one VI specified, it saves a bunch of VIs.  I have to pick out only the changed VIs and place them with the unchanged 8.0 VIs.  Is there a way to just save a single changed file as 8.0?
    Are these problems that were fixed in later versions of Labview, such as 8.5.1, 8.6 etc?

    Gaslight wrote:
    So keeping a copy of Labview 8.0 for an unspecified length of time means keeping one or more computers running Windows XP for an unspecified length of time.  Labview 8.0 will NOT run under Vista or Windows 7.  This also means the computers runing Labview 8.0 will no longer remain on out company LAN.  They are eliminating all computers running XP.
    I will be forced to order fewer copies Labview 2010 upgrade.  Less money for National Instruments.
    You could use the included VM version of xp in windows 7 if you needed to, but it runs really horribly.
    You could also keep a VMware image of XP on a computer.

  • Save for previous version (8.6 to 8.5) including dependencies

    Hello everyone,
    Once again please forgive me if I use the wrong terminology as I am very new to Labview.
    Here is what I am trying to do. I have a project written in Labview 8.6. It has a number of files and some dependencies (which include .lvlib's .lvlclass's and some .vi's). I need to save this project as a previous version (8.5) and send it downstairs to the lab. I've tried to save it as a previous version using the the project explorer: file->save for previous version. When I zip up the project folder and send it to the lab and try and run it on 8.5 it says there are missing files. Specifically:
    NI_report.lvclass
    NI_reportGenerationCore.lvlib
    NI_HTML.lvclass
    NI_StandardReport.lvclass
    I am not creating an executable as they need to be able to make some minor changes to the code. Both computers have the full Labview development suite. Also there is no chance that the lab can simply upgrade to 8.6 from 8.5 as these upgrades are scheduled by another department.
    Is there any way to save this project so that it includes the dependencies that are missing in the project folder? I'm sure there must be a simple solution but I can't seem to get it to work.
    As always any suggestions or advice is greatly appreciated. Please let me know if there is any more information I can provide. Also please feel free to tell me what I'm doing wrong as I'm keen to understand why what I'm trying to do isn't working.
    Cheers,
    Alex
    Alexander H. | Software Developer | CLAD

    Yes the toolkit is installed on the computer in the lab. I was able previously able to work on this project on either computer and only had problems once the upstairs computer was upgraded to Labview 8.6.
    Alexander H. | Software Developer | CLAD

  • Is there a way to package an InDesign CC book for earlier versions of InDesign - CS5 specifically?

    Is there a way to package an InDesign CC book for earlier versions of InDesign - CS5 specifically?

    You have to export the individual files to .idml, open those in CS5 and add the CS5 versions to a new CS5 book.

  • Where I can find documentation platforms (operating systems) CERTIFICATES for earlier versions of ASE (15.5, 15.0, 12.5, etc)?

    Hi....
    Where I can find documentation platforms (operating systems) certificates for earlier versions of ASE versions of ASE (15.5, 15.0, 12.5, etc)?

    The detailed certification information that used to be available on the Sybase web site is not currently externally accessible since SAP decommissioned the site - all that is currently available is the basic information in the SAP Product Availability Matrix (PAM) and the base release information available in the ASE documentation.
    ASE support is looking into ways of restoring external access to the certification reports, possibly here as SCN documents or on the SCN wiki.  I don't have any estimate for when this will be available, though.
    If you have a support contract, you can open an incident to ask about specific versions/platforms; we still have internal access to the reports.  If the support engineer doesn't know how to access the reports, ask them to get in touch with me.
    -bret

  • VBAI2011 Save for Previous Version option

    Hello,
    Since VBAI 2011 is one of NI products, I am curious that it has an option of Save As For Previous version like Labview, or is there any way around it?. 
    I currenlty have running Labview 8.6 in my systems which doesn't work well with VBAI 2011. What I have done is using Labview 2012 evaluation version to re-save my VI 8.6 till to 2010 version. I am thinking an option of down-grade my VBAI if possible.
    Thanks.
    Hoa Huynh
    University of Minnesota

    Not sure if you're aware, but you can use the Vision Builder API in LabVIEW to control an any version of VBAI 2010 or greater with any version of LV 8.5 or higher. There is a shipping example located in your Vision Builder AI\API Examples folder. The API has several advantages over migrating your inspection to LabVIEW, so you might want to check it out. Here is a web video of how to use the API to control VBAI, run inspections, and get the results and images:
    http://zone.ni.com/wv/app/doc/p/id/wv-2424
    Hopefully Vision Builder will eventually support saving for previous, but until then, using the API allows you to use a variety of LabVIEW versions with a variety of VBAI versions.
    Hope this helps,
    Brad

  • Looping options in Save for Web - Animated GIF

    I find this one rather annoying, in the latest verison of Adobe Photoshop CS6 when creating an animated GIF via the Save for Web dialog box; there is a looping option section that allows your animation to loop forever, or once...
    In the previous version, it would remember which setting you selected for subsequent saves.  In this new version, it forgets it and always defaults to ONCE; where I want FOREVER... making me forget to check it sometimes, when I'm working fast; and create animations that stop after one loop...
    Anyone else experience this annoyance?
    -Joe

    Seems like people shouldn't have to re-request features that were already features in the last version. 
    Either Adobe took the "stickyness" of that setting out on purpose, in which case I'd expect nothing more will be done, or they left it out accidentally with the restructuring of the Timeline window, in which case it would be a bug, no?
    But Christoph is right in either case - you can help ensure it is seen by posting it on the http://feedback.photoshop.com/photoshop_family/ site.
    -Noel

  • Save to Earlier Version (FLV)?

    I created a movie in Flash CS3, and uploaded the swf/flv
    files to my server.
    Everything plays fine in all my test browsers, but the client
    says she is seeing a 'flashing red icon' where the movie should be.
    She's viewing on Mac Safari (Flash version 9.0.20).
    Searching through this forum, it appears that the problem is
    that her version of Flash is not high enough to view my files.
    What I would like to do is save the movie to an earlier
    version (7? 8?).
    But when I change the 'Flash Player' in the 'Publish
    Settings' to version 8, I get the following error message...
    WARNING: The component 'fl.video.FLVPlayback' requires
    ActionScript 3.0.
    I'm fairly new to Flash so I'm not sure what this means.
    I would really like to save the file at 'version 8' (or even
    'version 7') if at all possible.
    * the movie is pretty simple, so if I need to start from
    scratch I'm willing to do that.
    Thank you very much for your advice.
    :Stacey

    Thanks! - That makes sense.
    For anyone who may be reading this later...
    - The problem was that I created a new 'Flash 9' document,
    and imported a movie into it.
    - I had changed the Publish Settings to 'Flash 8', but that
    only applied to the swf file. The FLV file was still 'Flash 9'
    format.
    - The solution was to start over (or delete the movie) and
    import the movie while the document settings were set to 'Flash 8'.
    Thanks again :-)

  • Quick Trim option in Save for Web & Devices

    Hi,
    a feature to do a quick Trim in Save for Web & Devices dialogue would be great, especially if it was enabled with a checkbox, then when you enable it, it activates a dialogue with the three options that already exist in Trim option (Transparent pixels, Top left color, Bottom right color).
    Let me know what you think.

    I need to figure out why my trim option is always grayed out. It's saved in PSD format, yet the option to trim the transparent pixels is grayed out. why is that? what am I doing wrong? I must have to change something.
    Thanks in advance, Linda

  • Bug in LV8 : 'Save for previous version' and 'Write to Binary File' VI

    Hello
    I am using LabVIEW 8's revamped 'Write to Binary File' VI with a 'TRUE' boolean constant wired to the optional 'prepend array or string size?' to write non-trivial structures to a binary file. I then read the file with the 'Read from Binary File' VI and everything is fine. I don't wire anything to the 'file (use dialog)' input (don't know if this can help).
    However, after saving my VI for LabVIEW 7.1, I cannot read the binary files created with the LV7 version of the VI anymore. After examining the LV7 converted version of the VI, there is a 'FALSE' boolean constant that is wired to the equivalent of the 'prepend array or string size' input, which breaks the binary format that is expected.
    The attached files are LV8 and 'saved for LV7' versions of a dummy VI that writes an array of 5 integers into a binary file. To test the bug, start LV8, open the LV8 version, run it and create a 'test-lv8.bin' file, then open the LV7 version, run it and create a 'test-lv7.bin' file. Check the content of the two files : the size of the array is indeed missing from the 'test-lv7.bin' file, which can be assimilated as a bug in my opinion.
    I think I found another one too : if in LV8 I wire the 'cancelled' boolean output of the 'Open/Create/Replace file' to the selector of a case structure, the 'converted to LV7' version VI will have an error, saying the Case Structure selector is not wired.
    Could someone please confirm these are indeed bugs ?
    Thanks in advance and have a nice day.
    Eric Batut
    Attachments:
    Test Binary File v7-v8 LV7.vi ‏15 KB
    Test Binary File v7-v8 LV8.vi ‏7 KB

    I'm using LV8.6 and need to read a .bin file created in MATLAB. This file obviously does not contain the 4 byte header that LabVIEW prepends .bin files with. So when I use Read from Binary File, I get no data (I'm trying to read an array of doubles). I've tried making my .bin file both in native and big-endian format and changing the representation (double, int64, float64) but none of this works. I noted that if I create the same array in a .bin file in LabVIEW and wire a FALSE to the "prepend array or string size?", my VI for reading .bin files can't read this file either.
    Any work-arounds here?
    (I'll try attaching my write & read VI's)
    Attachments:
    ReadWriteBinFile.zip ‏19 KB

  • HT4623 if i am unhappy with new software then how to go for earlier version

    if i am unhappy with new software the how to go for earlier version

    Sorry, Apple has no approved method to downgrade the version of iOS on your iDevice. You can voice your displeasure with the iOS by leaving feedback at the appropriate subsection from the link below.
    http://www.apple.com/feedback/

Maybe you are looking for