Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

CaptureOne 5 doesn't start any more

Kommentare

7 Kommentare

  • Paul Steunebrink
    When CO5 does not start or crashes at startup, there are a few options
    - the program files has become corrupt
    - a .NET Framework component has become corrupt
    - the default Capture One library or session file has become corrupt
    - the user preference file has become corrupt.
    To check these issues, follow the instructions from:
    http://xchange.phaseone.com/home/Conten ... nguageid=1
    http://xchange.phaseone.com/home/Conten ... nguageid=1
    http://xchange.phaseone.com/home/Conten ... nguageID=1
    0
  • ReachingHigher
    Paul,

    Thanks. Makes sense. Windows Update tried twice to install some new .Net component and hung both times over the past couple of days. Besides the Framework 2.0 and 3.0 listed in your link I have a .Net Framework 2.5 SP1 listed two separate times. One is only 24MB and one is only 18MB in size. Can I Remove both of them safely? Would be very glad to do that.

    Thanks,
    Robert
    0
  • Paul Steunebrink
    You can remove .NET Framework components from the Control Panel, Add/Remove Programs applet. Next, you can install them via Windows Update (I prefer the Custom update, and select these components from the optional list.) I suggest you remove them all and start with 2.0. Double 2.5 entries does not sound healthy.
    This way, you can refresh your .NET components. After re-installation of 2.0 and 3.0 run the update again to add SP1 and later of these components until Windows Update does not offer additional updates.
    For references, I noted that I have .NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1 installed on my Capture One/Win XP system.

    By the way, unless you have a specific reason not to, I suggest you update to XP SP3.
    0
  • NN214646UL11
    Thanks, Paul, will do that.
    [quote="Paul_E" wrote:
    By the way, unless you have a specific reason not to, I suggest you update to XP SP3.

    I agree. Unfortunately when I tried to right after SP3 first came out it blue-screened my computer. Couldn't even boot it up in Safe mode. I had to do a Repair Install of Windows to save it. And that's after I'd successfully installed SP3 on my backup computer as a guinea pig. No one on the Microsoft forums or at Dell could tell me why or what to do.

    The main difference I see between the machines (other than my backup machine being a couple of years older, it's a Dell Dimension) is that my newer machine, a Dell XPS 410, is RAID-0 and my Dimension is non-RAID.

    Quite a bummer because support for SP2 ends July 31.
    0
  • ReachingHigher
    Well, unfortunately removing those components only made things worse. I removed .Net 3.5 then 3.0 then 2.0, each time rebooting and trying CaptureOne again. I removed CaptureOne as well.

    AFter doing System Restore, Windows Update showed .Net Framework 2.0 as a High Priority update but each time I try to install it, it says "Failed". I tried System Restore back as far as April 24, 2010. All the .Net Frameworks show up in Add/Remove Programs but you can't remove them because they don't exist any more. System Restore has the unfortunate limitation that major changes like .Net upgrades can't be undone so if it fails you can't recover using System Restore.

    So now I'm stuck with .Net Framework 1.1 and now two more programs won't run (Quickbooks and Eizo ColorNavigator). Microsoft technology can be awful when something goes wrong.

    Any other suggestions?
    0
  • Paul Steunebrink
    Most unfortunate situation. Before I read your last post, I considered that this XP setup is not working correct anymore. The SP3 error and .NET problems are a bad omen. System Restore with XP? Hmmm, not yet bullet proof technology (it does not restore files, only some registry settings; you now know where that leads you to).

    Most XP setups today are running 2 or 3 or maybe more years. Too much dust is collected in the software to clean up. You'd better backup your data, get your disks from the shelf and make a fresh installation.
    I could help you in removing the erroneous .NET entries from Add/Remove Programs, but it won't help you, takes time and add frustration.
    Deactivate any software (Photoshop?) while still possible. Deactivate Capture One from the Phase One web site.

    Sorry, but think of the reward of having a fresh (and often faster) system.
    0
  • ReachingHigher
    [quote="Paul_E" wrote:
    Most unfortunate situation. Before I read your last post, I considered that this XP setup is not working correct anymore. The SP3 error and .NET problems are a bad omen.
    Point well taken, hadn't connected the two incidents myself.
    [quote="Paul_E" wrote:
    System Restore with XP? Hmmm, not yet bullet proof technology (it does not restore files, only some registry settings; you now know where that leads you to).
    Yes, I know. I just tried it to see what would/wouldn't happen. I've run into System Restore limitations at other times too. System Restore doesn't back up everything. In fact, it doesn't seem to back up most of the core O/S files, just some of the peripheral ones.

    [quote="Paul_E" wrote:
    Most XP setups today are running 2 or 3 or maybe more years. Too much dust is collected in the software to clean up. You'd better backup your data, get your disks from the shelf and make a fresh installation.
    Agreed in principle. Have considered that in the past. The problem, though, is re-installing dozens of applications. That would be a no-brainer on a Macintosh but it's horrible on Windows. I've heard about image backup programs that back up the o/s, any installed software, drivers, etc. I'll do another Repair Install first and see if that fixes the problem. I'd rather freeze my system state on this computer, buy a new one, and use this one for a 2nd backup machine (my old computer has become my backup machine currently). If I have to reinstall everything anyway I'd rather do that huge effort on a new machine.
    [quote="Paul_E" wrote:
    I could help you in removing the erroneous .NET entries from Add/Remove Programs, but it won't help you, takes time and add frustration.
    Understood. I've located a .Net Framework removal tool on MSDN that will hopefully clean all the crap the uninstalls left behind.
    [quote="Paul_E" wrote:
    Deactivate any software (Photoshop?) while still possible. Deactivate Capture One from the Phase One web site.

    Sorry, but think of the reward of having a fresh (and often faster) system.
    Good suggestions. Hopefully a Repair Install and/or the .Net Framework removal tool will buy me some more time. But it's time for a new computer anyway 😊
    0

Post ist für Kommentare geschlossen.