|31 Jan 2012||#1|
| || |
Rename the DelegateExecute registry value for WMP-associated filetypes
To run WMP 12 (32-bit) in multiple instances, I used a hex editor to change the values of 6 consecutive bytes of wmplayer.exe into 90h, starting from 0x823h, as instructed in this PDF.
I succeeded. I ran the patched wmplayer.exe several times, and I got several WMP's on the screen.
But it's still imperfect... because when I clicked on a couple of video/audio files in Windows Explorer, only one instance of WMP would run.
Later I found that if I renamed the registry value DelegateExecute for WMP associated filetypes, multiple video/audeo files could be played simultaneously, each in a WMP instance.
For example, if the DelegateExecute values in the following two registry keys are renamed, then WMP could play AVI files and WMV files seperately in the same time.
But a question lingers in my mind:"Will renaming DelegateExecute generate any bad things?"
|My System Specs|| |
|Similar help and support threads for: Rename the DelegateExecute registry value for WMP-associated filetypes|
|'Rename' box doesn't show up when I rename a file shortcut||General Discussion|
|Registry problem after windows update and registry optimization tool||Backup and Restore|
|Bypass Open with dialogue for known filetypes||General Discussion|
|Changing icons for specific filetypes?||Customization|
|Image filetypes with password option?||Chillout Room|