[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [StrongED] Re: "string not recognized" error



On 8 Sep 2010  Jim Nagel <stred@xxxxxxxxxxxxxxxx> wrote:

> Dr Peter Young  wrote on 7 Sep:
>> Should I put 0.29 into MPro? If so, where do I get it?

> you'll find it inside MPro:  !Messenger.RMStore.OLEsupport

yes, you're quite right, and I hadn't looked hard enough. I was a bit 
puzzled, however, as I couldn't find anything in MPro which would load 
OLESupport anyway.

> (i use MPro version 5.13 here, but this version of OLEsupport was
> probably shipped with several previous versions of MPro, judging by
> its 2007 date.)

> can someone please tell me where this OLEsupport 0.29 should be placed
> within !Boot so that it will be loaded rather than older versions such
> as the problematic 0.28?

> i ran !Locate to find other instances of OLEsupport in my !Boot
> directory.  several turn up in the results, but, strangely, none of
> them is version 0.28 and yet 0.28 is the one that is loading from
> somewhere at bootup.  (and no OLEsupport in *rommodules.)

I've done a bit more digging (and the caffeine levels of the 
brain-cell are optimal) and have found that Hermes, within NetSurf, 
contains 0.28, which it does load in its Run file. I've replaced this 
with 0.29 and rebooted, and all seems to run OK.

Incidentally, two other apps, which I don't run at start-up, seem to 
contain 0.28 here; DataPower, which doesn't seem to load it, and 
EasiWriter, which does.

All of this is probably irrelevant to Jim's problem, but it interests 
me. RComp seem to have got into a muddle, having different versions in 
Messenger, Hermes and DataPower.

With best wishes,

Peter.

 --
Peter, \  /      zfc Lu       \     Prestbury, Cheltenham,  Glos. GL52
Anne    \/ __            __    \                              England.
and     / /  \ | | |\ | /  _    \      http://pnyoung.orpheusweb.co.uk
family /  \__/ \_/ | \| \__/     \______________ pnyoung@xxxxxxxxxxxx

-- 
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxxxxx