WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

Winbatch Studio
plus

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

WSHELP.DLL - WSHELP.INI Question

Keywords: 	  WSHELP.DLL WSHELP.INI

Question:

First time, today, yes, I had the need to register a private helpfile into WinBatch's help lookup system.
I've read in the wshelp.ini file:
; Although you may define all the types you wish, please use numbers above
; 99 to define your own provate formats (WWW reserves help file types
; 0 thru 99. Currently defined HelpFileTypes are: ...
So I used the [WIL] section and put my file on place HF100 in the hope, it would be all right.
...
HF30=RAS.hlp 2
HF31=Reggie.hlp 2
HF100=xcam.hlp 2
... and failed.

But this works:

...
HF30=RAS.hlp 2
HF31=Reggie.hlp 2
HF32=xcam.hlp 2
I think the loop 1..1000 and the various break outs in wshelp.dll script runs not clean, so that the hole in the inifile hides the HF100 entry. Please look into.

Next question:

It would be nice, if the keyword/helpfile lookup routine can access the weh files in descending order of their last access. For my case I do not have the need to search through adsi.weh or hugemath.weh each time i do a keyword lookup. This would speed up the lookup process, I think so.

Answer:

Ummm. The HFxxx items must be listed in incremental order. wshelp.dll loops through the items one by one. When it doesn't find the next item it breaks from the loop.

Windows help files are "type 2" We want to hang onto types 1 thru 99, so if wou want to add some new strange kind of help file, please start at type 100

Searching the help files in order or last access or frequencey of use would be nice, but the current code works pretty well and I am kind of scared of changing it.

Question (cont'd):

My fault. I interchanged filetype with filenumber! Sorry. I will add a standard winhelp file, that is type 2. Should work, but it doesn't work yet. Have to look a bit closer into this tricky box.

Answer:

Don't forget the corresponding *.WEH file....
Article ID:   W15779
File Created: 2003:05:13:11:30:02
Last Updated: 2003:05:13:11:30:02