Robohelp 2015 installs stalls at .Net

4 replies
1048 views
Translate

This is a little off-topic, but I didn't see an install forum.

I am trying to install a trial of Robohelp 2015 onto a Windows 7 (64-bit) VM. I have installed MS Office 2007 (Word only) and am running the Robohelp 2015 install (RoboHelp_12_LREFDJ.exe directly). At first it had a hard time logging into my Adobe account. That cleared up after running it several times. Now, it gets to 48% ('Currently Installing Microsoft .NET Framework 4') and just hangs. The time remaining keeps increasing, but nothing happens - it's up to 53 minutes remaining now). Any ideas?

RH for Word

This topic is closed to new replies. Start a new post to keep the conversation going.

Peter Grainge

Community Expert

That version of Word is not supported by RoboHelp 2015 but I doubt that is the cause of any .Net message. I don't recall ever seeing RoboHelp wanting to install .Net.

Installation support is free from Adobe but I am not sure if that extends to installing it on a VM.

See www.grainge.org for RoboHelp and Authoring information

@petergrainge

Translate

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.

E

epsobolikAuthor

Inspiring

I finally found the help web page and got a chat session going. They recommended installing .NET manually and then re-installing Robohelp. That worked. However, Word documents are handled very differently on 2015 than it was on 7. Each document is one big help topic – not separated by hard page breaks. I determined that we can’t update now, but will in the future. In the meantime, I’ll just hobble along with 2 versions of Word installed and learn to live with the bugs in 7.

===============================================================================

Philip Sobolik

Wrightsoft Corporation

Translate

Captiv8r

Legend

Sounds to me like you somehow overlooked setting up the pagination settings.

Also, RoboHelp 2015 Release does offer two ways of working with Word content that version 7 did not. You may now *LINK* to a Word document. (Where perhaps another person makes edits periodically and all you do is pull in the changes) or you may simply Import just as version 7 offered. In that case, you suck in the document and convert to topics, then forget it ever existed as a Word document and from this point forward you only make edits using RoboHelp.

Cheers... Rick

Translate

Captiv8r

Legend

Perhaps ensure the VM has enough drive space allocated?

I used to run a Windows XP VM in Windows 7 and I recall running into space issues. The odd part was I don't recall seeing any warnings that helped me figure out that was the issue. Maybe because it was a VM? Not sure.

Cheers... Rick

Translate

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.