Comfort Keys Pro 3.1Comments on:

By: JoeSchmoe

JoeSchmoe — Mon, 01 Sep 2008 16:24:09 +0000

Looks nice but consistently crashes an otherwise very stable computer when you do “About” Comfort keys and then hit the X (not the close button the the window close X) – totally crashes with no way to recover – scandisk comes up and I had lost files and truncated stuff. Uploaded the Setup.exe to Virustotal and 1 of 32 reported a trojan in the setup – not sure on that but the crashing makes it suspicious.

By: Lokesh

Lokesh — Sun, 31 Aug 2008 19:50:30 +0000

Lots of many freewares available to do these things.
Virtual keyboard is in built into windows 2000 onwards. just run osk.exe (on screen keyboard).

This program consumes a bit of RAM. so may need a RAM optimizer running in some systems.

By: Vilulf

Vilulf — Sun, 31 Aug 2008 09:42:04 +0000

@ # 17 , perhaps you need to re-read what I wrote.
I SAID…… it is released ONCE per day. there are 24 time zones on this planet.
that single releae time is DIFFENERENT “local apparent” time per time zone
but the release time is the same, and only once a day

lol sheesh

By: antivirus

antivirus — Sun, 31 Aug 2008 09:30:07 +0000

To #71. Just a FALSE POSITIVE.

By: Fubar

Fubar — Sun, 31 Aug 2008 07:07:28 +0000

#71, giovi 69, you should note that the review you quoted is for version 2, as #42, harpo2448, did for BladedThoth’s review.

#38, Karl, #53, Celt42, it shouldn’t be necessary to run Comfort Keys Pro as an Administrator under Vista. The Readme for the giveaway said to run Activate as an Administrator. I always like to trace what’s happening, so I first ran Activate normally. The trace showed virtual and real keys with the same value (the real keys were probably created from an earlier Comfort Software giveaway). Since there were real keys, I decided to go ahead and do the Setup. It wiped the real keys, and came up unregistered. That’s why I ran Activate again, as an Administrator, as I noted in comment #19. I don’t like to run programs as an Administrator unless they really need to be run as such. It’s possible that there may be some cases where Comfort Keys Pro needs to be run as an Administrator, due to Vista security, but that would be in relation to other applications (i.e., Comfort Keys Pro itself should run without Administrator privileges).

By: kevin

kevin — Sun, 31 Aug 2008 04:36:31 +0000

Autohotkeys is free and MUCH MUCH more extensible.

By: Eldad

Eldad — Sun, 31 Aug 2008 03:53:32 +0000

Thanks for the program, works great!
Eldad

By: Bigun

Bigun — Sun, 31 Aug 2008 03:19:19 +0000

There is something associated with this program that I found annoying. The on-screen-keyboard kept popping up almost constantly.

I checked the options settings and found that multiple keys had been setup to bring up the on-screen-keyboard. Not surprising but still annoying, I found that the on-screen-keyboard could not be blocked. I unselected all of the hot-keys but the “Windows Key” (today is the first time I have ever used it). Since I never use that key, the keyboard will stay out of sight. Just in case I might want to use the keyboard some day I changed the “disappearance delay” setting to 7000 msec.

By: Bigun

Bigun — Sun, 31 Aug 2008 03:09:35 +0000

#19 Fubar

Fubar: There might have been a change in the activation script between the times you and I activated and installed this program.

I ran “activate” before the setup file and checked the registration information immediately afterwords. It showed that it was registered:
“License agreement issued GiveAwayOfTheDay”

Good Day,
Bigun

By: gonzo

gonzo — Sat, 30 Aug 2008 23:58:54 +0000

Anybody here tried to use Comfort Keys Pro while running Sandboxie? CKP sure does bitch a lot under DefenseWall, another sandbox program.

All the nasty messages from Comfort Keys stopped as soon as I turned off DefenseWall 2.45. I’m surprised, mostly because no other program has evoked this response before, after six months of using DefenseWall. Usually DefenseWall just asks for permission to complete whatever action is requested and gives you an option for the same action to trigger no permission request next time.