Posted by Hammerer on 07/27/06 16:08

"gregfarr" <gregfarr@oshit.comcast.net> wrote in message
news:8k4gc2h39mbnn9a6mio75gu1v21icvcvfp@4ax.com
>
> On Wed, 26 Jul 2006 17:21:22 +0100, "Hammerer"
> <Use-Author-Supplied-Address-Header@[127.1]> wrote:
>
> >
> > "gregfarr" <gregfarr@oshit.comcast.net> wrote in message
> > news:u98ac2lpmai8hgohahb3tpn6tdooog6v0o@4ax.com
> > >
> > > In 354 and now using leechhammer, when the hammer
> > > does it's thing, like zapping peeps, the entire winmx
> > > screen and text jumps flutters, goes invisible,
> > >
>
> > It jumps flutters, and goes invisible, Greg? Hell. Have you
> > tried not letting the hammer do its thing (like zapping peeps)?
> > The equation seems simple . . . . . .
> > zapping peeps = jumps flutters + goes invisible . . . . . .
> > Conclusion = There's something fucked somewhere.
> >
>
> > > and looks like a shock has run thru it.
> > >
>
> > Check your wiring, Greg. Is your WinMX earthed?
> >
>
> > > Any others get this, is it curable?
> > >
>
> > My advice is to drink heavily whilst WinMXing, Greg.
> > That should cure things.
> >
>
> It's too bad instead of enjoying themselves so much, there wasn't a
> good code writer out there that could fix winmx, as it's only about
> 3/4 of a program, many things have been left out and somebody
> needs to make another updated addition.
>

Yep. Admit it, though, Greg. You'd probably still manage to fuck things up
somewhere along the line. No offence.

[Back to original message]