Skip to main content
Participating Frequently
December 7, 2007
Question

Stalling on Launch - Captivate 3

  • December 7, 2007
  • 4 replies
  • 562 views
Hi -- This is pretty frustrating. Captivate 3 won't launch past the point where it says "copying first run files.' It will, but only after five minutes or so. If I click the task bar or desktop, however, it completes the load. It's as if the application is just waiting. To date, I've done the following:

- Rebuilt the .dat file
- Disabled hardware acceleration on the PC
- Disconnected my company's LAN before launch
- Uninstalled and did a clean install of Captivate

This is a Win2K box (sorry... it's what my company gives me) with SP4, running on a 2.66gig HP. And for what it's worth, I did a search for a "first run" folder and I find them for several applications, but NOT for Captivate. Is it possible that this is why it's dying? And if so, why wouldn't Captivate's Installer put these on the machine.

Thanks
-Marty


    This topic has been closed for replies.

    4 replies

    Participating Frequently
    December 11, 2007
    My value for that key points to a folder that doesn't exist (C:\WINDOWS\system32\config\systemprofile\My Documents\), so adding a value may or may not fix your problem.

    The key value is actually owned by the OS and Adobe is probably reading it to see if you have a custom location for your "My Documents" folder, since that is where your "My Captivate Projects" folder resides.

    My guess is that they never test for the key being empty, which then hangs the application. That's sloppy coding, but it *would* explain the situation.
    Participating Frequently
    December 10, 2007
    I was poking around and found this link. Maybe it will help with your problem?

    http://kb.adobe.com/selfservice/viewContent.do?externalId=74a912a7&sliceId=2
    archqAuthor
    Participating Frequently
    December 11, 2007
    Hi -- Thanks for the tip! That key is actually empty on my machine... all others are filled in but that one is null for some reason. And while I could certainly make the edit, aren't registry entries part of the installation process? If I installed with local admin rights to 'all users' why wouldn't this key have been populated by Adobe?
    Participating Frequently
    December 10, 2007
    I wouldn't get too caught up in the "First Run" message. Only Adobe (hopefully) knows what it's really saying.

    Bottom line is that Captivate is locking up up at launch. My money is on one of the following:

    1) Windows account restrictions and/or folder permissions preventing Captivate from creating temp files.

    2) Anti-virus stopping Captivate from doing something it expects to be able to do.

    3) A corporate firewall blocking an HTTP request to Macromedia/Adobe (my Captivate 2 start page has an "Upgrade to Captivate 3 today!' message, so it has to be calling home in some capacity).

    You might want to check the Windows Error Log to see if there are any system or application errors being logged that might point you in the right direction.
    archqAuthor
    Participating Frequently
    December 11, 2007
    You're right.. bottom line is bottom line. But just for grins & giggles....

    1) Windows account restrictions and/or folder permissions preventing Captivate from creating temp files.
    NONE... we have policy agents and enterprise virus scanners, but nothing restricting a write-to on temp folder

    3) A corporate firewall blocking an HTTP request to Macromedia/Adobe (my Captivate 2 start page has an "Upgrade to Captivate 3 today!' message, so it has to be calling home in some capacity).
    NOPE ... launching even without a network connection creates the same problem and I KNOW Captivate is smart enough to know whether it can 'phone home.'

    You might want to check the Windows Error Log to see if there are any system or application errors being logged that might point you in the right direction.
    No errors in any of the log files available through system management. As I say, I don't think it's an error, as much as it is a housekeeping issue.

    Thanks... I see the other post came in with the article reference...
    Captiv8r
    Legend
    December 8, 2007
    Hi archq

    Sorry about the Windows 2000 conundrum. I offer my condolences. Perhaps you could use this example to justify an upgrade!

    I'm doubtful that you will find a "First Run" folder for Captivate. I just looked at my Captivate folder where it's installed and I see no such folder. But I do suppose one could be being created in a different location on my hard drive. Which possibly offers a clue here. If such a folder were to exist, I'm guessing it would be created in a temporary location. So here is one possible suggestion. Try clearing your temporary files folder. You may find a few different locations that are possibilities.

    Hopefully this helps some... Rick
    archqAuthor
    Participating Frequently
    December 10, 2007
    Hi -- thanks for the response. Unfortunately, I'm in a large enterprise and we're fairly well-entrenched with Win2K. Rumor's on the horizon that XP is in our future, but I'm not sure when. The issue for ME, really, is why the program's exe is even looking for first run files.... if they existed and were part of the program launch, they wouldn't be loaded time & time again, right? And I can't find anything on this issue from Adobe.

    As to your response, clearing everything doesn't seem to alter the start-up issues. It's now a tolerable load, as long as I 'help it along.' Guess I'll just need to sit & wait until XP finds its way to my organization.

    Thanks
    Captiv8r
    Legend
    December 10, 2007
    Hi archq

    Just a gut feeling here, but I'm thinking that Captivate isn't really *looking* for "First Run" files. Instead, my guess is that it is copying certain data to a temporary folder before launching.

    Cheers... Rick