Actually, no...

I don't even have a "Local Settings" directory under "Docs and Settings". I searched for all *.log and there was nothing relating to CF 'cept the old one in my 1.14 backup directory.

{rant}
Add a vote that I think it's VERY wrong to have the logs away from the app. It's one of my common gripes about Windows in that AppCrap (technical term!) is laid all over the place. Logs should be in something like:

{application directory}\logs

Makes them very easy to find and helps in not having to chase all over the place looking to clean up an app.

Oh well.
{/rant}

XM didn't survive an overnight hibernate. When CF came back up, XM was there and would react to clicks, but there was no content information (station names were displayed). I bounced settings a couple of times from XMPCR to XMDirect and back again, but nada. Exiting CF and reloading brought XM up.

I just checked after a short hibernate (about 10 minutes) and it _did_ come back up just fine.

NOTE: This means that XM is now running with the device option set to "XMDirect". If I set it BACK to XMPCR, it doesn't work. Now, given that when hibernate kicked in last night CF "thought" it was talking XMPCR, then I would suspect that when the module reloaded, it really DID set XMPCR and thus it didn't work. But then, I would have thought that flipping back and forth from XMDirect to XMPCR would have joggled it back to life. Hmmm...

XM keeps playing after exiting CF

Setting "Buffer enable" doesn't do anything, but I'll bet you know that and it's 'cause that as a plugin you no longer have access to CF's buffering?

Single click is _DEFINITELY_ fixed. WELL DONE!