The LED setting is the effect of lack of a single standard. Some time ago, PDA's (without phone module) used only LEDs (
light emitting diodes, in case you don't know what it is) to signal device state to the user. Different devices could have different number of leds, and use them for different functions, so system "sees" them only by their number - led0, led1, etc. If 00 is the power led, a notification led, or something completely different is device-dependent. Things got worse when pda's got phone modules. Since they became phones, people wanted to have all functions phones can offer, including vibration alarm. Someone came up with a good idea to hook up the vibration motor instead of one of the signal leds. This way existing API could be used without any modifictions, and there was no need to modify the OS at all. And everything would be great if everyone connected the vibe as the same led number. But there's no unified standard and every company hooks it up differently. Probably it's part manufacturers' fault since they seem to connect vibra and LEDs randomly, partially it's microsoft's fault, since they don't even propose standard LED layout. So now we do have easy access to vibration motors from programs, as long as we know where to look for them.
If your device has vibration alarm, this program will probably work. You'll just need to experiment with different LED numbers. Some can light up ledss on your device, some won't do anything at all, and only one will activate vibration. So if you found it, you can stop looking