Shift-F1 stopped working

Keywords:   Shift-F1 stopped working

---

Question:

I was using Winbatch Studio on a different computer than it was installed on (through a mapped drive) and hit Shift-F1 to display help on the function my cursor was currently on. It prompted me to select the help file, but I picked the wrong one by accident. Now, even on the computer the software is installed on, Shift-F1 brings up the wrong help file. Any way to set it back to the way it was?

Answer:

Go into:

...\WinBatch\System\Help

Look at both the WSHELP.INI file and perhaps the WEH file associated with the help file. Examine both for the bad data. Fix.

Make sure all the HFxx entries are actually HFxx and not FHxx which was a bug floating around some time ago.

Basically the first time you hit a *.hlp file, a lot of thrashing aorund occurs to locate the file. Once the file is found, the located= entry is added to the weh file.

If you are interested in how all this really works, see the wspopup.mnu file that captures the right-click keyword lookup menu item and forwards it to the same place the Shift-F1 does, which is the wshelp.dll file.

Now, in spite of the DLL extension on this file, it is just a plain WinBatch script file. Find the :KEYWORDHELP entry point in the file. That's what both the SHift-F1 and the wspopup.mnu functions call. That kind of sorts out the help required, finds the files, runs help etc etc etc.

---

Article ID:   W15351