X-BeenThere: growl-for-windows@googlegroups.com
Received: by 10.150.207.3 with SMTP id e3ls546066ybg.3.p; Sun, 21 Mar 2010 
	18:30:01 -0700 (PDT)
Received: by 10.150.127.2 with SMTP id z2mr1953266ybc.17.1269221401151;
        Sun, 21 Mar 2010 18:30:01 -0700 (PDT)
Received: by 10.150.47.17 with SMTP id u17mr15489ybu.27.1269213294991;
        Sun, 21 Mar 2010 16:14:54 -0700 (PDT)
Received: by 10.150.47.17 with SMTP id u17mr15487ybu.27.1269213294900;
        Sun, 21 Mar 2010 16:14:54 -0700 (PDT)
Return-Path: <erikjan...@gmail.com>
Received: from mail-gy0-f188.google.com (mail-gy0-f188.google.com [209.85.160.188])
        by gmr-mx.google.com with ESMTP id 25si382458yxe.2.2010.03.21.16.14.54;
        Sun, 21 Mar 2010 16:14:54 -0700 (PDT)
Received-SPF: pass (google.com: domain of erikjan...@gmail.com designates 209.85.160.188 as permitted sender) client-ip=209.85.160.188;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of erikjan...@gmail.com designates 209.85.160.188 as permitted sender) smtp.mail=erikjan...@gmail.com
Received: by gyh20 with SMTP id 20so7948485gyh.5
        for <growl-for-windows@googlegroups.com>; Sun, 21 Mar 2010 16:14:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.83.19 with SMTP id g19mr166867anb.14.1269213294846; Sun, 
	21 Mar 2010 16:14:54 -0700 (PDT)
Date: Sun, 21 Mar 2010 16:14:54 -0700 (PDT)
In-Reply-To: <86c2cf49-c98f-4dd2-95d8-5a3a13fe5939@v20g2000prc.googlegroups.com>
X-IP: 83.85.7.140
References: <86c2cf49-c98f-4dd2-95d8-5a3a13fe5939@v20g2000prc.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) 
	AppleWebKit/533.3 (KHTML, like Gecko) Chrome/5.0.357.0 Safari/533.3,gzip(gfe),gzip(gfe)
Message-ID: <e824763b-6058-4007-b569-8088cbe2727f@15g2000yqi.googlegroups.com>
Subject: Re: 2.0.2.8 Issues
From: CoolJazz <erikjan...@gmail.com>
To: growl for windows <growl-for-windows@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1

I have no further information  but do want to report the exact same
issue.
Also been using the program a couple of months without problems but
since the update to 2.0.2, it's unusable because of the issue stated
above.