Those guidelines may be good for software companies that want to get a fancy "Designed for XP" logo on their product, but they are no commitment whatsoever for people who are developing software as a hobby, like me. If I would have to make sure that my programs follow all the guidelines, I would probably spend all my free time on just that and have no time left to implement any new features. That being said, I do try to follow most of them, but only when the required work is proportional to the importance.
Also, if I would have to choose between a new feature that only a few people will notice, and one that lots of people will like, I would much rather spend my free time on the latter.
If you are so concerned about security, then why aren't you running Vista?
I just think it's a bit disrespectful of you to label my plug-in as "crap", considering all the work I have put into it. Maybe the plug-in works alright for many other people and maybe they are happy with it? If you aren't happy with the plug-in, then just don't download it, it's that simple. And if you really feel the need to express your criticism in a forum, then please let it be a little more constructive than just calling it "crap".
That is correct, SPTI requires administrator rights on XP and 2003. The workaround is to make the SPTI calls in a service instead and let the service pass the results back to the application. A solution that is overkill for a simple plug-in that just wants to read CD-Text, IMO.
Tim De Baets