Video – Kiwi

Kiwi video screenshot - Click to go to the video's page on YouTube.
This is a bit of a sad video – watch it ’till the end and you’ll see what I mean…

Windows zero-day exploit – ANI Exploit

Depending on what you use, this is kind of an important issue you should look at – it’s about an unspecified vulnerability involving loading of ANI (animated cursor) files embedded in web pages, which can lead to arbitrary code execution.
Basically, if you use MSIE or Outlook (and maybe anything that uses the MSIE rendering engine), you are affected and should (in my opinion at least) take steps to mitigate the issue:
• Install the temporary patch provided by eEye:
• Update your AV program.
• Don’t use MSIE or anything that uses the MSIE rendering engine (i.e. Outlook 2003 (and below) ).
You can find further information at:
Microsoft’s website:
eEye’s website (inc. temporary patch):
—- Update —-
03/04/2007 @ 23:53
Microsoft have now released a patch for this (under MS07-017) – go update you computers!
See URI below for more information:

SQL Error solved – “Syntax error converting from a character string to uniqueidentifier.”

If any of you ever come across this kind of error when running a SQL query to query tables:
Server: Msg 8169, Level 16, State 2, Line 1
Syntax error converting from a character string to uniqueidentifier.
Make sure you cast the matching field to the correct data type – for instance (Querying for SQL Reporting’s report subscriptions):


FROM ReportServer.dbo.Schedule INNER JOIN ReportServer.dbo.ReportSchedule
 ON ReportServer.dbo.Schedule.ScheduleID = ReportServer.dbo.ReportSchedule.ScheduleID
  INNER JOIN ReportServer.dbo.Catalog
  ON ReportServer.dbo.ReportSchedule.ReportID = ReportServer.dbo.Catalog.ItemID
   INNER JOIN msdb.dbo.sysjobs
   ON = cast(ReportServer.dbo.Schedule.ScheduleID as sysname)

 In the example above, note for the last line:
ON = cast(ReportServer.dbo.Schedule.ScheduleID as sysname)
"ReportServer.dbo.Schedule.ScheduleID" is cast to sysname – which is the data type for ""
I guess if you think about this, it’s rather obvious you can’t compare apple to oranges…

My switch to Ogg Vorbis

Vorbis logo
Finally, I’ve dumped WMA and made the switch to Ogg Vorbis.
And for anyone who’s planning to do that, here’re some tools that you’ll probably need:
• Cool Edit Pro / Adobe Audition:
(You’ll just have to find a copy somewhere yourself…)
• OGG plugin for CEP / AA:
• dB Power AMP Music Converter (and Vorbis plugin):
• ffdshow:
• OGG Splitter (you’ll need this if you want to play Vorbis files with Windows Media Player – even with ffdshow installed…):
• WMP Tag Support Extender (if you use WMP and want to import OGG files into WMP library):
Explorer shell tools:
• Vorbis Extension (lets you edit tags via the file properties window):
One problem if you are using WMP 11 is that currently, seeking for Vorbis files is broken once it is imported into the library – the only usable solution is to downgrade to WMP10… Arh well