🚀 go-pugleaf

In article <1jph4kINNqur@nz12.rz.uni-karlsruhe.de> ig06@rz.uni-karlsruhe.de (Goetz) writes:
>
>200 DM+pp for a new VIDC did cure the problem but if the situation is
>as Ralph Barrett wrote in his e-mail:
>
>- The A305/310 ... suffer from this problem. It is due to the lack of any
>- protection circuitry on the video interface. Later machines have additional
>- components ... to protect the VIDC.
>
>then I'll need another 200 in a week when my brother visits us with
>his 3 year old monitor-cable-unplugger ...
>
>Or does anybody know if such protection circuitry exists for the A310
>and if so who is selling it, how much does it cost and can you install it
>yourself ?

It *is* possible to add some protection for the VIDC, by adding some
diodes to the output or something, but I'm not too clear on the details
and I didn't bother, myself. If you are careful with the machine, and make
sure you never plug or unplug the monitor cable when either the computer
or the monitor are switched on, then you shouldn't have any other
troubles.

>Here's another ?
>
>I have problems when rendering text using anti-aliased fonts - now that I
>have 4 Mb, a new VIDC, AtomWide's Enhancer and a colour monitor !
>
>If FontManager 1.15 is installed !Draw and !DrawPlus have no troubles with
>Acorns 'standard' fonts (Corpus,Porthouse,Trinity - I am RO2)
>
>When FontManager 2.44 is loaded and I try one of those outline fonts from
>Newcastle then:
>
>- !Draw doesn't display anything
>- !DrawPlus displays text only when I'm typing and the line disappears (with
>  a beep) after a RETURN. Now I select it and switch to the system font -
>  it appears again

Well I don't remember the various version numbers of the font manager, but
some things I do remember are...
FontManager depends on a module called SuperSample. The SWI numbers for
this module changed at some point, so if you are using a new fontmanager
with an old supersample module, it would be understandable if things
didn't work properly.
Secondly, I found that 'RISC OS 3' fontmanagers didn't work properly under
RISC OS 2 anyway - they come very close to working, and are fine on the
screen, but when it comes to printing, some of the colours come out wrongly
(eg black fonts come out as a grey shade). If you ask me, it's not worth
the trouble to deal with: just upgrade to RO 3.1 and be done with it!

Graham.