Assume you have windows help file(which is written using robo
help).Now launch that help file through your java application.
Now if you close the java application the windows help file
will not get closed.Similarly the multiple copies of the same
help file will get launced if you click help again and again.
Java does not have any control over the help file.
This is the code by which you launch the help file.

Runtime r= Runtime.getRuntime();

		try{

			Process p=r.exec("winhlp32.exe");
		}catch(IOException e){

			System.out.println(e);

		}

The windows help file gets lauched in it's own process space.
Java provides you with only methods to kill a sub-process
and it does not provide you methods to kill a process.This is
a bug.
(Review ID: 53593)
======================================================================

There is no work around for this problem right now. The only
work around this always use HTML files as your help files for
your java application.
======================================================================

As long as the native process is a subprocess of the Java process,
you should be able to kill it with Process.destroy().  If not, you
are on your own.  Killing an uncooperative process is in general not
something that can be done in a reliable and portable way.

  xxxxx@xxxxx   1999-05-03

It seems the winhelp explicitly detach from the parent java process. So there is nothing we can do. The java/lang/Process is a native os process. As long as it follows the common native semantics, it seems ok.

  xxxxx@xxxxx   1999-05-03


WinHelp uses two processes. While Process.destroy() kills the first one,
it has no means to find out about the other one.  This is not a Process
bug. The customer may want to implement a custom native function to kill
both processes or to send Close message to the top level window of
winhelp


  xxxxx@xxxxx   2001-11-08

This means you cannot use windows help for an java application. My application is only
for PC use.