zachd [MSFT] wrote:
> Let's step back to the beginning: ~why~ is the player using the CD
> player at that time when you're trying to burn?
My question exactly...
If the player isn't
> burning, I don't believe it's going to try to acquire a lock on the
> burner: that seems like something else might be going on.
> What app are you using to burn?
Been using it for ages on xp on the same hardware with no problem.
One thing I just realized is that I replaced a USB hard drive with
a USB flash drive at about the same time I switched from XPSP2 to
VistaSP1 They are known to behave differently.
> As regards "not starting the player" : you're starting services
> (mobsync, for example) that use the player.
Yep. That's been discussed. I found some tools to disable that,
but I'm waiting till the next system backup before I try it.
Unknown tools from unknown developers is risky.
When I plug in a usb drive, I want a drive letter assigned...NOTHING ELSE!!!
> As regards "killing the player": what you're trying to do there is not
There's supported and then there's useful unsupported. Most of the best
stuff is in the latter category.
Third party system-destroying tools such as vLite might give
> you what you want there
I'll have to take another look. Thought vlite only worked on the
initial install setup. Can I apply it after the fact?
, but : you really would be taking a hammer to
> your system and breaking it.
If that's what it takes...
I've never found ANY reason to knowingly activate wmplayer.
Removing the player system may have unintended consequences with other
players that expect certain OS support files. If I can just prevent
it from executing, I'd be a happy camper. Renaming the file works for a
while. If I could prevent it reinstalling itself, I'd be a happy camper.
One man's breakage is another man's fixing.