In article <592263a09dNews03@avisoft.f9.co.uk>,
Martin <News03@avisoft.f9.co.uk> wrote:

Then I got
Error : &1B80A914
Message: Invalid Component ID (0x20).
22:33:31.21 ** WimpError ** from CPUClock
Error : &00000000
Message: Unexpected Exception: Invalid Component ID (0x20).

... but not that one.

I do not know why that error was raised. Make sure you are running
version 0.10 of the module.

--
Chris Johnson

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <ap.3457115922.a701a0a.m.conroy@argonet.co.uk>, News <chrisjohnson@spamcop.net> wrote:

I am pleased to announce that version 2.09 of CPUClock is now
available. This is primarily a bugfix and general improvement version.

Version 2.09 of CPUClock can be downloaded from
https://homepages.plus.net/chrisjohnson/software/cpuclock.html or
https://www.chris-johnson.org.uk/software/cpuclock.html

I got this error.....


Message: The CPUClock module is too old to support this version of
CPUClock. CPUClock will continue to run, but monitor the CPU clock speed
only

Then I got

Error : &1B80A914
Message: Invalid Component ID (0x20).
22:33:31.21 ** WimpError ** from CPUClock
Error : &00000000
Message: Unexpected Exception: Invalid Component ID (0x20).

--
Chris Newman

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <59226134f4cvjazz@waitrose.com>,
Chris Newman <cvjazz@waitrose.com> wrote:

In article <ap.3457115922.a701a0a.m.conroy@argonet.co.uk>, News <chrisjohnson@spamcop.net> wrote:

I am pleased to announce that version 2.09 of CPUClock is now
available. This is primarily a bugfix and general improvement
version.

Version 2.09 of CPUClock can be downloaded from
https://homepages.plus.net/chrisjohnson/software/cpuclock.html
or https://www.chris-johnson.org.uk/software/cpuclock.html

I got this error.....

Message: The CPUClock module is too old to support this version of
CPUClock. CPUClock will continue to run, but monitor the CPU clock
speed only

So did I ...

Then I got
Error : &1B80A914
Message: Invalid Component ID (0x20).
22:33:31.21 ** WimpError ** from CPUClock
Error : &00000000
Message: Unexpected Exception: Invalid Component ID (0x20).

... but not that one.

The first one was caused by not quitting v2.08 with 'Module also'.
I did that with v2.09 and then it retstarted ok here.

--
Martin Avison
Note that unfortunately this email address will become invalid
without notice if (when) any spam is received.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <59226134f4cvjazz@waitrose.com>,
Chris Newman <cvjazz@waitrose.com> wrote:

Error : &1B80A914
Message: Invalid Component ID (0x20).
22:33:31.21 ** WimpError ** from CPUClock
Error : &00000000
Message: Unexpected Exception: Invalid Component ID (0x20).

OK. You must be running on a RaPi. The check for RaPi has been done
before the check for module version. Therefore the status window
setup is expecting there to be a fan icon, which it tries to disable.
However, in the clock only status window there isn't a fan icon!

It is a bug, but should not be triggered under normal operation. I
will fix it, but it is not desperate to issue a new version.

--
Chris Johnson

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <59226b2d17chrisjohnson@spamcop.net>,
News <chrisjohnson@spamcop.net> wrote:

In article <59226134f4cvjazz@waitrose.com>,
Chris Newman <cvjazz@waitrose.com> wrote:

Error : &1B80A914
Message: Invalid Component ID (0x20).
22:33:31.21 ** WimpError ** from CPUClock
Error : &00000000
Message: Unexpected Exception: Invalid Component ID (0x20).

OK. You must be running on a RaPi. The check for RaPi has been done
before the check for module version. Therefore the status window
setup is expecting there to be a fan icon, which it tries to disable. However, in the clock only status window there isn't a fan icon!

It is a bug, but should not be triggered under normal operation. I
will fix it, but it is not desperate to issue a new version.

Despite the error message, 2.09 is working on my Raspberry Pi4 RISC OS
5.28 & the error message has not reappeared.

--
Chris Newman

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <592348d049cvjazz@waitrose.com>,
Chris Newman <cvjazz@waitrose.com> wrote:

Despite the error message, 2.09 is working on my Raspberry Pi4
RISC OS 5.28 & the error message has not reappeared.

It will only give the error message if an old version of the module
is already running when you launch CPUClock. If the machine has been
powered off, rebooted, or the module has been rmkilled (which is what
CPUClock does when you choose 'Quit - Module also') then the new
module will be automatically loaded when you start CPUClock, and the
front end should be happy. The error message was given originally
because an older version of CPUClock was running, and was quit
without using the option 'Module also'. It is possible to quit the
front end, but leave the module working away in the background.

--
Chris Johnson

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <592352668fchrisjohnson@spamcop.net>,
News <chrisjohnson@spamcop.net> wrote:

In article <592348d049cvjazz@waitrose.com>,
Chris Newman <cvjazz@waitrose.com> wrote:

Despite the error message, 2.09 is working on my Raspberry Pi4
RISC OS 5.28 & the error message has not reappeared.

It will only give the error message if an old version of the module
is already running when you launch CPUClock. If the machine has been
powered off, rebooted, or the module has been rmkilled (which is what CPUClock does when you choose 'Quit - Module also') then the new
module will be automatically loaded when you start CPUClock, and the
front end should be happy. The error message was given originally
because an older version of CPUClock was running, and was quit
without using the option 'Module also'. It is possible to quit the
front end, but leave the module working away in the background.

Thanks. All is now clear.

--
Chris Newman

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)