GfW version 2.0.7 released

65 views
Skip to first unread message

Brian Dunnington

unread,
Sep 16, 2011, 1:07:05 PM9/16/11
to growl for windows
Everyone -

I have been meaning to release this small update to GfW for some time
now and just kept putting it off, but I am glad to announce that it is
finally available. This release mainly has minor changes and a few bug
fixes in it, but I am still hoping to do a much larger release at some
point with some bigger changes in it.

Here is the list of changes for this release:

2.0.7 changes (v2.0.7.1)
------------------------------
- updated all Growl claw icons to match new Mac icons
- made History item text copyable (select item and then Ctrl-C)
- created user-configurable setting for length of time to store
history items (HistoryDaysToStore in user.config)
- updated Websocket support to draft-ietf-hybi-thewebsocketprotocol-14
protocol version
- fixed an issue where thumbnail images for old history items were not
deleted from disk
- fixed issues with Standard display that caused issues with high DPI settings
- fixed a bug in Growl.Connector.dll that didnt handle newlines (\n)
in callback data properly

Try it out and let me know if you run into any issues.

Thanks,

- brian

sabin1001

unread,
Sep 16, 2011, 1:57:06 PM9/16/11
to growl for windows
When trying to update I get an error message:
The feature you are trying to use is on a network resource that is
unavailable. etc etc etc...

So it's not able to uninstall the old version using this installer. So
I'm trying to track down an installer for the version I have so I can
repair/uninstall it.


On Sep 16, 12:07 pm, Brian Dunnington <briandunning...@gmail.com>
wrote:

Brian Dunnington

unread,
Sep 16, 2011, 2:01:50 PM9/16/11
to growl-fo...@googlegroups.com
If you have the most recent previous version, the installer can be
found here: http://www.growlforwindows.com/gfw/d.ashx?f=Growl_v2.0.6.1.zip

> --
> You received this message because you are subscribed to the Google Groups "growl for windows" group.
> To post to this group, send email to growl-fo...@googlegroups.com.
> To unsubscribe from this group, send email to growl-for-wind...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/growl-for-windows?hl=en.
>
>

war59312

unread,
Sep 19, 2011, 10:51:57 PM9/19/11
to growl for windows
I too had this error when updating over 2.0.6.1 using the msi
installer.

I then ran the normal setup.exe program and it updated successfully
this time. :)

Running Windows 7 x64 SP1.

Hugo Ahlenius

unread,
Sep 20, 2011, 6:07:53 AM9/20/11
to growl for windows
I am having quite some problems upgrading, on my Vista Urtimate x64
machine. When trying to install over the existing installation I get a
MSI 2869 error. I even tried the msiexec /i trick, but I got the same
error. When trying to uninstall (from the control panel) the existing
version, I get an empty dialog box signifying some error in the
uninstall...

I haven't tried rebooting and trying again, will do that next...

Hugo Ahlenius

unread,
Sep 20, 2011, 7:20:29 AM9/20/11
to growl for windows
On Sep 20, 12:07 pm, Hugo Ahlenius <fraxi...@oxel.net> wrote:
> I haven't tried rebooting and trying again, will do that next...

Rebooting didn't help, but msiexec /a seemed to do the trick (note
that I have UAC turned off, and I do all operations as a local admin)

Here are some info from a MSI log file that might be of help... ?

MSI (s) (F8:08) [13:07:38:985]: Executing op:
CustomActionSchedule(Action=_269BC53F_271D_4F01_93C7_EF9B1E3DFB86.uninstall,ActionType=1025,Source=BinaryData,Target=ManagedInstall,CustomActionData=/
installtype=notransaction /action=uninstall /LogFile= "C:
\programx86\system\Growl for Windows\Growl.exe" "F:\temp\CFG2EE.tmp")
MSI (s) (F8:7C) [13:07:38:994]: Invoking remote custom action. DLL: C:
\Windows\Installer\MSI5EB.tmp, Entrypoint: ManagedInstall
MSI (s) (F8!54) [13:07:39:202]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (94:E4) [13:07:39:203]: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2869: The dialog ErrorDialog has the error style bit
set, but is not an error dialog
MSI (c) (94:E4) [13:07:39:707]: Font created. Charset: Req=0, Ret=0,
Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2869. The arguments are: ErrorDialog, ,
MSI (c) (94:E4) [13:07:51:841]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (94:E4) [13:07:51:841]: Product: Growl for Windows -- The
installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2869.
The arguments are: ErrorDialog, ,

Error 1001.
MSI (s) (F8!54) [13:07:51:843]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (F8!54) [13:07:51:844]:
MSI (s) (F8:7C) [13:07:51:845]: Leaked MSIHANDLE (44) of type 790531
for thread 1620
MSI (s) (F8:7C) [13:07:52:281]: Note: 1: 2769 2:
_269BC53F_271D_4F01_93C7_EF9B1E3DFB86.uninstall 3: 1
MSI (s) (F8:7C) [13:07:52:281]: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2769: Custom Action
_269BC53F_271D_4F01_93C7_EF9B1E3DFB86.uninstall did not close 1
MSIHANDLEs.

Noodles

unread,
Sep 20, 2011, 7:17:10 PM9/20/11
to growl for windows
Did the UDP protocol (for notification forwarding) change? Looking at
the GFW UDP notification packet, there's now an extra 2 bytes around
the flags or notification length (either that, or one of those 2-byte
fields is now a 4-byte field). I use GFW with mumbles (growl for
Linux), and the forwarding to mumbles wouldn't work until I changed
the packet decoder.

Brian Dunnington

unread,
Sep 20, 2011, 10:03:13 PM9/20/11
to growl-fo...@googlegroups.com
It shouldnt have changed at all. I dont recall being in any of that
UDP code for quite some time, but I will take a look at the version
history and see what I can find. If this was an accidental change,
then I apologize for breaking it for you. I will report back as soon
as I have had a chance to investigate a bit more.

Brian Dunnington

unread,
Sep 20, 2011, 10:25:28 PM9/20/11
to growl-fo...@googlegroups.com
Yup, you are right. The 'flags' are coming through as a 4-byte field
now instead of 2, which is incorrect. I modified an underlying class a
long time ago and forgot to change one of the casts from a 'int' to a
'short'. I will do a new build (2.0.7.2) and upload it to the server.
You should get the auto-update prompt when it is available.

Thanks so much for finding that and letting me know.

- brian

Noodles

unread,
Sep 20, 2011, 10:43:47 PM9/20/11
to growl for windows
Thanks!

On Sep 20, 7:25 pm, Brian Dunnington <briandunning...@gmail.com>
wrote:
> Yup, you are right. The 'flags' are coming through as a 4-byte field
> now instead of 2, which is incorrect. I modified an underlying class a
> long time ago and forgot to change one of the casts from a 'int' to a
> 'short'. I will do a new build (2.0.7.2) and upload it to the server.
> You should get the auto-update prompt when it is available.
>
> Thanks so much for finding that and letting me know.
>
>  - brian
>
> On Tue, Sep 20, 2011 at 7:03 PM, Brian Dunnington
>
>
>
>
>
>
>
> <briandunning...@gmail.com> wrote:
> > It shouldnt have changed at all. I dont recall being in any of that
> > UDP code for quite some time, but I will take a look at the version
> > history and see what I can find. If this was an accidental change,
> > then I apologize for breaking it for you. I will report back as soon
> > as I have had a chance to investigate a bit more.
>
Reply all
Reply to author
Forward
0 new messages