I think your COM or .NET assembly is a good thing -- for Windows users. Even if we could get it to work with MONO or something, may "Linux purists" such as my self would not want to use it. Why download MONO, and have to convert your project to use .NET, etc; when we could just design it for the common denominator: C?

That is why I want to port your RDS component to Linux. What we would have in the Linux Universe is this:

HQCT Kernel Module: Runs as a driver in the kernel. Handles Radio Interrupts and sends low-level commands to the module. Written in C and ASM.

HQCT User Library: A C Library that has useful API functions. This library talks to the kernel module. Other language bindings can either wrap the C functions, or just reimplement the C library (talk direct to the driver).

HQCT RDS Library: Used in unison with the User Library. Provide RDS decoding.

Anyways: I already have parts 1 and 2 done. Part 2 (the user library) is a very nice API IMHO. Much better than in Windows where each frontend has it's own redundant code. Part 1 could use some optimizations

Could I get a copy of the latest RDS source code in order to write Part 3? I don't think we can get a single 'universal driver' that will work on all OSes- Mainly because Windows is áss-backwards. However, we can have a similiar interface on all OSes. What we want, at least, is ONE implementation per OS.