replacement ImageAPI.dll causing new problems

Wanda - No, and it has been a nightmare. We logged our original support call

in July, and although our case is still active with Adobe, they still say

they can't reproduce the problem on their end. We have other products

documented using another tool that we're satisfied with, and we had resisted

converting the giant help project for this particular product to that tool,

because we were concerned about the time the conversion would take,

particularly to convert all the hotspot graphics. Well, I'm sure it would

have taken less time than what we've spent so far trying to get RoboHelp to

work.

I would like to encourage you and the other two guys who have reported the

problem to log a support call . . . maybe if we all reported it they would

feel a little more pressure to get the problem solved.

I have already put quite a bit of this long saga on the Forum, so I probably

shouldn't say any more about it there, but feel free to contact me directly

at sdryer@msa.com.

Hi Lost ,

We tried various things. If you do have a working version of an older copy of

RoboHelp (we had somebody still on RoboHelp 5), you can do the graphics in

the older version and then use them in your 8 project. I tried copying the

ReSize image program and the ImageAPI.dll from RoboHelp 5 to my machine to

use with RoboHelp 8, but, not surprisingly, this didn't work.

If you know exactly how you want to make your .shgs, and nothing will be

changing, you might try using the old RH8 ImageAPI.dll. As I mentioned, in my

particular experience of the problem, I was always able to save the .shgs

ONCE (after starting with a fresh .bmp) without them breaking. That is, they

would LOOK broken - the links would show up truncated, under "Broken Links"

in RH Explorer, but when I actually compiled, the graphic would work OK. If

I saved the .shg again, and compiled again, the graphics would not work. I

don't know if this has been your experience; I also don't know if you will be

able to go back to using the old ImageAPI.dll without the graphic vanishing.

One of my colleagues tried going back to the old ImageAPI.dll, and he says

now he's getting the same problem with that as with the new one. Just thought

I'd throw that possibility out there, though.

We finally broke down and logged a support call with Adobe. Because of a

combination of problems on our end (our company's firewall) and Adobe's end

(even after I finally was able to send them a sample help project so they

could see the error, they were trying to support me in RoboHelp HTML instead

of RoboHelp for Word, asking why I had sent them an .hpj instead of an

.xpj??!!) it has turned into something like a Monty Python quest. I'm

expecting the killer rabbit any day now.

Seriously - the last I heard from Adobe was last Monday, the 2nd, and they

said that they were escalating the problem but that it would be at least 48

hours before I heard from anyone. Obviously, it has been more than 48 hours.

We went ahead and sent our latest project out without the few new .shgs that

it would require. But I think at least they believe me about it being a

problem with the ImageAPI.dll, so I am hopeful that they will respond soon.

(Hope springs eternal . . .) I will certainly let you know if we hear

anything and I will certainly encourage them to post the new .dll, because

that's what it's going to take, as soon as possible.

Best of luck - Sandy