Multiple Versions of Robohelp and Problems

Forum|Forum|14 years ago
December 16, 2011
1 reply
1708 views

We are running Robohelp 7 and Robohelp 9 on all of our PCs and having problems with crashes, builds and just strange lockup stuff. Are there any known issues with running multiple builds of Robohelp on the same machine? In our case, we have projects that include hundreds of files, and to make a minor edit it doesn't make sense to convert the entire project to Robo9, so we open in 7 and make the change and do the builds. Any help would be greatly appreciated.

This topic has been closed for replies.

Jeff_Coatsworth

Community Expert

Captiv8r (Rick) has reported using multiple versions of RH on his machines. The main warning is that Acrobat doesn't play nice when multiple copies are installed on the same machine.

Where are these projects located? Are you using some form of source control?

P

Patrick McNaAuthor

Participating Frequently

Thanks for the reply Jeff. All of our project files are located on an SBS 2008 64 bit server. We are accessing the files via LAN from XP 32 bit and windows 7 64 bit machines. The problem doesn't seem to be isloated to the workstation OS. After speaking with Adobe support (yes we have paid support and they weren't much help) we are now copying files from the server to local drives and accessing the projects that way, but the problems are still occurring.

I am actually in the process of virtualizing "clean machines" that I can use to run Robo7 and Robo9 on separate virtual PCs. I was just wondering if i'm wasting my time or if there are known issues with the two builds playing together nicely. it sounds like their are issues when both versions are installed on the same machine.

Jeff_Coatsworth

Community Expert

I'd suspect that most of your issues are related to damaged projects that got that way when you were working on them over the network. There are many, many warnings on the forums about having projects running on network locations - just because RH lets you do it, doesn't mean that it works :>)

Best practices dictate that you run your project on your c:\projects\project_name\ folder & that you don't let your paths get too long. At the end of the day, zip up your project and back it up to the network. But if you've got multiple people working on topics within the same project, you need to invest in source control.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.