> Now for the problem. I can connect, "slip", username then 
 > password. It tells me what my IP address is (whatever that 
 > means), then tells me that I have a SLIP connection and to 
 > press "CTRL C" or "CTRL Break" to exit, BUT when
I try to use 
 > the browser it locks the computer for about 8 seconds then 
 > tells me that "Explore has stopped responding to system 
 > requests" and so I kill it. If on the other hand I go for 
 > Gopher then after about 20-30 seconds it says that it can't 
 > find the address and that it got no data back.

It could be that 1) the tcp/ip transport is up 'n running fine; and 2)
there's a dns or other configuration problem (easily fixed).

To test the native transport; once connected, from an OS/2 cmd prompt, try
pinging your ISP's srvr IP. e.g. "ping 203.17.249.161". You may
need to ask your ISP for the IP - the IP number of their terminal server or
com server machine. If all is well you should see a regular reply (echo)
every second. If not there may be transport problems (no valid connection).

If ping works fine, check that you have the ISP's dns (domain name server)
IP configured correctly. It's in the \mptn\etc\resolv2 file.

Here's an example RESOLV2 file:

domain ami.com.au
nameserver 203.17.249.162

The nameserver IP entry must be correct. Without it nothing will appear to
work even though you're connected correctly, and you'll see timeouts such
as you've described.

Regards.

--- Msgedsq/2 2.2e