www.virtualacorn.co.uk/forum

Hi,
I use VA-RPC now for about a month and believe it or not after using RPC's for over 10 years and screwing up a brand new Omega I think VA is the best piece of software i have bought the last 5 years.
There are a few thing that does not work and I wonder if there is a fix for my problems
A) The PRINT key is not working
B) I can configure VA up to use 192MB of memory and NOT >192 eg 256
I have 1Gb of main memory in my PC
C) Is there a way to use the scroll button (middle mousebutton )
D) I can install Select 4.37 but if I do so I loose my 8Mb videoram - is there a fix for it ?
E) On a AMD64 processor the clock is read wrong ( I use it now on a desktop PC with AMD64 3000+)
VA says it has a clock of 1800Mhz
(ok it does run at a decent speed)
CPU_speed reported it as a StrongArm 356Mhz
But if you choose manual clockspeed and use the AMD spec's (eg 3000Mhz)
then VA runs about 2 times faster.
CPU_Speed reported it now as a StrongArm 540Mhz !!!
I have made a few 'benchmarks' for myself and it is clear that the manual option for the clockspeed made a big difference on all operations.
PS
My PC is build into the Omega case so it looks as I have the fastest Omega in the world !!!
Nice work VA-team

Dealing with the points in turn.
The Print key seems to be a reserved key and we can't seem to trap it.
Delete the 2nd bank of RAM from the config file and set the first bank to be 256Mb in size -but beware some older programs can throw a wobbly with this much memory available.
You could try installing CallWin32 - although note that we don't support CallWin32 itself.
Select thinks its running on a RiscPC and is limited to 2Mb of VRAM.
With regard to AMD processors the number (e.g. 3000+) is not the clock speed. It's the equivalent speed - so it roughly means that the processor performs the same as an Intel with a clock speed of 3000Mhz. So if you manually set the clock speed things may well go wrong as some of the timers will be out (look for the time in Alarm jumping back and forward).

I'm aware of it
But the strange thing that happened is:
I have ported quickpar to RISCOS
From the 12 MPEG samples (on the VA CD-rom) I made a 20% recovery set with quickpar.
With clock on auto (=1800) it is done in 47 seconds
With clock on manual (=3000) the same set is created in 39 seconds.
The timings are done with an external stopwatch. (and not on RISC OS )