Defect sounds so severe! I'm sure its something wrong on my end... but I don't 
know 
what to do to fix it. Although, I suppose since it didn't work right out of the 
box... technically... it is something that should either be noted as a required 
setup 
item or be fixed by the installer. As such, technically, it is a defect. Let me 
know 
if there is anything additionally that I can do to try to help solve the issue.

I have now found this command as a means of making this work:
regsvr32 "C:\Program Files\Vortex Software\Growl For 
Windows\Displays\WebDisplay\WebKitDependencies\WebKit.dll"
The only issue I'm now running into is one of the images being displayed as 
question 
mark blocks (reminds me of the question mark blocks in Super Mario Bros.).
Investigating further now... I don't see what's going wrong. :-(
Seems that the "growlimage://%image%" doesn't work correctly on my system. I'm 
keeping this with the HTML engine rendering not working as I think its somehow 
related to that.

thanks for the bug report. unfortunately, registering the WebKit.dll manually 
is the 
only fix for the initial problem you describe. a few other people have reported 
it 
as well, but i have not been able to reproduce it in order to find out what is 
wrong. (during the install process, the .dll is supposed to be registered using 
regsvr32 as well, but either it is 1) not doing it (perhaps due to Vista 
permissions?), or 2) the command is failing silently for other reasons). i will 
keep 
investigating to see what i can find, but i only have an XP computer to test on 
at 
the moment.

as for the broken images not showing up in the WebKit displays - does it work 
for 
the 'Standard' display but none others? or does it not work for 'Standard' 
either? 
the WebKit support in this version is very experimental and i dont think 
the "growlimage://<%image%>" syntax works at all. the 'Standard' display has 
some 
modified HTML that doesnt use that syntax is why i ask.

(if you go through the other WebKit displays, you will see that a few of them 
look 
messed up beyond just the broken image - i am not sure if this is a WebKit-on-
Windows problem, or something else on our end, but a few are essentially 
unusable.)

all that said, the WebKit support was an experiment to see if we could use the 
Growl 
for OSX displays without modification, thus enabling the displays to work on 
both 
platforms without changes. since Windows is not very WebKit friendly at the 
moment, 
this may be harder than i wished. I am even considering dropping the WebKit 
support 
altogether (and either coming up with a different HTML-based display option, or 
abandoning the concept altogether).

Correct me if I'm wrong... but if we're not using the Growl for OSX displays 
without
modification ... how are we really all that different from Snarl?

although the displays may be different, it is the underlying notification that 
is 
the same. we are using the Growl UDP protocol for the format of the 
notifications, 
which means two things:

1) notifications from Growl for Windows can be forwarded to Growl for OSX and 
they 
will understand them, and

2) notifications from Growl for OSX could be sent to Windows and understood 
(although currently Growl for OSX limits the computers you can forward to to 
computers on your same network running Bonjour). (also note that i have an 
uncommitted change in place that exposes Growl for Windows via Bonjour so Mac 
clients can see them)

also, keep in mind that this is only an early version of the software. i am 
currently working with the Growl for OSX guys on defining a new cross-platform 
protocol that can be used on Mac, PC, Linux, AIR, web, etc that will allow 
everyone 
to 'talk the same language'. once that is done (it is close), i will release a 
new 
version of the software that supports the new protocol.

the displays are really just the eye candy portion. to make the best displays, 
it is 
useful to use native OS functionality (like Win32 APIs, etc). in fact, most of 
Growl 
for OSX's displays are native displays (Cocoa), not WebKit. someone could 
create a 
display that 'looks' just like Music Video for instance, but the underlying 
code 
would be different for the different platforms.

This is very useful information. I'm currently working on an Intranet 
application 
that I'd like have issue Growl notifications on various events. With the 
combination 
of PHP-Growl and your Growl-for-Windows... hopefully that will be possible.

With the new protocol... will old Growl still work or will it break the 
existing 
Growl infrastructures?

I'm eager to help with anything I can... I don't have much time to offer, but 
I'm 
more than willing to help test and report issues or problems. Let me know if 
there's 
anything that I can do to help further. :)

glad it helped. i know that a few people have used PHP-Growl to send 
notifications 
to Growl for Windows and it works just fine, so you should be in luck there.

with the new protocol and new software, i plan to continue to support the old 
protocol as well, at least for a few versions. since it is already built, there 
is 
not that much overhead in keeping it around. however, the new protocol will 
offer 
much more functionality (ability to send images, perform callbacks, etc) so 
most 
apps will probably want to upgrade anyway.

as for helping out - keep testing the current version and reporting any issues. 
it 
is beta software, but the main functionality (other than WebKit displays) 
should 
work. once the new protocol is finalized and the new software gets farther 
along, i 
(we) will need all the help we can get in testing it out and hunting down bugs.

thanks!

If you'd like any assistance with the code.google wiki, etc... let me know... 
i'd be
happy to help keep the feature list maintained for you so that you could focus 
on
development in-between your trips into the woods. ;-)

i added you to the project (i just guessed on your email address, so let me 
know if 
i added the wrong andrew gearhart). it would be great if you wanted to do some 
documentation and get the wiki going. thanks a ton!

Just a note that i installed the latest growl on two winndows xp machines and 
the
html popups were broken on both.  After manually registering webkit.dll both 
worked.

as this issue only affects the 1.x codebase, and the new 2.x code doesnt use the
WebKit.dll for rendering, i am marking this issue as closed.