I’ve been using this very useful product on a Windows XP machine for some time.
Recently I acquired a new Vista machine, and of course put Quick Unicode onto it. I tested it, and it seemed to work fine. To make sure it was always running, I dragged a shortcut of Quick.exe into the Startup folder on the Start menu so that it would automatically be started whenever I began a new session.
A couple of days later, when I tried to use Quick Unicode Tools, I found that it wasn’t working properly. The pseudo-alpha keys on the numeric keypad mostly weren’t working and the hex mode didn’t work, along with a few other erratic errors I don’t recall now. I put it down to just another program that didn’t (yet?) work properly under Vista.
However, a web acquaintance who was also using Quick Unicode Tool on Vista stated he had encountered no problems. It turned out that he had not placed a shortcut of the program into the Startup folder and was always manually turning on the program. I also tried that on my system, and the problems vanished entirely.
I don’t know whether this is a peculiarity of Vista or whether there is some other program that is coming up during startup which is interfering with Quick Unicode Tool. I doesn’t matter much, as the program now works properly provided I manually start it up.
I’ve posted this in case anyone else has encountered this problem.
