What to do with old versions?

Every time I install a new version of production Premium, the old one is still there. Is it safe to uninstall the old ones, or do they share common components?

I agree with piprod. This is a tedious if not time and computer memory consuming  transition from CS4:CS6. I have XMP templates and actions that I do not want to loose when I do get around to uninstalling the older version of the CS4. Should I just manually extract these files onto my MAC OS X6.x desktop? Will uninstalling the other CS4 programs like Acrobat and Dreamweaver create mayhem or will I get some space back and a seamless transition?

Similar Messages

  • What to do with old versions of iLife and iWork

    Hi,
    I just now upgraded to Mavericks and subsequently updated all of my Apple apps. I now have dedicated folders for some of the older apps. I'd like to preserve hard drive space and was wondering if I could delete the previous versions without any harm done? Thanks in advance!

    Do not be in any hurry to delete the old versions.  The jury is out on the new iOS type Pages and Numbers, which have one or two functions omitted.  I personally am fully in favour of having iOS7 and Mavericks apps the same, for familiarity sake, but others miss Mail Merge for one thing and Header/Footers in Numbers.  I don't use these and there are ways around the problem.
    Also note that once a document has been saved in the new version, it cannot be opened in the old one, so be careful.

  • Addons - new versions of addon with old versions of B1

    Hi guys,
    Does anyone know if new versions of addons work with old versions of SAP B1?
    I have a client who is asking for the latest Payment Engine (PL70) but they are on SAPB1 2005A SP01 PL12 which has the Payment Engine PL30.
    My thinking is that you will need to upgrade the B1 app to PL34, if you want to use the latest addon?
    or am i way out and infact the addons work independently of B1 and will therefore work on an old patch of B1?
    TIA,
    John Treweeks

    Hi John,
    Patches are bug fixes and do not change functionality (unless the functionality was broken of course ). Addons communicate through the UI and DI APIs which are installed as part of the patch. Therefore, the theory should be that addons are pretty much patch independent.
    But, as has been pointed out above, it's really difficult to predict exactly what results you'll get. I guess sometimes an addon patch could have been released in order to correct a problem that was both addon and DI API related. In that case, you'd need to install the addon patch and the SBO patch.
    I never recommend you go to the latest patch until it has been around for a few weeks. However, going to a patch that is dated just prior to the addon patch release sounds like a sensible policy. In any case, testing is vital, prior to installation on a production site.
    Kind Regards,
    Owen

  • How do i remove the songs from my iphone used to be easy with old version of itunes just unticked them but cant seem to find it any where on new version

    how do i remove the songs from my iphone used to be easy with old version of itunes just unticked them but cant seem to find it any where on new version

    how do i remove the songs from my iphone used to be easy with old version of itunes just unticked them but cant seem to find it any where on new version

  • HT202879 How can I open a file made with old version of Pages (before 09)?

    I need to open a file made with old version of Pages (before 09).  How can I do this?  I only have iworks Pages free with Mac Book Pro.

    You need either Pages '09 or the original Pages '08? programs.
    With Pages '09 you simply open it and it accurate converts it to Pages '09. Pages 5 will open the Pages '09 version but may alter/damage the file.
    With Pages '08 you Export it to Word .doc/.docx with mixed results, then open that in Pages 5 which may alter/damage the file.
    Peter

  • What to do if old version of Quick time does not remove?

    What to do if old version of Quick Time is unable to be removed to receive update?

    What is the version of QuickTime currently installed on the computer? Can you be a little more precise on what you've tryed and any error messages you may be getting? It could be anything from windows administrator permissions, an old windows installer msi file, to a simple setting

  • What's wrong with old applet tag?

    Hi there,
    What is wrong with old <applet> tag? It will stop displaying java applet in the new browsers? What do we gain by using <embed>?
    Thanks.
    Mike

    The applet element was deprecated in HTML 4.01 but still works. Continue to use it to display AWT applets in NE else if using SWING applets must to use EMBED. See Java documentation for details, in special the OBJECT tag chapter..better reading about HTML converter.

  • Problems with Old version of iTunes!!!

    After finding out that my AOpen DVD drive is not compatible with ITunes version 6, I downloaded version 5 from oldapps.com. When I try to play a song or burn a cd, it tells me that my computer is not authorized. After authorizing it, a message says: "This item (song) requires a later version of ITunes to purchase". Of course I've alreay purchased these songs and simply want to play or burn them. Also, I have not authorized my songs on any computer but mine. Is there anyway to play and burn songs I've recently downloaded using an old version?

    DON'T UPGRADE!!! If you have seen any of the discussions regarding 7.5, and there are too many to count, you will know why. I avoided upgrading, the whole "if it isn't broke" theory, until I tried purchasing some new music and I was prompted that I had to upgrade in order to get the new music. I upgraded and now I can't burn the music I purchased. Trying to burn causes my computer to "crash". I've spent countless hours trying to figure this out, and frankly I'm afraid to connect my iPod for fear of what will happen to that. Read through some of the discussions regarding 7.5, I think you'll choose not to upgrade.

  • Ingest new version with old version archived - Revisited & solved

    I couldn't react to the old thread anymore, but I'd like to share the solution with this forum, because it shows the power of the default functionality in the system.
    Start situation: asset is archived, new version comes in, overwrite is set to 'on'.
    What happens and could happen afterwards: new version 'takes the place' on the hard drive of the old version, new proxies are created, the archive flag on the asset is still on. A restore would place the old version back on the hard drive erasing the new version. No new proxies are created, so original asset would be old version, proxies are from new version. New version - Original Media is lost.
    So this is how I solved it:
    I created a subscription - event type = modified - in which the Asset Filter is set to:
    Archive Status EQUALS Offline
    File Modification Date: the Trigger-if-changed box is ticked.
    The response is changing the status of the asset to 'New Version'.
    A second subsription - event type = modified - has the Asset Filter set to:
    Archive Status EQUALS Offline
    (Asset) Status EQUALS 'New Version' with Trigger-if-changed box ticked.
    The response is:
    1. changing the status to 'Completed'
    2. duplicating the file to another device, "Archive_Exchange" (no Asset, no Proxy created)
    3. restoring the (old) file from the archive.
    A third subscription - event type = modified - is subscribing to a job:
    The job filter is:
    Title CONTAINS 'Restoring'
    Owner EQUALS 'admin'
    Status EQUALS 'DONE' - Trigger-if-changed box is ticked
    plus definition of FROM and TO devices.
    The response is:
    Scan the device "Archive_Exchange"; the only metadata which is set here is:
    Metadata Set equals 'Media' and status equals 'New Version'. No proxies needed.
    Subscription #4 - event type = created - is looking for the newly created asset on 'Archive_Exchange'
    So filter is: Metadata Set EQUALS Media, Device (Stored On) EQUALS Archive_Exchange and status EQUALS 'New Version'.
    The response is this time exactly the same response as when this new version had come in while the old version was not in the archive. So it's copying the new version in the usual device, overwriting the old version and that's it! To keep the temporary device Archive_Exchange clean, there is also a delete response.
    It's a little bit 'Working-around-the-bugs', because why is the system copying the new version to another device, while it knows the Original Media is in the archive, but still, it works and the beauty is: no scripts needed!
    Thanks for your input; it made me understand processes better so I could create this monster.

    There are two basic paradigms that you can use to interact with Final Cut Server files.
    One is to let the filesystem be the master. With this, the original files are sitting in the filesystem, and anyone with permissions can mess with them. FCSvr can see changes (via scans) and update itself accordingly. File names must be unique for anything stored in the same directory.
    The second method is to let FCSvr be the master. In this, you don't mess with the filesystem--all file interactions are done indirectly like through watchers, uploads, and archiving/restoring. File names must be unique, unless you create the device as a contentbase device type.
    Each method can make sense at different times. Generally the second is the safer approach, but the first makes sense like for FCP capture scratch folders and production scans.
    If you upload an asset directly to the FCSvr client application, it will provide you with a dialog box to prevent you from overwriting an existing file if there's a name conflict and it's not a contentbase device. (Nick, it will prompt you even if the old file is archived.)
    If you choose to overwrite, the original asset will be deleted and any archive device instance will be orphaned. If that's what you're doing, I don't understand your issue since you told it to overwrite.
    But if you've mixed paradigms by going behind FCSvr's back (via the Finder or Terminal) to copy a new media file into a place that FCSvr knew was reserved by an archived file and would have prevented had you done it through the client app, then you're asking for trouble.
    Your solution options are: use unique names for files, store them in subfolders that are scanned, or store them in contentbase devices. For the first two you can use the project name or number to help make the file names/folder names unique.

  • Ingest new version with old version archived

    Does anyone knows a solution for this:
    My original asset is archived - a new version is ingested - setting is to overwrite the old version.
    Final Cut Server is saving the new version on the local storage, leaving the version in the archive untouched. Proxy and thumbnails are created from the new version.
    In this situation many functions are greyed out. Actually the system sort of only allows the user to restore the asset from the archive.
    Restoring is overwriting the new version with the old version from the archive leaving the proxy and thumbnails as they are.
    So now situation is: old version of original file on the local drive, we lost the new version all together, proxy and thumbnails from new version.
    This is all very unwanted - any solutions?
    Thanks, Henk

    There are two basic paradigms that you can use to interact with Final Cut Server files.
    One is to let the filesystem be the master. With this, the original files are sitting in the filesystem, and anyone with permissions can mess with them. FCSvr can see changes (via scans) and update itself accordingly. File names must be unique for anything stored in the same directory.
    The second method is to let FCSvr be the master. In this, you don't mess with the filesystem--all file interactions are done indirectly like through watchers, uploads, and archiving/restoring. File names must be unique, unless you create the device as a contentbase device type.
    Each method can make sense at different times. Generally the second is the safer approach, but the first makes sense like for FCP capture scratch folders and production scans.
    If you upload an asset directly to the FCSvr client application, it will provide you with a dialog box to prevent you from overwriting an existing file if there's a name conflict and it's not a contentbase device. (Nick, it will prompt you even if the old file is archived.)
    If you choose to overwrite, the original asset will be deleted and any archive device instance will be orphaned. If that's what you're doing, I don't understand your issue since you told it to overwrite.
    But if you've mixed paradigms by going behind FCSvr's back (via the Finder or Terminal) to copy a new media file into a place that FCSvr knew was reserved by an archived file and would have prevented had you done it through the client app, then you're asking for trouble.
    Your solution options are: use unique names for files, store them in subfolders that are scanned, or store them in contentbase devices. For the first two you can use the project name or number to help make the file names/folder names unique.

  • Pages 5.2 documents unsuccessfully try to open with old version 4.3

    I understand that I have two version of pages, new (5.2) and old (4.3), with separate icons in my Applications folder.
    The way it has been working is this:
    • If I opened an document created with Pages 4, it prompted me to automatically update with Pages 5.
    • Documents created with the new Pages 5 could be opened, as expected, by just double clicking. The document would pop open with Pages 5.
    Now, for some reason this is happening:
    • When I try to open a document created with Pages 5 by double clicking I get the message: "You need a newer version of Pages." If I right click the document I can select "open with." The window show "Pages (default) (5.2)" at the top and Pages (4.3) right below. I select "Pages (default) (5.2)" and the document opens.  It seems that my comuter is using the old version of Pages as the default, even though, according to the "open with" window, Pages 5.2 is the default.
    • When I open a document created with the old version, it opens using the old version and no longer prompts me to update it to the new version.
    Is anyone else having this problem?  Any suggestions. 

    Try this. Select (but don't open) a document created with the new Pages. Press Command-I. Under "Open with", select Pages 5.2. Click on "Change All".
    An alternative to try is to move the old Pages app to another folder. Do not delete the old Pages - you may need it later!
    Be aware that once a document is converted to the new Pages format it will not open with the old Pages (unless you specifically export it in old Pages format). I mention this because the new Pages lacks features found in the old version and this might be a problem for you.

  • New version of safari won't work on mac 10.7.5, can't be removed, can't be replaced with old version

    new version of safari won't work on mac 10.7.5, can't be removed, can't be replaced with old version

    When I try to open safari a message says: You can't use this version of the application Safari with this version of Mac OS X 10.7.5. The application requires Mac OS X 10.9 or later.
    I see Recovery needs Wi Fi which is not available here and Recovery is loaded with a list of  potential disasters.
    To heck with Safari I'll just use Firefox. Apple sure screwed up here judging from the multitude of similar complaints on the internet.

  • Serious problem with old versions of sub-vi's installing on application upload

    Hi
    I am having a series problem which is proving wildly frustrating.
    I have recompiled an application but when I upload it on the host computers the host computers seem to upload old versions of the code even though they have been deleted.
    I smell a Windows Cache problem but can't see how to get round it.
    Anybody have any ideas.  If not should I shoot myself before or after I get fired?
    Either way help appreciated
    Ash

    Hi Ashley,
          I've been compiling and deploying LabVIEW applications for a long time, and never seen a windows-cach problem!
    Here are a few (of my) mistakes that resulted in execution of old code:
    Forgetting to update the Top-level VI in the .bld, after the top-level VI's location changed.
    Compiling to a different location than the one I copied the "new" EXE from.
    Compiling with Installer option, then switching-off Installer option (for faster compiles), then, post compile, instead of copying new EXE - doing an Install and installing old EXE!
    After copying or installing new EXE to host, forgetting to update menu-options and "shortcuts" - which still point to old EXE.
    Some ideas:
    Write a new/unique version# to the Main VI's Window Title (VI properties), so you can tell quickly which version is running.
    After compiling, pay close attention to the creation time of the "new" EXE to be sure it is new.
    After copying or installing, launch the new EXE by double-clicking on it (don't trust existing shortcuts.)
    Cheers!
    "Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

  • What to do with old ATC?

    My Airport Time Capsule (purchased April 2009) has apparently died.
    A 'factory reset' results in a green light, then flashing amber, then solid amber, then the LED goes dark.  It never appears in Airport utility during this process.
    I was using it mainly for backup and don't need a wireless router, so I bought an external hard drive to serve that purpose.
    So what do I do with the old ATC?  I don't know if my data is still on it or not.  I hate to throw it in the trash.  Is it recycleable?  Is it worth anything to someone with the know-how to fix it?  If they fix it, will my data be exposed?
    I just don't know what to do with it now.  Any suggestions?

    You were right.  Power supply was dead.
    I've never done anything like this before, but thanks to the link you provided with instructions, I opened up my time capsule.
    I have no way to wipe the hard drive, so I decided to take a chance on replacing the power supply.
    Ordered one on eBay ($79.95) and installed it.  Time Capsule powered up and is running fine.  It runs really hot so after reading about all the issues with the design, I decided to leave the rubber mat off the bottom and got some 'feet' for it so it doesn't sit flat on the shelf.
    I wiped the hard drive and started my Time Machine backups again.  I really prefer the 'wireless' backup to the TC rather than having the USB hard drive plugged into my Macbook Pro for backups.
    If I can get another 4 years out of it, it will be well worth it! 
    Thanks again for the advice!

  • Important! search function for everybody with old version 5G ipod video

    Hey everybody. A lot of people want to have a search function on their old version ipod video, as do i. But an update fixing the problem is not in the apple planning. So i called tech support and they made a request to apple for me, telling them that such an update is wanted. But they won`t act on it until they have enough requests. So i`m asking everybody with this problem, and perhaps also people who just want to help, to call tech support (not the apple store) and make a request to apple for them to make this update. If a lot of people do this hopefully we`ll get the update!

    You can send feedback to Apple here;
    http://www.apple.com/feedback/ipod.html
    I don't know if the can or will add this feature, but
    it doesn't hurt to make the suggestion using the
    proper feedback channels.
    Cheers!
    -Bryan
    Good idea.. I'll do this.
    thanks.

Maybe you are looking for