G'day Paul,

Replying to a message of Paul Edwards to Jeff Green:

 PE> You're the only one who is getting the problem! 

I'm also one of only two people (from persons reporting problems anyway)
who cannot get a connection with the IBM Global Network (at least with the
inet.sys problem that I have). It is a slip only connection.

That problem seems to be with RTS/CTS flow control. I've tried two
different comms boards that I have, but both are old ie > 5 years. I've
been to IBM with my modem and tried it on one of their machines. It all
works fine which makes me think it's my old comms hardware that's at fault.

BTW, the above problem is with a slip connection with the Warp stuff. It
requires RTS/CTS to be enabled and working. I can get a PPP connection with
other service providers, but have never had a successful slip connection
with anyone. 

 PE> I wish it wasn't the case, as I can't be sure that it's not
 PE> something in 3.03 that's causing the problem, so am delaying
 PE> releasing it.

It's more than likely my old comms hardware. I've gone shopping for a new
comms card but not one store out of th five that I visited had any! I'm
going to try again this Friday (i'll let my fingers do the walking this
time though!)

At the moment I'm still getting the following:

> 13 Jun 00:35:34.50 sending yoohoo (0xf1) and tsync (0xae)
> 13 Jun 00:35:37.94 got junk character 0d
> 13 Jun 00:35:37.94 got ENQ, exiting sendsync
> 13 Jun 00:35:37.94 This is yoohoo session

Send along a DOS boot image if you can. I have the loadskf (???) program.

Regards...Jeff (jeff{at}grntrs.dialix.oz.au)

--- FleetStreet 1.04 NR