Community archive

Ask something
Discussion Locked

WinHelp Temp Files Problems - Help?

0 helpful
5 replies

by dprenger

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have an application that uses WinHelp (created using eHelp/RoboHelp Classic) and our Help files have always been maintained on the Server where Clients access the programs. The temp files (.FTS and .GID) have also always been created in that same Help folder. We recently upgraded our RoboHelp Software version (coincidence?)and now we seem to be having various and sporadic Help related problems. E.g. one user can't display the 'Find' tab of Help, although another user with the exact same setup can. There are no .GID's or FTS files on the Client machines or references to such in their Registry.

At eHelps recommendation, we tried to write protect the Help folder on the server so that the temporary files would be forced on the Client machine in C:Windows\Help, however they continued to be created in the write protected Help folder on the server!

5 replies

by bobho

If you write protected the folder and the gid files are being created in the folder then either someone or a group still has write access there. Make sure that all access rights are removed other than read (and possibly file scan depending on your network). This would be like opening a help file on a cd. The gid files will be created in the user's \help directory.

Enjoy,

DrBob:>)

by dprenger

I passed this info on to my in-house Tech Support and he tells me that this answer doesn't apply as we are working on a controlled environment with a 2-machine setup, the server is Windows '98 and the Client is Windows '98, which doesn't ahve the acess rights and groups mentioned.

by bobho

Well, that makes a difference. Since you are using win98 and not a network system like nt, 2000 or novell you can still make the directory read-only. Do not share the entire drive. Go to the folder with your help files ? Right click on the application program folder.

Select sharing.
Select shared as and choose read-only
Use a password if needed. Click apply and ok

Try it.

DrBob:>)

by dprenger

Setting the folder to "Shared as Read Only" resolved the problem. The temporary files defaulted to the client pc.

This discussion is closed to new replies.