Captivate 5.5 - Application Still Sits In Memory

[hps_5]

Hi,

I am working locally (per the recommendations in this forum), and all my projects have been trimmed of extra objects in their libraries.  Still, after I properly exit the application, Captivate is still showing in memory (Win XP - Task Manager.)  Is this normal activity?  Is there anything I can do to terminate Captivate and free up memory?  Both my project locations and cache locations are on my local machine.

Thank in advance.

Henry

[Anjaneai_Srivastava]

Hello Henry,

The Captivate should not be showing up like that when you close the application.

Can you reboot your machine, Launch Captivate and close and observe at each step that is it when it appears in Task Manager?

Additionally, try observing if it occuring with any other software too?

Thanks,

Anjaneai

[hps_5]

Thanks, Anjaneai,

I'm still scratching my head on this one.  I'm not too technical, and it is not a deal breaker (though it would be nice to have memory freed up.)  I consistently go to Task Manager and 'End Process.'  If I reboot without ending these processed, Windows XP barks at me and throws a message if I reboot.  I'll do some further troubleshooting if time allows.

Cheers,

Henry