看看这份doc吧，长了点，hehe,但愿对你有帮助：2.0 Nothing happens when you try to start the help
Note: this section does not apply to Component Broker or WebSphere Business Components. For Component Broker please see the information on help troubleshooting in the doc\readme directory.If nothing happens with VisualAge for Java, Version 3.5 and you use a desktop icon to launch the VisualAge for Java IDE, see 2.1 Special case - VisualAge for Java, Version 3.5.If nothing happens when you try to launch help, your first step should be to determine whether you can launch help from the command line. To do this, you will first need to know what directory you installed your product in. In the text that follows, wherever you see INSTALL_DIR, you should substitute the actual directory your product was installed in, for example x:\ibmvjava or "x:\Program Files\IBM\VisualAge for Java". Use quotation s around the entire path (INSTALL_DIR plus any subdirectory or filename) when the path contains spaces. Follow these steps to try launching the help from the command line: Open a command prompt window.
Change to the logical drive the product is installed on, then to the directory on that drive. For example, if your product is installed at "g:\Program Files\IBM\VisualAge for Java", type the following:
g:
cd "\Program Files\IBM\VisualAge for Java"
Change to the directory beneath the product directory where the executable vahelp.exe is located. You can determine the location by first typing:
dir /s /b vahelp.exe
If this returns:g:\Program Files\IBM\VisualAge for Java\eab\bin\vahelp.exe
You would then type:cd eab\bin
Issue the following command (quotes are required only if the path contains spaces):
For VisualAge for Java:
vahelp instance "INSTALL_DIR\doc\ivjhlp.cfg" open index.htm
For VisualAge COBOL:
vahelp instance "INSTALL_DIR\help\Iwzif1.cfg" open index.htm
For other VisualAge products, first determine the name of the help directory for the product (typically doc, help, or hlp) by finding the directory containing .zip, .toc, and .htm files; then determine the name of the product configuration file in that directory (typically a file with a .cfg extension), then type:
vahelp instance INSTALL_DIR\HELP_DIR\CONFIG_FILE open index.htm
If help launches successfully from the command line and you can search the help successfully, there may be a problem with the way your path is set up, that prevents your product's user interface from connecting to the help system DLL. See 2.1 Special case - VisualAge for Java 3.5, or, for other products, try uninstalling and reinstalling your product, as this sometimes solves such problems.If you are satisfied with launching help from the command line as a workaround or temporary fix, you can create an icon on your desktop to do so. See 11.0 Creating an icon to launch product help.If the help does not load from the command line, or if it loads from the command line but not from within the product, you may not have the proper file associations set up for your browser within the Windows registry. See 16.0 Setting HTML file associations in the Windows registry. If changing file associations also does not help, you can try the following to obtain a log file from the help system:Edit the product help configuration file (INSTALL_DIR\HELP_DIR\CONFIG_FILE) in a text editor (e.g. Notepad) and add the following line to the end of the file:
HTMLHELP_LOG=1
Save the file. Be careful to save as plain text if using an editor like WordPad.
Exit and restart your IBM product.
Press F1 or use the Help menu to try to launch help from within the product.
In the directory pointed to by the TMP environment variable, you should see one or more files of type HTML*.C2T. These files contain detailed log information on requests made to the help system. You can send these files to IBM support to have them analyzed. A fee may apply to support requests. You can also try to examine these files yourself to see if you can determine what is causing the failure.If you do not see any HTML*.C2T files in your TEMP directory, try invoking help from the command line again. If HTML*.C2T files only get created from the command line, the problem is with your product invoking the help. If neither method of invoking help produces log files, the help system itself has a problem. In either case you can contact IBM support.Remember to remove the HTMLHELP_LOG=1 line from your product help configuration file when you are done, as the logging will produce unnecessary log files each time you request help.If you are still unable to launch help by any method, check that your product help configuration file is still valid. Open INSTALL_DIR\HELP_DIR\CONFIG_FILE in an editor and verify that: There are no leading or intermediary whitespaces within parameter settings:
HTMLHELP_HIDDEN=1
is valid, but:
HTMLHELP_HIDDEN = 1
is not. The only exception is a directory value with spaces in its path; for these values, enclose the entire path in quotes:
HELP="C:\Program Files\IBM\VisualAge for Java\doc\"
is correct, but:
HELP=C:\Program Files\IBM\VisualAge for Java\doc\
is not; this effectively sets HELP to the value C:\Program because without the quotes the value is parsed only to the first space.
The setting of the HELP= variable points to a valid directory (or multiple valid directories separated by semicolons)
If multiple entries occur of the same variable, delete any that seem incorrect. The first entry of a given name takes precedence over subsequent entries of that name.
Note: this section does not apply to Component Broker or WebSphere Business Components. For Component Broker please see the information on help troubleshooting in the doc\readme directory.If nothing happens with VisualAge for Java, Version 3.5 and you use a desktop icon to launch the VisualAge for Java IDE, see 2.1 Special case - VisualAge for Java, Version 3.5.If nothing happens when you try to launch help, your first step should be to determine whether you can launch help from the command line. To do this, you will first need to know what directory you installed your product in. In the text that follows, wherever you see INSTALL_DIR, you should substitute the actual directory your product was installed in, for example x:\ibmvjava or "x:\Program Files\IBM\VisualAge for Java". Use quotation s around the entire path (INSTALL_DIR plus any subdirectory or filename) when the path contains spaces. Follow these steps to try launching the help from the command line: Open a command prompt window.
Change to the logical drive the product is installed on, then to the directory on that drive. For example, if your product is installed at "g:\Program Files\IBM\VisualAge for Java", type the following:
g:
cd "\Program Files\IBM\VisualAge for Java"
Change to the directory beneath the product directory where the executable vahelp.exe is located. You can determine the location by first typing:
dir /s /b vahelp.exe
If this returns:g:\Program Files\IBM\VisualAge for Java\eab\bin\vahelp.exe
You would then type:cd eab\bin
Issue the following command (quotes are required only if the path contains spaces):
For VisualAge for Java:
vahelp instance "INSTALL_DIR\doc\ivjhlp.cfg" open index.htm
For VisualAge COBOL:
vahelp instance "INSTALL_DIR\help\Iwzif1.cfg" open index.htm
For other VisualAge products, first determine the name of the help directory for the product (typically doc, help, or hlp) by finding the directory containing .zip, .toc, and .htm files; then determine the name of the product configuration file in that directory (typically a file with a .cfg extension), then type:
vahelp instance INSTALL_DIR\HELP_DIR\CONFIG_FILE open index.htm
If help launches successfully from the command line and you can search the help successfully, there may be a problem with the way your path is set up, that prevents your product's user interface from connecting to the help system DLL. See 2.1 Special case - VisualAge for Java 3.5, or, for other products, try uninstalling and reinstalling your product, as this sometimes solves such problems.If you are satisfied with launching help from the command line as a workaround or temporary fix, you can create an icon on your desktop to do so. See 11.0 Creating an icon to launch product help.If the help does not load from the command line, or if it loads from the command line but not from within the product, you may not have the proper file associations set up for your browser within the Windows registry. See 16.0 Setting HTML file associations in the Windows registry. If changing file associations also does not help, you can try the following to obtain a log file from the help system:Edit the product help configuration file (INSTALL_DIR\HELP_DIR\CONFIG_FILE) in a text editor (e.g. Notepad) and add the following line to the end of the file:
HTMLHELP_LOG=1
Save the file. Be careful to save as plain text if using an editor like WordPad.
Exit and restart your IBM product.
Press F1 or use the Help menu to try to launch help from within the product.
In the directory pointed to by the TMP environment variable, you should see one or more files of type HTML*.C2T. These files contain detailed log information on requests made to the help system. You can send these files to IBM support to have them analyzed. A fee may apply to support requests. You can also try to examine these files yourself to see if you can determine what is causing the failure.If you do not see any HTML*.C2T files in your TEMP directory, try invoking help from the command line again. If HTML*.C2T files only get created from the command line, the problem is with your product invoking the help. If neither method of invoking help produces log files, the help system itself has a problem. In either case you can contact IBM support.Remember to remove the HTMLHELP_LOG=1 line from your product help configuration file when you are done, as the logging will produce unnecessary log files each time you request help.If you are still unable to launch help by any method, check that your product help configuration file is still valid. Open INSTALL_DIR\HELP_DIR\CONFIG_FILE in an editor and verify that: There are no leading or intermediary whitespaces within parameter settings:
HTMLHELP_HIDDEN=1
is valid, but:
HTMLHELP_HIDDEN = 1
is not. The only exception is a directory value with spaces in its path; for these values, enclose the entire path in quotes:
HELP="C:\Program Files\IBM\VisualAge for Java\doc\"
is correct, but:
HELP=C:\Program Files\IBM\VisualAge for Java\doc\
is not; this effectively sets HELP to the value C:\Program because without the quotes the value is parsed only to the first space.
The setting of the HELP= variable points to a valid directory (or multiple valid directories separated by semicolons)
If multiple entries occur of the same variable, delete any that seem incorrect. The first entry of a given name takes precedence over subsequent entries of that name.
Note: this section does not apply to Component Broker or WebSphere Business Components. For Component Broker please see the information on help troubleshooting in the doc\readme directory.If nothing happens with VisualAge for Java, Version 3.5 and you use a desktop icon to launch the VisualAge for Java IDE, see 2.1 Special case - VisualAge for Java, Version 3.5.If nothing happens when you try to launch help, your first step should be to determine whether you can launch help from the command line. To do this, you will first need to know what directory you installed your product in. In the text that follows, wherever you see INSTALL_DIR, you should substitute the actual directory your product was installed in, for example x:\ibmvjava or "x:\Program Files\IBM\VisualAge for Java". Use quotation s around the entire path (INSTALL_DIR plus any subdirectory or filename) when the path contains spaces. Follow these steps to try launching the help from the command line: Open a command prompt window.
Change to the logical drive the product is installed on, then to the directory on that drive. For example, if your product is installed at "g:\Program Files\IBM\VisualAge for Java", type the following:
g:
cd "\Program Files\IBM\VisualAge for Java"
Change to the directory beneath the product directory where the executable vahelp.exe is located. You can determine the location by first typing:
dir /s /b vahelp.exe
If this returns:g:\Program Files\IBM\VisualAge for Java\eab\bin\vahelp.exe
You would then type:cd eab\bin
Issue the following command (quotes are required only if the path contains spaces):
For VisualAge for Java:
vahelp instance "INSTALL_DIR\doc\ivjhlp.cfg" open index.htm
For VisualAge COBOL:
vahelp instance "INSTALL_DIR\help\Iwzif1.cfg" open index.htm
For other VisualAge products, first determine the name of the help directory for the product (typically doc, help, or hlp) by finding the directory containing .zip, .toc, and .htm files; then determine the name of the product configuration file in that directory (typically a file with a .cfg extension), then type:
vahelp instance INSTALL_DIR\HELP_DIR\CONFIG_FILE open index.htm
If help launches successfully from the command line and you can search the help successfully, there may be a problem with the way your path is set up, that prevents your product's user interface from connecting to the help system DLL. See 2.1 Special case - VisualAge for Java 3.5, or, for other products, try uninstalling and reinstalling your product, as this sometimes solves such problems.If you are satisfied with launching help from the command line as a workaround or temporary fix, you can create an icon on your desktop to do so. See 11.0 Creating an icon to launch product help.If the help does not load from the command line, or if it loads from the command line but not from within the product, you may not have the proper file associations set up for your browser within the Windows registry. See 16.0 Setting HTML file associations in the Windows registry. If changing file associations also does not help, you can try the following to obtain a log file from the help system:Edit the product help configuration file (INSTALL_DIR\HELP_DIR\CONFIG_FILE) in a text editor (e.g. Notepad) and add the following line to the end of the file:
HTMLHELP_LOG=1
Save the file. Be careful to save as plain text if using an editor like WordPad.
Exit and restart your IBM product.
Press F1 or use the Help menu to try to launch help from within the product.
In the directory pointed to by the TMP environment variable, you should see one or more files of type HTML*.C2T. These files contain detailed log information on requests made to the help system. You can send these files to IBM support to have them analyzed. A fee may apply to support requests. You can also try to examine these files yourself to see if you can determine what is causing the failure.If you do not see any HTML*.C2T files in your TEMP directory, try invoking help from the command line again. If HTML*.C2T files only get created from the command line, the problem is with your product invoking the help. If neither method of invoking help produces log files, the help system itself has a problem. In either case you can contact IBM support.Remember to remove the HTMLHELP_LOG=1 line from your product help configuration file when you are done, as the logging will produce unnecessary log files each time you request help.If you are still unable to launch help by any method, check that your product help configuration file is still valid. Open INSTALL_DIR\HELP_DIR\CONFIG_FILE in an editor and verify that: There are no leading or intermediary whitespaces within parameter settings:
HTMLHELP_HIDDEN=1
is valid, but:
HTMLHELP_HIDDEN = 1
is not. The only exception is a directory value with spaces in its path; for these values, enclose the entire path in quotes:
HELP="C:\Program Files\IBM\VisualAge for Java\doc\"
is correct, but:
HELP=C:\Program Files\IBM\VisualAge for Java\doc\
is not; this effectively sets HELP to the value C:\Program because without the quotes the value is parsed only to the first space.
The setting of the HELP= variable points to a valid directory (or multiple valid directories separated by semicolons)
If multiple entries occur of the same variable, delete any that seem incorrect. The first entry of a given name takes precedence over subsequent entries of that name.
如果是，直接用websphere studio 3.02+editplus开发就可以了
如果不是，快放弃这个软件吧，比她好得多的是（：
如果是，直接用websphere studio 3.02+editplus开发就可以了
如果不是，快放弃这个软件吧，比她好得多的是（：