File Compatibility for lower version

I have a captivate file that was made using captivate 2 , now
I want to open the file in captivate 1.
How to convert the file so that I can open it in Captivate 1.

Hi Rahul Surong and welcome to our community
There really is no way to do this inside Captivate 2. You can
look all day and you will not find the ability to Save As or
anything that will allow saving in an older format.
But all hope is not lost. What you can do is to have
Captivate 1 and Captivate 2 both installed on the same PC. Launch
both applications. Open the project in Captivate 2. In Captivate 1,
create a new blank project that is sized identically to the one
open in Captivate 2. Now carefully copy the slides from Captivate 2
and paste in Captivate 1.
Hopefully this was helpful... Rick

Similar Messages

SUD file incompatible in lower version 10.2

Hi,
I have developed an user dialog box using our sud editor in Diadem version 11.2. I tried using the same file in version 10.2 but it throws an error message of 'invalid file upload". Request someone to support on this issue. Is there any converter that can be used to convert it in to lower version.
Regards,
X. Ignatius
Solved!
Go to Solution.

Hello X.Ignatius,
Our Scripts and SUD files are generally backward compatible (i.e. a Script or SUD created in 10.2 will run in later versions of DIAdem, such as 11.2), but they are typically not compatible when a newer version of DIAdem is used to create an asset (VBS or SUD) and then using that file in an older version of DIAdem.
We add functionality to DIAdem with every release, and references to these new functions will be included in the SUD file. Thus, when the file is loaded into an older version of DIAdem it makes references to functions that are simply not available in the older version of DIAdem and it will not work with that older version. We do not spend time creating converters that would basically have to strip functions from SUD files to make them run with older version of DIAdem.
You have several options to avoid this issue in the future:
Create the SUD in version 10.2, it will work with the 11.2 version of DIAdem, but of course not make sue of the additional functionality of DIAdem 11.2.
Update the DIAdem 10.2 version to 11.2 (or later) to avoid compatibility issues.
I'm sorry to say that there is very likely no way to use your DIAdem 11.2 SUD in version 10.2 of DIAdem.
Otmar
Otmar D. Foehner
Business Development Manager
DIAdem and Test Data Management
National Instruments
Austin, TX - USA
"For an optimist the glass is half full, for a pessimist it's half empty, and for an engineer is twice bigger than necessary."

Acrobat X doing PS to PDF conversion and can view the PDF file in the Lower version?

Hi,
I am converting the Postscript file to PDF file using Acrobat X, but the end user is having the Acrobat older version. Can we use the lower Acrobat version for the viewing? Also it's under EULA?
Thanks for looking into this.
Thanks,
KSK

If you make PDF 1.7, Acrobat 6 and later can handle the file.
If you make PDF 1.6, Acrobat 5 and later can handle the file.
A little more on EULA: this is not official, but I have seen a lot of discussion in these forums about it. It seems to be that you cannot use Acrobat (or Distiller from Acrobat) as a server process, automating creation of PDF for others without the control of an individual even on a desktop.
So, if these PostScript files are made by an individual who runs Distiller, this is fine.
If the individual puts files from anywhere into Distiller that is fine.
It is not fine if PostScript files are delivered from somewhere else and automatically processed.
It is not fine if PostScript files are made automatically on this machine and automatically delivered to the file server for others to read.
Distiller is for making files for its licensed user to read, or to share themselves manually.

Coherence incubator for lower versions of coherence

Hi,
I saw that oracle has released the new version of coherence incubator for monitoring. https://blogs.oracle.com/OracleCoherence/entry/coherence_jvisualvm_plugin_released_in
We are using coherence version 3.7.1.11. Can we use the incubator to monitor the grid with version 3.7.1.11?
thanks

Forms designed with Acrobat 6 and below are called "Acro Forms". Forms designed with Form Designer 6 and Acrobat Professional 7 's Form designer are "XFA forms".
Acro Forms will still be supported for some time, but the reality is that XFA forms will be what is used in all future releases. XFA forms do have advantages, such as XML, and data packages. Just take a look at the Designer. Much more simple than Acrobat.

File system for low specs :?

Hi,
I've got a Pentium III 350mhz, 96mb ram, 3gig hdd, 3d rage pro video card. Which filesystem would be better suited ext3 or reiserfs? Mainly going to be used for server - php, mysql, apache. Occassionally be used for checking webmail & music playing.
Cheers,
dammit

ReiserFS 3.6 is very fast, even on older systems. Using the notail option with it is supposed to increase performance at the expense of storage efficiency, but I can't really see any difference in speed from using notail.
If you want speed, use a fast WM. Openbox and Fluxbox, for example, are both excellent and very fast WMs. I personally have found the speed of big desktop environments to be more dependent on RAM than CPU speed, and 96 megs is not enough for KDE or GNOME... So if you want a DE, go with XFCE and/or ROX - ROX + *box or some other WM, or said other WM + XFCE, also works (XFCE isn't as tightly integrated as other DEs). Believe me, though, with only 96 megs both Nautilus and Konqueror, never mind KDE's preloading trick, can screw you over badly.
The 3 gig HD shouldn't be a problen, unless you're planning on putting a lot of music on it.

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.

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

Programatically convert CS5 and CS6 illustrator files to lower versions

Is there a way to programatically convert CS5 and CS6 illustrator files to lower versions (CS4, CS3 etc) programatically. Are there any third party tools to do it or does Scripting let you do that.

The illustrator save options has a property for dealing with backward compatibility… As far as I know you can only do this using Illustrator…

People picker is not working for ie11 but working fine for other lower version

i am using sharepoint 2010 and windows authentication
recently i have updated my ie to ie11 and problem goes here.
when i try to select from people picker, there are an unexpected error happened
however when i use other ie version, people picker work fine, what goes wrong?
i have already added my system as trusted site
if there any others thing i miss out?

Hi,
According to your post, my understanding is that People picker is not working for ie11 but working fine for other lower version.
IE 11 is known to have compatibility issues on SharePoint 2010, please make sure to:
first of all, try installing latest update for IE 11 (several compatibility issues were fixed since the first release)
add the site to compatibility view (in IE> Tools> Compatibility view settings> type site name> add)
add the site to trusted sites and set the zone security level to low (in IE> Internet Options> Security> trusted sites> sites>add your site there> ok> custom level> select low> reset> ok)
You can use developer tools (f12) and set browser mode to the version that is most compatible with your environment.
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Is there a way to not auto-convert documents to FrameMaker 9 when opening lower version files?

Hi, All!
Is there a way to prevent FrameMaker 9 from automatically converting lower version files to FrameMaker 9 when opening them?
It becomes a problem when I just want to view the files. I have to save each chapter in the book to the lower version file again after viewing for my teammates to use them.
Thanks.

*** haven't checked, because I don't have any pre-9.0 files easily available *** ... but from what I remember, if you're really just viewing the files in 9.0 you should need to save them explicitly back to an earlier version. FM may mark the files as "changed" when it opens them, but that's because it checks things like datestamps and cross-references. If you do not, yourself, explicitly change any content in the file you have opened, you don't need to save the changes; just close the file unsaved. Check my supposition with a couple of files before relying on it! And other people will be able to give you a more detailed explanation of why file you haven't touched yourself still show up as "changed".

.llb file Lower Version Conversion

Hi,
Looking for some guidelines to convert the .llb file into lower versions of LabVIEW. The thing is we have an instrument driver project created using LabVIEW 8.6, containing public and private folders and some .mnu files as well. I can save the whole project into the lower version, for say 8.0, using "Save for Previous Version" that again compiles and saves the whole project into another folder. The newly 8.0 project I opened and found that the private folders (containing .llb files) and .mnu file in public folders are still pointing to the older location i.e. 8.6 location. I removed the 8.6 code from its location and manually added private files to point to the 8.0 location. After I create installer for 8.0 codes using project file, I installed on new machine and found that private and .mnu files are missing and therefore could not proceed further. I can understand that .mnu files won't require any conversion but wondering why my 8.0 project are considering 8.6 location at all even after manually adding all the missing files back into the 8.0 code from 8.0 location.
Please do suggest me if anyone has any idea for the same. Looking Forward.
Thanks in Advance,
Vivek

Hi,
The problem seems to be with the way the project folders are saved. There are two types of folders viz Virtual and Autopopulating. By default when you create new instrument drivers project , Virtual folders are created. You need to convert them to Auto populating folder as shown in the figure below. Autopopulating folder refrences and updates as and when you make any changes to the actual file. Whereas A virtual folder is a folder in the project that organizes project items and does not represent files on disk.
Hope that solves your querry.
Shreyas Hebbare
Shreyas Technologies
India

Conversion of CS5 and CS6 Illustrator files to lower versions programatically

Is there a way to programatically convert CS5 and CS6 illustrator files to lower versions (CS4, CS3 etc) programatically. Are there any third party tools to do it.

He's probably looking for a script to do the job. The answer is yes. There is an AI scripting forum. Check there.
http://forums.adobe.com/community/illustrator/illustrator_scripting?view=discussions

I finished adding my transtions to my timeline. I was having crashing issues so I shut down everything before I rendered the project and now it tells me that the project is unreadable or the file is too new for this version of final cut. What Happened?

I finished adding my transtions to my timeline. I was having crashing issues so I shut down everything before I rendered the project and now it tells me that the project is unreadable or the file is too new for this version of final cut. What Happened?

What Happened?
No way for us to know. But if your system was crashing, there definitely was a problem. The FCE error message you got normally indicates the FCE project file has been corrupted. This probably happened due to whatever caused your system to crash & shutting down the system.
First, make sure your system is running correctly. Then, use the Finder to navigate to /users/yourusername/Documents/Final Cut Express Documents/Autosave Vault and find the most recent backup copy of your FCE project file. Copy the file to your Final Cut Express Documents folder (copy the file, don't just move it). Then double-click the copy to open it in FCE. It should open ok, but will probably not have your most recent edits (transitions). You may have to rebuild the transitions, but at least you will be back in action.

Can't open Project - The file format is too new for this version of the pro

Hi everyone
I have the following Problem with my Final Cut Express: When I try to open a project i get an error message: "The file format is too new for this version of the program". (my FCE is in german, this is the google translation!)
I have already erased all the rendering files, but no luck.
Please Help!

Have you recently reinstalled FCE and forgotten to update it?

When exporting files to web pages Aperture keeping losing files, so for instance, if I choose to export 600 images to a new web page, it might do 524 images but not the full 600. I've tried resetting Aperture, it's the latest version etc etc. Help please!

If anyone can help me with this I would be seriously grateful.
When exporting mutliple files to web pages Aperture keeping losing files, so for instance, if I choose to export 600 images to a new web page, it might make 524 pages but not the full 600. I've tried resetting Aperture and its persmission and am using the latest version of 3.
I have 3600 images which I need to upload as sublfolders, each with their own URL and at the moment Aperture is dropping of anything from 1 to 90 images.
This is critical as people need to see each and every on of these images online. So if a file has 600 photos in it, Aperture should make a URL with 600 full image pages. And this is what it's not doing. On small files, say 30 or so it seems to work well, it's when it gets to more than that the problem starts.
I've used Aperture in the past under previous versions and not had this problem.
Any help would be great.
Thanks.
Bob.

Hi Jack,
Thanks for responding (as it seems as though no one else has been able to provide any insight as of yet)! Not sure if you saw my recent post, but the version of Aperture on the 2008 MacBook has been upgraded to 3.1.2 (not sure how; I bought it in 2009, but only have OS X 10.5.8... which apparently can't house 3.1.2 of Aperture, but hey, like many other anomalies i'm encountering, I'm no longer surprised!). I am unable to upgrade it any further, as it warns me that my OS X does not fit the requirements. I exported the projects as libraries; however, like I posted before, apparently these are from too old of a version for the new Aperture (3.3.1) to handle and import.
It's getting to the point where I'd almost pay to upgrade the OS X on my previous MacBook (10.5.8) to something newer in order to THEN update Aperture to a newer version; however, my previous MacBook simply cannot handle this (the specs are awful -- hence my decision to save up and upgrade to the newest MBP with Retina).
I've spent hours upon hours transferring files, libraries as projects, previews, versions, even masters (though, apparently some of them aren't accessible?) with no luck. I've rebuilt the library and reprocessed everything. And this is all after having to return one MBP already since Aperture 3.3.1 is glitch-y as it is, and froze everything for having a "managed library". So, now that I know that I have to deal with a referenced library in Aperture... I just need to actually transfer my previous library to my new one (hopefully WITH adjustments since these are years worth of photos and work).
Again, any help is appreciated. I've lost enough sleep, time, and vision health over this at this point.
Also, I know Migration Assistant is an option, I was told that it wouldn't work properly anyway because of the different operating systems, and the potential for problems.

File Compatibility for lower version

Similar Messages

Maybe you are looking for