The Day I managed to Quake over a dialup account. A rudimentary faq on how to setup quake to work with the B&W TCP/IP stack. Brought to you by Berndalf 2/27/96 -------------------------------------------------------------------------- Allright, I'll try to explain this step by step. Keep in mind this is only a description of what I did to get this working, it may completely backfire for you. I'm assuming you already have quake up and running successfully. Step 1) Get the B&W TCP/IP stack. I managed to get on ftp.bws.com and found it in the /pub/bbs/Beames & Whiteside/ directory I think. If you get it form there, you need the ppp.zip file, and that's it. if you get it from somewhere else, you still need everything in ppp.zip Step 2) Unzip ppp.zip into a directory somewhere. We'll assume you unzip to c:\b&w for this example. RENAME the file ethdev.pkt to ethdev.sys Step 3) Run the file bwcustom.com. First, go into Hardware Customizations. You'll want to change the Hardware Interrupt to whatever your modem is set to, ie 4 for COM1 and 3 for COM2 in most systems. Then, change the I/O address to the appropriate value for your modem, ie. 3F8h for COM1 and 2F8h for COM2 on most systems. Leave the rest of the values alone on that page Return to the Main Menu. Enter the Site Customizations screen. First, go into set internet address. Now, all I did here was choose option one, and entered in a value similar to the ones I usually get, as my ip is dynamic. If none of this works at all for you it's probably because of this. For me it looks like B&W readjusts itself after it is finshed connecting, but it may not for you. You'll just have to expiriment. Next, enter at least one server in both Domain server and Name server. For most people these will both be the same server. I myself use 131.156.1.11 .. These values are your Domain Name Server. Return to the main menu again, and Exit saving you changes. Step 4) You now are going to need to edit your config.sys and autoexec.bat files to load the B&W drivers. I'm assuming you're using c:\b&w as your program diretory. In config.sys, add the following lines: DEVICE=C:\B&W\ETHDEV.SYS DEVICE=C:\B&W\TCPIP.SYS 512 512 30 In autoexec.bat add the following: SET BWSTATE=c:\b&w SET USERNAME= (I'm not sure if this one is necessary. It should be the username you log into your provider) SET DOMAIN= (Again, not sure if this is needed. Mine is niu.edu) C:\B&W\PKTPPP.ZOM 0x60 Of course, replace everything above with the appropriate values depending on where you unzip ppp.zip to. STEP 5) You're almost done, all you need to do now is write a script to allow the bwdialer to log into your provider. The bulk of the script can be ripped from the script.txt file that came in the ppp.zip file, but I'll repeat it here in case you don't have that file. trace on Open COM1:57600 :try_again output \rAT\r waitfor 1 OK output ATDTphonenumber\r rget s0 10 :again rget s0 30 FIND s0 RINGING if found goto again endif FIND s0 BUSY if found gosub wait goto try_again endif FIND s0 CARRIER if found waitfor 10 CONNECT else FIND s0 CONNECT if not found Display Error Connecting exit endif endif output username\r output password\r #waitfor output ppp\r ppp online exit :wait Display Wait 15 seconds and try again ... sleep 15 return Of course, you'll need to modify this. First, insert the proper number for your provider at the top in place of phonenumber. Now, replace username with, magically, your username on that system, and password with your password. This may not be the best way but it works. Now, if you're provider is using a standard unix login prompt on the other end, that's all you need to do. If not, ie they use some sort of menu to log you in, you'll need to insert the appropriate commands to make the script connect. I unfortunately have not been able to loate any docs for the scripting language, but by analyzing the above example you can get most of them. I, for example, had to use the sleep command to get the script to wait until the other end had responed to certain commands. You'll have to play with the script a bit most likely. Step 6) Run the bwdialer program. I simply type: bwdialer niu.txt /p /d .. NIU.TXT is the name of my script file, you should replace it with your own If all goes well bwdialer should, dial and connect to your provider and quit on it's own, saying something to the effect of ppp complete near the bottom. Don't be upset if you see a bunch of giberish fly by after it connects, mine does that and it's normal apparently. If the script starts taking a long time and you think something's not working, you can press ALT-X a few times to abort the program Step 7) Assuming you're all connected, start up quake. Type in any commands you want, and when you're ready to start playing, type: connect XXX.XXX.XXX.XXX when all the x's are the IP of the Quake server you want to connect to. If everything's working, it should say trying, then connected, and launch the game. NOTES: I did all this using Windows 95, first in DOS mode then later from a DOS window. The game was very choppy for me. VERY CHOPPY, unplayably so. I'm hoping this wil get better in the future, and as youve probably heard Running as a server is apparently much better. If you are tryng to set up a quake server, you're on your own. Since your IP is most likely dynamic and changes with each login, you're going to have some trouble telling your friends where your server is. I think there is a dos based B&W telnet program that you can use to access IRC, but you'll have to figure that stuff out on your own. Happy Quaking! berndalf