Notes on Alfredo Cole's Setup for Dospppd ----------------------------------------- For those who find Dospppd difficult to set up, particularly if you find it hard to write a Chat script, Alfredo Cole has provided this package to help automate things. To use this package, decompress it into the same directory where you installed Dospppd. This directory should preferably be your main Internet directory (I suggest that you have the packet driver, dialer, and central WATTCP.CFG in one directory, and install your Internet applications in subdirectories off of that). The first thing to do is run SETUP.EXE. In the Configuration menu, fill in the items in the Hardware and Network menus, then Quit. Next run PPPTERM.EXE. On the command line for PPPTERM, you specify the COM: port address, the serial port speed you want to use, the IRQ number, and your ISP's phone number, like so: pppterm 4 38400 5 t9733710 My modem is at port 2E8h, which is the COM4: port. It has tone dialing, whence the "t". You will log in interactively. Each time you type something, hit F10 first. When you start getting garbage (indicating that a PPP connection has been established), hit <ctrl>-Z. The file LOGIN.PPP will be generated. You need to print out that file or jot it down. Run SETUP.EXE again. In the Configuration menu, select Login. Fill in your ISP's phone number. Line type is "T" if you have a touch-tone phone line, "P" if you have pulse dial. Use LOGIN.PPP to fill in the Expect and Send strings. Go to the Generate menu and select All Files. CHATSCR, PPPDRC.CFG, and DIALER.BAT will be created. The files generated should be considered a useful first step; they will not work without some further modification. Quit from SETUP.EXE. In CHATSCR, you will have to change a few lines. You need to add "OK's" to make sure that there is both an "expect" and a "send" string on each line. The string to the left is what CHAT.EXE expects from the modem, the string to the right is what Chat sends to the modem. For example, on my system, the following lines appear in the generated CHATSCR: '' ATZ AT&F AT&D2&C1X4V1Q0S7=70\\N3&K3 OK ATDT9733710 I changed those lines to this: '' ATZ OK AT&F OK AT&D2&C1X4V1Q0S7=70\\N3&K3 OK ATDT9733710 The idea here is that CHAT.EXE sends "ATZ", and the modem replies with "OK". Chat then sends "AT&F", and the modem replies "OK". Chat sends "AT&D2&C1X4V1Q0S7=70\\N3&K3", and the modem replies "OK". Chat then dials the phone. The next expected string from the modem is "CONNECT", which appears further below in CHATSCR. Without the changes, Chat would send "ATZ" and expect the modem to reply with "AT&F", which would not work - Chat would report failure, and EPPPD.EXE would not load. In DIALER.BAT, there are also a few lines you need to change. There is a group of lines that looks like this: :DIALER echo Dialing ... epppd if errorlevel goto CONNERR if exist currconn.cfg del currconn.cfg copy myisp.dat currconn.cfg echo Connection succesful goto END If you have DOS 5.0 or later, and your ISP uses dynamic IP, change those lines to this: :DIALER echo Dialing ... lh epppd.exe if errorlevel 1 goto CONNERR if exist currconn.cfg del currconn.cfg copy myisp.dat currconn.cfg call ip-up.bat del ip-up.bat echo my_ip=%MYIP% > ipaddr.cfg echo gateway=%REMIP% > gateway.cfg set ip=%MYIP% set gateway=%REMIP% echo Connection successful goto END If you have DOS 3.3 or later (but below 5.0), and your ISP uses dynamic IP, change them to this: :DIALER echo Dialing ... epppd if errorlevel 1 goto CONNERR if exist currconn.cfg del currconn.cfg copy myisp.dat currconn.cfg call ip-up.bat del ip-up.bat echo my_ip=%MYIP% > ipaddr.cfg echo gateway=%REMIP% > gateway.cfg set ip=%MYIP% set gateway=%REMIP% echo Connection successful goto END If you have DOS earlier than 3.3, and your ISP uses dynamic IP, try changing them to this: :DIALER echo Dialing ... epppd if errorlevel 1 goto CONNERR if exist currconn.cfg del currconn.cfg copy myisp.dat currconn.cfg echo Connection successful ip-up For DOS earlier than 3.3, you will then need to run a second batch file (assuming DIALER.BAT successfully connected) that looks like this: del ip-up.bat echo my_ip=%MYIP% > ipaddr.cfg echo gateway=%REMIP% > gateway.cfg set ip=%MYIP% set gateway=%REMIP% You might call that file SETPARMS.BAT or some such. The "call" syntax does not work with DOS earlier than 3.3, hence the second batch file. Those changes accomplish several purposes. First, they set the MYIP and REMIP environment variables to your local and gateway IP addresses. MYIP can be used to configure Minuet for dynamic IP. Next, they create IPADDR.CFG and GATEWAY.CFG, which you can include into WATTCP.CFG to deal with dynamic IP. They then set the IP and GATEWAY environment variables, configuring Trumpet TCP applications for dynamic IP. If you have DOS 5.0 or later, "lh epppd.exe" will cause EPPPD.EXE to be loaded into upper memory if available, giving your applications more room to work in. You need to change "if errorlevel" to "if errorlevel 1" so that DIALER.BAT will correctly detect when connection has failed. And last, and definitely least, you correct the misspelling "succesful" ;-). Above is for dynamic IP. If you have static IP, the situation is much simpler. If you have DOS 5.0 or later, change the lines above to this (for static IP): :DIALER echo Dialing ... lh epppd.exe if errorlevel 1 goto CONNERR if exist currconn.cfg del currconn.cfg copy myisp.dat currconn.cfg echo Connection successful goto END If you have DOS earlier than 5.0, change them to this with static IP: :DIALER echo Dialing ... epppd if errorlevel 1 goto CONNERR if exist currconn.cfg del currconn.cfg copy myisp.dat currconn.cfg echo Connection successful goto END Note that you will still have to configure your applications, editing WATTCP.CFG for WATTCP apps, filling in the dialog boxes in U. Minnesota apps, setting variables like DNS that don't change in AUTOEXEC.BAT for Trumpet TCP applications, editing CONFIG.TEL to use BOOTP for NSCA or CUTCP applications. In some cases (Trumpet News, PC Gopher), you will also need to create additional batch files to run the programs. Each individual program also generally needs some configuration of its own. See the README on my site for some general hints, and see the .txt files for more specific information on each program. If your BIOS doesn't support the COM: port your modem is on, you will also have to modify PPPDRC.CFG. For example, my modem is on COM4:. My PC's BIOS only supports COM1: and COM2:. To deal with that, I changed this line in PPPDRC.CFG: COM4 to this: base 0x2e8 If your BIOS recognizes the port your modem is on, you won't need to make that change. Otherwise, COM1: is base 0x3f8, COM2: is base 0x3e8, and COM3: is base 0x2f8. If your ISP uses CHAP for authentication, make sure you're using the version of EPPPD.EXE that supports CHAP. Once everything is done, type "DIALER" at the DOS prompt to connect, load Dospppd, and configure the dynamic parts of your setup (if you have dynamic IP). Type "DIALER H" to unload the packet driver and hang up the modem when you're done Internetting. Postscript: CURRCONN.CFG is useless. It is designed for use with Bobcat or Doslynx, but it will not work with them because they are WATTCP applications, and BOOTP does not work with WATTCP over a PPP or SLIP link.