Video Screencast Help

Photoshop CS5 VSA problem

Created: 30 Apr 2010 • Updated: 11 Nov 2010 | 5 comments

CS5 was just released and I wanted to try it. Using VirtualBox, on a Windows 7 host, with Windows XP SP3 guest, clean machine with SWV 6.1.5126, I installed it. Single program capture. During the install, I got two error boxes:
"MS Visual C++ Runtime Library. Runtime Error! Program: C:\P...[this was truncated] This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." OK.
"SwitchBoard Server (32bit). SwitchBoard Server has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something the info you were working on might be lost." Close.

In spite of the two error boxes, installation continued and apparently completed successfuly. I noticed when the SWV capture ended and the "do you want to install another program in this layer" box appeared, but the SWV Admin window did not appear as is usually the case. I had to click the SWV Task Bar icon to make it appear. It showed the layer activated, as normal.

The program apparently ran OK in the Windows XP VM. I exported the VSA and imported it into a Vista real machine and a Windows 7 real machine. In both machines, when I attempted to run the program, I got a Windows error box "Photoshop CS5 has stopped working...check online for a solution, or close the program." The program would not run.

Any ideas why I couldn't run the program when I imported the layer?

Comments 5 CommentsJump to latest comment

Jordan's picture

I haven't had the chance yet to look at CS5 yet so I'm not 100% sure what the issues are but I can guess pretty well.

We have capture issues with the VC runtime, while I've never seen them on XP it's generally a best practice to install the VC runtime to the base before capture as well as when you import to a new machine.  If you want to read more there's an article I just posted about Microsoft Office and Win 7 that covers this subject.

The issue with SVSadmin not restoring after some captures is a known issue.

If a forum post solves your problem please flag is as the solution

RedBug's picture

Both the Vista machine and the Win 7 machine had Avira Antiv installed on the base. Found out that Avira installs MS Visual C++. Saw a note in a fourm here that said Avira installs MS V incorrectly. I suspect now the failure of the Photoshop VSA on the Vista and 7 machines was due to Avira. I'll have to poke around when I get time to verify my suspicion. I reckon I'll have to create Vista and 7 clean VMs for testing. I like virtualization, but it sure is making my life more complicated.

EdT's picture

There are runtime installs for both VC++ 2005 and VC++ 2008, and I would assume there is a runtime of some sort for the recently released VC++ 2010.
Where possible, my preference is to include these runtimes as part of the base build or default application layer in any corporate operating system build. This avoids having to install these runtimes as part of any application which needs the runtimes, and also ensures they are installed correctly using the native Microsoft installer.
In your scenario, it may be prudent to set up your VM with the VC++ runtime installed but not installing Avira on the VM at all. Creating your VSA on a clean and minimalist O/S install is going to give you the best results, in my experience.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

RedBug's picture

As a personal, non-business SWV user with a limitied understanding of transactions and runtimes, it seems to me now that it might be prudent to preemptively install the VC++s, .NET Frameworks, and the Java Runtime on the base of my virtual Win XP packaging machine as well as on my real Vista and Win 7 machines (where I would import the VSAs). 

Jordan's picture

We're working on some things, such as the layer LDF files that we've been posting recently, to make packing apps that require the VC runtime and .Net easier for users.

If a forum post solves your problem please flag is as the solution