🚀 go-pugleaf

Hello every body !

I want to thank

Ralph Barrett
Graham Allan
John Tytgat    ( it IS c.s.a.t - the only substitute for my favorite
		 alt.pictures.erotica killed by our News-boss )

for replaying to my 'Help !'-request

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 ?

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

!Vector demo suddenly got problems too: it displays text areas allright but
single lines are invisible and on every redraw request an 'SWI not found'
error box pops up (no number, no name, no nothing)

Only !NewChars and !KeyBoard are working lovely, displaying any of Acorn's,
Newcasle's or TeX's fonts

I'm really puzzled (and frustrated)

Does the FontManager 2.44 rely on some 'hardware configuration' ?
Is this a FM problem at all ?
I thought the broken VIDC could be the reason but now that I've exchanged it...

Can anybody help ? (that's the last one ;-)

Bye
	Franz