Standard.js...is this file backward compatible?

I am importing a number of Captivate files into my RoboHelp project. The files were generated using at least two different versions of Captivate. (Maybe more!) It appears that the standard.js file that comes with Captivate-4-generated files is quite different than the earlier one I was used to seeing. (11 KB vs. 1 KB.) When I did a further search in the help projects, I discovered standard.js files of several different sizes (1, 2, 10, and 11 KB).
The newest Captivate files were not compatible with the older standard.js. Can anyone tell me if the newest standard.js is backward compatible? That is, if I use the new Captivate 4 standard.js, will all my older Captivate files run properly? (I hope the answer is "yes," because we group our Captivate files in a single folder with a single standard.js file.)
Also, can you verify that the standard.js file is associated with the Captivate version, rather than being specific to the particular set of Captivate output files? I work on the RoboHelp end, and I don't have Captivate, myself, so I can't look.
Thanks for any insight.
G.

Hi G
I just finished some testing. It would appear that things are Forward compatible but not backward.
I created a project using Captivate 2, Captivate 3 and Captivate 4. I copied the version 2 project to the 3 and 4 folders and it still ran (using the JS file for 3 and 4). Same goes for the 3 project. Copied it to the 4 folder and it still ran using the JS file for 4.
I then tested the other way. A version 4 output refuses to run using a version 3 JS file. However, the version 3 output seemed to happily use the version 2 JS file.
Hopefully this helps... Rick
Click here for Adobe Certified Captivate and RoboHelp HTML Training
Click here for the SorcerStone Blog
Click here for RoboHelp and Captivate eBooks

Similar Messages

Are the "edge_includes/edge.x.x.x.min.js" files backwards compatible?

I have a case, where I include multiple animations on the same page. The issue is, that some of the animations are built with current version of Animate 1.5 and others with older versions.
Can I correct the includes in xxx_edgePreload.js of older animations to the current version of edge.1.5.0.min.js instead of edge.1.0.0.min.js?
I tested this replacement with a couple of older animations and everything seems to work just fine.
So my question is:
Are the edge.x.x.x.min.js files backwards compatible? Is it safe to assume, that older animations will work with newer edge include files or was I just lucky with my test examples?

Hi, Elaine
I have tried loading both 1.0.0 and 1.5.0 runtimes on the same page before I posted the question here. And it usually fails. I say usually, because in some rare cases it kind of works, but not exactly as expected. Animations don't animate as they should or mouse events don't work as they should. Also JS console is swarming with warnings (even more than usually)
On other cases when the animations don't even start, there is some fatal error in the javascript. Different error, depending on the animations and the order I include them in the javascript. After observing the stack trace where the error happened I noticed, that in that single stack there were function calls from 1.0.0 and 1.5.0 - jumping from one version to another. And the error was always connected somehow with "window.[some_property]".
With all the above information on the table I can only assume that there comes to name clashes and polluting of "window" instance. Given the runtimes are obfuscated, debugging is practically impossible and even out of the scope of my problem solving here I think.
Of course I allow the possibility that I'm doing something wrong. So Elaine if you could provide me with a working example I would appreciate that and I would gladly explore it.
Best regards.

Are template files backward compatible?

Are template files I (INDT) backward compatible? In other words say CS3 to CS2 or perhaps CS3 to CS1. I know about using INX files but the info out there about template backward compatibility is slim.
Thanks!

There are only two differences between a regular document and a template: Default opening behavior and previews. Regular documents open as originals by default and store a preview only of the first page. Templates open by default as an untitled copy to protect them from accidental overwrites, and will store a preview of every page. You can convert the opeing behavior, but not the preview complement, from one to the other just by changing the file extension.
Peter

Are CS5.5 files backwards compatible?

I know I won't have the neat features of 5.5, but can I at least open and mess with the code in Dreamweaver cs3 when the file was saved from CS5.5? Simple question, but can't find anything in the search about this.

Yes. HTML is HTML, and same goes for CSS, JS, PHP, .NET, etc. The code will remain the same. But as you pointed out the neat features won't be there. So while Spry will be editable you won't be able to edit it using the GUI in DW (if you download the Widget browser that's another story). And it will be the same whether it is Mac or PC too so there is really nothing to worry about.

How far are iMovie files backwards compatible?

Last night, I tried to create a project similar to something that I had done before--creating an iMovie from old analog 8mm videotape, using my Digital8 camcorder as a Firewire bridge or A/D converter. It didn't work! Somewhere along the line, Apple must have dropped this feature from iMovie.
Long story short, I dragged my old Quicksilver G4 tower with OS 9.2.2 and iMovie 2.1.1 out of the closet, and got back up and running with the analog import. Everything is going great on that computer.
Now comes the question. This tower doesn't have iDVD. Will I still be able to move my iMovie 2.1.1 files over to a modern Mac, open up the project, and export to iDVD for burning? If not, is there a work-around?
Thanks in advance for any advice!
Curt

Hey Curt
Your comment about the Digital8 camcorder via FW not being able to import into your iMovie08 struck me as odd since I am successfully importing from my Canon HV30 through a FW400 to FW800 cross-over cable to my new iMac 27" (with FW800) running Mt. Lion and the latest iMovie 9.0.8 that is in iLife'11. I have full control over my camcorder and the import process.
But I thought perhaps the A/D converter process (from your analog 8 to dv) might be some sort of reason you couldn't get the import to work. I decided to do some experimenting on your (and my) behalf. I have a lot of Hi8 analog footage I play on a Sony EV-C100 Hi8 analog VCR plugged into a Canopus ADVC-100 A/D converter with FW400 output to the Mac. I use the S-video cable from the VCR into the Canopus with output thru the FW400 cable. In my situation the A/D converter is a box and therefore not controllable by the on screen controls in the import window so I must use my IR remote to control the VCR playback, clip locating, and stopping.
Here is what I experienced.
My Hi8 through the A/D converter to iMovie'11 worked and I was able to successfully import my footage. But without software control I had to put the Import process in Manual mode. The program recognized the connected Canopus as an acceptable DV source ("cam"). I started the VCR and in about 30 seconds the iMovie import view screen locked into my DV signal and began displaying the video. The time code numbers were off but no biggie. I could then use my remote to move the tape to the desired clip locations and click the Import button during playback and it captured the footage. However since this was an A/D converter source iMovie was not able to break clips at each camera start/stop. One long continuous clip as long as I was importing/capturing but nothing that can't be dissected into pieces for use as you edit.
I've got iMovie'06HD on this Mac too. It runs fine on Mt. Lion. I booted it up and performed the same Hi8 import "test" with the same results. Manual control of the VCR but once it was running the video displayed in the Import window and importing worked as above....one long clip until I stopped the capture.
So your Digital8 camcorder not functioning with iMovie'08 is unusual. When I encounter such things I usually go through a typical routine of repairing permissions, then rebooting the Computer and then boot up the app. Try that BUT try booting iMovie with your camera already connected and powered up in VCR mode to see if that triggers recognition as the software loads. I've encountered that before on my G5 dually and iMovie'06 once in a while.
Another thing to try is manually playing your camcorder into iMovie and see if the app will eventually lock into the dv video signal like I experienced in my test with my converter. But with a Digital8 camera & FW it should give you camera control as that is a recognized/approved camera. A friend uses his Sony Digital8 with iMovie but don't know which version he runs.
Another test you could try is use your iMovie2 program to grab a one minute test clip and save it as an iMovie project. Then bring it over to your "modern" Mac and then right click the project file to "Open in iMovie" and see what the results are. You'll most likely get an Alert notice that says your project was created on an older version of iMovie and opening it in this version will convert it so that it won't open in the old program anymore. Not an issue in your case. If this works just grab all your clips in iMovie2 without any editing, transitions, titles or anything else. Just raw clips and bring the project into 08 that way. Then you won't lose any previous editing work that won't convert.
Keep us posted.

Can Framemaker 12 save files down in Framemaker 11 and 10 ? Is it backward compatible?

Can Framemaker 12 save files down in Framemaker 11 and 10 ? Is it backward compatible?
Thanks,

> Times New Roman ... you’re probably using the Unicode version of it ...
Port a legacy font from the FM7 machine to the FM12 machine, such as Type1 Times, and convert the document to that on the FM12 machine.
This may not completely solve the problem, as FM8 and later, when opening a pre-FM8 document, appears to convert some things to Unicode code points (even to the point of synthesizing a Unicode encoding of a legacy font, see Re: Adding the Trademark symbol to a document). Saving back to MIF7 probably does not convert the code points back, and FM7 may well complain, or crash, or something.
If the problem is limited to certain special characters, like ™, there may be work-arounds, like invoking them only as Variables.
This Unicode border between FM7.2 and FM8 may prove to be one-way for many documents, rather like the spikes at the exit of rental car lots. Do not back up. Extreme document damage may result.

Is a PCI-488.2-1M card backwards compatible with the 488-1975 standard?

Is a PCI-488.2-1M card backwards compatible with the 488-1975 standard?

IEEE 488-1975 is one of the early revisions of the IEEE 488.1 stardard, other revisions include 488-1978 and 488.1-1987.
Because the original IEEE 488 document contained no guidelines for preferred syntax and format conventions, work continued on the specification to enhance system compatibility and configurability among test systems. This work resulted in a supplement standard, IEEE 488.2.
So, both 488.1 and 488.2 support 488-1975
I checked the link and it is fine, make sure you have the right web browser settings.
http://sine.ni.com/apps/we/nioc.vp?cid=1233〈=US

Photoshop CS2: "file not compatible with this version of Photoshop" error

So, I've been working with Photoshop for almost 20 years now, and lately I've been getting this error message on occasion (but not on every file) when I go to open a file I worked on just yesterday: "Could not complete your request because the file is not compatible with this version of Photoshop." I just worked on it yesterday in Photoshop. The file was saved as a PSD, and when I attempt to open it through Painter IX, that program tells me that it's not a Photoshop document. Why can't I open this file anymore, and why is it giving me this error message when I don't have Norton AntiVirus installed, and my 'maximize PSD and PSB file compatibility' is set to 'always'??
Does anyone have an idea on how I can open my file? How can I get around this, and how do I prevent it from happening again?
OS: OSX 10.4.11
Photoshop CS2
Info:
Kind: Adobe Photoshop file
Size: 394.4MB
Created: December 13, 2007
Modified: Yesterday at 3:54 PM

This is the boilerplate text I use in connection to saving to a network (please NOTE the part where it explains that normally, it does work, but that it is impossible to troubleshoot someone else's network remotely, and that's why it's not supported by Adobe):
If you are opening files over a network or saving them to a network server, please
cease and desist immediately
in the event you are currently experiencing problems with one or more files.
Working across a network is not supported.
See:
http://www.adobe.com/support/techdocs/322391.html
Copy the
CLOSED file from your server to your local hard disk, work on it, save it again to your local hard disk, close it, and copy the closed file back to the server.
Of course, the fact that Adobe does not support working across a network does not necessarily mean it won't work. It should.
Adobe's position is that there are too many variables in a network environment for them to guarantee that everything will work correctly in every network, especially given the fact that if something does
not work properly, it's probably the network's fault, and Adobe has no way of troubleshooting your network.
If you can't work locally, you are on your own, and if something happens, you're on your own. If you must work from a server, make sure your network administrator is a competent professional.
When problems arise, a lot of valuable work can be lost.

The Bluetooth low energy protocol is not backward compatible with classic Bluetooth protocol. My iPhone 4s can not find my sonny in-dash player. However my iPhone 3GS does it. Very disappointed with this. Any idea how it can be fixed???

The Bluetooth low energy protocol is not backward compatible with classic Bluetooth protocol.
My iPhone 4s can not find my sonny in-dash player. However my iPhone 3GS does it. Very disappointed with this.
Any idea how it can be fixed??????

Hello,
You are correct, Blue tooth low engergy, BTLE.(only) devices are not backward compatible with Classic bluetooth and cannot connect.
However the Apple 4S and above have Bluetooth 4.0 support.. Hardware wise it has bothClassic Bluetooth, like the 3GS, as well as Bluetooth Low Energy. There is no good reason why your 4s cannot communicate to your Sony in-dash player using the Classic bluetooth that resides in the 4S.
I know that this does not answer the why it does not work, but it should work. Do you have to somehow re-pair the new phone up to the player? Not knowing the model of the Sony it is hard to investigate.
And I hate to ask but are you sure that the Bluetooth radio is on in the phone?
JT

CS6 file "not compatible with this version of Photoshop"

We are using Adobe Creative Suit 6. Yesterday i've created a file, and today i cannot open it with any software. (Bridge shows the thumbnail but the file is corrupted.) I get the "Could not complete your request because the file is not compatible with this version of Photoshop" error. The file contains multiple layers, without any masks. Originally it was a NEF file (Nikon raw). I used vanishing point, because its an interior photo. (it doesnt relevant for the problem) I have an earlier version, where the vanishing points are defined, but the textures are missing. Main question is, how this can be??? I worked on that version for more than 2 hours. The file size is small, it's only 133.579.959 bytes (133 Mb). The image is 4288 x 2848 px, 240 DPI, RGB 8-Bit, Fogra39 ICC profile. The computer is up to date, nor the hw or the softwares are corrupted. The file saved locally, so it's not a network problem. I saved the document, and left the machine for about 15 minutes, then i went back, so the save had to be complete. (on SSD it took about a couple of secs) The biggest problem is, i have to work with a large amount of photos in Photoshop. But after this i have some bad feelings about this job. We have to create these PSD files both for ourselves and for our client for further use. (It's a huge furniture factory) The hardware has 16 gigs of RAM with an Intel i5 operating system Windows 8.1. Any ideas? (ps.: i didnt' find PSErrorlog.txt file) Oh i almost forgot. After installing CS6 my Adobe Acrobat Pro stopped working in about 2 weeks... So. The job is waiting, but we cannot wait for a long time, we gonna loose our biggest client because of a sw error?

You write this is not compatible with this version. Did you install all updates and did you update the camera raw too?

When trying to install ITunes I get: The version of this file is not compatible...

I've been trying to install a new version of ITunes on my computer for over a month now with no luck. Here's the message I get every time: "The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need an x86 (32bit) or 64 (64 bit) version of the program, and then contact the software publisher."
I had the previous version of ITunes on my system and it was working fine, except that is was having an issue with my DVD burner. It was a real bear to remove from my computer in order to upgrade. Now I can't get any version of ITunes to install. :-(
I am running an AMD Phenom IIX4 965 Processor, 64-bit Operating System. The original computer OS was Windows XP Professional 32-bit. I upgraded to Windows 7 Professional 64-bit over a year ago and didn't have any trouble with it until this last attempted update. Help!

I have the exact same problem as well. I've been having this since I tried installing the 3.0 drivers for Bootcamp drivers. The 2.2 drivers worked perfect, and I wasn't getting this error. I'm pretty sure It's something in the drivers as well, but nailing it would be very hard. It also doesn't appear to happen to everyone with similar spec'd Macs either. It's weird. Any solution to this would be really helpful. Thanks.

Firefox was working, today did not start with error message the the version of this file is not compatible with the version of windows you're running.

Computer has Windows 7 Ultimate 64bit. Firefox has run fine for over a year on this computer. Nothing was changed or updated except Windows update shows that it installed updates on Aug 19. I had computer off for week before because out of town, came back and started on Aug 18, but Firefox worked on that day. Did not use FF again till today. Today on Aug 22nd, firefox will not start, shortcut icon has changed to program not there. Exe in folder when clicked brings up error message say the version of this file is not compatible with version of Windows I am running. Firefox exe shows created Aug 20. I suspect update, either Windows or FF but lean towards windows, happened that broke things. I notice IE 10 updates, .NET framework updates and malicious software removal tool updates were installed. I have tried restarting computer, did not fix. Tried to run as admin, didn't work. I do not want to uninstall FF unless have to because of all the stuff I have in there, bookmarks, last pass passwords, etc.

Hello,
Certain Firefox problems can be solved by performing a ''Clean reinstall''. This means you remove Firefox program files ('''not the profile folder where the bookmarks are stored''') and then reinstall Firefox. Please follow these steps:
'''Note:''' You might want to print these steps or view them in another browser.
#Download the latest Desktop version of Firefox from http://www.mozilla.org and save the setup file to your computer.
#After the download finishes, close all Firefox windows (click Exit from the Firefox or File menu).
#Delete the Firefox installation folder, which is located in one of these locations, by default:
#*'''Windows:'''
#**C:\Program Files\Mozilla Firefox
#**C:\Program Files (x86)\Mozilla Firefox
#*'''Mac:''' Delete Firefox from the Applications folder.
#*'''Linux:''' If you installed Firefox with the distro-based package manager, you should use the same way to uninstall it - see [[Installing Firefox on Linux]]. If you downloaded and installed the binary package from the [http://www.mozilla.org/firefox#desktop Firefox download page], simply remove the folder ''firefox'' in your home directory.
#Now, go ahead and reinstall Firefox:
##Double-click the downloaded installation file and go through the steps of the installation wizard.
##Once the wizard is finished, choose to directly open Firefox after clicking the Finish button.
Please report back to see if this helped you!
Thank you.

Bootcamp support drivers "the version of this file is not compatible with the version of windows you are running"

Hi,
I've searched everywhere I can think of for a solution to this problem with no success. I see other people have reported similar issues and these have not yet been resolved.
I have installed Windows 7 32 bit on a new Mac Mini under Bootcamp. When I go to install the Bootcamp drivers in Windows, I get the message "the version of this file is not compatible with the version of windows you are running".
Other people have reported this issue when trying to install 3rd party software on a 64 bit version of windows but I'm simply trying to install the Bootcamp drivers on a 32 bit version of Windows.
Is it possible the Mac Mini needs a 64 bit version of Windows installed under Bootcamp? I haven't seen this requirement mentioned anywhere.
Appreciated all and any help that can be offered.

Welcome to the Apple Support Communities
That's because the Late 2012 iMac and Mac mini only supports the 64-bit Windows 7 version, so the drivers you downloaded are designed to work with the 64-bit version and you can't install them on a 32-bit version. Install the 64-bit Windows 7 on your computer

"The version of this file is not compatible with the version of Windows you're running.[...]".What can I do?

I must run a 32-bit programe on a windows 64-bit operating sistem, and i receive this message:"The version of this file is not compatible with the version of Windows you're running.[...]". I tried with Troubleshoot compatibility - didn't
work. I tried set to run in compatibility mode for Windows XP in file properties window and it didn't work. What can I do more? I
must run this programe to acces my database.

Hello qqnicol,
What program do you run?
Please contact the software provider to confirm if this 32-bit program can run in 64-bit Windows.
As some programs can only run in specific version of Windows, please download the right version of software.
Most programs designed for the 32-bit version of Windows will work on the 64-bit version of Windows. Notable exceptions are many antivirus programs.
Device drivers designed for the 32-bit version of Windows don't work on computers running a 64-bit version of Windows too.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

Windows desktop application -- version of this file is not compatible with the version of Windows you're running

I am developing on 64-bit Windows7 Enterprise using VisualStudio 2013. I created a new Windows desktop VB.net application and just created a release build of the default solution/project targeting "Any CPU". I provided the EXE to a
colleague who is also running 64-bit Windows7 Enterprise but receives the following error...
"The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see
whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."
I changed the build configuration to create a "x86" build but my colleague received the same error. Any ideas why this would be happening (I checked and my colleague has .Net4 Framework installed as well)? Thank you for your time and
response!
Sunish Abraham
"The version of this file is not compatible with the version of Windows you're running.
Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."

Hi sunisha,
According to your description, you'd like to run the application in your colleague's computer.
I provided the EXE to a colleague who is also running 64-bit Windows7 Enterprise but receives the following error...
If you want to test the application, you could provide the whole Debug folder to colleague instead of the single exe.
"The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."
Check if the collegue's computer is running 64-bit windows:
Enter Control Panel, click on System and Security.
Under this, you can view the system type. This will describe whether you have 32-bit or 64-bit.
You can also try compatiblity mode.
If the program is not compatible, then you may try to install and run the program in compatibility mode.
Use the following steps:
1)   Right click on the Program
2)   Click on Properties
3)   Click on Compatibility tab
4)   Select Run this program in compatibility mode and select Windows Vista or whatever operating system the program was running successfully.
And if you still have questions, I suggest you deploy the application to the Local Network with clickOnce, then your collegue can install the application from the network.
#ClickOnce deployment
http://msdn.microsoft.com/en-us/library/t71a733d(VS.80).aspx
And also, you could recreate a new small application in your computer in Any CPU, then check if this small new application can work well in your colleague's computer. This can judge if the problem is caused by your application.
If you have any other concern regarding this issue, please feel free to let me know.
Best regards,
Youjun Tang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Standard.js...is this file backward compatible?

Similar Messages

Maybe you are looking for