[Coco] Coco compatible monitors...

[gene heskett]

On Saturday, July 02, 2011 10:44:50 AM John Kent did opine:

> Ooops sorry ... antivirus spam messages in the header.
> 
> John.
> 
> On 2/07/2011 4:19 PM, John Kent wrote:
> > On 2/07/2011 3:22 PM, gene heskett wrote:
> >> It is not interlaced John.
> >> 
> >> Cheers, gene
> > 
> > Hi Gene,
> > 
> > In that case you just need a line buffer, or actually 2 to ping pong.
> > It would work as a line doubler which would make it a bit simpler.
> > Ideally you'd want a PLL to lock onto the pixel stream so that you
> > could sample synchronously with the pixels or else clock the scan line
> > converter with the VDG clock. Ideally the timing would be adaptive but
> > if the scan converter was designed for the VDG the timing is fixed so
> > it wouldn't have to be adaptive.
> > A friend from the Flex users group was looking for a scan rate
> > converter for his old Flex / UniFlex machine and showed me the link I
> > posted. I'm not sure if he bought one.
> > 
> > John.

Didn't notice.  What I got here was added by my own spamassassin treatment, 
and because its the top of the header, does not normally show as long as 
spamassassin sets the  spam level string to 4 *'s or less.  At 5 it gets 
filtered into the spam folder for my inspection, and fed to further train 
spamassassin at about 1 pm each day, then deleted, all by scripts I wrote.

6 or more *'s and procmail sends it straight to /dev/null.

In other words, only if something is odd, do I click to look at the 
headers.

Cheers, gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Quid me anxius sum?

[ What? Me, worry? ]