🚀 go-pugleaf

Hello fellow NUPop readers. 
I am posting this reply to the whole group as I know there are others out 
there who are interested in SLIP type questions...this follows my earlier 
post to the group concerning SLIP vagaries and NUPop.
-----
Hi there Kent! (kennethb@nbnet.nb.ca)

Your very informative reply was most appreciated! Ta...

At 02:02 AM 25/6/94, kennethb@nbnet.nb.ca wrote:

>   The only solution is not to use UMSLIP.COM. It needs the phone program
>   in order to dial in the slip server.

Yes, I have had have the PHONE program dialling up and connecting seemingly 
successfully. I did establish a SLIP connection, to the point where I could 
READ mail OK, but not send it, as I said in my earlier mail.

>   I had exactly the same problem as you, then I switched to SLIPPER,
>   which is brw better than slip8250 and now everything's fine.
>   UMSLIP was the culprit; Nupop cannot initialize the modem using UMSLIP,
>   only the PHONE.EXE program can.
>   I would suggest you getting slippr15.zip(or later).
>   You can get on ftp.utas.edu.au:/pc/trumpet/slipper

Thank you for pointing me agin to SLIPPER. I did not have this version but 
an older (ver 1.3) that I had not yet experimented with. I downloaded 
slipper 1.5 (it is the latest!) with its new u-beaut "keepalive" thigny. 
Thanks _very_ much for that.

>   Here are my parameters:
>   SLIPPER COM2 VEC=0x62 baud=57600

Wow! 57600 bps. Is that a dedicated line connection or a telephone line or 
what? I certainly haven't got that at home. Nor can my service supplier (ie. 
Murdoch University) provide that speed (I connect through their terminal 
server). But I am curious about getting a voice grade telephone line 
directly into the back of a UNIX box. Then I think I could have a very high 
speed connection from home to work.

>> And one last thing: When composing this message (under SLIPDIAL/SLIP8250)...

I state again that I _did_ get NUPop running nicely using SLIP via DialIP in 
Options/Network/Advanced and using a SLIPDIAL.SCR and the SLIP8250 packet 
driver. Pib's provided solution (as a package) worked very neatly. (As I 
said, I cannot use BOOTP as my University terminal server does not have that).

My difficulties lay with the UMSLIP / PHONE / NUPop combination as an 
alternative to using SLIPDIAL.SCR  I wanted to use some other DOS IP apps as 
well (eg. MINUET).

>  You are lucky that you don't charge by the minute!

I am the very first to use SLIP at our University. I am experimenting for 
future provision. The plans are, unfortunately, to charge for use, via 
Schools and Departments. But until then, yes, I am very fortunate...

>  Seriously, if you use slipper version 15, there is an option
>  called keepalive which send a byte per minute.

Yes, thank you again. I have not actually sat back and timed how long it 
takes for a timeout, using SLIPPER 1.3 and the "keepalive" thing. However 
NUPop, SLIP8250 and SLIPDIAL seemed to drop out quickly if inactive.

>  I guess it would be something like this:
>  SLIPPER COM2 VEC=0x62 baud=57600 keepalive

Yes, thank you. Mine is:
CSLIPPER COM2 VEC=0x62 baud=9600 keepalive

I'm testing the compressed slip, header compression thing (ie. CSLIP). Seems 
to work OK with NUPop email at least.

My modem is 9600; I usually set the baud rate to 19200 as I'm using MNP5 
compression and RTS/CTS flowcontrol, but my old modem is tempramental today 
and doesn't like the 19600 setting.

So my AUTOEXEC.BAT looks like:

REM CSLIPPER 1.5 driver with "keepalive" on vector 60
CSLIPPER COM2 VEC=0x60 baud=9600 keepalive
echo.
REM Load WINPKT driver
WINPKT 0x60

>  If you use Winsock and you want to make sure it doesn't disconnect,
>  then do not use the internal SLIP option. Load the SLIP driver as above
>  ANDwinpkt.com.
>  Something like this:
>  SLIPPER COM2 VEC=0x62 baud=57600 keepalive
>  winkpkt 0x60   <- This has to be lower than 0x62(SLIP).

Now, that surprised me. 
I thought they needed to be both set to the same vector. I set both mine to 
0x60 and things seem to be working well. When I set the winpkt to 0x62 
(diff. from cslipper's) I got an AUTOEXEC message saying that no packet was 
present after the winpkt had been loaded. I'm setting both mine to 0x60.

So I tried that and everything is working well. What I want to know is:

1. HOW do you dial up your server or service? 
Do you use NUPop's SLIPDIAL or do you use another term comms package to 
access the SLIP server? I found that using CSLIPPER and NUPop with it's 
SLIPDIAL.SCR works well. I want to download and check out something called 
DIALER.

Of course, the winpkt driver is not needed for NUPop under DOS. But 
CSLIPPER/WINPKT/SLIPDIAL combination worked fine for NUPop under DOS.

3. I was really SURPRISED that Trumpet WinSock 1.0 Rev A loaded up OK, after 
I had quit from NUPop and launched Windows. I had not tried this before - 
ie. SLIP connect using NUPop under DOS, exit NUPop and then lauch Windows 
and WinSock. 
Howver, I had to copy the IP number (copied from NUPop's Network settings) 
and put that IP number into the WinSock setup first. 
How do you get WinSock to acquire the IP in this case? Mine did not 
automatically grab it, as WinSock does if you set it to use its internal 
SLIP driver and dialup facility.

Now, I will go and see if I can get NUPop to work via SLIP, but under Windows.
I think Pib once said that NUPop will not work under Windows using Trumpet 
WinSock, but another is needed. Do I need to load a different winsock after 
the winpkt driver to get NUPop to work via SLIP under Windows? I will see...

Thanks for your help. Much appeciated.

Regards
Geoff R.

----
Geoff Rehn
Academic Service Unit   Murdoch University
rehnpc@cleo.murdoch.edu.au  (PC mail)
rehn@cleo.murdoch.edu.au    (Mac mail)
uucp: rehn@smokey.eepo.oz.au