Help on keyword ImageExtendModule is: Image Extension 0.80 (03 Feb 1993)
For some reason I can't run !OHP to run on ARMX6. The
!Run file reports:
"This application needs ImageExtend 0.80 or newer".
However a check on the module states
*help imageextend ==>Help on keyword ImageExtend Module
is: Image Extension 0.80 (03 Feb 1993)
So what's up? I tried with/without Aemulor.
For some reason I can't run !OHP to run on ARMX6. The !Run file
reports:
"This application needs ImageExtend 0.80 or newer". However a check
on the module states
*help imageextend ==>Help on keyword ImageExtend Module is: Image
Extension 0.80 (03 Feb 1993)
So what's up? I tried with/without Aemulor.
In article <[email protected]>, Richard Porter <[email protected]> wrote:
For some reason I can't run !OHP to run on ARMX6. The !Run file
reports:
"This application needs ImageExtend 0.80 or newer". However a check
on the module states
*help imageextend ==>Help on keyword ImageExtend Module is: Image
Extension 0.80 (03 Feb 1993)
So what's up? I tried with/without Aemulor.
I get the same error message.
So what's up? I tried with/without Aemulor.
What version are you running? I've just upgraded 2.00 to
2.6 and the only trouble I've had is messages about lack of
memory. On an ARMX6?
My travails (all sorted now) are recorded in a thread on
Archive-on-Line.
The date being 5 May 2022, John
<[email protected]> decided to write:
So what's up? I tried with/without Aemulor.
What version are you running? I've just upgraded 2.00
to 2.6 and the only trouble I've had is messages about
lack of memory. On an ARMX6?
My travails (all sorted now) are recorded in a thread
on Archive-on-Line.
Thanks. The help file says version 2. The app is dated
2000. Upgrade now on order.
What version are you running? I've just upgraded 2.00 to
2.6 and the only trouble I've had is messages about lack of
memory. On an ARMX6?
In article <[email protected]>,
John <[email protected]> wrote:
What version are you running? I've just upgraded 2.00 to
2.6 and the only trouble I've had is messages about lack of
memory. On an ARMX6?
Where do you find the upgrade?
In article <[email protected]>, Richard
Porter <[email protected]> wrote:
The date being 5 May 2022, John
<[email protected]> decided to write:
So what's up? I tried with/without Aemulor.
What version are you running? I've just upgraded 2.00
to 2.6 and the only trouble I've had is messages about
lack of memory. On an ARMX6?
My travails (all sorted now) are recorded in a thread
on Archive-on-Line.
Thanks. The help file says version 2. The app is dated
2000. Upgrade now on order.
Mine was the same version before I got the upgrade.
I have run into another snag. I wanted to create the slide
show on the ARMX6 but run it on RPCEmu on a Linux laptop.
Unfortunately, the background colours don't transfer
accurately. Only black and 20%RGB grey come out correctly.
It's the same on both Windows and Linux installations of
RPCEmu.
The problem was the Deja Vu family of fonts which are RO5
only. Once I deleted them, all was well.
In message <[email protected]>
John <[email protected]> wrote:
Unfortunately, the background colours don't transfer accurately. Only
black and 20%RGB grey come out correctly. It's the same on both Windows
and Linux installations of RPCEmu.
I suspect this is the BGR <> RGB colour mapping
On 11 May, Chris Hughes wrote in message
<d4ddeee659.chris@mytardis>:
In message <[email protected]>
John <[email protected]> wrote:
Unfortunately, the background colours don't transfer accurately. Only
black and 20%RGB grey come out correctly. It's the same on both Windows
and Linux installations of RPCEmu.
I suspect this is the BGR <> RGB colour mapping
Aren't both the ARMX6 and RPCEmu using the same byte order, though?
Unfortunately, the background colours don't transfer
accurately. Only black and 20%RGB grey come out
correctly. It's the same on both Windows and Linux
installations of RPCEmu.
I suspect this is the BGR <> RGB colour mapping
Or maybe are you using different colour depth on the
different machines 16 million colours on say ARMX6 and
32 thousand on the other devices.
The problem was the Deja Vu family of fonts which are
RO5 only. Once I deleted them, all was well.
You need the Verity font instead which is the version
that works on all machines, available from !Store - they
are free
In article <d4ddeee659.chris@mytardis>, Chris Hughes
<[email protected]> wrote:
I suspect this is the BGR <> RGB colour mapping
I thought that only affected the Titanium.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 149:14:55 |
| Calls: | 12,091 |
| Calls today: | 4 |
| Files: | 15,000 |
| Messages: | 6,517,572 |