Re: [Zapping-misc] Zapping: bugs and thanks!

[Nate D. <na...@ks...>]

> > I is confuzed ;)
> me2 :-)
> Do you mean than this behaviour only appears when SETI@Home is running,
> even if it's running in a different *text* console??

Correct - whether it's running in an A-Term (or X-Term) or from a plain text
console doesn't seem to matter.

> Oh My God, can you see the implications? I've built the world's first
> seti@home catalyzer!!!! ;-)

Catalyzer?  [dumb look]

> Seriously, I need some more info:
> - Does this happen in both capture/preview modes?

Preview mode.  Can't test Capture mode, that isn't supported on my card yet.

(So the chroma-key thing I mentioned does briefly get messy :)

> - Does this happen with vbi disabled/enabled? (zapping --no-vbi)

VBI isn't supported on my card yet, but explicitly disabling it doesn't seem
to affect Zapping any. (Zapping normally tells me it can't open /dev/vbi
anyway)

> - Does this happen with plugins disabled?
> (zapping -p)

I haven't tried any plug-ins, so I assume they are disabled by default?

> I've just installed setiathome here and cannot reproduce (well, didn't
> try with afterstep, but Gnome+sawfish)

It doesn't seem to affect Gnome/Sawfish.  Kinda odd really.

-- 
 _________________________ ___ ___
|  na...@ks...    //ZZ]__ |
|      C64/C128/SCPU     |'/  |Z/ |
| What's *YOUR* Hobby!?  | \__|_\ |
|_________________________\___]___|