Hi all, I've logged a new bug for win32-eventlog based on Joey Gibson's ruby talk post (116528). Park, I've assigned it to you for now, figuring that you're probably the one who best knows how to fix it. All help welcome. Dan