Just to share a few things. I got it set sucessfully as HotKey =0x653 ; hex 200 + 400 + 53 where 200 is Ctrl + 400 is Alt + 53 is S Thanks to ricktendo64, OnePiece & bphlpt for some thought & info on this. I google around and found this vb forum post (small software) where you press a key and it returns dec & hex code. Might be useful somehow without going to MSDN for the keycodes. http://www.vbforums.com/showthread.php?t=499084 Download 1st post attachment, extract and find in bin folder, keycodes.exe (found it can run standalone) So while fiddling with combination of hex codes, found Shift + (which might be useful) has 0x115 or 0x107 (yes both codes set the same hotkey) Since 200 = Ctrl + and 400 = Alt + , it might means some other values might also be valid for Ctrl + and Alt + respectively. Just need to know which value. (I was googling when I stumbled 200 & 400 value and I didn't take note of the url. But it was from a vb forum thread where some codes are posted for Ctrl + and shift +. Unfortunately, the thread did not indicate how it derived these values as discussion was something else) With this info, bphlpt, setting Ctrl + Alt + A hotkey is much easier now. Just add these hex code: 200 + 400 + 41 You don't have to install Pretty Run to test. I made another simple inf for anyone who wish to test. I use "Disk Defragmenter.lnk" that is found in Accessories\systen Tools on XP so that you can see the effect. (View the .lnk properties before applying this inf test) [Version] Signature=$Windows NT$ [DefaultInstall] ProfileItems=Start.Shortcut1 [Start.Shortcut1] Name =%ShortcutN1%,0x8,23 SubDir =%ProfileSubdir% CmdLine =11,,dfrg.msc WorkingDir=11 ;HotKey ="Ctrl + Alt + A" ;Desired hotkey HotKey =0x641 ; hex 200 + 400 + 41 ; where A=0x41 Infotip =Defragments your volumes so that your computer runs faster and more efficiently. [Strings] ShortcutN1=Disk Defragmenter ProfileSubdir=Accessories\System Tools Now, just press Ctrl + Alt + A and wait for Disk Defragmenter to launch. Now we have some real solution to this thing but do not know if it is consistent globally or just limited to English US 101 keyboard . Same thing to consider when running on laptop or non-english keyboard such as Japanese / French etc. What if it is english keyboard but not 101 type? I really don't know. Perhaps "Windows SDK documentation" might throw the rest of the light over this issue, but then it is yet another mystery to find out. (lol) Cheers