1. What is the WBI server error when using OS/2 Web Explorer?

2. There seem to be problems installing WBI with Windows 95. Is there a way to fix this?

3. Performance seems slower using the WBI agent. What's going on?

4. Under OS/2, "ping localhost" is working but agent communication is not. What's happening?

5. My Web browser can't load any pages.

6. WBI isn't accessing any pages outside the firewall.

7. Pages with frames and Java script are having problems working with WBI.

8. No Web "traffic lights" appear beside hyperlinks.

9. Web "traffic lights" only appear beside some hyperlinks.

10. How do I change my index size?

11. Using OS/2 Web Explorer I get "server stops in middle of conversation" running WBI.

12. Does WBI provide details on how it operates?

13. Can the WBI GUI window be eliminated from WBI start-up?

14. The WBI toolbar isn't displayed on any pages.

15. Why are there two versions of WBI on windows?


1. What is the WBI server error when using OS/2 Web Explorer?

OS/2 WebExplorer requires a closing slash "/" at the end of the proxy statement in it's configuration. The following is an example of a correct entry: http://localhost:8080.

[Goto Top]

2. There seem to be problems installing WBI with Windows 95. Is there a way to fix this?

The latest version of WBI fixes that problem. Run rmwbi.exe file to un-install WBI and then reinstall the newest WBI code for Windows 95.

[Goto Top]

3. Performance seems slower using the WBI agent. What's going on?

Using WBI's "Traffic Lights" feature may create a longer response time because the WBI agent is checking the speed of each link on the page. Certain browsers may not be able to access links on the page while this feature is running. This feature can be turned off from the WBI set-up page. Un-checking the "Graphical WBI Toolbar" setting will get text, rather than an image, on each page and may speed up performance. You can access the WBI Setup page from Help or by clicking on "setup" in the WBI toolbar.

[Goto Top]

4. Under OS/2, "ping localhost" is working but agent communication is not. What's happening?

With some levels of OS/2 TCP/IP, the localhost appears to be configured but really isn't. Check the TCP/IP configuration using "Configuring loopback under OS/2" to see if the localhost is configured properly. The netstat -a command will check to see if the address 127.0.0.1 is in output. If so, localhost is configured.

[Goto Top]

5. My Web browser can't load any pages.

Be sure that WBI is running. There should be a WBI window which says "listening on port 8088." If this window isn't open, double click on the WBI program icon from the Windows 95's Start menu or from the OS/2's "WBI Agent" folder. Users connected to a network should put a shortcut or shadow of the program icon in their Startup folder so it will be installed at boot time.

[Goto Top]

6. WBI isn't accessing any pages outside the firewall.

Be sure that WBI is configured with socks and proxy firewall information. Access the WBI Setup page from Help, by clicking on "setup" in the WBI toolbar or by going to http://_wbi/setup. Then make sure that the socks and proxy machine names and port numbers are correct. Then press the "Yes" button. WBI will always use socks over proxy if both are entered.

[Goto Top]

7. Pages with frames and Java script are having problems working with WBI.

WBI is not particularly frames-friendly and Java script is sometimes corrupted by WBI. These problems will be fixed in a future release. For the moment, reconfigure the Web browser so that WBI does not point to these pages.

[Goto Top]

8. No Web "traffic lights" appear beside hyperlinks.

Be sure that "traffic lights" is on. Access the WBI Setup page from Help, by clicking on "setup" in the WBI toolbar or by going to http://_wbi/setup. Then make sure that "traffic lights" is on. Then press the "Yes" button.

[Goto Top]

9. Web "traffic lights" only appear beside some hyperlinks.

WBI limits the number of hyperlinks that are tested on each page. Pages with lots of hyperlinks may not all get "traffic lights" on them. To get more "traffic lights," reload the page with the browser and more hyperlinks will be measured.

Hyperlinks with unquoted HREF tags are not measured for network speed. This bug will be fixed in a future version.

[Goto Top]

10. How do I change my index size?

The index size cannot be changed once it has been set. The only option is to delete the WBI.INI and HISTORY files and start again. See the next section to read about how to do this.

[Goto Top]

11. Using OS/2 Web Explorer I get "server stops in middle of conversation" running WBI.

WebExplorer needs the proxy field and the full URL of the proxy including the prefix "http://." Entering a proxy in the WBI proxy field only requires the URL address. For example, if the WebExplorer proxy was http://proxy.raleigh.ibm.com/, the WBI proxy should be proxy.raleigh.ibm.com.

To get back to the WBI setup screen, start the agent and from the browser go to the URL http://_wbi/setup. The proxy name can be changed at this point. If the problem continues, erase the WBI.INI file in the WBIDEMO\BIN directory and restart the agent. The configuration screen should appear again on the first connect from the browser.

[Goto Top]

12. Does WBI provide details on how it operates?

To see more details, start WBI using the -v option. Type "WBI -v" from an OS/2, DOS or Windows 95 window. A text window will appear with detailed information.

[Goto Top]

13. Can the WBI GUI window be eliminated from WBI start-up?

Start WBI using the -m option by issuing "WBI -m" from the command line. To set the -m parameter when starting WBI from OS/2 add the "-m" parameter to the Settings notebook. To start it from Windows 95, add the "-m" after the WBI program in the Target field of the Proper

[Goto Top]

14. The WBI toolbar isn't displayed on any pages.

For those browsers which support JavaScript, ensure that JavaScript is enabled. Failure to do so, will cause this problem to occur.

[Goto Top]

15. Why are there two versions of WBI on windows?

With the introduction of the new WBI user interface, we now require that Java be installed on your system. For those users which have Java Development Kit 1.1.1 or Java Runtime Environment 1.1.1 or higher, wbi20b5w.exe can be installed. For those users without JDK 1.1.1 or JRE or higher, wbj20b5w.exe should be installed.

[Goto Top]