Scott Hanselman's Computer Zen - How to get SlickRun to activate with Windows-R

First time here? Check out the site's "greatest hits" or read a post from the archives. Feel free to leave a comment or ask a question, and consider subscribing to the latest posts via RSS or e-mail. Thanks for visiting!

« Making a list and checking it thrice | Main | System won't pass the BIOS POST - Yank e... »

How to get SlickRun to activate with Windows-R

Posted in Tools.

It's funny, when folks see me using SlickRun, they always notice that I've bound it to Windows-R, replacing the standard Start|Run dialog.

This is one of the questions I get the most often. Unfortunately it's not very well documented in SlickRun, and if you try to set it via the options dialog, you'll get get a a message saying it can't grab the global hotkey.

You have to open SlickRun.ini in C:\Documents and Settings\username\Application Data\SlickRun and add an option under the [General] section "GrabWinR=1". I also like to set ChaseCursor=1 so SlickRun will come up under the current mouse cursor position.

Posted at 2006-11-28 02:04 PM by Scott
Comments [10]
Permalink

Tuesday, November 28, 2006 2:28:24 PM (Pacific Standard Time, UTC-08:00)

I have Slickrun bound to both Windows-R and Windows-Q. I only do that to completely remove the Run command from the Start menu, but I've found Windows-Q to be far more comfortable, especially being completely unable to use my pinky for key combo's.

I thought you were a notepad2-er though?

Ryan Cromwell

Tuesday, November 28, 2006 2:30:09 PM (Pacific Standard Time, UTC-08:00)

Ya, I am, but I lost my slickrun keys a while back, and I haven't hooked notepad2 up yet. Now I will. ;)

Scott Hanselman

Tuesday, November 28, 2006 2:49:17 PM (Pacific Standard Time, UTC-08:00)

Thanks for writing about this. I installed slickrun a while ago, but never could get used to hitting windows+q. Old habits die hard. Now I'm back on the slickrun train.

Chris Norris

Tuesday, November 28, 2006 4:06:31 PM (Pacific Standard Time, UTC-08:00)

Scott, are you still using slickrun with Windows Vista? I'm loving the new search/run feature in vista. Just press the Window key and start typing. It gives you all the functionality of run, with the added benifit of filtering down your start menu and searching your documents at the same time. All this with only one key to press.

Rob Boek

Tuesday, November 28, 2006 7:33:04 PM (Pacific Standard Time, UTC-08:00)

Hmmm, there's no SlickRun.ini file where you say so? I'm running 3.9.4.1.

Bil Simser

Tuesday, November 28, 2006 10:30:03 PM (Pacific Standard Time, UTC-08:00)

I use slimKEYS, and I use Win+Space as the hotkey for the launcher. The advantage of slimKEYS is that it's not just a launcher. It's a plugin-based hotkey manager, so you can pretty much assign any hotkey to any plugin (launching apps/documents, manipulating windows, ...)

Tommy Carlier

Wednesday, November 29, 2006 5:40:27 AM (Pacific Standard Time, UTC-08:00)

Bil Simser, I had the same problem. Go into your settings for SlickRun, and change one or two. This should then put the SlickRun.INI file in place, and you can edit the GrabWinR setting.

Eric D. Burdo

Thursday, November 30, 2006 3:47:58 AM (Pacific Standard Time, UTC-08:00)

Scott, one problem to note (well on Vista anyway) if you set ChaseCursor but not GrabWinR then SlickRun seems to stop popping up on my Win+Q key selection. Bizzare.

Simon Wilson

Friday, December 01, 2006 9:50:29 AM (Pacific Standard Time, UTC-08:00)

Hey Scott,

I changed the GrabWinR value from 0 to 1 in my SlickRun.ini but it didn’t work. And when I shut down the SlickRun app and restart it, the value is reset to 0 in the ini! Have you heard of this?

Bob

Bob Uva

Friday, December 01, 2006 10:21:09 AM (Pacific Standard Time, UTC-08:00)

Bob,

Before you change the .ini file you must exit SlickRun. SlickRun saves .ini files when it exits and overwrites the changes you made. So do the following steps:

1. Exit SlickRun.
2. Modify and save SlickRun.ini.
3. Start SlickRun.

It should work.

Vadim

Vadim

Comments are closed.