installing 6.0 m090 alongside existing 6.0 m010 installation

Author

1-Visitor

Following your suggestion to brute-force a pair of installs, I think what
I'd have to do to end up with an m010 and an m090 pair is this:

Install m010 to:
c:\win\ptc\editor60m090

Copy that folder to some "holding" location.

Install m090 allowing it to upgrade m010.

Then copy the "holding" folder back to this folder:
c:\win\ptc\editor60

And see if both ran successfully? Is that what you're suggesting?

I already launch editor.exe via a batch file. I already know how to
regsrv32 the WDK dlls (and allegedly Editor should register itself). What
else might I need to think about?

Author

1-Visitor

That appears to work ... Each time m010 runs after m090 runs and vice
versa, I am presented with this:

[A31568] Arbortext Editor has detected that this version is no longer
configured correctly.
To automatically correct this problem, Arbortext Editor requires elevated
permissions.
After you select OK, Windows will ask you to confirm the permissions.

But clicking OK seems to work. Pretty sure that is Editor registering
itself.

Phew. Some small sigh of relief. Still, I'm sure this isn't supported but
... tra la.

Author

1-Visitor

Thanks, Gareth!

1-Visitor

Paul,

You can disable that COM prompt, but now you're really tempting fate. Especially starting in 6.0, there are a number of UIs that rely on including an Editor ActiveX control embedded in a dialog - for example, the Text Entity and Tag Template dialogs, or the DITA Resource Manager/Image tab. If the wrong COM process is registered, some bad things can happen.

With that having been said, you can tell Editor to not worry about COM registration by setting the APTNOCOMCHECK environment variable to some value. But you probably shouldn't.

Chris

Chris Nitchie
(734) 330-2978
chris.nitchie@oberontech.com
www.oberontech.com
Follow us:

1-Visitor

Now that I think of it, a better solution would be to run the various versions of Editor from a batch file and call

editor.exe -RegServer

before launching the program proper (via editor.exe or editor.exe -styler). This will 'manually' register the given executable as the COM server, and then it won't nag you about it when you start up.

Chris

Chris Nitchie
(734) 330-2978
chris.nitchie@oberontech.com
www.oberontech.com
Follow us:

Author

1-Visitor

So I like the suggestion, Chris. However (and this has nothing to do with
Editor, it's all Windows 7) I have to run the shortcut or batch file as an
Administrator or I get a longer series of dialogs.

Specifically, with the command added, if I run as administrator, Windows 7
confirms I want to run it as an Administrator, and then Editor loads.

If I do not run it as an administrator, then with the command, the initial
com registration fails but then when Editor runs (not attempting to
specifically register itself), it alerts that it is not configured properly
and asks to make changes, on OK, Windows 7 requests confirmation of running
as an Administrator.

Without the command (editor -RegServer) and without running as
Administrator, I get just the "not configured" prompt, and then Editor
loads.

So it's a choice ... do you want authors to confirm they want to run Editor
as an Administrator, or to confirm it needs reconfiguring after a switch
between m010 and m090. Six of one, half a dozen of the other.

Oh, and I am able to launch both m010 and m090 and have them running at the
same time. No testing beyond launch, so I don't know if there are issues
that would develop doing more than just launching the app (not even opening
a file).

Anyhow, thanks, Chris, as I said, I like that suggestion. I am not sure
which error / confirmation the authors will prefer to see, but I'll let
them decide ... I never know how they're going to think.

On Wed, Aug 21, 2013 at 5:15 PM, Chris Nitchie <chris.nitchie@oberontech.com<br/>> wrote:

> Now that I think of it, a better solution would be to run the various
> versions of Editor from a batch file and call
>
> editor.exe -RegServer
>
> before launching the program proper (via editor.exe or editor.exe
> -styler). This will 'manually' register the given executable as the COM
> server, and then it won't nag you about it when you start up.
>
> Chris
>
> *Chris Nitchie*
> (734) 330-2978
> chris.nitchie@oberontech.com
> www.oberontech.com
> Follow us: <">http://www.linkedin.com/company/oberon-technologies>
> <">https://twitter.com/oberontech> <">https://www.facebook.com/oberontech>
> <">http://www.oberontech.com>
>
> On Aug 21, 2013, at 8:13 PM, Chris Nitchie <chris.nitchie@oberontech.com>
> wrote:
>
> Paul,
>
> You can disable that COM prompt, but now you're *really* tempting fate.
> Especially starting in 6.0, there are a number of UIs that rely on
> including an Editor ActiveX control embedded in a dialog - for example, the
> Text Entity and Tag Template dialogs, or the DITA Resource Manager/Image
> tab. If the wrong COM process is registered, some bad things can happen.
>
> With that having been said, you can tell Editor to not worry about COM
> registration by setting the APTNOCOMCHECK environment variable to some
> value. But you probably shouldn't.
>
> Chris
>
> *Chris Nitchie*
> (734) 330-2978
> chris.nitchie@oberontech.com
> www.oberontech.com
> Follow us: <">http://www.linkedin.com/company/oberon-technologies>
> <">https://twitter.com/oberontech> <">https://www.facebook.com/oberontech>
>

G

GarethOakes

16-Pearl

> Oh, and I am able to launch both m010 and m090 and have them running at the same time.
> No testing beyond launch, so I don't know if there are issues that would develop doing more
> than just launching the app (not even opening a file).

The COM stuff is where the side-by-side Editor will come unstuck. The Windows COM registry only allows you to register one instance of a COM object at a time. So if you started M090 first then M010 will use the M090 COM object in situations such as Chris described.

Glad to hear you're making progress though 🙂

-Gareth

1-Visitor

Yeah, I totally forgot about the Windows 7 security stuff. I havne't had to run two versions simultaneously in a while; when I did, I used the APTNOCOMCHECK trick.

Chris

Chris Nitchie
(734) 330-2978
chris.nitchie@oberontech.com
www.oberontech.com
Follow us:

Author

1-Visitor

I will sleep on it, but I do not think it will be hard to declare an end to
supporting dual versions running simultaneously. Would there be a way to
test from the batch file whether the OTHER version is loaded or not? For
example, if an author launches m090 but m010 is loaded, can I detect that
and "gracefully" (as gracefully as one can in DOS 🙂 exit?

On Wed, Aug 21, 2013 at 5:46 PM, Chris Nitchie <chris.nitchie@oberontech.com<br/>> wrote:

> Yeah, I totally forgot about the Windows 7 security stuff. I havne't had
> to run two versions simultaneously in a while; when I did, I used the
> APTNOCOMCHECK trick.
>
> Chris
>
> *Chris Nitchie*
> (734) 330-2978
> chris.nitchie@oberontech.com
> www.oberontech.com
> Follow us: <">http://www.linkedin.com/company/oberon-technologies>
> <">https://twitter.com/oberontech> <">https://www.facebook.com/oberontech>
> <">http://www.oberontech.com>
>
>