Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

Samples from Users

• 1028 Error using Go rather than Run Button
• Add Separator to the WinBatch Studio Toolbar
• Adding File Types to Studio
• Background Check
• Bitness of WinBatch Studio
• Block comment and uncomment code
• Change File Save-Open Default
• Change Studio Default File Open Path
• CLR Files for Other Extensions
• Code to Convert Hex to Decimal in Studio
• Custom Syntax Colorization
• DirGet returning Winbatch System Subdir
• Disable Studio Keyboard Shortcut
• Extended ASCII Cursor Placement Issue
• F12 in WinBatch Studio
• Foreign Language Search
• Hitting n Key Causes Strange Behavior
• Interactive Debug Mode and GoSub
• Keyboard Shortcuts
• Keyword Lookup not Working
• Manipulate open file or highlighted lines in WinBatch Studio
• Null characters found
• Pass Params in Winbatch Studio
• Pass Parms to WBT while in WB Studio
• Problem wRight wLeft and wGetChar
• Recreate WinBatch Studio Environment
• Regular Expression searches in WinBatch Studio
• Save As Dialog in WB Studio
• Shift-F1 stopped working
• Turn off WinBatch Tips
• Unable to Run WIL Extension
• Using Debug to See Contents of Array in Studio
• WinBatch Studio Choppy and Slow
• WinBatch Studio Window Missing
• Wrap lines to a specific length
• WSHELP.DLL - WSHELP.INI question
• WSINIT.DLL Process Stays When Studio Opens

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

My 'n' key does not work right

Keywords:   My 'n' key does not work right  hotkey Winbatch Studio hotkey hitting n key wrong bad shortcut

---

Question:

Since testing my Winbatch installation on two different computers, the "n" key does not work properly on either.

When I try to rename a folder with an "n" in the name, it: - either does not work at all, or - it switches to the opened MS Explorer window, if one is opened. The shift N works fine.

I even removed the WinBatch popup from my startup group, but no joy.

Answer:

This bug does seem to show up from time to time. Mostly with people from Europe. It is always the "n" key and it seems to launch Explorer.

This is a tough one. In the past I've heard mention that installation of WinEdit causes this problem. WinBatch Studio is a cousin of WinEdit so I thoguht that the problem was related.

I have also heard mention that de-installing fixes the problem. But I have never actually seen the bug myself, and most of the people who mentioned it were from Europe.

Hmmm. I searched the net for a while (google, altavista deja) and did not find much. But I did find a PC Magazine utility that may be helpful.

http://www.zdnet.com/pcmag/pctech/content/15/11/ut1511.001.html

You might consider installing this software and see what it thinks about your hotkeys. The results may be informative.

Resolution:

I downloaded and ran the hky utility. It showed one hot key defined (not the "n" key). So here's where things get real confusing...

I disabled a background task using StartupCop and rebooted the PC to test and see if it affected the problem. When the PC was rebooting I decided to come up in "Safe Mode" first to see if the problem existed at that level. It did not so I rebooted again to complete the original test.

The problem disappeared!

I re-enabled the same background task again and rebooted once again. Now the PC is back to it's original configuration (still minus WinBatch). The problem is still gone. The only thing left to do is reinstall WinBatch... I have no idea what's going on, now...

I think I'll try bringing up one the other PC's (that still have the problem) in Safe Mode and see if that "cures" the problem...

I'm ready to break out the rubber chicken...

The Next day....

Here is what I found...

I re-installed Winbatch on the PC that I was testing with. The problem has not re-appeared.

I checked a different PC this morning to confirm that the problem did still exist. I ran the hotkey utility and it showed no hotkeys defined. It did still have "the problem", so I rebooted the the PC in "Safe Mode" and tested to see if the "n" key was still a problem. As expected, there was no problem in "Safe Mode".

I Rebooted the PC normally and re-tested. The problem is gone!!!

That was the ONLY things done to that PC. NOTHING else was done or run on that PC.

So, maybe someone else can confirm that rebooting in "Safe Mode" somehow magically clears this mysterious problem. It's worked on 2 PC's here...

Chalk another one up to the Rubber Chicken!

---

Article ID:   W15016

File Created: 2001:11:13:11:52:14

Last Updated: 2001:11:13:11:52:14