When It Ain't Broke...

We use login scripts at work. We support a variety of clients, from Win9x up to XP Pro. One of the usefull shortcuts we've been able to use has been the %0 shorthand for the currently running program. We were finding that certain parts of our login script, the parts using %0, weren't running properly, but only on XP Pro clients. I spent quite a while on this, and felt like I was banging my head against a brick wall. Then I found the following: A Logon Script Does Not Work If %0 or %0\..\ Calls Multiple Commands. Apparently, %0 is not required in NT, 2000 or XP, so they decided to change the way it works in XP. Not to drop support for it, just change the way it works. Why do they insist on setting these kinds of booby traps for unwitting sysadmins and developers? Anyway, at least my code wasn't at fault.

[Listening to: Red Blooded Woman - Kylie Minogue - Body Language (04:22)]