Mid-Missouri OS/2 Users Group Newsletter September 1993 Volume 1 Number 4 NOTE: The views expressed in this newsletter are not necessarily the views held by the MMOUG or it's members. Don't agree with something you've read here? Write and tell us about it! Mid Missouri OS/2 Users Group ============================= The MMOUG meets on the third Wednesday of each month, meeting at the Columbia IBM office on even months and at the Jefferson City office on odd months. September Meeting Announcement ============================== When: September 15, 1993 at 4 PM Where: Jefferson City IBM Office (See directions) Activities: A representative of WordPerfect Corporation will be on hand to demonstrate the new WordPerfect for OS/2 5.2. Directions: ---------- Jefferson City IBM Office One Elm Plaza Jefferson City, MO 65101 314-634-0200 Highway 63 South to Highway 54 West (across the bridge) to (be careful, this is still a dangerous intersection) Highway 50 East. Go through lights at MO. Blvd, Broadway, Jefferson, Madison and Monroe Take the CLARK AVENUE exit off of Highway 50. Turn right onto Clark Ave, THEN make an almost immediate left onto ELM Street. Take Elm Street to IBM. IBM will be on the left. Eastland Highway / Patrol Elm Street McDonalds________ HQ ________________ | IBM\___________/ | |______________________________________________\_______ Highway 50 Clark Ave Exit Thanks to Gary Pool for providing these directions. What you missed at the August meeting: ===================================== The "real" number for the OWM Jeff City Point is 634-0393. It's up and running, with free access for MMOUG members. If you have any problems with this system, feel free to drop a note here to me or Phillip. Tom Stuart and David Irovic from DataStorm (makers of ProComm) visited with us and discussed several aspects of running PC+ and PW (ProComm for Win) under OS/2. Here are some DOS settings to use: HW_TIMER = ON COMM_HOLD = ON IDLE_SECONDS = 60 IDLE_SENSITIVITY (as low as 40, they suggest 100). If you're planning on using COM3 or COM4, make sure they're declared in the CONFIG.SYS in the following manner (assuming you're using COM.SYS): DEVICE=C:\OS2\COM.SYS (3,addr,irq) (4,addr,irq) (addr is the base address in hex, and irq is the IRQ to use). Under OS/2, IRQ7 is used for the printer. Generally, IRQ5 is used for COM3. If you're encountering errors installing the Windows version of ProComm, here are some tips: If you get a "Fatal Exit Error", then there's a good chance that you may be missing the LZEXPAND.DLL and/or a valid COMMDLG.DLL in your \OS2\MDOS\WINOS2 directory. You can manually copy these files to overcome the error. Note that this error usually only pops up while trying to install using OS/2 2.0. Version 2.1 has all the required objects in the Windows directory, and you shouldn't have a problem installing. Interestingly, DataStorm has performed some testing and has discovered that they can obtain up to 1000 CPS at 9600 baud using the Windows version (PW) with a *16450* UART chip (non-buffered) under OS/2 2.1. This makes OS/2 look even better than before, especially for communication applications. When prompted for info on an OS/2 version of ProComm, Tom replied that DataStorm is a market-driven company. If people want an OS/2 version, they'll make one. Feel free to let them know what you'd like to see in an OS/2 version. Here's 3 ways: to make your voice heard: Compuserve: (GO DSTORM) send a message to 72250,3463 Voice: Call their tech support at (314) 875-0530 Fax: Tech support fax is at (314) 875-0595 If you represent more than one person, make sure and mention how many people you DO represent! Every person counts! GIVEAWAYS! Diane Kehl won a free copy of Lotus' 123 for OS/2. Several people won coffee mugs, shirts, and other prizes. GIVEAWAYS TO BE! Here's a short list of things to be GIVEN AWAY in the NEAR future: ToolWorks CD Game Pack NEC Adobe Type Gallery LJ (CD) Kiplinger's CA-Simply Money Clear and Simple's Performance Tuning 2.1 and MORE! NEXT MEETING Looks like the next MMOUG meeting will be at 4pm Wed, Sept 15th, at the Jeff City IBM office. These meetings are open to all! Feel free to stop by and check us out! Mid Missouri OS/2 Users Group Information: ========================================= Current Officers: ---------------- Phillip Wilson - President Diane Kehl - Vice President Robert Shelley - Treasurer Shawn Frazier - Membership Secretary David Finch - Recording Secretary Woody Sturges - BBS Officer Dale Hackemeyer - Information Officer Official MMOUG BBS: ------------------ OS/2 Woodmeister - (314) 446-0016 (1:289/27) Jeff City Point - (314) 634-0393 (MMOUG Members only) MMOUG Mailing Address: --------------------- Mid Missouri OS/2 Users Group P.O. Box 30645 Columbia, MO 65205-0645 MMOUG Internet E-mail Address: ----------------------------- uc545502@mizzou1.missouri.edu Presidential Corner =================== Welcome to the Mid-Missouri OS/2 Users Group Newsletter. I hope you find it a beneficial one to you in your home as well as in your office. We are growing steadily, and are already over 20 members strong. If you check the BBS officers section you will find quite a few new developments in the area of our expansion of BBS access. We have a group of Officers that are doing a great job. I would like to thank our Treasurer Robert Shelley for taking the double duty of Membership officer as well until we were lucky enough to latch onto Shawn Frazier. Last month's Datastorm presentation was received very enthusiastically from everyone who attended. Don't forget if you received a software product as a prize from the drawing you are to upload your personal review of the prize. Otherwise I get to badger you until you do. We will have an exciting meeting next month with our next guest speaker (read other sections to see who ) and more giveaway drawings for members who are present. We are also going to vote on becoming a member of the Association for PC User Groups. I believe it will allow us access to more information of interest to you our members. If you have any suggestions or comments on how the Mid-Missouri OS/2 Users Group might better serve you and our other members please feel free to leave a message in the User group forum on the BBS nearest you. Thank you for support. Phillip Wilson President, Mid Missouri OS/2 Users Group The Latest from the BBS Side... =============================== Just a few things this time... IBM has officially released their 256 color S3 drivers. These drivers appear to work flawlessly on most S3-based video cards and go up to 1280 resolution. If you've been waiting, wait no more. The file is a free download, available as S3-256.DSK. I'm using the drivers on my Orchid VA/VLB running at 1024x768x256 without a hitch. Seamless Windows work excellent! IBM has also just released the first beta of their 64k color (!) S3 drivers. This file (also free) is available as S3-64K.DSK. This version is a little rough at 1024 resolution, but appears to work much better at 800 and lower. These drivers offer TRUE color at up to 1024 resolution. Though not done, they're fun to at least look at if you've got the time. There have been a number of great files show up lately. If you haven't checked them out, you're missing out on some good stuff. And, as always, drivers and patches show up weekly. Finally, I've bumped up subscribers to get 1.5M of download credit per day. This allows all subscribers (including MMOUG members) to get ANY file off the BBS. Just another benefit of being a subscriber, or MMOUG member! Woody Sturges BBS Officer Mid Missouri OS/2 Users Group Setting up IBM's TCP/IP with OS/2 ================================= Guide to getting started with OS/2 networking using IBM's TCP/IP software By Dean Pentcheff dean2@BIGBIRD.CSD.SCAROLINA.EDU Table of Contents: ( 1.) Purpose and introduction ( 2.) Request for more information ( 3.) Some terminology ( 4.) Selecting parts of the IBM TCP/IP packages ( 5.) Preparing to hook up to a TCP/IP network ( 6.) Installing IBM's TCP/IP Package ( 7.) Installing the driver for the network adapter ( 8.) Initial tryout ( 9.) Downloading CSDs (bug fixes) (10.) A few reminders (11.) Security concerns (12.) Tuning your setup (13.) Interesting TCP/IP software you can download (14.) Good luck (A1.) Appendix I: Coexistence of TCP/IP with Netware (A2.) Appendix II: Supplementary information on SLIP (A3.) Appendix III: Setting up LaMail NOTE: This document was produced for use with IBM TCP/IP for OS/2 Version 1.2.1. Version 2.0 of the TCP/IP product was recently released. This document does NOT reflect any changes that may be introduced with the new version. Dean has said he might produce an updated version of this document in the future, but it's on the back burner for now. ( 1.) Purpose and introduction ============================== The purpose of this document is to: 1. Orient someone who has heard a bit about networking on OS/2, but can't yet hold an entire conversation in three to five letter networking acronyms ("So, Bob, how's TCP/IP coming along today?" "Well, Jane, NFS if fine, but I'm having trouble with FTP." "Have you installed the CSDs?" "Yes, but can you ping over SLIP before sending a job to LPD?"....). 2. Help a new networker install the IBM TCP/IP networking package and some of its more popular additional modules. I'm no networking pro, but I've managed to start a working network system using OS/2 and IBM's TCP/IP offerings. It took me long enough to sort it all out. I hope I can save someone else the trouble. I make no guarantees that the following is entirely correct! It's based on my experiences. PLEASE correct me by mailing me your comments if you find anything misleading or wrong. Please send me additional hints based on your own experiences that you feel would be helpful to put into this document. N. Dean Pentcheff Biological Sciences Univ. of South Carolina Columbia SC 29208 (803-777-8998) Internet addresses: pentcheff@pascal.acm.org dean2@tbone.biol.scarolina.edu ( 2.) Request for more information ================================== Please let me know of improvements I can make to this document! Notable gaping holes that I notice (hint, hint) are: 1. Performance tuning - success stories and failure stories are both equally welcome. 2. Other useful network software - surely some net.geeks have some nifty utilities and addons that make a networked OS/2 system more of a joy. 3. Tricks and tips that you've discovered. ( 3.) Some terminology ====================== TCP/IP is the name of a communications protocol - it defines a way for computers to chat with each other. (PC)NFS is a family of products from several vendors that use TCP/IP on a PC, generally under the DOS operating system. Note that PC/NFS is a specific product marketed by SunSoft (the (PC)NFS name has been adopted as a generic name for that type of product). (PC)NFS is not addressed in this document - you may have heard about it from DOS systems. The programs described here do what PC/NFS on DOS does (and more). Ethernet is a specific hardware protocol for computer communications. For example, a 3Com 3C503 card is a (very cheap and popular, if not screamingly fast) Ethernet board for PCs. Using it (and appropriate software) you can connect a PC to an Ethernet TCP/IP network. TCP/IP is just one of many communication protocols that can run atop Ethernet. For example, a Novell Netware network running the IPX protocol could run on the same Ethernet - same hardware, just different protocols. Token-Ring is another hardware protocol in common use. IBM's TCP/IP package supports both Ethernet and Token-Ring network adapters. FTP is a "file transfer protocol" that runs on top of TCP/IP (there are implementations of FTP for pretty much any computer that can talk TCP/IP, making it a lingua franca for file exchange - it's not pretty but it works). Telnet is a defined way for TCP/IP-speaking computers to set up terminal sessions between each other so that you can actually log onto a remote computer and interact with your account there. SLIP stands for serial line IP. It defines a way that you can connect to a TCP/IP network over a serial line (via a phone modem, for example). Serial communications is slower than a direct network connection, but can sometimes be useful. IBM's TCP/IP packages does support SLIP. CSD is IBM's word for a publicly distributed bug fix package. Note that CSDs obsolete prior CSDs. That is, application of any later CSD will take care of everything that was done by earlier CSDs. You don't have to apply the whole chronological string of CSDs, just the most recent one. God help you if you install an earlier CSD over a later one (IBM sure won't help you). ( 4.) Selecting parts of the IBM TCP/IP packages ================================================ IBM sells a bunch of pieces, many of which are optional, for TCP/IP networking. Following is a brief summary of them. Note that all of the following come with both 1.2 Mb 5-1/4" and 1.44 Mb 3-1/2" disks in the same package (you don't need to specify medium). -- TCP/IP Base Program (Part #02G6968). Price: US$131. You need this in order to use any of the other following parts. It gives you the software to connect your Ethernet or Token Ring card to a network, plus a few character-oriented programs (Telnet, FTP, ping, etc.). It's sort of equivalent to the public domain NCSA Telnet package for DOS. -- NFS Kit (Part #02G6970). Price: US$95. This gives your OS/2 system the ability to serve as both a client and a server for sharing disk space using Sun's NFS (Network File System) protocol. In other words, you can mount disks over the network that are physically attached to other minicomputers or OS/2 systems as though they were attached to your computer. Conversely, you can make parts of your OS/2 computer's disks available for sharing by others. With this package (along with the Base Program), you've got the makings of a small local area network that can share disk space and printers. -- X-Windows System (Part #02G6980). Price: US$95. This gives your OS/2 system the ability to display output (and relay input) to X programs running on other computers. X-Windows is a standardized way for programs (mostly on Unix-based systems) to put graphics on the screen and interact with the user. X terminology is a bit peculiar: the program doing the work is called the "client"; the program doing the display is called the "server". This package allows your OS/2 system to be an "X server", but not an "X client": you can display and interact with X programs running elsewhere, but you can't run an X program on your OS/2 system and have its results displayed elsewhere. -- X.25 Networking (Part #?). Enables X.25 communications from your OS/2 system. I have no exposure to this product, so I won't comment. I assume you'll know if you need it. -- Source code and programming packages. If you're ordering these you sure as hell don't need me giving you hints on what to do. And finally, where to order. Peculiarly, IBM often seems unaware that they sell this product. So far, people have had the best luck with calling: 1-800-IBM-2-YOU (1-800-436-2968). Another IBM order line (1-800-IBM-CALL) apparently knows about the product but likes to charge you more money (?!). ( 5.) Preparing to hook up to a TCP/IP network ============================================== Once you have the TCP/IP base package, you can be a full-blown node on the Internet. To do that, you _must_ contact a local system adminstrator on the network to which you will physically connect your OS/2 machine. He or she must give you an Internet number. Choosing one at random is unlikely to work and is exceedingly antisocial (since it may well disrupt others' use of the network). You can probably select your own cute name for your machine, unless there is an iron-fisted net administrator who enforces a naming convention. As examples, our lab works on crab behavior, so our PCs are called "fiddler" and "cancer". The last place I worked had a lot of people working on marine larvae, so they had "cypris", "zoea", "actinula", etc. When you decide on a name and send it to your Local Network Guru, also ask the following questions: o What will my machine's full Internet name be (e.g. fiddler.biol.scarolina.edu for the machine at which I'm sitting)? o What is my IP address (e.g. 123.234.221.112 as a totally fictitious example)? o Is this network subnetted? If so, what's the subnet mask (e.g. 255.255.255.0)? o Is there a non-default broadcast address? If so, what is it? o What is the IP address of a default router for me to use? o What are the IP addresses of three domain nameservers? And, before you start the software installation, do yourself a favor. Open up your machine and take a good look at the network adapter card. Write down any strap or switch options that are set. You'll probably need them later when you do the software configuration of the driver for TCP/IP. ( 6.)Installing IBM's TCP/IP Package ==================================== All the documentation comes with the Base Program. The other packages just consist of a folder with disks. It is not initially clear how to proceed, so here's enough to get you going: Begin with the manual "TCP/IP Version 1.2.1 for OS/2 (Refresh): Installation and Maintenance". You install the TCP/IP software first, then the specific driver software for your Ethernet or Token Ring board. There's a nice little configuration program called ICAT (Installation and Configuration Automation Tool). As per instructions, stick in disk 1 and run ICAT from an OS/2 command line. Push the "Install" button first. It will give you the opportunity to install any/all of the options you've ordered (base package, NFS, X-Windows, X.25, and source packages). Check off whatever boxes you want and feed disks as requested. Go ahead and install everything you've got. Once everything has been copied to disk, push the "Configure" button of ICAT. Now comes the fun stuff. I'm assuming you have the documentation, so I'll just give you some hints based on what I did. There's a numbered list of 6 configuration things to do. We'll run down the list. 1. Configure Network Interface Parameters. You probably only have one Ethernet or Token Ring board in your computer, so you only have to fill in half this screen (the other half is for another board - and up to two more on a "Next Screen"). Your IP address is whatever was issued to you by your Friendly Local Network Adminstrator. If he/she told you anything about a "Subnet Mask", enter it appropriately. Leave "Broadast" and "Destination Address" blank (unless you've been explicitly instructed otherwise). For that matter, leave the rest of the screen untouched unless told otherwise. Don't forget to check the little "Enabled" box in the top left corner. When done, press the "Menu" button to return to the main Configure menu. 2 . X.25 Parameters. You're on your own here (I haven't done this), but it looks straightforward - stick in your IP address. 3. SLIP Parameters. This is if you're going to use a serial port for access, instead of a network adapter (SLIP = Serial Line Internet Protocol). Fill in the IP address, and the rest is like setting up the dialer in a communications program. 4. Automatic Starting of Services. Again, the following are reasonable defaults if (a) you haven't been told otherwise; and (b) you have the software involved. DO enable the inetd super server - this is one program which runs all the time and spawns off some of the other network service programs on an as-needed basis. This way they don't all have to be started at once. If you want yourself or others to be able to Telnet into this machine, enable the Telnet server (BUT SEE NOTES BELOW - THIS CAN BE A REAL SECURITY RISK). This does not influence your ability to telnet out of this machine to other machines. If you want to be able to access files on this machine from other machines using the FTP protocol, enable the FTP server. This does not influence your ability to use FTP on your machine to access other machines. (SEE NOTES BELOW - THIS IS A POTENTIAL SECURITY RISK). Unless you know otherwise, DO NOT enable TFTP. I lean towards not enabling rexec and rsh unless there's a compelling reason to do so. THESE ARE A REAL SECURITY RISK. Again, this does not affect your ability to rexec or rsh from your OS/2 machine to other machines. If you are going to make a printer attached to your computer available to other computers (i.e. your machine will be a network print server), enable the lpd server. NOTE: To prevent lpd from printing a banner and control file before each document, set lpd to run in the "Foreground" (not via inetd), and type in "-b -c" (without the quotes) in the blank for arguments. This is particularly important if you have a Postscript printer (since the banner and control files are in ASCII, not Postscript, they will mysteriously stuff the printer). If you've got the X-Windows stuff, enable it (leave the "Parameters" as it is). If you're into online typing to people, enable Talk, but honestly, why not just use the phone? Enable the NFS Server if you want other people to access your hard disk (SEE SECURITY NOTES BELOW). Enable NFSCTL if you want to be able to mount other machines' disks (but note that they must allow you to do so). If you have the IP address of a default router on your network, you can skip enabling the automatic routing server "routed". If you couldn't get such an address from the Local NetNerd, go ahead and enable the automatic routing server "routed". (See some further remarks on this below in the "Tuning" section.) FINALLY, if you're going to receive mail directly onto your machine, enable "sendmail". If you're already receiving mail on another machine, this is FAR more trouble than it's worth (in my opinion). With the other software you've got, you'll easily be able to read your mail on another machine, so why bother with all the sendmail setup stuff (which is relatively fierce)? 5. Configure Services. I'm going to give hints based on my slightly net.paranoid approach. See the security notes below for some details. Put one and only one entry in the FTP Access Protection: anonymous. (But see further notes in the "Security concerns" section below.) If you're doing X-Windows, X Host Authorization gets the name of the machine(s) on which your X "clients" (e.g. main programs) will run. In the X Client Display Variable, enter your OS/2 machine's IP address (or Internet name, whichever). Not the name of the host to which you will be connecting, but this very OS/2 machine's address. Follow the IP address or machine name with ":0" (without the quotes of course). For example, I entered: fiddler.biol.scarolina.edu:0 Fill in the timezone in standard Unixoid format. See page 95 of the manual for some of the more popular timezones. If you will use another machine's printer, enter that machine's name and its printer's name. If you took my advice on rexec, enter nothing in the rexec username and password. Enter nothing in the password field for telnet (BUT SEE THE SECURITY NOTES BELOW). Enter your machine's name in the Hostname field (just the very first part of the name: "fiddler" in the case of "fiddler.biol.scarolina.edu"). Enter the rest of the name in the Domain Name field ("biol.scarolina.edu"). Type in (correctly!) the IP numbers of the (up to) three local nameserver machines your Always Cheerful Network Adminstrator gave you. 6. Routing Information. If you have the IP address of a default router, enter it here. Follow the keypress instructions to insert an entry. Toggle the "Route Type" field using space, leave "Route Destination" blank, type in the IP address into "Router", and leave "Metric count" at 1. If you do _not_ have the IP address of a default router, make sure you enabled the "routed" daemon. Then check below in the "Tuning" section to see how you can find out your default router's address later, insert it here, and dispense with "routed." When this is done, go ahead and "Exit" all the way out of the ICAT program, reassuring it that you really do want it to write this stuff to disk as it quits. ( 7.) Installing the driver for the network adapter =================================================== Once you finish with all that nonsense, you will realize that you haven't told the software anything about the network adapter you've got. Time to turn to the "LAN Adapter and Protocol Support Introduction and Configuration Guide". Cram in the LAPS disk, and, from an OS/2 command prompt, start up the "LAPS" program from the floppy. The following discussion assumes you will be using a network adapter card (either Ethernet or Token-Ring). If you will be using SLIP (IP over a serial line with a modem), I suspect things may be a bit different, but I don't know, I've never tried (as in: "Can you play the violin?" "I don't know, I've never tried"). See Appendix A2 below for some supplementary information on SLIP. I don't use it, so I haven't tested this, but give it a whirl. For now, we'll continue to assume that you're using a network adapter card... First do the "install" to copy in the software. Next, go to the configuration part. What you do is simple: pick one from column A and one from column B. In fact, IBM has made it simpler still - there's only one choice in column B (but you still have to explicitly pick it). Choose your network adapter from the Network Adapters list (select and "Add" it). (If your network adapter isn't on the list, see the remarks a few paragraphs below here.) Then choose the only choice (IBM TCP/IP) from column B. You've now declared that your network adapter number 0 (the first one) is of a particular type, and it will run TCP/IP. Now highlight the adapter name in the Current Configuration window and press "Edit". Now's your chance to make sure that the hardware options on your adapter match up with the software's idea of them. Change anything that needs changing. When in doubt, leave it as it was. Notably, you should probably leave the "Network Adapter Address" blank. That number is supplied by the board hardware unless you enter an overriding number here. Once you're done with the configuration, press "OK" and the proper configuration will be copied in. What if your network adapter isn't "supported"? That is, you didn't see it on the LAPS list. Odds are good that it really is supported. First of all, check the documentation - your adapter may emulate an adapter that is in the LAPS list. If so, you're home free. If not, you need to get hold of an "NDIS driver" for your adapter. There may be one on a disk that came with the card. Alternatively, you may be able to find one on the ftp-os2.cdrom.com archive (see the section on downloading CSDs in this document to see how to access the archive). Once you've got the NDIS driver, you'll need to do a little hand editing of some configuration information. The following description is edited from some advice posted to the Usenet group comp.os.os2.networking by Kai-Uwe Rommel (rommel@Informatik.TU-Muenchen.DE) regarding the popular 3Com Etherlink III card (a very fast, excellent Ethernet card, by the way). I haven't done this myself, so I don't know how easy it will be to adapt these instructions to other cards, but take a look at this and see how it goes... NDIS drivers for DOS and OS/2 come included with the Etherlink III card. I'm not sure if the LAPS install program of the TCP/IP package allows "other cards" to be installed, but otherwise simply install the Etherlink II drivers first. Then, before rebooting, copy ELNK3.OS2 from the Etherlink III driver floppy to the same location where ELNKII.OS2 is and replace ELNKII.OS2 in config.sys by ELNK3.OS2. In the protocol.ini in \IBMCOM, add [ELNK3_nif] DriverName = ELNK3$ right below the [ELNKII_nif] section and replace Bindings = ELNKII_nif in the [TCPIP_nif] section by Bindings = ELNK3_nif and it should work after rebooting. You may want to boot DOS and run the 3C509 program from the Etherlink III driver disk to set up the card to use an IRQ > 8 (i.e. IRQ 10, for example) and set the "client type" to a better suited one (you can choose DOS client, Windows or OS/2 client or server). If you install the Etherlink III in EISA machines, run the 3C509 program to switch the card into EISA mode (yes it has one although it is an ISA card) and use the EISA setup program and the config files on the Etherlink III driver disk to configure it. See Appendix E in the Etherlink III manual. ( 8.) Initial tryout ==================== Are ya feelin' lucky? Hope so. Quit out of LAPS. Do the standard OS/2 Shutdown. Make sure your network adapter is actually plugged into a network. Cross fingers and toes. Start up OS/2. It will take much longer to boot as five zillion networking programs crank up. Lots of them will put screens up as they come on. Once things are up, you can minimize these screens. Meanwhile, they will tell you of your progress. If things really choke and you don't get a boot, well, you knew the job was dangerous when you took it. Get an OS/2 guru to boot from a floppy for you and REM out the line in "startup.cmd" that says "CALL C:\TCPIP\BIN\TCPSTART.CMD". Assuming things more-or-less come up, try things out. First, from an OS/2 command line, try a ping to yourself. In my case, that's "ping fiddler.biol.scarolina.edu". You should get a series of one-liners once a second informing you that you've sent 64 bytes to yourself and received it. Press Control-C to quit that. If, after you enter your ping command, you get nothing (the command just hangs there), you've got a problem: you're unable to find yourself. Check your machine name and Internet number using ICAT, and make sure your network adapter board is properly set up, and the correct parameters are set using LAPS. One thing you'll want to try (but DON'T) is to double-click on the cute little INETD icon. Don't do it. You'll get a textmode screen with Inetd's potential clients listed. That's it. No menus. No nothing. It makes you feel like DOS is back. Press Alt-Tab or Alt-Esc to get the hell out of there. Memorize this, because one day you'll do it accidentally anyway. Try telnetting to your local host. Try an FTP file transfer. Once FTP file transfers work, I advise you to take the following step next, before doing much more playing. Note: unless you've started telnetd and/or ftpd (or have them set to start from inetd), don't try to telnet and/or ftp to yourself! ( 9.) Downloading CSDs (bug fixes) ================================== My system almost-kinda-sorta worked (flakey is the word that comes to mind). Following application of the bug fixes, it works very smoothly. So, to avoid wasting time, apply the bug fixes early. Following is the scoop on how to do this. DON'T BE INTIMIDATED BY THE LENGTH OF THIS SECTION! Because the CSDs change with time, this section is verbose to cover different contingencies. It's really quite straightforward in practice. Install the bug fixes - you'll be very happy you did. 1. For neatness' sake, make a subdirectory called "csd" (well, don't listen to me about it, call it "rosebud" if you want). Do a "cd" to that directory (all this is done from an OS/2 command line). 2. Give the command: ftp ftp-os2.nmsu.edu 3. If that doesn't work ("host unknown" or "network unknown") you've got a problem with domain name resolution. MAybe routed.exe isn't running or you have a bad DNS nameserver entry? Ignore that for now, but fix it later. Try giving the command: ftp 128.123.35.151 4. Log in as user anonymous, with your full login (joe@ace.b.c.edu) as password. Yeah, you don't really have a user name ("joe") since you're on a single-user machine. Make one up. For my machine, for example, I might enter "dean@fiddler.biol.scarolina.edu" (without the quotes). 5. Give something like the following FTP commands [things in square brackets are my comments, not parts of the commands]: binary cd os2/ibm/tcpip [get to the directory with fixes] get tcpcsd1.exe [Base TCP/IP package patches] get tcpcsd2.exe get basecsd.doc [how to install Base CSDs] get nfscsd1.exe [if you've got NFS] get nfscsd.doc [how to install NFS CSDs] get pmxcsd1.exe [if you've got X-Windows] get pmxcsd.doc [how to install X-Windows CSDs] You may find that some of the CSDs have filenames ending in ".zip" instead of ".exe". If so, do the following as well: cd /os2/2_x/archiver get unz50x32.exe [Info-ZIP unzipper for unpacking] Quit from FTP with the following command: bye Of course, this will be out of date soon. Just look for the most recent CSD packages in the directory and snarf them. Likewise for the Info-Zip unzipper. You should also check the directories "/os2/new" and "/uploads": new uploads go there first and may not have made it to the patches directory yet. If there are several different CSDs for products you have, download them all. Unpack them (see below) each separately on your machine and check the comments in the installation scripts for the latest date. 6. Unpack the suckers. If you got the unzipper program, just just run unz50x32. It will unpack itself into the unzip program. Each CSD release seems to be slightly differently packaged, so I'll just give some general guidelines here. You can probably install them from your hard disk, without having to copy them onto floppies (though they are usually designed to be installed from floppies). Make a subdirectory for each type of CSD (for example, I made subdirectories "base", "nfs", and "pmx") under the directory where you have the zip files. Then unpack each bundle into its appropriate subdirectory. If the CSD filename ends in ".exe", things are easy: it will unpack itself into its component files. For example, to unpack the Base packages, I'd do the following: mkdir base cd base ..\tcpcsd1 ..\tcpcsd2 If the CSD filename ends in ".zip", you have to explicitly use the unzip program to unpack the file. For example (if the CSD files were called "tcpcsd.base1.zip" and "tcpcsd.base2.zip"): mkdir base cd base ..\unzip ..\tcpcsd.base1 ..\unzip ..\tcpcsd.base2 Normally, the unzipping leads to the creation of 5-50 updated programs and files, one of which is an installation script (ending in ".cmd"). In some cases, the zip files will unzip into one or two monolithic ".exe" programs. These aren't really standalone programs, but are self-unpacking zip files. If, when you're done unpacking the first level of zip files, you only have one or two huge ".exe" files and you DO NOT HAVE ANY FILES THAT END IN ".CMD" (i.e. you don't have an installation script yet), check to see if the couple of huge programs are actually zip files in disguise. To do that, run the listing function of unzip.exe. For example, to check a hypothetical file "basecsd.exe", try running: ..\unzip -v basecsd.exe If the unzip program barfs, it's not a zip file. If you get a nice listing of lots of filenames, you can unzip the archive by simply running the program. For example: basecsd Don't do any of this fussing if there's a ".cmd" file in the directory from your inital unzipping - that's probably the installation script which will take care of the next level of unzipping for you. 7. Check the installation scripts. I've found two types. One is a pretty elaborate script that quite neatly checks your system out and installs the CSDs from the hard drive directory. These longer scripts are over 100 lines long. If there are just a few files that need copying, there may be a short script instead. In some cases, these short scripts are "hardwired" to copy from the A: drive (tacky!). A quick edit of any offending lines takes care of the problem. For example, changing the line: copy 'A:nfsctl.exe' BASE'\bin\nfsctl.exe' to read: copy 'nfsctl.exe' BASE'\bin\nfsctl.exe' converts the command so that it will run from the hard drive instead of needing to be put on a floppy. 8. Now you've got your CSDs (bug fixes) on disk, ready to install. You have to first REM out a couple of lines in your startup scripts, then reboot. Otherwise, OS/2 will refuse to let you update programs that are currently running. Using your favorite editor, edit your c:\config.sys. Find the line that runs CNTRL.EXE. Insert REM (followed by a space) before it. Save the file (as Plain Text, if you're asked). I found that I also had to edit the file c:\startup.cmd and REM out the line that reads "CALL C:\TCPIP\BIN\TCPSTART.CMD". Now reboot. Why not do all this before even rebooting once? Because applying the CSD depends on a lot of networking environment that is set up in the main config.sys file, so you've got to have booted with the networking stuff installed but REMed out for the CSD to apply properly. 9. If you're lucky, IBM will have included a "*.doc" file that will give you some hints on how to install each CSD. If so, read the file, and read the hints in the next paragraph. Between them all, decide how to install the CSDs. In the absence of an official "*.doc" file, you're on your own. Each CSD has its own handy install script. Go to each CSD's subdirectory and run the something-or-other.CMD file. For example, for the Base Package it might be basecsd.cmd; for NFS it might be nfscsd.cmd; for X-Windows it might be installx.cmd (thanks for the consistency, guys). Or it may be called something new and exciting. Basically all that these do is copy over a bunch of new versions of programs on top of the old ones. As far as I can tell, they don't meddle with initialization setups. [Late note on that - one of the newer CSDs does install a new xinit.cmd, but quite politely informs you that it is moving your old one to "xinitbak.cmd".] 10. With your trusty editor, remove the REMs from config.sys and startup.cmd. 11. Reboot OS/2 to a far less bugfull networking setup. 12. Periodically check in at ftp-os2 for new CSDs. Apply as above and they will overwrite whatever is needed to bring you up to date. Note that later CSDs make earlier CSDs obsolete: each CSD is complete. You do NOT need to install the whole chronological string of CSDs to get up to date. The latest CSD will do everything that any earlier CSDs did. (10.) A few reminders ===================== If you want to mount part of a Unix box's disk, the Unix machine will need an entry in its /etc/exports file describing what you're allowed to mount. Similarly, your OS/2 system's \tcpip\etc\exports file will have to list systems you allow to mount your disks (SEE SECURITY NOTES BELOW). If you want to redirect printer output from your machine to an LPD program on some other machine, you'll have to start up an lprmon process for each of the printer ports you wish to redirect. See the manual for the syntax. The trick is where to put the startup commands. If you don't mind seeing the lprmon windows appear at boot time, edit the file \startup.cmd and insert the command(s) there. That's a better solution than putting them in \tcpip\bin\tcpstart.cmd, since tcpstart.cmd gets clobbered if you rerun ICAT to reconfigure your setup. If you are going to edit your tcpstart.cmd file anyway (see the section below on tuning for reasons you might do that), go ahead and stick them into tcpstart.cmd. Note that there's a weirdness associated with lprmon: it apparently cannot monitor a port that has a larger-than-default buffer size. So make sure that you check the PRINTMONBUFSIZE in your \config.sys. For any port(s) on which you will run lprmon make sure that the buffer size is left on the default setting (134). For example, a vanilla version should be: PRINTMONBUFSIZE=134,134,134 (11.) Security concerns ======================= You are now a node on the Internet (assuming you've hooked up to an Internet-worked network). That means you have to be security conscious. You don't have to be an international bank to be chosen as a victim. There really are people out there trying to break into whatever computers they can. You don't want to leave yourself open to that. Furthermore, if your computer is ever broken into, you stand a far better chance of getting sympathetic help if you didn't leave it wide open in the first place. If I leave my door open and someone walks in and takes things, they are still doing wrong, but I'd be more likely to get sympathetic help had I locked the door. I will outline the approach I've taken to setting up our OS/2 systems. I AM NOT A UNIX OR NETWORK SECURITY EXPERT. Just for good measure, I'll say that again: I AM NOT A UNIX OR NETWORK SECURITY EXPERT. I've done enough reading to know that (a) it matters; and (b) security holes can be very subtle. So don't necessarily believe what I'm recommending. I welcome comments (but I will not open a debate on the morality of computer breakins). 1. Enable Telnet but only with the real password option. The default password option offered is very weak. It requires a single password that is readable by anyone who has access to the system. VERY WEAK. But, buried deep is a better solution. On page 72-73 of the Installation and Maintenance Manual is the description of how to set up telnet to require a Unix-style password file. Now, Unix-style passwords are far from hyper-secure, but they're better than a clear-text "password"! Perversely, IBM doesn't provide you with a program to make the passwd file: you'll need to copy an /etc/passwd file from a Unix host. But you've probably got a login on a Unix machine - you can use its password file. Follow the directions to install the passwd file and shuffle in a different version of the login.exe program on OS/2. In general, don't depend on any of the so-called "passwords" that appear in environmental varibles. World-visible passwords are a (bad) joke. 2. Disable incoming FTP except for the very restricted "anonymous" account. Your TRUSERS file should look like this: user: anonymous rd: c:\anonymous wr: c:\anonymous Make sure to create the directory c:\anonymous. Someone can stuff your system by filling disk's c:\anonymous directory with garbage, but that's relatively benign. If that's a problem, remove "c:\anonymous" from the "wr:" field. How can anyone FTP a file into your machine if you don't even let them have ftp write access to "\anonymous"? With this setup, a really trusted user can have an entry in the Unix-style passwd file. Then she or he can telnet into your machine and run FTP on your machine to suck the file in. Don't have anything else in the TRUSERS file. The idea of unencoded passwords is ludicrous. [Supplementary note added later:] Perhaps the above approach is a little harsh. It turns out that FTP will not allow reading or writing of the TRUSERS file. Hence, you _could_ put other entries into the TRUSERS file and an FTP-logged-in person couldn't pilfer the TRUSERS file itself. NOTE however, that TRUSERS will be accessible to any NFS or Telnet users, so passwords there are still available. You decide. Personally, it makes me too nervous. 3. Don't enable the rexecd server. It depends on clear-text passwords in the environment or in the NETRC file. People can Telnet in through the passwd-protected telnet, then execute the command. Same goes for the rshd server. Come on. Do you really want Joe Unwashed-behind-the-ears to be able to do "rexec yourmachine del c:\*"? And then giggle a bit. Yup, that could happen. 4. Don't enable the TFTP daemon "tftpd" unless you really need it for some obscure reason. FTP does the job. 5. Vanilla NFS is well known to be full of security holes. You'll notice the tight security demanded by the Unix host: give it a UID and GID number and that's who you are. Cute. I'd be very wary about giving write permission to my disk. REMEMBER: THERE ARE NO ACCESS CONTROLS ONCE SOMEONE HAS ACCESS TO YOUR OS/2 SYSTEM. No files are protected from reading or deletion. Once someone is into your system, they can happily read any of your setup files in \tcpip\etc (which could [if you're naive] contain real live readable passwords). They can also read your \config.sys and tcpstart.cmd files, in case they missed a password or two. The only people I want to have write access to my system are people who've passed the (really minimal!) test of having logged in past the Telnet-with-Unix-style-passwords. (12.) Tuning your setup ======================= Following are a few hints and suggestions that may help your networking system work better. Where I remembered, I've attributed suggestions to the people who suggested them. In most cases, these suggestions appeared on the Usenet newsgroup comp.os.os2.networking. I have edited many/most of these for conciseness and format, so I'm to blame if I've screwed them up (sorry). My apologies to those whom I forgot! 1. If you edit any of the installation scripts yourself, note that IBM uses an undocumented syntax. They use "attrib file parameters" instead of "attrib parameters file". This works fine unless you use 4OS2 (a command-line enhancer). If you do, start up an unenhanced cmd shell first. (mathelmr@nuscc.nus.sg (Helmer Aslaksen)) 2. After the initial thrill wears off, you'll wish there was some way to get OS/2 to stick all the networking windows into the Minimized Window Folder automatically at boot time. Following is a scheme for doing so. The basic idea is to stop tcpstart.cmd from being run in the \startup.cmd script (running it as a "Startup" folder object instead) and get all the programs started minimized, instead of as normal windows. (sip1@midway.uchicago.edu (Timothy F. Sipples), mathelmr@nuscc.nus.sg (Helmer Aslaksen), others) a. Edit \startup.cmd and put a REM in front of the line that runs the tcpstart.cmd script. Add an "exit" to the end of the \startup.cmd file (if you want its window to vanish, too). In fact (if nothing else is started in that file) instead of editing it, you can just move it to \startup.old and forget about it. b. From the desktop, open the "OS/2 System" object, then the "Startup" object within that. c. From the "Drives" object, open up directories until you have an icon view of the \tcpip\bin directory. Click the right mouse button once on the \tcpstart.cmd script. Using the resulting popup menu, create a shadow of the object, selecting the "Startup" window to be its location. The reason for doing A-C is that things in the "Startup" folder start up late enough in the boot process that they start after the Minimized Window Viewer is in place. Otherwise, you get icons across the bottom of the desktop (eeeeww!). d. Now edit the file \tcpip\bin\tcpstart.cmd. Wherever you see a "start ..." line, change it to "start /min ...". That will cause the programs to start minimized. NOTE: Check this file again any time you run ICAT: your changes may get blown away so that you'll have to reinsert the "/min"s. e. For any line in tcpstart.cmd that starts "call ...", edit the script that gets called. In those scripts, again change "start &period.&period.&period." lines to "start /min ...". Check this also after running ICAT. 3. Some of the networking software doesn't actually need to be run as a subprocess of a "cmd" process. For these cases, rather than issuing a "start ..." or a "start /min ..." to kick them off, you can issue a "detach ...". For some processes (ones that have certain requirements for interaction with keyboard and display), this won't work. Experiment with it, though, you can save some memory that way. I've found that it works with lprmon, lpd (run standalone, not via inetd), portmap, and nfsd. It does not work with telnetd. I think it works with inetd itself, but if inetd starts telnetd for you, then telnetd is stuffed. Hence, I gave up on inetd. Others, you're on your own... 4. If you have already put a default router's IP address into your configuration, you're probably not running routed. If you are running routed, however, you may be able to discover what your default router is, insert its address, and stop running routed. After you've been doing network things for a while (including pinging or ftping some remote sites), give the following command from an OS/2 command window: netstat -r Look for an entry that begins with "default". You guessed it: use that IP address as your default router address. Use ICAT to edit your network configuration: turn off "routed" and configure the default router's IP address into the Routing Information section. (Routed information: assela@rpi.edu (Andre Asselin)) 5.The networking software sucks memory. If you have 8 Mb or less of memory, your performance will go down noticeably (but far from fatally) as OS/2 swaps things in and out more often. Don't need the TELNET server? Close it. Don't need the FTP server? Shut it down. Don't need the TALK daemon? Get rid of it. Mailer unnecessary? Leave it aside. Only use X Windows occasionally? Start up the PMX daemon "by hand" when you need it. That said, we find that full blown TCP/IP does quite well in (true) 9 MB. The extra megabyte appears to make all the difference in the world. If you don't run with everything but the kitchen sink, 8 MB is viable. The 2.1 release should improve on that even more [since IBM is making efforts to make the OS/2 base use up less memory]. Pay attention to cache sizes, by the way: a disk cache that is too large will actually decrease performance. (sip1@midway.uchicago.edu (Timothy F. Sipples)) Our experience is that beefing up our systems to 16 Mb made things run _far_ more nimbly: the near-continual disk grinding stopped and the agonizing pauses went away. (13.) Interesting TCP/IP software ================================= There is a plethora of free software available on the Internet. One of the largest repositories of OS/2 software is the machine: ftp-os2.cdrom.com. Access it using anonymous FTP. That is, connect to it using ftp (give the command: ftp ftp-os2.cdrom.com) and give the user name "anonymous" (without the quotes) when prompted for a user ID. When prompted for a password, give your email address. See the manual entries on the FTP program for more details. Also see part (8) of this document for an example of downloading some files using FTP. Following are some pointers to useful TCP/IP-oriented programs (and some other "indispensables") that can be downloaded from ftp-os2 or other archive sites. The filenames are indented under the names of the directories under which they are found on ftp-os2 - locations may vary on other archives. A "*" for the filename indicates that there are several files in that directory that are relevant. pub/os2/all/info/faq/ * The OS/2 Frequently Asked Questions (with answers!) pub/os2/ibm/ews/ gopher.zip PM client for the Internet Gopher Client goserv.zip A Gopher Server protocol for OS/2 2.x pub/os2/2_x/network/ nistime.zip Update time/date from NIST Internet server os2gofer.zip Gopher client for OS/2 PM (requires VREXX & TCP/IP) os2nosv4.zip TCP/IP for OS/2 (via SLIP) - text-based passwd.zip IBM TCP/IP passwd file maintenance utilities slip20b1.zip Better performing SLIP for IBM TCP/IP 1.2.1 tcpstart.txt This document you're reading now! tn_enh11.zip Enhancement for IBM OS/2 2.0 telnet daemon wsos21.zip Novell Netware Requester 2.01 for OS/2, Disk 1 of 3 wsos22.zip Novell Netware Requester 2.01 for OS/2, Disk 2 of 3 wsos2d.zip Novell Netware Requester 2.01 for OS/2, Disk 3 of 3 nsd202.zip Novell Service Diskette (NSD #2) for WorkStation Kit pub/os2/2_x/network/ndis/ * NDIS drivers for many Ethernet cards pub/os2/all/network/ndis/ * NDIS drivers for many Ethernet cards pub/os2/ibm/tcpip/ * Home of "official" IBM bug fixes to TCP/IP pub/os2/2_x/patches/ * Home of more CSDs and bug fixes pub/os2/2_x/unix/unixutil/ elvis172.zip Elvis 1.7, a vi clone (for Unix devotees) xfeel11.zip A utility to make PM behave like X-Windows (14.) Good luck =============== That's about it for now, folks. Read the IBM manuals - they're actually not too bad. Not hold-your-handish, but most of what you need is (somewhere) in there. Best of luck with networking. Maybe we'll ping each other one day... (A1.) Appendix I: Coexistence of TCP/IP with Netware ==================================================== Personally, it's hard for me to believe, but apparently there's this other networking scheme out there by this little startup called Novell... I haven't needed to interact with a Novell network, but lots of people do. I've collected some of the postings from the Usenet newsgroup comp.os.os2.networking that address this issue. I hope that they will help you get things working if you need to access TCP/IP and Novell. I have edited the text for brevity and consistency, so please pardon any errors I may have introduced in the process. Thanks go entirely to the original posters of these messages - I've done nothing but copy their work. From: ccherry@vnet.ibm.com Organization: IBM Boca Programming Center Date: Wed, 27 Jan 93 23:53:32 GMT Install the NetWare requester. Then install LAN Adapter Protocol Support (LAPS). This came with your TCP/IP disks. Choose NetWare Requester support if it is available. Next install TCP/IP Support. If your version of LAPS offered NetWare requester support, double click on the NetWare line and a dialog will appear. The first line will be for the universal address of your Ethernet card. Enter that number and exit LAPS. Alternately, you can edit the LANADDRESS = line in \IBMCOM\PROTOCOL.INI If LAPS did not have NetWare support, you must follow the directions in Chapter 6 of the NetWare Requester for OS/2 manual. Good luck! From: davbur@joyner.lib.ecu.edu (David L. Burke) Organization: UNC Educational Computing Service Date: Mon, 25 Jan 1993 23:54:56 GMT Hope this stuff helps, guys. It was a bitch, but I got Requester to work with TCP/IP for OS/2 1.2.1. Below are The Big Three: CONFIG.SYS, NET.CFG, and PROTOCOL.INI. Before I say anything else, I hope to hell that after making these changes that your machine doesn't boot up with a register dump or some stupid message like "unable to locate Country.sys," or anything else which stops you in your tracks. Please make sure you have a floppy boot disk handy (I prefer makeboot.cmd myself.) Good luck. General points: Don't let ICAT or LAPS alter your config.sys. Add the appropriate lines and include \TCPIP... and \IBMCOM... in the necessary path statements. Setup: I'm using an NE2000 NIC (there's a NE2000.NIF on hobbes for LAPS). This setup works with 2.1b (as long as OS/2 is not loaded on Drive E: for some wierd reason). I'm superstitious about the INET.SYS and IFNDIS.SYS files, making sure I use the same ones with each new install. Don't have any idea why that is though. * * * * * * * CONFIG.SYS (Notice that all the TCPIP and IBMCOM stuff is at the end of * the file, after the requester stuff.) * * * * * * IFS=D:\OS2\HPFS.IFS /CACHE:512 /CRECL:4 /AUTOCHECK:D PROTSHELL=D:\OS2\PMSHELL.EXE SET USER_INI=D:\OS2\OS2.INI SET SYSTEM_INI=D:\OS2\OS2SYS.INI SET OS2_SHELL=D:\OS2\CMD.EXE SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS SET RUNWORKPLACE=D:\OS2\PMSHELL.EXE SET COMSPEC=D:\OS2\CMD.EXE LIBPATH=.;D:\OS2\DLL;D:\OS2\MDOS;D:\;D:\OS2\APPS\DLL;D:\NETWARE; D:\TCPIP\DLL;D:\IBMCOM\DLL;D:\TALKTHRU\PROGRAMS; SET PATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2;D:\OS2\INSTALL; D:\;D:\OS2\MDOS;D:\OS2\APPS;L:\OS2;P:\OS2;D:\NETWARE;D:\TCPIP\BIN; D:\IBMCOM;d:\tools\utilities;D:\TALKTHRU\PROGRAMS; SET DPATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2;D:\OS2\INSTALL; D:\;D:\OS2\BITMAP;D:\OS2\MDOS;D:\OS2\APPS;D:\NETWARE;D:\IBMCOM; SET PROMPT=$i[$p] SET HELP=D:\OS2\HELP;D:\OS2\HELP\TUTORIAL;D:\TCPIP\HELP; SET GLOSSARY=D:\OS2\HELP\GLOSS; SET IPF_KEYS=SBCS PRIORITY_DISK_IO=YES FILES=20 SET DIRCMD=/O:GN DEVICE=D:\OS2\TESTCFG.SYS DEVICE=D:\OS2\DOS.SYS DEVICE=D:\OS2\PMDD.SYS BUFFERS=30 IOPL=YES DISKCACHE=512,LW MAXWAIT=3 MEMMAN=SWAP,PROTECT SWAPPATH=D:\OS2\SYSTEM 2048 2048 BREAK=OFF THREADS=256 PRINTMONBUFSIZE=134,134,134 COUNTRY=001,D:\OS2\SYSTEM\COUNTRY.SYS SET KEYS=ON REM SET DELDIR=C:\DELETE,512;D:\DELETE,512; BASEDEV=PRINT01.SYS BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD BASEDEV=OS2DASD.DMD SET BOOKSHELF=D:\OS2\BOOK SET EPMPATH=D:\OS2\APPS SET FAXPM=D:\OS2\APPS REM DEVICE=D:\OS2\APPS\SASYNCDA.SYS PROTECTONLY=NO SHELL=D:\OS2\MDOS\COMMAND.COM D:\OS2\MDOS /P /E:1024 FCBS=16,8 RMSIZE=640 DEVICE=D:\OS2\MDOS\VEMM.SYS DOS=LOW,NOUMB DEVICE=D:\OS2\MDOS\VDPX.SYS DEVICE=D:\OS2\MDOS\VXMS.SYS /UMB DEVICE=D:\OS2\MDOS\VDPMI.SYS DEVICE=D:\OS2\MDOS\VWIN.SYS DEVICE=D:\OS2\MDOS\VCDROM.SYS REM DEVICE=D:\OS2\PCMCIA.SYS REM DEVICE=D:\OS2\MDOS\VPCMCIA.SYS DEVICE=D:\OS2\MDOS\VMOUSE.SYS DEVICE=D:\OS2\POINTDD.SYS DEVICE=D:\OS2\MOUSE.SYS SERIAL=COM1 DEVICE=D:\OS2\COM.SYS DEVICE=D:\OS2\MDOS\VCOM.SYS CODEPAGE=437,850 DEVINFO=KBD,US,D:\OS2\KEYBOARD.DCP SET VIDEO_DEVICES=VIO_SVGA DEVICE=D:\OS2\MDOS\VSVGA.SYS REM --- NetWare Requester statements BEGIN --- DEVICE=D:\NETWARE\LSL.SYS RUN=D:\NETWARE\DDAEMON.EXE DEVICE=D:\NETWARE\NE2000.SYS DEVICE=D:\NETWARE\IPX.SYS DEVICE=D:\NETWARE\SPX.SYS RUN=D:\NETWARE\SPDAEMON.EXE rem DEVICE=D:\NETWARE\NMPIPE.SYS rem DEVICE=D:\NETWARE\NPSERVER.SYS rem RUN=D:\NETWARE\NPDAEMON.EXE NP_COMPUTERNAME DEVICE=D:\NETWARE\NWREQ.SYS IFS=D:\NETWARE\NWIFS.IFS RUN=D:\NETWARE\NWDAEMON.EXE DEVICE=D:\NETWARE\NETBIOS.SYS RUN=D:\NETWARE\NBDAEMON.EXE DEVICE=D:\NETWARE\VIPX.SYS DEVICE=D:\NETWARE\VSHELL.SYS REM --- NetWare Requester statements END --- REM Below is all the TCPIP and IBMCOM stuff (not before!) DEVICE=D:\IBMCOM\LANMSGDD.OS2 /I:D:\IBMCOM DEVICE=D:\IBMCOM\PROTMAN.OS2 /I:D:\IBMCOM rem DEVICE=D:\IBMCOM\MACS\NE2000.OS2 /I:D:\IBMCOM DEVICE=D:\NETWARE\ODINSUP.SYS RUN=D:\IBMCOM\PROTOCOL\NETBIND.EXE RUN=D:\IBMCOM\LANMSGEX.EXE SET ETC=D:\TCPIP\ETC SET TMP=D:\TCPIP\TMP DEVICE=D:\IBMCOM\PROTOCOL\IFNDIS.SYS DEVICE=D:\IBMCOM\PROTOCOL\INET.SYS RUN=D:\TCPIP\BIN\CNTRL.EXE SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA) DEVINFO=SCR,VGA,D:\OS2\VIOTBL.DCP * * * * * * * NET.CFG (nothing special here) * * * * * * Link driver ne2000 protocol ipx 8137 ethernet_ii frame ethernet_ii int 5 port 360 node address 1B198826 netware requester preferred ecu_joyner_library protocol odinsup bind ne2000 link support buffers 16 1514 * * * * * * * PROTOCOL.INI (Don't worry about the LAPS settings during install. They * only write to the PROTOCOL.INI as far as I know.) * * * * * * [PROT_MAN] DriverName = PROTMAN$ [IBMLXCFG] NE2000_nif = NE2000.nif TCPIP_nif = TCPIP.nif ;*----------------------------------------------* ;*------------- PROTOCOL SECTION ---------------* ;*----------------------------------------------* [TCPIP_nif] DriverName = TCPIP$ ; Bindings = NE2000_nif Bindings = NE2000 ;*----------------------------------------------* ;*--------------- MAC SECTION ------------------* ;*----------------------------------------------* [NE2000] [NE2000_nif] DriverName = MS2000$ IOBASE = 0x360 INTERRUPT = 5 From: loflin@emx.cc.utexas.edu (Don Loflin) Organization: The University of Texas at Austin, Austin, Texas Date: 28 Jan 1993 08:55:21 -0600 I found the following settings to be the most crucial, especially the "protocol odinsup / bind ne2000" part, which the ODINSUP readme claimed was optional if you only had 1 ODI driver loaded (e.g. it would bind to the only driver found). * * * * * * NET.CFG * * * * * protocol odinsup bind ne2000 * * * * * * PROTOCOL.INI * * * * * [TCPIP_nif] Bindings = NE2000 From: RZHM@rz.uni-osnabrueck.DE (Helmut Meyhoefer) Organization: Computing Center Date: Thu, 28 Jan 1993 13:38:27 GMT This is my configuration for CM, TCPIP and NW Requester with NSD201. No problems. * * * * * * CONFIG.SYS * * * * * IFS=C:\OS2\HPFS.IFS /CACHE:384 /CRECL:4 /AUTOCHECK:CDE REM ******* LAPS: RUN=C:\OS2\INSTALL\IBMLANLK.EXE C:\OS2\INSTALL\IBMLANLK.LST RUN=C:\OS2\XCOPY.EXE C:\OS2\OS2*.INI E:\OS2\IniSave PROTSHELL=C:\OS2\PMSHELL.EXE SET RESTARTOBJECTS=STARTUPFOLDERSONLY SET USER_INI=C:\OS2\OS2.INI SET SYSTEM_INI=C:\OS2\OS2SYS.INI SET OS2_SHELL=C:\OS2\CMD.EXE SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE SET COMSPEC=C:\OS2\CMD.EXE LIBPATH=.;C:\OS2\DLL;C:\MUGLIB\DLL;C:\OS2\MDOS;E:\CMLIB\DLL;C:\;C:\OS2\APPS\DLL ;C:\IBMCOM\DLL;E:\NETWARE;E:\TCPIP\DLL; SET PATH=C:\OS2;C:\OS2\CMD;C:\MUGLIB;C:\OS2\SYSTEM;D:\SYSTEM;C:\OS2\MDOS\WINOS2;E:\ CMLIB;E:\CMLIB\APPN;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\OS2\APPS;L:\OS2;P:\OS2;E: \NETWARE;E:\TCPIP\BIN; SET DPATH=C:\OS2;C:\MUGLIB\DLL;E:\CMLIB;E:\CMLIB\APPN;C:\OS2\SYSTEM;C:\OS2\MDOS\WIN OS2;C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS;C:\IBMCOM;E:\NETWA RE;L:\OS2; SET PROMPT=$e[32;40m$e[1mrc=$r [$p] $i$e[0m SET HELP=E:\CMLIB\APPN;C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;E:\TCPIP\HELP; SET GLOSSARY=C:\OS2\HELP\GLOSS; SET THE_HELP=D:\OS2\UTILS\THE\OS2.HLP SET THE=D:\OS2\UTILS\THE\PROFILE.THE SET DIRCMD=/O:GN PRIORITY_DISK_IO=YES FILES=20 DEVICE=C:\OS2\R0CSDD.SYS REM ******* LAPS: DEVICE=C:\OS2\INSTALL\IBMLANLK.SYS C:\OS2\INSTALL\IBMLANLK.LST DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM DEVICE=C:\ibmcom\protman.os2 /I:C:\ibmcom DEVICE=C:\OS2\TESTCFG.SYS DEVICE=C:\OS2\DOS.SYS DEVICE=C:\OS2\PMDD.SYS BUFFERS=30 IOPL=YES DISKCACHE=64,LW MAXWAIT=3 MEMMAN=SWAP,PROTECT SWAPPATH=E:\SWAPSPACE 2048 4096 BREAK=OFF THREADS=256 PRINTMONBUFSIZE=134,134,134 COUNTRY=049,C:\OS2\SYSTEM\COUNTRY.SYS SET KEYS=ON SET DELDIR=C:\DELETE,512 D:\DELETE,1024 E:\DELETE,1024 BASEDEV=PRINT02.SYS BASEDEV=IBM2FLPY.ADD BASEDEV=IBM2ADSK.ADD BASEDEV=OS2DASD.DMD SET BOOKSHELF=C:\OS2\BOOK; SET EPATH=C:\OS2\APPS DEVICE=C:\OS2\APPS\SASYNCDB.SYS PROTECTONLY=NO SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS /E:1000/P FCBS=16,8 RMSIZE=640 DEVICE=C:\OS2\MDOS\VEMM.SYS DEVICE=C:\OS2\MDOS\VMOUSE.SYS DOS=LOW,NOUMB DEVICE=C:\OS2\MDOS\VDPX.SYS DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB DEVICE=C:\OS2\MDOS\VDPMI.SYS DEVICE=C:\OS2\MDOS\VWIN.SYS DEVICE=C:\OS2\MDOS\VCDROM.SYS DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP SET VIDEO_DEVICES=VIO_VGA SET VIO_VGA=DEVICE(BVHVGA) DEVICE=C:\OS2\MDOS\VVGA.SYS CODEPAGE=850,437 DEVINFO=KBD,GR,C:\OS2\KEYBOARD.DCP DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MOUSE.SYS DEVICE=C:\OS2\COM.SYS DEVICE=C:\OS2\MDOS\VCOM.SYS DEVICE=C:\OS2\MDOS\ANSI.SYS REM Protokollierung einschalten: DEVICE=C:\OS2\LOG.SYS RUN=C:\OS2\SYSTEM\LOGDAEM.EXE REM ********* Netware Requester *************** REM --- NETWARE REQUESTER STATEMENTS BEGIN --- DEVICE=E:\NETWARE\LSL.SYS RUN=E:\NETWARE\DDAEMON.EXE DEVICE=E:\NETWARE\TOKEN.SYS DEVICE=E:\NETWARE\ROUTE.SYS DEVICE=E:\NETWARE\IPX.SYS DEVICE=E:\NETWARE\SPX.SYS RUN=E:\NETWARE\SPDAEMON.EXE DEVICE=E:\NETWARE\NWREQ.SYS IFS=E:\NETWARE\NWIFS.IFS RUN=E:\NETWARE\NWDAEMON.EXE DEVICE=E:\NETWARE\VIPX.SYS DEVICE=E:\NETWARE\VSHELL.SYS DEVICE=E:\NETWARE\ODINSUP.SYS REM --- NETWARE REQUESTER STATEMENTS END --- REM ********* Communications Manager *************** DEVICE=C:\ibmcom\protocol\LANDD.OS2 DEVICE=C:\ibmcom\protocol\LANDLLDD.OS2 DEVICE=E:\CMLIB\ACSLDLAN.SYS RUN=C:\OS2\EPW.EXE RUN=C:\ibmcom\protocol\landll.exe DEVICE=E:\CMLIB\APPN\CMKFMDE.SYS DEVICE=C:\IBMCOM\PROTOCOL\IFNDIS.SYS DEVICE=C:\IBMCOM\PROTOCOL\INET.SYS REM ******* TCPIP SET ETC=E:\TCPIP\ETC SET TMP=E:\TCPIP\TMP RUN=E:\TCPIP\BIN\CNTRL.EXE REM ******* LAPS: RUN=C:\ibmcom\protocol\netbind.exe RUN=C:\ibmcom\lanmsgex.exe REM ******* TCPIP SET XFILES=E:\TCPIP\X11 SET USERNAME= SET HOSTNAME= SET TELNET.PASSWORD.ID= CALL=CMD.EXE * * * * * * NET.CFG * * * * * Link Driver token frame token-ring frame token-ring_snap node address 400031741015 Link Support buffers 14 4210 protocol odinsup bind token protocol stack ipx sessions 50 Sockets 64 PROTOCOL STACK SPX Abort Timeout 30000 Verify Timeout 3000 Listen Timeout 6000 Send Timeout 6000 Retry Count 20 Sessions 50 Netware Requester cache buffers 20 sessions 8 request retries 20 preferred server server_name Netware Spooler copies 1 keep size 8 banner form feed * * * * * * PROTOCOL.INI * * * * * [PROT_MAN] DriverName = PROTMAN$ [IBMLXCFG] TCPIP_nif = TCPIP.nif LANDD_nif = LANDD.NIF [TCPIP_nif] DriverName = TCPIP$ Bindings = TOKEN [LANDD_nif] DriverName = LANDD$ Bindings = TOKEN From: reus@mic.dth.dk (Roger de Reus) Organization: Mikroelektronik Centret, DTH, Denmark Date: Thu, 10 Jun 93 12:11:44 METDST One suggestion for your document: Since you refer to ftp.nmsu.edu to get the CSD's for TCP/IP, you may as well refer to the same place to get the latest Netware release (/pub/os2/2_x/network/novell) and documentation. Here the (excerpts) of the configuration files. I have TCP/IP (with X11) and Netware (finally) running simultaneously over one single 3COM 3C503 card. I did not use the configuration programs (ICAT and LAPS) but manually edited the files. Note that all the ELINKII stuff is commented out. I was happy when things finally worked out, and did not try more. Probably lots of extraneous code lying around. Did not get things running by automatically routing, so explicitly added a default gateway in the routing command (last line of this file). Hope this will get some people getting ahead quicker than I did. Credits should go to the Hobbes ftp server (ftp-os2.nmsu.edu) which made the latest changes to both TCP/IP and Netware software available (and now supplies all the OS/2 goodies on CD-ROM for $25,-, I believe---grab it you American guys), Kerry Sesker (cmdses@pmvax.weeg.uiowa.edu) who supplied me with some configuration files I could start with, and Prof. Mike Thompson (Cornell University), who pointed me to ftp-os2 for the Novell software update. * * * * * * CONFIG.SYS (relevant parts) * * * * * LIBPATH=...;C:\TCPIP\DLL;C:\USR\NETWARE;C:\IBMCOM\DLL; SET PATH=...;C:\TCPIP\BIN;...;C:\USR\NETWARE;C:\IBMCOM; SET DPATH=...;C:\USR\NETWARE;C:\IBMCOM; SET HELP=...;C:\TCPIP\HELP; REM --- TCP/IP and NetWare Requester statements BEGIN --- DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM SET ETC=C:\TCPIP\ETC RUN=C:\TCPIP\BIN\CNTRL.EXE SET XFILES=C:\TCPIP\X11 SET DISPLAY=reus026.mic.dth.dk:0 SET TZ=CET SET LPR_SERVER=mic.dth.dk SET LPR_PRINTER=ps SET HOSTNAME=reus026 SET LANG=Da_DK SET NWLANGUAGE=ENGLISH DEVICE=C:\USR\NETWARE\LSL.SYS RUN=C:\USR\NETWARE\DDAEMON.EXE DEVICE=C:\USR\NETWARE\3C503.SYS DEVICE=C:\USR\NETWARE\ODINSUP.SYS DEVICE=C:\USR\NETWARE\IPX.SYS DEVICE=C:\USR\NETWARE\NWREQ.SYS IFS=C:\USR\NETWARE\NWIFS.IFS RUN=C:\USR\NETWARE\NWDAEMON.EXE RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE RUN=C:\IBMCOM\LANMSGEX.EXE DEVICE=C:\USR\NETWARE\VIPX.SYS DEVICE=C:\USR\NETWARE\VSHELL.SYS DEVICE=C:\IBMCOM\PROTOCOL\INET.SYS DEVICE=C:\IBMCOM\PROTOCOL\IFNDIS.SYS rem DEVICE=C:\IBMCOM\PROTOCOL\ELINKII.OS2 REM --- TCP/IP and NetWare Requester statements END --- * * * * * * NET.CFG * * * * * cache buffers = 40 file handles = 120 max tasks = 60 pb buffers = 10 preferred server = mic show dots on link driver 3C503 frame ethernet_802.3 frame ethernet_ii frame ethernet_802.2 frame ethernet_snap node address 02608c8c04eb protocol ipx 0 ethernet_802.3 link support buffers 15 4210 mempool 4096 protocol odinsup bind 3c503 protocol stack IPX bind 3c503 protocol tcpip ip_address 129.142.64.205 ip_router 129.142.6.16 ip_netmask 255.255.0.0 tcp_sockets 8 udp_sockets 8 raw_sockets 1 nb_sessions 4 nb_commands 8 nb_adapter 0 nb_domain netware requestor cache buffers 20 displayharderrors no preferred server mic netware spooler no banner no form feed * * * * * * PROTOCOL.INI * * * * * [PROT_MAN] DriverName = PROTMAN$ [IBMLXCFG] ; ELNKII_nif = ELNKII.nif TCPIP_nif = TCPIP.nif ;*----------------------------------------------* ;*------------- PROTOCOL SECTION ---------------* ;*----------------------------------------------* [TCPIP_nif] DriverName = TCPIP$ Bindings = X3C503 ;*----------------------------------------------* ;*--------------- MAC SECTION ------------------* ;*----------------------------------------------* [X3C503] ;[ELNKII_nif] ; DriverName = ELNKII$ ; netaddress = "02608C8C04EB" ; interrupt = 3 ; ioaddress = 0x300 ; transceiver = "ONBOARD" ; maxtransmits = 8 ; xmitbufs = 2 * * * * * * TCPSTART.CMD (initializes also X11) * * * * * @echo off echo CONFIGURING TCP/IP ..... CALL C:\TCPIP\BIN\SETUP.CMD echo ..... FINISHED CONFIGURING TCP/IP echo STARTING THE TCP/IP PROCESSES ..... rem start pmx -nocopyright -staticcolor -k 102 CALL C:\TCPIP\BIN\XINIT.CMD -staticcolor -k 102 echo ..... X System Server Started rem call nfsstart rem echo ..... Network File System Client Started echo ..... FINISHED STARTING THE TCP/IP PROCESSES echo ..... EXITING TCPSTART.CMD ..... * * * * * * SETUP.CMD (called by TCPSTART) * * * * * route -fh arp -f ifconfig lan0 129.142.64.205 netmask 255.255.0.0 route add default 129.142.6.16 1 (A2.) Appendix II: Supplementary information on SLIP ==================================================== Rather than editing matter that I don't fully understand, I've included this dialog essentially verbatim. It is Dave Bolen, author of a SLIP driver (alternative to IBM's own) replying to SLIP configuration questions from Don Lindbergh. Dave Bolen's SLIP driver is presently still in the testing stage, but users reporting in the comp.os.os2.networking newsgroup are uniformly glowing in their reviews of it. At the time of writing, Bolen's slip driver can be had via anonymous FTP from ftp.ans.net in file /pub/misc/slip20a3.zoo. In any case, the following notes should give you a _lot_ of information about SLIP connections in general, as well as information that may be specific to Dave's drivers. From: dabl2@nlm.nih.gov (Don A.B. Lindbergh) Date: Wed, 17 Feb 93 14:04:06 EST Message-Id: <9302171904.AA09472@nlm.nih.gov> X-To: dean2@bigbird.csd.scarolina.edu Subject: Re: TCP/IP, SLIP, Beat 2.1 Setup Questions (LONG) Ok, I'm sending you what Bolen sent me. He has sent me two replies. The first is pretty much *it* as far as what you're probably interested in. It is long and has diagrams :) The second piece is an attempt at further clarification. I also included the first piece of mail from a gentlemen trying to help me put the final piece in place, using ROUTED. I basically haven't been able to get it to work (I think) because of: 1. not much time 2. incorrect syntax There will undoubtably be some more email from him, after which I predict the light will shine on me, the angles will sing, and I will actually have a full blow slip home system going...... Oh, near the end of Bolen's first note is an 'off the cuff' 'untested' method of using 'arp -s' to 'publish' a network card to do routing. I wasen't able to get this to work for me, it may be I'm doing something wrong. I intend to at least confirm with him that this method *does* in fact work. It seems I will be using either this method or ROUTED as getting a static route added for my SLIP subnet may be a hassle (Bolen talks about all this). So, truthfully, I'm not quite out of the woods yet, but I wanted to send you what he sent me, because it seems he has told me pretty much everything. I figured it's better to send you more than you need rather than edit it down myself. If you like, I'll forward what I get and wrap it up when I get it really working. Your stuff was invaluable to me when I was trying to get tcp/ip going. --Don Lindbergh dabl2@lhc.nlm.nih.gov From db3l@ans.net Mon Feb 15 16:41:48 1993 To: dabl2@nlm.nih.gov (Don A.B. Lindbergh) >REQUEST FOR HELP, somewhat lengthy..... Well, let's see what we can do... Warning - your request may have been lengthy, but these answers get real long sometimes :-) >I'm really unclear on how to setup at home for SLIP. I've read over >EVERY occurance of 'slip' in the TCPINFO doc's, I don't get it.... Part of the difficulty explaining this sort of stuff is that if you get generic enough in your explanation to cover anyone's case, the explanation becomes vague enough to be less than helpful :-) For example - you don't give any actual IP addresses in your supplied office and home configurations, and yet it is likely the actual IP addresses (and routing between them) that is the problem. So - for these examples, I'll use some explicit IP addresses that we use here at ANS - hopefully, it will not be difficult to translate their use into your own addresses. Let's take the office machine. In my case, it has two interfaces - an ethernet (lan0) and com1 (sl). The important elements for packet flows are the addresses of the interfaces, and the routes that the machine has to specific hosts or networks. Let's say the office LAN is 147.225.10.x, and my machine has the address 147.225.10.18. Thus, subnet 10 of network 147.225 (a class B network) is dedicated to the office ethernet. There is a default router on the office lan, 147.225.10.1, that I should send packets to when I don't know where to send them. The subnet mask for my LAN is 255.255.255.0. Also, I have a nameserver at 147.225.10.1. Now let's say that I choose subnet 11 for my SLIP connection. You can't give hosts at the far end of the SLIP link an address in subnet 10 since the rest of your LAN all think that subnet 10 hosts are directly connected to the ethernet itself. (This isn't completely true, but it's tricky to work around, so let's say it is true for now). It is possible, as your example showed, to have your office machine be 147.225.10.18 on both interfaces, but is often clearer if you give it an address in the same subnet as the far end of the link. Let's say in my case, I've made the office machine 147.225.11.1 on the sl interface, and my home machine is going to be 147.225.11.2. Thus, you end up with the following configuration: -+- | | +----------------+ +--------------+ LAN | | Office Machine | | Home Machine | | | -- -- -- -- -- | Phone Line | -- -- -- -- | | | | 147.225.11.x | | 147.225.10.x +------| lan0 sl |--------------| sl | | .18 | | .1 .2 | | | +----------------+ +--------------+ | -+- Now I don't think you've had a problem getting to this stage of everything, even though your addresses may be different. The next big problem is getting packets to flow where you want. In this example, hosts on the 147.225.10 network don't have a problem talking to one another. They all know that anything in 147.225.10 should be on the LAN wire. They also know a default router at 147.225.10.1. If I did a "netstat -r" on your office machine, I would find an entry like: Office with LAN: destination router intrf (interface) default 147.225.10.1 lan0 147.225.10.0 147.225.10.18 lan0 or in other words - packets heading to anything on 147.225.10 would go through my local interface to the LAN, lan0, while anything else also goes out over lan0, but it gets sent to the 147.225.10.1 host, which should know what to do with it. That's just the LAN. Once you start SLIO and create the "sl" interface, and ifconfig the appropriate addresses, your routing table will look like the following: Office with LAN and SLIP: destination router intrf (interface) default 147.225.10.1 lan0 147.225.10.0 147.225.10.18 lan0 147.225.11.2 147.225.11.1 sl which is the same as before except that traffic for host 147.225.11.2 will go over the serial interface. If you use the same address for your office machine on lan0 as on sl, the above would be the same except the router field would show 10.18 in both the lan0 and sl cases. Now, to finish off the scenario, on your home machine all you did is configure the sl interface - nothing else is running. That gives you a routing table like the following: Home with SLIP: destination router intrf (interface) 147.225.11.1 147.225.11.2 sl Now, given the differences in IP address, I think that's the state you've been able to get to in your experiments. Or, to add this routing information to my original picture, my hosts would look configured something like the following: -+- | | +----------------+ +--------------+ LAN | | Office Machine | | Home Machine | | | -- -- -- -- -- | Phone Line | -- -- -- -- | | | | 147.225.11.x | | 147.225.10.x +------| lan0 sl |--------------| sl | | .18 | | .1 .2 | | | +----------------+ +--------------+ | <-- 147.225.10 | <-- default | 147.225.11.2 --> <-- 147.225.11.1 -+- Ok. Presuming you're still with me :-) Here's where you begin to run into problems. As long as you are on your office machine, you'll be fine. If you try to send packets to someone on the LAN, the route for 147.225.10 will work and you'll find them. If you try to send packets to your home machine, it will go out over the serial interface and find it. If you send packets somewhere else, they'll go to the default router, which will get them there. And, since your office machine is part of your LAN, packets will find their way back to you since the rest of the LAN (and outside networks) know how to reach your 147.225.10 addresses. Nameserver stuff will work fine too, since the nameservers are presumably on your LAN, so queries are just like other LAN traffic. The home machine has some problems however. Once you get SLIP running there, you should be able to ping your office machine's address over the SLIP link. In other words, in my example, a "ping 147.225.11.1" would work, and I could do things like FTP to the office machine. But that's the only communication that works. The problem with other hosts is routing related. For example, let's say that your home host tried to talk to the default router, 147.225.10.1. On your home machine you only know how to reach 147.225.11.1, so when you use the 10.1 address, your home machine doesn't know how to get there. That's where you get the "no route to host message". It is telling you it doesn't know where to send packets for hosts other than 147.225.11.1. Now that's an easy one to fix. Add a default route on your home box pointing to your office box. Then, if you try to use an address that the home machine doesn't know about, it will still send it to the office machine. The office machine will then either know about it (if it's part of 147.225.10, such as your nameserver), or it will forward it on to *its* default router, 147.225.10.1. This is only part of the problem, however. That solves the outgoing packets from your home machine, but it doesn't fix the case of packets coming back in to your home machine. For example, your home machine will now know how to send a packet to the nameserver that you use in your office, but the nameserver won't know how to send the packet back to the home machine. The nameserver will know that 147.225.10 addresses are on the LAN, but it won't know what to do with a 147.225.11 address. There are a few ways to fix this. What you really need to do is to get all the other hosts on your LAN to know that subnet 147.225.11 is routed through you, and that they should send packets to you for those addresses. This is not normally practical, however, since a number of owners of hosts are involved. Another alternative is for everyone to run a routing daemon (such as the ROUTED that came with the TCP/IP package), which lets your machine announce to the other machines that it has the SLIP route, and then they know where to send the packages. Again, this may not be reasonable as everyone may not want to or be able to run a routing daemon. Probably the easiest thing for you to do is to get whoever administers the default router to add a static route for your SLIP subnet to that router. Then, since everyone else on the LAN defaults to that router, when it gets packets for your SLIP host it will forward them back to you. Often, it will also issue a redirect to the hosts telling them where they should have really sent the packets. So to summarize - your problems are likely twofold. One, that your home host doesn't know to default to the office host for stuff that it doesn't have an explicit route to. And two, that the hosts on the LAN (or the outside world for that matter) don't know to use you to reach your home host. You need to solve both of those routing problems before you can see packets flowing between your home host and any other IP attached host. In terms of the configurations you posted: >OFFICE MACHINE SETUP.CMD: >route -fh >arp -f >ifconfig lan0 myipaddress netmask 255.255.255.0 >REM ifconfig lan1 >REM ifconfig lan2 >REM ifconfig lan3 >start slio.exe >sliowait >ifconfig sl myipaddress otherpcaddress >route add default myrouter 1 This should be fine. In general, I don't expect your office machine would have any problems. It's the one machine in this whole configuration that knows just what is going on, and how to reach everyone it needs to reach. >HOME MACHINE SETUP.CMD: >route -fh >arp -f >REM ifconfig lan0 myipaddress officeipaddress netmask 255.255.255.0 >REM ifconfig lan1 >REM ifconfig lan2 >REM ifconfig lan3 >start slio.exe >sliowait >ifconfig sl myipaddress officeipaddress This is fine. >route add host officeipaddress officerouter You don't need this. ifconfig'ing sl will automatically add this route to your routing tables. What you do need is a statement: route add default officeipaddress 1 to let the home host pass all other packets through to the office as well. And you need the office machines (or default router) to know about your home address too. If this sounds convoluted, it's because it's a lot harder to write about and explain than just to do - at least I find it that way. If you've stuck with me this far, I'll also throw in a way you can cheat with your SLIP address and make the rest of your office LAN think your home machine is right on the LAN - thus avoiding the need to tell them about routing or get your default router to change. Some of this is off the cuff - I don't think I've done this explicitly myself yet, although it should work fine. What you do first is get another LAN address for your home SLIP machine - in my case, let's say it was 147.225.10.19. You then configure everyone just as before, including the default route on your home SLIP machine. You end up with the following: Office with LAN and SLIP: destination router intrf (interface) default 147.225.10.1 lan0 147.225.10.0 147.225.10.18 lan0 147.225.10.19 147.225.10.18 sl Home with SLIP: destination router intrf (interface) default 147.225.10.18 sl 147.225.10.18 147.225.10.19 sl For your office machine, any packets to host 147.225.10.19 (your home host) will go over the serial line. All other packets for 147.225.10 hosts will go over the LAN interface. And anything else will be put over the LAN interface to the default router also on the LAN. For your home machine, packets to your office machine will go over the serial interface, and packets to anything else will first be passed to your office machine (over the serial interface) for handling. Now the only rub is getting machines on the LAN to talk back to your home machine. The problem is that those machines will think (since it has a 147.225.10 address) that your home machine is directly connected to the LAN. What happens on the LAN is that other machines issue ARP (Address Resolution Protocol) requests to translate an address (147.225.10.19 in this case) into a hardware level address (such as a token ring or ethernet adapter address). Packets are then sent over the LAN to that hardware address. For most machines, they answer for their own address, and give their hardware address. Obviously, your home machine can't do that in this case since it isn't attached directly to the LAN. So what you do is tell your office machine to answer for your home machine. You use the "arp" command to "publish" a permanent arp entry for your home machine. The entry will use your office machine's hardware address as the arp answer. Then, other machines in the office will use your office machine's hardware address on the LAN when sending packets to your home machine - so the packets will end up on the office machine. The office machine will look at the actual IP address and recognize that it should go down the serial link to the home machine. This entire process is called "Proxy ARPing", and is often supplied as an automatic process in SLIP servers or routers - we'd just be doing it in a more manual fashion. To set up the arp entry, you need to figure out your hardware address. You can either do this by looking at the LANTRAN.LOG file in your LAPS directory (normally C:\IBMCOM). It should have a line like: "Adapter 0 is using node address 10005A82501A (...)" Or, check someone else's machine that has recently exchanged traffic with you and do an "arp -a" and look for your address as in: hardware address IP address 10005A82501A 147.225.10.18 In either event, you want to know your 12-digit hexadecimal hardware address. Once you know that, you can stuff an entry for your home machine in your arp table with the command: arp -s 147.225.10.19 10:00:5A:82:50:1A pub which will permanently "publish" an arp entry for your home machine. From now on, other machines on the LAN will think that your home machine is right on the ethernet (or token ring) itself, although your office machine will actually be routing packets through the serial link to the home machine. Note that if you are on a token ring, you need to use a bitwise reversed address (shown in the LANTRAN.LOG file as the token ring format on the same line as the adapter node address). I think that's about it. Like I said - it's more complicated to explain than it really is. I hope this helps more than it confuses. I'd suggest also trying to find a local support person at your site that may be able to help out with the routing issues. Or, if you have some sort of central SLIP server facility, it will probably be easier to make use of that, as the routing issues will most likely have already been addressed for that server. -- David From db3l@ans.net Tue Feb 16 18:37:53 1993 To: dabl2@nlm.nih.gov (Don A.B. Lindbergh) Subject: Re: TCP/IP, SLIP, Beat 2.1 Setup Questions (LONG) Don, . > I had no idea that the slip connection ip addresses > should have a different subnet than the 'real' > lan ip addresses. Yeah - the problem is that while you can get it partially working without using a different subnet, you really need the separate subnet for proper operation (barring proxy arp solutions). The reasons for this are rooted in the fundamentals of how IP routing is handled, which can be daunting topic for those new to IP networking (or even old hands :-)). Couple this with the fact that most IP office users don't necessarily know the subnetting and routing scheme in place at their site, and it becomes even more fun. (At the risk of repeating info from my previous message) I think it starts to become more understandable - and explainable - if you make believe you are a machine on your LAN. Let's say I'm on your LAN as address 138.68.31.50. My machine has a routing table telling me where to send packets for particular destinations, as: destination 134.68.31.0 gateway 134.68.31.50 (anything on 134.68.31 goes out onto my local LAN via my LAN interface, and gets my LAN address on it as the source address) destination default gateway 134.68.31.103 (anything else goes to the specified gateway. To reach that gateway, I use my previous route to reach the LAN) Now I'm in good shape - I know how to reach machines on the LAN, and those off your LAN. Now say that friendly Don - you - down the hall (with his machine 134.68.31.25) add a SLIP link, and gives your home machine address 134.68.31.26. You sets things up so that if you type "ping 134.68.31.50" from home, the packets reach my machine in the office. So far so good - the problem is where do I send the answer? I need to reach 134.68.31.26, which according to my routing table is right on my LAN. I therefore try to send it right over the LAN, but there's no machine there with that address. Now I personally can fix that problem by adding a specific (static) route to my machine that says: destination 134.68.31.26 gateway 134.68.31.25 which says that if I need to reach the specific machine 31.26, I send it to your office machine. Anything else in 134.68.31 follows the old rule and goes directly to the LAN. Now I can communicate with everyone including your home machine. Of course, this solution doesn't scale well, and it doesn't help you from home since you have to get everyone else (or at least the default gateway) to add the route. Thus the rest of my previous note :-) > He says getting something like a > static route added to our subnet requires calling someone else, which > is not a huge problem, but if we did this, hopefully we could add this > slip subnet ONCE and that one addition would work for all our group > who want to use slip. I would like to try your suggestions about > permanently publishing an arp entry first I think..... Having a dedicated SLIP subnet and a primary SLIP router is in fact the way many sites (including ours) handles the issue. For single SLIP connections into individual office machines a proxy arp solution may be the simplest and most effective - although it does require manual configuration - and you still have to get yourself allocated an extra address in the LAN subnet. > Some further comments and questions.... Ok. > I know, I questioned the wisdom of publicly posting all my ip > addresses, on the other hand, who really cares and what if they did > right? I've at least got password entry's for telnet and ftp.... Actually, that's a pretty prudent idea, and not so strange, especially when posting to such a large list. I don't have much of a problem myself as the addresses I've used are protected by a security firewall, so external hosts can't reach those subnets of 147.225 anyway. Since your address is in fact exposed to the outside world, it's not unreasonable to avoid publishing it in such a wide forum. > I tried this briefly last night, but apparently it's a whole other > lesson to get this damned thing to work. I don't really understand > *who* these manuals are written for..... You'd be surprised - the IBM stuff really isn't all that bad when you see what else is out there. Of course, routing daemons are in fact another whole world of information, of which ROUTED is one of the simplest daemons. I could start another whole book on handling routing daemon issues, but since it's unlikely your entire LAN will start listening to RIP broadcasts, I think I'd just bypass this option for now. Even if you do run ROUTED and config everything right, it only fixes things for people who are also listening for the information that you are then broadcasting. > As per my comments earlier, is this something we can do once and will > then work for a number of people? ie if we pick subnet 41 for slip, > then programmers using slip will be > > 134.68.41.1 > .2 > .3 etc? It depends on how you are servicing the SLIP connections. As long as there is a single host that is responsible for all of the SLIP users, then yes - this will work fine. For example, here at ANS, we use subnet 2 for SLIP - all SLIP users get 147.225.2.x addresses. Our primary machines have a static route for 147.225.2.0 into our Annex terminal server (that handles the SLIP users) at 147.225.10.40. If however, each user is going to handle his or her own SLIP connection into an office machine, it gets a little tricker. Given that changing a centrally administered host is probably harder, what I would suggest is telling those responsible for the site router to send all SLIP (134.68.41.x) traffic to one particular host - pick someone's office machine, or some central machine that you manage. Then, as individual programmers set up SLIP links to a new machine, add a static route to the machine you manage for that SLIP link. Then, traffic from LAN or external hosts heading for SLIP home users will first go to the central machine you manage, which will then forward it on to the appropriate office machine handling the link. This will represent an additional hop, but for the amount of traffic generated by SLIP it won't be much. Also depending on the central machine of yours, it can send a redirect message to the site router, telling it the real machine to send the SLIP traffic to. So it can "learn" to avoid the extra hop. I'm pretty sure that OS/2 (and most Unix platforms) send a redirect by default, but don't hold me to that. > Ah, here's where it gets fun, this would be a good hack...... > I'll try this and let you know. By the way, I keep hearing about your > super nifty alternate slip drivers, should I try those? Dave are you > holdin' out on me? :) One guy said I could find them at ftp.ans.net Well, yes, I do have "super nifty alternate slip drivers" :-) I wasn't really holding out on you - getting my drivers wouldn't have solved your problem as it was routing and addressing related. Also, my driver is technically alpha code so I don't generally recommend it to just anyone yet. Of course, it's alpha mostly because I'm too backlogged to do the final cleanup and call it beta, so it's actually quite stable at this point. If you're interested - you can anonymously ftp the driver from ftp.ans.net in the file /pub/misc/slip20a3.zoo. This has the driver, several utilities, and a readme that should get you up and running. My driver both performs better than the standard IBM driver (better performance while using less CPU) as well as including support for header compression and priority queueing. This yields better interactive performance over a SLIP link. The driver does require OS/2 2.0, and TCP/IP 1.2.1 at least at CSD level 2252. (You can always get the latest CSD from ftp-os2 if you have an earlier version of TCP/IP - check SYSLEVEL) The below is today's first installment from a gent attempting to help me put the final piece in place.... ROUTED From jardined@qucis.queensu.ca Wed Feb 17 13:12:00 1993 To: dabl2@nlm.nih.gov Subject: Re: TCP/IP, SLIP, Beat 2.1 Setup Questions (LONG) I was going to suggest Bolen's stuff. He is _most_ knowledgeable. The secret appears to be as follows: The ifconfig statement _must_ have your home ip address and the office (slip) machine ip address. Use a netmask of 255.255.255.0 make sure you set the mtu in ifconfig (and in slip.cfg if you use Bolen's driver). Now: in order to get at any other machine on your office net, you must tell your home machine where on the office LAN is the nameserver. You use the OS2 ROUTE command to do this. What you do in it is to a) clear the previous entiries (-fh flag), then b) set up as 'default' the ip address of the name server on your office LAN This means that when at the OS2 end you mention a machine on your office lan athat is other than the machine to which you are directly connected via slip, the request will be routed by your office PC to that name server, which will do the address resolution. The test for connection is to use the 'ping' command at your home end. If you default route to the nameserver, you should be able to ping any machine on the internet. I tested it by pinging local machines here, and then finally hobbes. It replied! I'm at the office so I don;t have access to my rexx scripts. If you are still having problemsa, I'll send them to you. I agree the manuals are ghastly. Luckily I have a bunch of Unix TCPIP experts here to help me, (we have 4 dept. lans with about 100 Sun workstations, 4 file servers, 3 compute servers etc. etc. here) but even they took a while to figure it out. I asked, but there is no good book on TCPIP or X11. You learn it by recursively reading assorted ill-written documents, and asking someone who knows. I've been around long enough to have used IBM manuals back in the '50s and '60s, so I'm resigned to this situation :-) Prof. Donald Jardine Software Technology Laboratory Comp. Sci. Dept. Queen's Univ. Kingston Ont. Ph (613) 545 6070 Fax (613) 545 6513 (A3.) Appendix III: Setting up LaMail ===================================== This is a product that I don't use, but rwalker@rwalker.doa.lastat.gov kindly sent me a document that he prepared for his users there. I've excerpted and edited from that. Hence I am definitely to blame for errors of omission and comission in the following suggestions... 1. Installation: You will want to check off "Sendmail" and "LaMail" in the ICAT "Automatic Starting of Services" setup section (see (5) section 4. above). 2. Customize your LaMail configuration: In the LaMail screen, select Options/Set Note Options, then: Personal Options 1. Your login or userid (e.g. dean) 2. Your hostname (e.g. fiddler.biol.scarolina.edu) Note Header 1. Check "Add Subject Line" 2. Recommend checking "Long Address Format" Note Options 1. Signature file: You can create a plain-text file that contains some address information about yourself. It will be automatically appended to your outgoing mail. For an example, see the three lines at the end of section (0) of this document (that's my .signature file contents). At this point, enter the name of the plain-text file that holds your signature information. 3. Send some test mail: Send some mail to someone who's email address you are sure will work. Ask them to send you a reply. It may be helpful if you are in adjoining offices so you can ask each other if it worked... 4. Delivery notification: There's no such thing as registered mail with SMTP (the mail services that Internet mail uses). But sometimes if mail cannot be sent to the recipient, LaMail will pop-up with the rejected mail item. 5. Note editor: The LaMail editor is built upon the OS/2 Enhanced Editor (EPM). Most users would be more familiar with the OS/2 System Editor. To configure the LaMail editor to resemble the System Editor more closely do the following while editing a note: Select: Options/Preferences: Deselect: Advanced Marking Select: Stream Editing Select: Options/Save 6. How to forward a note: While you are reading/editing a note (i.e. the box title begins "Note") hit Ctrl-I. In the command dialog box, either click on an existing command in the top half (if there are any shown) or type a forward command in the lower half (e.g. FORWARD dean2@tbone.biol.scarolina.edu). Edit the command in the bottom half and then select OK. This will bring up a standard LaMail Create Note menu with the forwarded note included. Edit the subject and other header lines as usual and select Send to actually forward the mail. LaMail will keep a copy of the command in its history file for the next time you select the command option. 7. Spelling check: To check the spelling of an outgoing note, select the Options/Proof menu item. Note that the spelling checker appears to have some bugs. Sometimes it gets confused and flags even common words (e.g. "is"). At other times, it appears to just hang. You may want to verify the location of the following LaMail files by choosing the Options/Preferences/Settings/Paths menu: US dictionary (normally \tcpip\bin\us.dct) Personal dictionary 8. Folders: At installation, the ALL folder is the default folder for notes. A copy of your outgoing mail is automatically stored in the default folder. You can create multiple folders (e.g., and OUT folder or organize folders by subject). You can also associate folders with individuals in your NICKNAME.NAM file. Within each folder, the appearance of mail items can be customized (color and order of fields, etc.). Each folder can have a distinct icon associated with it. Create the icons using the OS/2 icon editor and save them in \tcpip\lamail as xxxxxx.ICO where xxxxxx is the name of the folder that you want associated with the icon. 9. Sendmail: Sendmail is the background process to LaMail that actually sends and receives SMTP messages. This normally should be running all the time, although it can (and probably should) be minimized on the screen. In general, there is nothing you can do in this session. If you need to shut sendmail down, you can terminate it by switching to that session and hitting Ctrl-C. This will bring you back to the OS/2 command prompt where you can type EXIT to close the session. 10. Join some mailing lists: The Internet has hundreds of mailing lists on every conceivable topic. Good ones include ietf-announce (for Internet Task Force announcements), the OS/2 mailing lists, new-list (a mailing list that announces new mailing lists!), and many other computer and non-computer-specific lists. The Internet master list of mailing lists can be retrieved via anonymous FTP from ftp.nisc.sri.com as netinfo/interest-groups. Because this is such a large file (over one million bytes uncompressed), it should be retrieved only on an exception basis. Do NOT print the mailing list index. 11. Be sure to include your Internet mailing address on your correspondence and business cards. Because many recipients may not be entirely familiar with internetwork addressing, and may have accounts on alternate services (MCI, Genie, etc.), make sure to be explicit. Tell them that it is an Internet address and be sure to give your entire address. For example, I'd give the following information: Internet: dean2@tbone.biol.scarolina.edu ÿ Software Showcase: ================= Performance 2.1 Review By H. E. Summers Performance 2.1 is a collection of REXX programs that modify your config.sys per IBM's tuning suggestions to help improve performance. While Performance 2.1 seems like a bargain at $29, many of the utilities are simply not very useful unless you are VERY novice. Some of them are downright dangerous, like the program to remove all HPFS programs! While the utilities are marginally useful and the book lays out the performance information more clearly than the manuals from IBM, I would not recommend buying Performance 2.1 even for those wanting to learn Rexx. Extended Desktop 1.4 Review By Dale Hackemeyer Extended Desktop is an IBM Employee Written program that greatly enhances control of the desktop in OS/2 2.x (you MUST have the Service Pack installed if you're running on 2.0). Extended Desktop is a WPS Class DLL for the "ExtendedDesktop" object class, which is a subclass of the "WPDesktop" object class. Its purpose is to extend the functions of the OS/2 2.x Desktop object. Extended Desktop extends the OS/2 2.x WPS Desktop to: 1. Optionally remove Arrange & Sort from the Desktop context menu. 2. Align groups of icons on the Desktop vertically or horizontally. 3. Snap-to-Grid with user defined Grid Spacing. 4. Precisely position individual icons on the Desktop from the Settings Notebook 5. Precisely position individual icons on the Desktop from C or REXX. To install you simply run the install program and reboot. All your desktop settings and icon arrangements are unchanged. Only when you bring up the desktop Settings notebook do you see the additions. Should Extended Desktop not meet your needs, there is a un-install program included. I think this program is a must for any serious user of the Workplace Shell, especially if you're like me and like to arrange groups of icons in different places all over the desktop. You can find Extended Desktop 1.4 in the file EXDESK.ZIP on the OS/2 Woodmeister BBS (314) 446-0016. Watchdog Review By H. E. Summers Do you have a hangup using OS/2? That is, does the mouse still work but nothing happen when you click? If so, try adding WATCHDOG to your system. It can detect the WPS locking up (while OS/2 is still working) and reboot the WPS without rebooting OS/2. This IBM employee written software (EWS) is useful even under the much improved OS/2 2.1 if you are running on an ISA PC where WPS has problems. Watchdog is avalible from Woody's BBS as WDOG10.ZIP. OS/2 Tips & Techniques ====================== WPS Tricks ---------- Here's a neat trick which has been thoroughly discussed on Compuserve, but I don't see mentioned here. Call up the window list, hold down the shift key, double click on the Desktop item, and your desktop will minimize itself! Apps will continue, and Ctrl-Esq will recall the Window List, allowing you to bring up any open windows and work with them as usual. Sometimes it's nice to hide all those objects and focus on what you're doing. Next, on the Desktop item on the Window List, hold down Ctrl, and double click the right button. Now the desktop's title bar appears, and you can move it around! Two ways to remove the title bar: (1) Reboot; (2) open the minimized window viewer, minimize the desktop, recall the viewer, Arrange if you don't see the desktop icon, RMB the icon for its menu, select Restore. William Marvin, Fidonet OS/2 conference. ÿ Toolbox in SAS for OS/2 ----------------------- If you want to change the default icons available in the default toolbox, use the Toolbox Editor. To bring up the Toolbox Editor, select EDIT TOOLBOX from the OPTIONS in the menu bar. Alternatively you can issue the TOOLEDIT display manager command. To add your own icon to the Toolbox, folow these steps: Create an icon. What I did was download a zip file with tons of icons from ftp anonymous at ftp-os2.cdrom.com and edited one with the OS/2 Icon Editor. Mark and copy your new icon to the clipboard. Open the Toolbox Editor and select the icon that you want to replace by clicking on it. Choose PASTE to move your icon from the clipboard into the Toolbox Editor. Enter the text string you want to associate with the tool (e.g. Insight). Save your changes, you can save temporarely using the APPLY button or permanently using the SAVE button. Enjoy, Arturo Barrios / OIT User Services New Products! ============= OS/2 Software recently announced or released: Back In A Flash! ---------------- From the Fidonet OS2 conference: From: Robert Montgomery Back In A Flash! (aka BIAF) 32-bit File Backup and Archival Utility Demonstration Version 1.00 A product of CCT, Inc. 111 3rd Avenue South Minneapolis, MN 55401 (612) 339-5870 Some more to report. I have purchased the registered version. I have talked with the author, Brad Benson. Very nice, knowledgeable OS/2 programmer that works for a big company called CCT, does programming for them. Did BIAF on his own time and when he brought it to work to run on his IBM MCA, his boss (a very wise Paul Druckman, President, of CAD/CAM Technology, Inc.) suggested they market it. And the rest as they say is history. I have run it on three machines, all clones with OS/2 2.1, and MFM, ESDI and a SCSI. The backup to the floppy works perfectly for backing up the desktop configuration to one diskette and doing a command line restore. Superb and clearly worth the price of the product. The desktop can be very personal and unique with OS/2 and rebuilding it a pain. With BIAF, no problem. Only major problem has been backing up to more than one floppy and doing a command line restore. Has some sort of bug that causes it too fail. But inside OS/2 2.1, running the restore with the GUI part, works wonderfully. Brad knows about this as of last week and will look into it. This is not a major flaw, but it is annoying. Ah, to save the best for last. BIAF can save to another partition, or to any directory on a hard drive or across a LAN (the LAN was not tested by me, since I have no LAN). 38MB can compress to about a 25MB file. Very fast, varies with hard drive speed and cpu, but best was 7MB/min to about 3MB/min with compression on. Here is what the dir/w of the saved files looks like at the dos prompt C:\OS2BACK>dir/w The volume label in drive C is CJODY. The Volume Serial Number is 3F49:1BD0 Directory of C:\OS2BACK [.] [..] DESKTOP.001 FULL.001 4 file(s) 25069336 bytes used 228212736 bytes free Note that two files exist, one called desktop.001 and the other full.001. Desktop.001 is just the critical files that can restore the desktop. And full.001 is a complete OS/2 restore. If these files are kept "safe", in my case, stored on C:\os2back directory with OS/2 on my d: drive, as simple reformat of D: and the insert the disk install and disk 1 of os/2, esc to command line, run cctrest desktop.001 c:\os2back or run cctrest full.001c:\os2back, and in a matter of minutes, D; is restored form c:. Simply amazing to watch, and it ran flawlessly on all three very different machines. This has countless variations. Imagine saving this backup file, either desktop.001 or full.001 or whatever you might configure (and BIAF will let you do anything) and the using a DOS, fat based backup to tape of these files. In the event of a disaster, just reformat, set up the original drive specifications, restore the desktop.001 or full.001 to the right area on C: (which is C:\os2back in my case, it could be any you want, boot the two os/2 diskettes, the install and disk one, run cctrest.exe as above, and voila! Complete restore! I have done it, works beautifully! So now, here is the new suggestion, for the beginner, who needs a generic hardware setup that will work on many machines and be "portable". Get a SCSI based cdrom that works with OS/2 2.X and the trantor SCSI Plus cable, then install OS/2 2.1. Make a backup with BIAF, and then get one of those nice parallel port backup machines like trakker, connect it to the parallel port direct or to the Trantor parallel port and backup the BIAF files to tape. In the even of a "crash", no problem. Just use the cdrom to reinstall the OS/2 2.1 from CDROM, and redo the customized desktop saved in desktop.001, or just restore the full OS/2 from the full.001 file restore by the tape machine hooked to the parallel port, then run BIAF command line restore (cctrest.exe) and restore the entire OS/2 2.1 operating system. The variations are endless, limited only by ones imagination. MY OS/2 installs are pretty standardized now, since use boot manager, with a C"FAT and D:HPFS. I run C: drive as FAT, allows use of "real" DOS, with all the versatility I need, then install OS/2 2.1 on D:HPFS, enjoying OS/2 on HPFS (a real treat). I save my BIAF backup files on the cdrive in a directory called, appropriately, C:\os2back. Then I can reinstall anytime I want back to D:HPFS and leave my C:DRIVE alone, safe and secure. The reverse is true as well, save my C:DRIVE on a C:\DOSBACK or D:\DOSBACK and use BIAF to restore the entire DOS back to my C:FAT drive. So there you have it, one of many solutions for the OS/2 user that allows the use of there present hardware. And it allows the "neophyte" OS/2 user to graduate into OS/2 without the "fear" of no backup and avoid the expense of upgrading all their equipment just to run OS/2 2.1. The new user (or old) can keep their old Colorado, or other FAT backup system, knowing that with BIAF, they can backup the BIAF backup files with ease. So let me know what you think. And finally, lets support this excellent product. Highly recommended. Price? $29.00 intro $49.00 final. Worth it! BakupWiz -------- PCX Announces the Release of OS/2 BakupWiz San Diego, CA, August 4, 1993 PCX announced today that OS/2 BakupWiz will be released for general sale on August 16, 1993. OS/2 BakupWiz is a comprehensive Backup/Restore program that takes full advantage of OS/2's many advanced features. Typical OS/2 configurations include a large amount of fixed disk storage which requires a backup system capable of effectively backing up large amounts of data. OS/2 BakupWiz's backup capacity is only limited by the current state of the art in backup devices. A long list of SCSI tape devices is supported by OS/2 BakupWiz. These range from 150 megabyte 1/4" cartridge devices to multi gigabyte 4 and 8 millimeter devices to automated tape loading devices with capacities in excess of 100 gigabytes. OS/2 BakupWiz will work with all SCSI adapter cards that are supported by OS/2. Being a character mode OS/2 program, OS/2 BakupWiz is capable of fully restoring the users OS/2 boot partition, thus saving the time that would normally be required to manually reinstall the operating system from diskette or CDROM. OS/2 BakupWiz also supports OS/2's extended attributes, long file names, and the High Performance File System. While OS/2 BakupWiz is PCX's first entry into the ever growing OS/2 marketplace, BakupWiz has a long history in the DOS market. BakupWiz for DOS, marketed directly by PCX, is also resold and bundled under private label by various SCSI board manufacturers. The software ships on 3.5 inch diskettes. Retail price is $189.00. PCX is offering an introductory price of $129.00 until September 30, 1993. Due to customer demand, PCX has started accepting orders for OS/2 BakupWiz for shipment beginning August 16, 1993. PCX, founded in 1982, develops and markets personal computer software and is firmly committed to the OS/2 platform. In addition to OS/2 BakupWiz, PCX also markets BakupWiz for DOS and performs consulting services under contract. PCX specializes in the development of device drivers and utilities for OS/2, DOS, and Netware. For more information, contact PCX at 3525 Del Mar Heights Road, Suite 313, San Diego, CA 92130, phone: 619-259-9797, fax: 619-481-6474. 2nd Edition of OS/2 2.1 Unleashed --------------------------------- Second edition of OS/2 2.1 Unleashed Announced NORRISTOWN, PA, June 1, 1993 Productivity Solutions Book Division announced today availability of the second printing of OS/2 2.1 Unleashed. The first printing sold out in just 6 weeks placing this book among the fastest selling and most popular of available OS/2 books. In the forword to the second printing James Cannavino, IBM Senior Vice-President and General Manager Personal Systems said, "the authors span our industry and possess years of experience with the OS/2 operating system. Several of the authors are members of the original OS/2 design and development team, bringing an unequaled level of OS/2 knowledge to a single book." The book was also praised by Lee Reiswig, President of IBM Personal Software Products Division, during official launch announcements of the OS/2 2.1 operating system on May 18. David Moskowitz, President of Norristown, PA firm, Productivity Solutions, with David Kerr of IBM are the featured authors, with 11 additional contributing authors including Rick McGuire head of the IBM REXX Language Development Group and Mike Perks, Advisory Programmer for OS/2 Technical Planning. Scott Kliger of the OS/2 development team at Word Perfect Corporation was the primary technical editor of the book. Kliger was previously a member of the IBM OS/2 Development Team in Boca Raton, Florida. What readers around the world say First published at the end of February, 1993, thousands of OS/2 users heard about OS/2 2.1 Unleashed from discussions in on-line services such as CompuServer, Internet, Fido Net as well as at OS/2 User Group meetings and technical conferences around the world. According to David Cittadini, Senior Consultant of Price Waterhouse of Wellington, New Zealand, "The three most important ideas I picked up from this book were about using and controlling the Workplace Shell, tuning the system and video subsystems. These ideas are missing in lots of other books." Andy Yu, Senior Technical Analyst of the BC Systems Corporation of Victoria, B.C. Canada, "I enjoyed reading the book very much. It's an excellent reference book on OS/2 for both advanced and beginner users. If I had this book on Day 1, it would have saved me **lots** of time!" Software developer president, Lee W. Wiley of International Expert Systems of Houston, Texas, "Your book is great! Your explanation of system configuration, setup and tuning answered questions which we have been wondering about for over a year. This alone is well worth the price of OS/2 2.1 Unleashed." According to David Kerr, "in writing my sections I set out to document information not properly described in any other book. All of the other authors did the same thing." This attention to detail paid off. One reader, Steve Gallagher, IBM Team OS/2 member in North Carolina says, "I have read probably a dozen books on OS/2, but OS/2 2.1 Unleashed is the only one that 'made the cut' and sits next to my computer at work." Paul Duncanson, President of the Los Angeles OS/2 Users group says, "I've been programming OS/2 for over 5 years, and am amazed at the amount of new information for me in this book!" Best Source for Tips and Tricks The book is 1134 pages in 18 chapters and includes a disk of 8 of the best shareware utilities for OS/2. There are many techniques and tricks about OS/2 2.0 and 2.1 which are not documented, or inadequately documented anywhere else. Readers can troubleshoot their Windows 3.1 and DOS Applications as well as discover ways to prevent problems. According to David Moskowitz, "we included tips and tricks that are useful to almost everyone who uses or supports OS/2 from beginner to power-user. Even the person who only uses OS/2 2.1 to multitask DOS and Windows applications will find usable information in the book. All the contributors wanted to make this _the_ OS/2 2.1 reference book." Pricing and Availability Price is $34.95, plus shipping and handling. Telephone or fax orders for the book can be placed by calling Productivity Solutions: 215-631-5685 or fax: 215-631-0414. All books ordered from Productivity Solutions are signed by featured author David Moskowitz. The publisher is SAMS Publishing, ISBN No. 0672-30240-3. OS/2 Computing Magazine ----------------------- MILLER FREEMAN LAUNCHES OS/2 COMPUTING SAN FRANCISCO Miller Freeman, Inc. today announced the launch of OS/2 COMPUTING MAGAZINE out of its San Francisco headquarters. OS/2 COMPUTING is focused on users and system administrators who work with IBM's OS/2 operating system on a daily basis. "OS/2 COMPUTING represents another step in developing a well-rounded group of top-notch computer and electronics magazines here at Miller Freeman," said Don Pazour, Vice-President of Miller Freeman's High-Tech Division. Ted Bahr, Group Publisher of the company's Electronics/Design Group, was named Publisher of OS/2 COMPUTING, and added, "No major publishing company is currently serving those individuals and corporate users and systems administrators who have chosen OS/2 as their operating system. OS/2 users are hardcore enthusiasts and OS/2 COMPUTING will be serving a definite need in this growing market." The first issue of OS/2 COMPUTING will hit newsstands in mid-November 1993, and will be distributed at Fall Comdex in Las Vegas. Monthly publication begins with the February 1994 issue. OS/2 COMPUTING will be distributed through paid subscriptions and on newsstands. "We believe paid circulation is important in satisfying advertisers' needs to reach a qualified audience," Bahr explained. OS/2 COMPUTING will be audited as soon as possible. Effective immediately, Miller Freeman has appointed Alan Zeichick as Editor-in-Chief of OS/2 COMPUTING. "OS/2 is the most popular 32-bit operating system for IBM-compatible personal computers," Zeichick said. "Members of the OS/2 user community, whether individuals, small businesses, or large corporations, are looking for a dedicated source of information about how to maximize their productivity." Miller Freeman's High-Tech Division also publishes Dr. Dobb's Journal, OS/2 Developer, Cadence Magazine, UNIX Review, LAN Magazine, Software Development, Embedded Systems Programming, Database Programming & Design, Microsoft Systems Journal, and AI Expert. It is also the sponsor of high-technology conferences, including Autodesk University, Software Development Week, Embedded Systems Conference, Computer Security Conference, Electronic Imaging, and Business Software Solutions (formerly the Windows & OS/2 Conference). A wholly owned subsidiary of United Newspapers plc, Miller Freeman, Inc. publishes 32 other magazines and is the third largest producer of trade shows and technical conferences in North America. CONTACT: TED BAHR, 415-905-2269. ALAN ZEICHICK, 415-905-2382, CompuServe 76703,756 Miller Freeman Inc., 600 Harrison St., San Francisco, CA 94107 REXX Handbook ------------- REXX Reference Summary Handbook Announcement Good News: The REXX Reference Summary Handbook is available for shipping. We are accepting orders beginning on Tuesday, August 10, 1993. Bad News: Our friendly bank has informed us that since C F S Nevada, Inc. is accepting orders for the Handbook via electronic mail, we qualify as a mail order business and, as such, they have made the requirements for us to provide Master Card / Visa services, prohibitive. Therefore, we are forced to require a check (personal or business) or money order. Checks MUST be in U.S. funds drawn on a U.S. bank or the order will be returned, unprocessed. This 112 page, pocket sized guide details all of the instructions and functions in SAA REXX distributed with OS/2. It also describes all of the functions included in the REXXLIB and RXWINDOW external function packages available from Quercus Systems - the Personal REXX developer. I think that anyone involved with REXX, from curious beginners to people who, like me, first began using REXX (or EXEC2) under VM/370 or VM/SP on IBM mainframes, will find the Handbook to be a constant "keyboard-side" companion. I realized the need for the handbook when, even after writing REXX programs for close to ten years, I found myself still reverting to the REXX manuals for confirmation of things such as the order or format of function parameters, the format of the value returned by a function, etc. The handbook has a 20 page, cross referenced index, that will allow the novice REXX user and the REXX veteran alike to easily locate a needed function as well as identifying the various functions which deal with a particular subject. The Handbook has been accredited by IBM for use of the official OS/2 logo and C F S Nevada, Inc. is a member of the IBM Independent Vendor league. The price is $9.35 plus $2.00 per copy shipping & handling. Nevada residents must add 7% ($0.65) sales tax. Quantity discounts are available for dealers as well as a special program for user groups being available. Checks should be made payable to C F S Nevada, Inc. and mailed to: 953 E. Sahara Avenue, Suite 9B Las Vegas, Nevada 89104-3012 Inquiries may be directed to C F S Nevada, Inc. at: 702-732-9616 voice 702-732-3847 FAX 72200,347 CompuServe (1:209/705) FIDO Please note your CompuServe ID, Internet address or FAX number on your order. Orders will be processed in the sequence they are received and the Handbook will be shipped within 10 business days of the receipt of your order. S3 Video Drivers ---------------- S3 Video Driver Announced for OS/2 2.1 August 11, 1993 The S3 video device driver support is now available for OS/2* 2.1! This means that OS/2 users now have access to even better graphics, faster video and higher resolution in a proven and reliable operating environment. "The S3 video driver is designed to provide OS/2 users with seamless support for accelerated video graphics and advanced color resolution," says Wally Casey, director of marketing for PSP. "The new driver ensures compatibility with the S3 technology shipping in today's newer PCs." The OS/2 2.1 S3 video driver supports the following resolutions and colors: 640 x 480 x 256 colors 800 x 600 x 256 colors 1024 x 768 x 256 colors 1280 x 1024 x 256 colors PC manufacturers, such as the IBM PC Company and Dell Computer Corporation, will begin shipping the OS/2 2.1 S3 driver with their systems. The S3 driver has also been tested on and is compatible with many industry leading S3 adapter cards. The S3 driver is available from multiple electronic download services, including Internet and CompuServe, or can be ordered on diskette for $15 (cost + shipping and handling) by calling 1-800-3IBM-OS2. It is located on software.watson.ibm.com on the Internet, and in OS2SUPPORT, Library 17, IBM files on CompuServe. The file name is S3-256.DSK. 15 Questions & Answers About the S3 Driver 1. Does the S3 driver exploit the accelerated functions of the S3 Corporation's chipsets? This display driver takes advantage of the hardware acceleration capabilities of S3 Corporation's 86C801/86C805 and 86C928 chip sets. It conforms to the OS/2 32-bit flat memory model and is designed to function as a 32-bit Presentation Manager (PM) display driver under the OS/2 32-bit graphics engine subsystem. 2. Which resolutions are supported? The S3 display driver supports the following resolutions/colors and OS/2 full-screen columns/rows: 640 x 480 x 256 colors 800 x 600 x 256 colors 1024 x 768 x 256 colors 1280 x 1024 x 256 colors (min 2MB video memory) OS/2 full screen 132,25 OS/2 full screen 132,43 3. What other features does it support? OS/2 PM Palette Manager Software Motion Video Static mode change. 4. When will it be available? It will be available August 9, 1993, via electronic download. It will be available on diskette via the 1-800-3IBM-OS2 number approximately two weeks later. PC manufacturers, such as the IBM PC Company and Dell Computer Corporation, will begin shipping the OS/2 2.1 S3 driver with their systems. In addition, IBM will add this S3 driver to shrink-wrapped packages of OS/2 2.1. 5. Where will it be available? The driver is available via multiple electronic download services, including CompuServe and Internet, or can be ordered on diskette for $15 (cost + shipping and handling) by calling 1-800-3IBM-OS2. It is located on software.watson.ibm.com on the Internet, and in OS2SUPPORT, Library 17, IBM files. The file name is S3-256.DSK. 6. Does IBM fully support this driver? Yes. It is covered by the same support plan as the OS/2 2.1 product. The 256-color driver is now available. 7. Does IBM intend to enhance the driver to include additional colors, ie., 65K and 16M (true color)? It is IBM's intent to enhance the current driver to support additional colors. Beta-level code will continue to be made available electronically as additional function is added. 8. Did IBM develop this driver? Personal Systems Programming views our customer requirements for OS/2 drivers supporting the leading video chip sets as a top priority. We invested in developing this driver to satisfy these requirements. 9. This driver is compatible with which versions of OS/2? This driver is compatible with OS/2 2.1, and it is covered by the terms and conditions of the the Program License Agreement for the OS/2 2.1 product. 10. Does this driver support less than 1 MB of video memory? No, a minimum of 1MB of video memory is required. 11. Is this a seamless driver, ie., does it support Windows and OS/2 applications running side by side in windows on the desktop? Yes. 12. Is this a fully 32-bit driver? Yes. 13. Are there any functional restrictions? This display driver may not support ALL S3 adapters or systems with EVERY chip set. The S3 display driver has been tested on and is compatible with the S3 adapters or systems with the chip sets indicated in parentheses. Additional adapters or systems may be added as testing continues in the future. Actix (801) Actix (928) Diamond Stealth 24 (801) Diamond Stealth 24 LB (805) Diamond Stealth Pro (928) Diamond Stealth Pro LB (928) Orchid Fahrenheit 1280 (801) Orchid Fahrenheit 1280 Plus (801) Metheus (928) Video 7 Win.Pro (801) IBM ValuePoint (805) Dell 433/L (805) Dell 433/M (805) Dell 466/L (805) 14. How do I install it? With an easy-to-use command file. Instructions are in the accompanying README file. 15. Is this the same driver that is available from the S3 Corporation? No, this driver is the generally available version of the S3 driver that has been in beta test on IBM bulletin boards. In addition, a 16-bit driver for the S3 chip has been available from the S3 Corporation. * Indicates trademark of the International Business Machines Corporation. OS/2 Bookshelf ============== Books useful to the OS/2 user: PM Programming for COBOL Programmers ------------------------------------ Title: OS/2 Presentation Manager Programming for COBOL Programmers Author: Robert B. Chapman ISBN: 0-89435-439-6 (QED Publishing Group) Price: $39.95 with diskette Pub date: January 1993 Contents: Introduction. Presentation Manager. Create PM environment and a window. Display information in a window. Displaying real information. Menu bar, dialog box, icon, and accelerator table. Multiline entry, listbox, combo box, radio buttons, check boxes. Modeless dialog boxes. Multiple windows. Help processing via IPF. Printing a PM report. Introducing SQL I/O. Dynamic link libraries. Sample programs compile and execute environment. PM subroutine calls (The PM API). PM messages, styles, classes, and codes. Glossary. Index. Thinking Person's Guide to OS/2 2.1 ----------------------------------- Title: Thinking Person's Guide to OS/2 2.1 Author: Maria E. Tyne ISBN: 0-89435-467-1 Price: $24.95 Pub date: June 1993 Contents: Introduction. Using Objects. Windows. On-line information. Desktop pop-up menus. Object pop-up menus. Open-settings for objects. Open-settings for programs. Extended menu selection. OS/2 system folder. Customizing the system. Installation features. Palettes. Using templates. Printer and shredder. Helpful hints. Conclusion. Index. OS/2 2.1 Installation, Configuration, and Use --------------------------------------------- Title: OS/2 2.1 Installation, Configuration, and Use Author: Doug Azzarito ISBN: 0-89435-456-6 Price: $34.95 Pub date: August 1993 Contents: Introduction. OS/2 requirements. Installing OS/2. Introduction to the Workplace Shell. Migrating applications. DOS under OS/2. Windows under OS/2. OS/2 applications. Command-line interfaces. The productivity programs. Advanced features. Glossary. Index. Other Sources ============= Other places to locate OS/2 information. OS/2 BBS's ========== This BBS listing is provided courtesy of David Sichak, Editor of the San Diego Users Group Newsletter. Thanks David! BBS Introduction ---------------- Well, I am trying to update this file in an expedient way so it doesn't become too stale when I include it in the INF version. But I'm trying to catch up on a backlog. I've got the list in an Rbase for OS/2 database file right now, so all I need to do is figure out a way to create a report that does much of my INF coding for me. Next month, I'd look for a few more additions. And by all means keep Dave Fisher posted on your BBS's if he's still keeping his list up and current. Without him, we wouldn't be able to include as much as we do. This listing is for the BBS junkie in you who needs to have a phone bill treat once in a while . Or bored to death while you're travelling. Our listing is based on a rather extensive listing put together by Dave Fisher of OS/2 type Bulletin Boards. Space limits this month prevent us from listing all the details he has for each BBS, but we've tried to include a couple from every state in the US (Notice and hint to you sysops...not all states are represented.) and a few foreign countries, too. Dave Fisher's list is a compilation of OS/2 BBS's across the world. If you wish to make an addition or correction to his list, he's asked that you please netmail your BBS information to Dave Fisher at LiveNet, 1:170/110@fidonet.org. For the newsletter, I've sorted the in alphabetical order by Country for the international ones and by state for those in the USA to make it easier to find one close to you. His file has other details related to these BBS's but we didn't have room, okay? The file we're using showed that the last update was September 7, 1992. Does anyone know if this list of his is being kept up to date? I hope to expand it more next month; ran out of time. But I've got his list in a database right now and I'll be able to code that list a lot easier next month. Hope you find this inclusion useful. Large phone bills are not my fault...!!! Australia --------- Graham Stair 3M Australia +61-2-498-9184 Australia Alan Salmon PC User's Group +61-6-259-1244 Australia Norbert Fuerst The Styrian OS/2 Jumbo +43-316-673237 Australia Bill Bolton Software Tools Mail Exc +61-2-449-2618 Australia Bill Bolton Software Tools Mail Exc +61-2-449-9477 Australia Felix Tsang Programmer's BBS +61-2-875-1296 Australia Alan Salmon PC User's Group +61-6-259-1244 Australia Ian Watson OZ-Share OS/2 BBS +61-7-398-3759 Australia Belgium ------- Bas Heijermans Moving Sound OS/2 BBS +32-3-3850748 Belgium Benoit HUON Os/2 MANiA BELGIUM +32-2-3872021 Belgium Danny Bruggeman Hellfire +32-2-7515203 Belgium Bas Heijermans Moving Sound OS/2 BBS +32-3-3850748 Belgium Canada ------ Kevin Lowey Univ. of Saskatchewan (306) 966-4857 Canada Evan Smith ECS Net (403) 253-5996 Canada Ian Evans Baudeville BBS (416) 283-0114 Canada Herbert Tsui BBS Council (604) 275-6883 Canada Jerry Stevens The Locutory (613) 722-0489 Canada Denmark ------- Rene Carlsen OS/2 Task and FrontDoor H +45-98451070 Denmark Jorgen Ollgaard Josti-BBS +45-47-380120 Denmark Jorgen Ollgaard Josti-BBS +45-47-380524 Denmark France ------ Emmanuel Sandorfi Os/2 MANiA (Help Maximu +33-164-090460 France Germany ------- Ulrich Roeding BOX/2 +49-89-6019677 Germany Peter Kaszanics APOLONIA +49-201-200381 Germany Peter Kaszanics APOLONIA +49-201-200382 Germany Peter Plischka IBM Mailbox +49-201-210744 Germany Peter Kaszanics APOLONIA +49-201-237509 Germany Peter Plischka IBM Mailbox +49-201-295181 Germany Chris Leuder Zaphod BBS +49-228-229147 Germany Chris Leuder Zaphod BBS +49-228-262894 Germany Kalle Braun Terrania City +49-228-317752 Germany Oliver Lass LRZ-System +49-228-331214 Germany Oliver Lass LRZ-System +49-228-334372 Germany Harald Kipp OS/2 Point +49-234-9279222 Germany Karlheinz Kissel The_File_Store +49-6106-22266 Germany Juergen Berger JERRY'S OS/2-BBS +49-6134-26563 Germany Oliver Schwabedissen MoonFlower +49-6145-31602 Germany Richard Clement OS/2 Express +49-6183-74270 Germany Michael Breukel PC Softbox OS/2 +49-6196-27799 Germany Romeo Bernreuther CCWN-BOX +49-7151-68434 Germany Markus Noller Second Source +49-7191-56267 Germany Juergen Fritz CheckPoint OS/2 +49-7331-69116 Germany Thomas Tegel The CAT +49-7971-72446 Germany Italy ----- Luigi Ravina Italy Network +39-11-8180069 Italy Roberto Sonzogni Runnin' with The Devil +39-363-302798 Italy Pasquale Cantiello FastForward BBS +39-823-812099 Italy Netherlands ----------- Peter Smink BBS The Experiment +31-1150-15245 Netherlands Dave Jones The TJD Support BBS +31-1720-38558 Netherlands Joop Mellaart INFOBOARD +31-4752-6200 Netherlands Marcel Stikkelman PC-Square +31-79-424107 Netherlands Norway ------ Terje Slydahl PerlePorten +47-83-33003 Norway Singapore --------- Ivan Leong Miqas/2 Singapore +65-755-6463 Singapore Switzerland ----------- Alex Wyss Gepard's Oracle Zuerich +41-1-3637037 Switzerland Michael Buenter MICS OS/2 Paradise +41-41-538607 Switzerland Ernesto Hagmann PC-Info +41-61-9412204 Switzerland United Kingdom -------------- Mike Gove MonuSci BBS +44-0-454-633197 United Kingdom Phil Tuck The TJD Support BBS +44-535-665345 United Kingdom Arizona ------- Mike Mahoney Emerald Isle, The (602) 749-8638 Arizona Frank Ward Encounter, The (602) 892-1853 Arizona California ---------- Patrick O'Riva AsmLang and OS/2 (408) 259-2223 California Michael Cummings Zzyzx Road OS/2 BBS (619) 579-0135 El Cajon, California Craig Swanson OS/2 Connection (619) 558-9475 San Diego, California Chuck Gilmore Magnum BBS (805) 582-9306 California Michael Nelson SeaHunt BBS (415) 431-0227 California Michael Nelson SeaHunt BBS (415) 431-0473 California Colorado -------- William Herrera Cuerna Verde (719) 545-8572 Colorado Randy Edwards Socialism OnLine! (719) 392-7781 Colorado OS/2 BBS Denver (303)755-6859 Colorado OS/2 Source Denver (303)744-0373 Colorado Connecticut ----------- Chris Regan Storm Front - OS/2, The (203) 234-0824 Connecticut Felix Tang Excelsior, The (203) 466-1826 Connecticut Emmitt Dove Fernwood (203) 483-0348 Connecticut Steve Lesner Bullet BBS (203) 322-4135 Connecticut Steve Lesner Bullet BBS (203) 329-2972 Connecticut Rob Schmaling Caladan (203) 622-4740 Connecticut Don Dawson Treasure Island (203) 791-8532 Connecticut Bob Morris Ascii Neighborhood (203) 932-6236 Connecticut Bob Morris Ascii Neighborhood (203) 934-9852 Connecticut Deleware -------- John Tarbox Singer Bear BBS (302) 984-2238 Deleware Scott Street Space Station Alpha (302) 653-1458 Deleware Florida ------- Mark Wheeler SandDollar, The (407) 784-4507 Florida Rusty Plant The 19th Hole (904) 479-8538 Pensacola, Florida Don Bauer OS2 Exchange (904) 739-2445 Florida Chris Wolcott The Outer Limits (904) 934-1141 Gulf Breeze, Florida Kathy Todd The Apothecary's Archives (904) 934-3146 Gulf Breeze, Florida Richard Todd The Disintegrated Circuit OS/2 (904) 934-9796 Gulf Breeze, Florida Georgia ------- IBM IBM National Support Ce (404) 835-6600 Georgia IBM IBM National Support Ce (404) 835-5300 Georgia Ed June Information Overload (404) 471-1549 Georgia Hawaii ------ Craig Oshiro Ghostcomm Image Gallery (808) 456-8510 Hawaii Illinois -------- Bill Cook GREATER CHICAGO Online! (708) 895-4042 Illinois Bogie Bugsalewicz I CAN! BBS (312) 736-7434 Illinois Indiana ------- Mike Phillips Catacombs, The (317) 525-7164 Indiana Jay Tipton Play Board, The (219) 744-4908 Indiana Kansas ------ Troy Majors Byte Bus, The (316) 683-1433 Kansas Louisiana --------- Stan Brohn HelpNet of Baton Rouge (504) 273-3116 Louisiana Jim Sterrett Padded Cell BBS, The (504) 340-7027 Louisiana Maryland -------- James Chance Last Relay, The (410) 793-3829 Maryland Michigan -------- Dave Shoff Cornerstone BBS, The (616) 465-4611 Michigan Minnesota --------- Brady Flowers Oberon Software (507) 388-1154 Minnesota Missouri -------- Woody Sturges OS/2 Woodmeister, The (314) 446-0016 Missouri New Jersey ---------- Bob Germer Capital City BBS (609) 386-1989 New Jersey Mike Fuchs Dog's Breakfast, The (908) 506-0472 New Jersey Nevada ------ Kerry Flint Caddis OS/2 BBS (702) 453-6687 Nevada Dennis Conley Communitel OS/2 BBS (702) 399-0486 Nevada New York -------- Mikel Beck Kind Diamond's Realm (516) 736-3403 New York North Carolina -------------- Thomas Bradford Backdoor BBS (919) 799-0923 North Carolina Richard Lee Psychotronic BBS (919) 286-7738 North Carolina Ohio ---- Mark Lehrer Akron Anomoly, The (216) 688-6383 Ohio Oklahoma -------- Bill Schnell Asylum BBS, The (918) 832-1462 Oklahoma Scott Dickason BBS/2 (918) 743-1562 Oklahoma Oregon ------ Bill Taylor Integrated Media Servic (503) 667-2649 Oregon ------ Paul Breedlove Multi-Net (503) 883-8197 Oregon Pennsylvania ------------ Louis F. Ursini Quantum Leap (215) 967-9018 Pennsylvania Ed Barboni System-2 RBBS (215) 631-0685 Pennsylvania South Carolina -------------- Paul Beverly PMSC OnLine Resource (803) 735-6101 South Carolina Tennessee --------- Operand BBS Lonnie Wall (901) 753-3738 Tennessee Edward Owens Looking Glass, The (901) 872-4386 Tennessee Texas ----- Robert McA Live-Wire (214) 307-8119 Texas Doug Palmer Rock BBS, The (512) 654-9792 Texas David Dozier Roach Coach, The (713) 343-0942 Texas Ken Rucker RucK's Place/2 (817) 485-8042 Texas Virginia -------- Pete Norloff OS/2 Shareware (703) 385-4325 Virginia Pete Norloff OS/2 Shareware (703) 385-0931 Virginia Bill Andrus Systems Exchange, The (703) 323-7654 Virginia Joe Salemi Max's Doghouse (703) 548-7849 Virginia Washington ---------- Adolph Weidanz The Gold Pegasus BBS Running Maximus/Binkley using OS/2 Versions (206) 698-8404 Fidonet: 1:350/35 Eznet: 255:1206/101 and 0 Bremerton, Washington LeRoy DeVries Sno-Valley Software Exc (206) 880-6575 Washington Rodney Lorimor Gecko Control (509) 244-0944 Washington Todd Riches Alternate Reality (206) 557-9258 Washington OS/2 User Group Directory ========================= This OS/2 User Group listing is provided courtesy of David Sichak, Editor of the San Diego Users Group Newsletter. Thanks David! User Group Introduction ----------------------- We try to list known OS/2 User Groups whenever we get the information. Of course, we can't be responsible if the information proves to be unreliable -- you, the reader are our best source of this information. And we're learning of more and more OS/2 user groups across the country and even around the world every week. It's been slow, but we have made some contacts and we may be able to exchange information and articles in the future. If you're travelling and have some free time, stop in on one these meetings. If you know of another OS/2 user group, drop us a line and we'll mention them. Remember, we'll list them all in the INF file each time. And thanks! Australia - Glen Waverly ------------------------ Victorian OS/2 Developers SIG Contact: Jon Wright 5 Brighton Street Glen Waverly, Victoria 3150 Australia CompuServe: 100032,776 Ontario - Bailieboro -------------------- Kawartha Computer Club Contact: Cedric Silvester RR #1 Bailieboro, Ontario Canada KOL 1B0 Note: OS/2 SIG is part of the KCC Phone: BBS -- (705) 748-0023 Quebec - Montreal ----------------- Montreal OS/2 Users Group Contact: Gilbert Lefebvre IBM Tower 10214 Peloquin Avenue Montreal, QC H2C 2J8 Canada Meets: 7:00pm, 3rd Wednesday Phone: Voice -- (514) 382-9858 (evenings) Netmail: Programmer's Quest 1:167/110 The Montreal OS/2 Users Group held their first meeting on February 17. Gilbert reported that their first meeting had over 70 persons in attendance. They're real happy to see the interest in OS/2. Please note that this group does not expect to meet during June, July and August. Saskatchewan - Regina --------------------- Regina Saskatchewan OS/2 User Group Contact: Robert Shiplett Cooperators 1920 College Avenue 5W Regina, Saskatchewan S4P 1C4 Canada United Kingdom - Gloucestershire -------------------------------- International OS/2 User Group Contact: Mike Gove Barton House Cirencester Gloucestershire GL7 2EE UK Phone: - +44-285-641175 Phone: - +44-285-640181 (FAX) Phone: - (UK) 0285-641175 Note: - Also home to OS/2 Solution Centre South Africa ------------ OS/2 User Group of South Aftrica P.O. Box 875 Halfway House 1685 South Africa Sweden ------ Swedish OS/2 Users Group The Cruiser BBS, +46-8-704 9438 California - Fresno ------------------- Fresno OS/2 SIG (Fresno PC Users Group) Contact: Sandeleh Francis (209) 229-0473 Contact: Rod Jessen (209) 323-9849 Meetings at: 1425 Shirley Circle Clovis, CA 93611 Meets: 7:30pm, last Monday Phone BBS -- Wild Side BBS (209) 226-3476 Phone BBS -- Clovis Connection (209) 229-3476 They are a part of the Fresno PC Users group which meets the first Monday of the month at the Ramada Inn at Hwy 41 and Shaw Avenue in Fresno at 7:30pm. California - Huntington Beach ----------------------------- Orange Coast IBM PC Users Group OS/2 SIG Contact: Dave Lorenzini 17632 Metzler Lane, Suite 211 Huntington Beach, CA California - Los Angeles ------------------------ Los Angeles OS/2 Users Group Contact: Paul Duncanson 3008 Texas Avenue Simi Valley, CA 93063 Phone: (805) 584-6721 Meets: 3rd Thursday @ 6:30pm IBM 21041 Burbank Boulevard Woodland Hills, CA California - Sacramento ----------------------- Sacramento OS/2 Users Group Contact: Charlie Kotan IBM 400 Capitol Mall Sacramento, CA Meets: First Wednesday @ 7:00pm Phone: - (916) 641-4007 CompuServe - 70110,254 California - San Diego ---------------------- San Diego OS/2 User Group Contact - Craig Swanson P.O. Box 13346 La Jolla, CA 92039-3346 Meets - 7pm on 3rd Thursday Meets at -- IBM @ LaJolla 8845 University Center Lane San Diego, CA 92122 Phone - Voice -- (619) 587-5955 Phone - BBS -- (619) 558-9475 The San Diego OS/2 User Group has participated in the San Diego Computer Fair in which over 18,000 people attended over a three day weekend last September. This group has started an OS/2 newsletter with the goal of providing information to not only OS/2 users but also to others who are interested in learning more. Our aim is to also develop the newsletter so that it becomes a community effort among the OS/2 user groups and SIGs. Past meeting topics have included presentations by IBM's Ultimedia for OS/2; Lotus demonstrating beta versions of 1-2-3 and Freelance Graphics for OS/2; an introduction to REXX, demo of the December OS/2 2.1 beta along with Visual REXX; Eddie Miller, one of the authors of "OS/2 2.1 Unleashed" sharing insights into the OS/2 mini-applets; and, local OS/2 developer Jeannine Wolf discussing the OS/2 Config.SYS file and providing tips. California - San Francisco -------------------------- Bay Area OS/2 User Group Contact - Guy Scharf Software Architects, Inc. 2163 Jardin Drive Mountain View, CA 94040 Meets - 4th Monday @ at IBM Mountain View Phone - Voice -- (415) 948-9186 Connecticut - Enfield --------------------- New England OS/2 User Group Contact: Dave Pinard 145 Candlewood Drive Enfield, CT 06082 Phone: Voice -- (203) 954-1872 Phone: BBS -- (203) 763-1674 Connecticut - Darien -------------------- Darien OS/2 Users Group Contact: Steven J. Palmer 75 Rings End Road Darien, CT 06820 Delaware - Wilmington --------------------- Delaware Valley OS/2 Users Group Contact: Chuck Gaglia 1120 Webster Drive Wilmington, DE 19803 Florida - Boca Raton -------------------- OS/2 Users Group of Boca Raton Contact: Doug Azzarito Meets at: PC Systems Store 2855 S. Congress Avenue Delray Beach, FL Meets on 2nd Thursday of the month at 7pm Phone: BBS -- (407) 997-2235 Phone: Voice -- (407) 276-2945 Florida - Tampa Bay ------------------- Tampa Bay OS/2 User Group Contact: Paul Wylie M. Bryce & Associates, Inc. 777 Alderman Road Palm Harbor, FL 34683 Phone: Voice - (813) 786-4567 Phone: FAX -- (813) 786-4765 Meets: - 1st Tuesday @ 3:00pm. Meets at: IBM 3109 W. Martin Luther King, Jr. Boulevard 4th Floor Tampa, FL Illinois - Chicago ------------------ North Suburban Chicago OS/2 User Group Contact - James R. Schmidt Meets - William M. Mercer, Inc. 1417 Lake Cook Rd. Deerfield, IL 60015 Meets - 5.30pm Tues preceding 3rd Thurs. Phone - Voice -- (708) 317-7485 Indiana - Fort Wayne -------------------- Fort Wayne OS/2 User Group Contact - Stephen Gutknecht Fort Wayne, Indiana Meets - Central Soya on Cook Rd. Meets - 7pm, 2nd Tuesday Phone - Voice -- (219) 484-0062 (Bus. Hrs.) Phone - BBS -- (219) 471-3918 Indiana - Indianapolis ---------------------- Indy OS/2 Users Group Contact: Jay Schultz 350 E. New york Suite 300 Indianapolis, IN 46204 Phone: Voice - (317) 634-8080 Louisiana - Baton Rouge ----------------------- Baton Rouge OS/2 users Group Contact: David Arbour 16726 Bristoe Avnue Baton Rouge, LA 70816 Phone: - (504) 753-9637 Massachusetts - Boston ---------------------- Boston Area OS/2 User's Group (BCS) Contact: Marcia Gulesian (508) 369-3918 Meetings at: IBM Boston Computer Center One Copley Place Boston, MA Meets: 7:00pm, first Tuesday Meeting location is near Back Bay and Copley train stations. From the Mass. Turnpike East, exit 22 (Copley Square Lane) - first left onto Dartmouth St. Next left onto Huntington Ave. Enter COPLEY PLACE PARKING on left. Parking is free when you spend $5 and have your parking ticket validated in any restaurant or store at Copley Place and enter the garage after 5:00pm. Michigan - Grand Rapids ----------------------- West Michigan OS/2 User Group IBM 2900 Charlevoix Dr. SE Grand Rapids, MI Minnesota - Minneapolis ----------------------- Minnesota OS/2 User Group Contact: Marcus Krumpholz IBM Building 650 Third Avenue South Minneapolis, MN Meets last Thursday each month 7:00pm - 10:00pm Voice: (612) 869-7956 BBS: (612) 379-8272 ISV's wishing to do a presentation can contact Marcus Krumpholz at (612) 869-7956. Registrations for meetings are requested and can be done by calling (612) 397-6444 and then asking for course code "OS2". The IBM building is shared with First Bank on Third Avenue south between South Sixth Street and South Seventh Street. Parking is recommended at Northstar Center (1 block west), Pillsbury Center (1.5 blocks north), Hennepin County Government Center (diagonally across street) and Court Park (2 blocks north). Nebraska - Omaha ---------------- Omaha OS/2 Users Group Contact: Joe Peterson 7724 Fort St. Omaha, NE 68134 New Jersey - West Orange ------------------------ Northern New Jersey OS/2 Users Group Contact: Jason H. Perlow (201) 224-7605 Meetings at: IBM 300 Executive Drive West Orange, NJ Meets: 7:00pm, second Tuesday INFO: Phone: (201) 325-5600 This group is affiliated with the Westchester OS/2 Users Group. New York - Westchester ---------------------- Westchester OS/2 Users Group Contact: Craig Smith (914) 686-9828 Meetings at: IBM 2000 Purchase Street Purchase, NY Meets: 7:00pm, second Tuesday INFO: Phone: (914) 697-6000 Westchester was instrumental in getting IBM's OS/2 featured on the PBS Computer Chronicles show in March. North Carolina - Durham ----------------------- Triangle OS/2 User Group Contact -- Steve Gallagher IBM Building 4800 Falls of The Neuse Road Room 5074 Durham, North Carolina Meets -- 7.30pm, 3rd Tuesday Phone -- Voice -- (919) 254-5637 Internet -- sjgalla@vnet.ibm.com Ohio - Akron ------------ Northeast Ohio OS/2 User Group IBM 3 Cascade Plaza Akron, Ohio Contact: Gary Smiley Phone: (216) 630-3565 CompuServe: 75600,1737 Ohio - Cleveland ---------------- Cleveland OS/2 User Group IBM Bond Ct. Building 2nd Fl E. 9th St. Cleveland, Ohio Pennsylvania - Erie ------------------- Computer Users of Erie OS/2 SIG Contact: Tom Kuklinski 3928 Sassafras Street Erie, PA 16508 Phone: (814) 866-5396 Phone: (814) 898-2905 Tennessee - Knoxville --------------------- East Tennessee PC User Group OS/2 SIG Contact: Arnold Sprague 808 Fairfield Drive Knoxville, TN 37919-4109 Texas - Dallas - Fort Worth --------------------------- Dallas-Forth Worth OS/2 User Group Contact - Toby Pennycuff CompuServe ID - 70007,6267 1211 Wilshire Blvd. Arlington, TX 76012-4623 Meets at: American Airlines HQ 4255 Amon Carter Blvd. Arlington, TX Meetings - Time and dates not listed. Wisconsin - Madison ------------------- Madison OS/2 Users Group Contact&olon. Tom Ender or Donn Tolley 2703 Rolling View Rd. Stoughton, WI 53589-3386 ÿ Information on Internet resources supporting OS/2. ================================================== This list is maintained by Dale Hackemeyer. Please e-mail any additions or corrections you might have to him at uc545502@mizzou1.missouri.edu. OS/2 Related mailing lists -------------------------- ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³BITNET Address: ³Internet Address: ³About the list... ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³JPSOFT@IRISHVMA ³jpsoft@vma.cc.nd.edu ³Discussion of JP Software ³ ³ ³ ³products (4OS2, 4DOS). Subscribe ³ ³ ³ ³by sending a message to ³ ³ ³ ³LISTSERV@xxx (where xxx is the ³ ³ ³ ³part of the list address after ³ ³ ³ ³the @) with SUB JPSOFT name ³ ³ ³ ³(where name is your first and ³ ³ ³ ³last name). ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³OS2@BLEKUL11 ³os2@cc1.kulueven.ac.be ³Moderated OS/2 discussion. ³ ³ ³ ³Subscribe by sending a message to³ ³ ³ ³LISTSERV@xxx (where xxx is the ³ ³ ³ ³part of the list address after ³ ³ ³ ³the @) with SUB OS2 name (where ³ ³ ³ ³name is your first and last ³ ³ ³ ³name). ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³OS2-L@HEARN ³os2-l@nic.surfnet.nl ³OS/2 discussion. Subscribe by ³ ³ ³ ³sending a message to LISTSERV@xxx³ ³ ³ ³(where xxx is the part of the ³ ³ ³ ³list address after the @) with ³ ³ ³ ³SUB OS2-L name (where name is ³ ³ ³ ³your first and last name). ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³OS2USERS@MCGILL1 ³os2users@vm1.mcgill.ca ³OS/2 users discussion. Subscribe ³ ³ ³ ³by sending a message to ³ ³ ³ ³LISTSERV@xxx (where xxx is the ³ ³ ³ ³part of the list address after ³ ³ ³ ³the @) with SUB OS2USERS name ³ ³ ³ ³(where name is your first and ³ ³ ³ ³last name). ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³SASOS2-L@UNCVM1 ³sasos2-l@uncvm1.oit.unc.edu ³RTPNC SAS/OS2 user group list. ³ ³ ³ ³This list doesn't allow automatic³ ³ ³ ³subscriptions. You may send a ³ ³ ³ ³message requesting to be added to³ ³ ³ ³LISTSERV@xxx (where xxx is the ³ ³ ³ ³part of the list address after ³ ³ ³ ³the @) with SUB UTOS2-L name ³ ³ ³ ³(where name is your first and ³ ³ ³ ³last name). This message will be ³ ³ ³ ³forwarded to the maintainers of ³ ³ ³ ³the group who can grant ³ ³ ³ ³subscriptions. ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³UTOS2-L@UTKVM1 ³utos2-l@utkvm1.utk.edu ³Discussion of OS/2 at UTK. ³ ³ ³ ³Subscribe by sending a message to³ ³ ³ ³LISTSERV@xxx (where xxx is the ³ ³ ³ ³part of the list address after ³ ³ ³ ³the @) with SUB UTOS2-L name ³ ³ ³ ³(where name is your first and ³ ³ ³ ³last name). ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³N/A ³mmos2@knex.via.mind.ORG ³Discussion group dealing with ³ ³ ³ ³multimedia aspects of OS/2. To ³ ³ ³ ³subscribe to the digest version, ³ ³ ³ ³send email to ³ ³ ³ ³Mail-Server@knex.via.mind.ORG ³ ³ ³ ³with SUBSCRIBE Mmos2-L firstname ³ ³ ³ ³lastname in the BODY of the mail.³ ³ ³ ³To subscribe to the bounce ³ ³ ³ ³version, send email to ³ ³ ³ ³Mail-Server@knex.via.mind.ORG ³ ³ ³ ³with SUBSCRIBE Mmos2-Digest ³ ³ ³ ³firstname lastname in the BODY of³ ³ ³ ³the mail. ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ About electronic mailing lists. Electronic "mailing lists" are large group discussions held via electronic mail (e-mail). These lists require that you have either BITNET or Internet e-mail access (which one depends on the particular list). Generally the list works by receiving mail from a list participant, and then sending a copy of that message to all the people subscribed to the list. On very active mailing lists this can result in a deluge of e-mail. Some lists avoid this problem by having "digests", where each day all the messages sent to the list are saved and then sent out in a single large piece of e-mail at night. Generally a mailing list has two e-mail addresses: the mailing list proper, and an administrative address to handle subscriptions and cancellations. Never send requests to subscribe or unsubscribe to the main address unless you can find no other way to bring your problem to attention. For more information, please ask you site administrator or sysop. OS/2 related FTP sites: ---------------------- ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³NAME: ³IP ADDRESS: ³Directory & Notes: ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ftp-os2.nmsu.edu ³128.123.35.151 ³/os2 (mirror of cdrom.com) ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ftp-os2.cdrom.com ³192.153.46.69 ³/os2 (mirror of ftp-os2.nmsu.edu)³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³software.watson.ibm.com ³129.34.139.5 ³/pub/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³mtsg.ubc.ca ³137.82.27.1 ³/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³luga.latrobe.edu.au ³131.172.2.2 ³/pub/os2 (mirror of cdrom.com) ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³msdos.archive.umich.edu ³141.211.32.2 ³/msdos/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³funic.funet.fi ³128.214.6.100 ³/pub/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ftp.ieee.org ³140.98.1.1 ³/pub/fidonet/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³boombox.micro.umn.edu ³134.84.132.2 ³/pub/gopher/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ftp.3com.com ³129.213.128.5 ³/adaptors/drivers ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ftp.germany.eu.net ³192.76.144.75 ³/pub/comp/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ftp.luth.se ³130.240.18.2 ³/pub/pc/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ftp.uni-kl.de ³131.246.9.95 ³/pub/pc/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ftp.uni-stuttgart.de ³129.69.1.12 ³/pub/soft/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ftp.usask.ca ³128.233.3.1 ³/pub/archives/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ifcss.org ³129.107.1.155 ³/software/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³luga.latrobe.edu.au ³131.172.2.2 ³/pub/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ma2s2.mathematik.uni-karls³129.13.115.2 ³/pub/lisp/clisp/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³mcafee.com ³192.187.128.1 ³/pub/antivirus ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³mtsg.ubc.ca ³137.82.27.1 ³/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³nic.switch.ch ³130.59.1.40 ³/mirrors/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³novell.com ³137.65.4.1 ³/netwire/novfiles/client.kit/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³plaza.aarnet.edu.au ³139.130.4.6 ³/micros/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³rhino.microsoft.com ³131.107.1.121 ³/LANMan/OS2xBeta ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³rs3.hrz.th-darmstadt.de ³130.83.55.75 ³/pub/machines/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³software.watson.ibm.com ³129.34.139.5 ³/pub/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³sprite.cica.indiana.edu ³129.79.26.102 ³/pub/pc/borland/c/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³src.doc.ic.ac.uk ³146.169.2.1 ³/computing/systems/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³sun0.urz.uni-heidelberg.de³129.206.100.126 ³/pub/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³tethys.rz.uni-osnabrueck.d³131.173.17.10 ³/pub/os2 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³world.std.com ³192.74.137.5 ³/src/os2 ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Other FTP sites of interest ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³NAME: ³IP ADDRESS: ³NOTES: ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³rtfm.mit.edu ³18.70.0.226 ³FAQ lists ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³cs.uwp.edu ³131.210.1.4 ³Music related stuff ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³wuarchive.wustl.edu ³128.252.135.4 ³Lots of other stuff ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³saffron.inset.com ³192.94.75.2 ³Sounds (various formats) ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³sounds.sdsu.edu ³130.191.224.2 ³Sounds (.au format) ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³watsun.cc.columbia.edu ³128.59.39.2 ³/kermit/b ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³prep.ai.mit.edu ³18.71.0.38 ³/pub/gnu ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ftp.uu.net ³192.48.96.2 ³/usenet (e.g.) ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ About FTP. FTP stands for "File Transfer Protocol" and is the standard protocol on the Internet for transfering files. With a fast, direct internet connection, download speeds can approach 32Kbs under light network load. The sites listed allow "anonymous" logons. When prompted for a User name when logging in, enter ANONYMOUS and then enter your e-mail address as your password. This assists the administators at the remote site in tracking usage of the site. Don't forget that you're downloading from someone else's computer, someone who has to pay for and use that computer. Given the global reach of the internet, even though you may be downloading at 4am, it could be noon at the site you're downloading from. To avoid putting more of a load on a machine someone may depend on for work during the day, try to only download sometime other than 9-5, remote time. The last couple of letters in the remote sites address can help you determine where your downloading from. The last 2 to 3 letters indicate the location of the site: .de Germany .au Australia .ca Canada .fi Finland .uk United Kingdom NNTP usenet servers: ------------------- ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³NAME: ³IP ADDRESS: ³NOTES: ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³mont.cs.missouri.edu ³128.206.100.208 ³Local to University of Missouri ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³sol.ctr.columbia.edu ³128.59.64.40 ³Huge place. Takes a long time ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³umd5.umd.edu ³128.8.10.5 ³No posting allowed as guest ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³raven.alaska.edu ³137.229.10.39 ³No posting allowed as guest ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ These OS/2 newsgroups are available: comp.os.os2.multimedia For information on OS/2 multimedia features, including MMPM/2 and Ultimotion. comp.os.os2.setup For all questions relating to setup, installation, and driver support under OS/2. comp.os.os2.bugs For the discussion and reporting of OS/2 bugs (flaws). comp.os.os2.advocacy For the discussion of OS/2 compared with other products, marketing, and "politics." comp.os.os2.networking For any OS/2 questions dealing with networking. comp.os.os2.ver1x For any OS/2 questions dealing with OS/2 versions prior to OS/2 2.0. comp.os.os2.programmer.porting For talk about porting software from other environments to OS/2. comp.os.os2.programmer.misc For discussion of any other OS/2 programming issues. comp.os.os2.apps Discusses DOS, Windows, and OS/2 applications running under OS/2. comp.os.os2.announce Carries important OS/2 announcements. This newsgroup is moderated -- you cannot ask a question here. comp.binaries.os2 If you do not have ftp access you can obtain OS/2 software using this newsgroup. This newsgroup is also moderated. comp.os.os2.beta For discussion of beta releases of OS/2 (versions of OS/2 that are released for testing purposes by IBM and that you cannot buy in stores). comp.os.os2.misc For general OS/2 discussion. Post here only if none of the above categories fits. From the Wire ============= A selection of messages about OS/2 seen fleeting across the wires on Fidonet and Internet. Demand ProComm for OS/2! ------------------------ From the Fidonet OS2 conference From: Woody Sturges Subj: ProComm for OS/2! Our OS/2 user group met yesterday and we had a couple of the staff from Datastorm tech support, makers of ProComm Plus, talk to us about running PC+/DOS and PC+/Win under OS/2. Of course, talk came around an OS/2 version of ProComm. Datastorm, like most companies, is market driven. The gentlemen said that if enough people were to ask for it, it would get done. Now's your chance! They acknowledged that they're listening, all we have to do is let them know that we're out here. Here's how you can contact Datastorm and let them you would like to see an OS/2 version of PC+. Feel free to mention specifics! Character mode? Presentation manager? Special features? Leave a note, fax, or call the numbers below! Compuserve, GO DSTORM, Leave a message to 72250,3463 (David Irovic) Tech Support, Voice (314) 875-0530 Tech Support, Fax (314) 875-0595 More on Stacker for OS/2 fix ---------------------------- From the OS/2 Woodmeister Public Message area. From: Phillip Wilson I found this on CIS regarding the fixes for Stacker for OS/2: Sb: STAC Patch Fm: Stac Electronics 75300,2755 To: ALL All, To determine if you need the Patch for Stacker for OS/2 use the following. If your Serial number has 1AH or 1BH then you should request the patch by PRIVATE MAIL to ROGER HICKS 74250,1407. Include your Serial number in the request. Any requests without serial numbers will be rejected. If your Serial number has 1CH in it then you already have the patch. Hope this helps STAC Product Support OS/2 vs. NT Revisited --------------------- From the Fidonet TEAM-OS2 conference. From: Pete Norloff Subj: OS/2 still without competition Recently I had the privilege of attending a head-to-head demonstration of OS/2 2.1 and Windows NT. While the demo probably didn't contain the same level of excitement of the shoot-out done recently for the Houston PC User Group, it was an excellent demonstration of the state of the two products. Since I'm already fairly familiar with OS/2 and content with the features and function of the operating system, I felt that it was important to familiarize myself with the new release from Microsoft. If nothing else, NT will serve to give IBM some competition in the operating system business and hopefully cause those responsible for OS/2 to continue to advance the feature set. The presentation was sponsored by Bohdan Associates Inc. and held in a Bethesda, Maryland hotel. Both IBM and Microsoft were given an hour for their presentation followed by a half hour question and answer session. OS/2 was presented very well and most of the audience seemed to be reasonably familiar with the product. I made notes during the Microsoft part of the presentation. This is a condensation of those notes. The Microsoft presenter seemed to be reasonably familiar with the product and seemed to be giving us a pitch somewhere between an honest tour of the features and a snake oil sales job. We were told that "NT is Windows" and that because of that there will be no learning curve. I suspect that we'll be hearing a lot more of this selling point in the future. The salesman described NT as "having everything that is in Windows 3.1" and used this as the justification for trying to convince us that Windows NT 1.0 is really version 3.1. If you haven't done so yet, you really need to have a look at the document "Windows NT and OS/2 2.1: The advantages of Windows NT for Today's Client-Server Computing" and the subsequent rebuttal document from IBM entitled "IBM PSP Rebuttal to the Microsoft Document Windows NT and OS/2 2.1...". {EDITOR'S NOTE: See the August 1993 issue of the MMOUG Newsletter for the IBM PSP Rebuttal} With these two documents, you begin to get a flavor for the truth stretching that Microsoft seems inclined to try to foist off on us. It was surely in this same spirit of "lie and hope no one notices" that the MS salesman began telling us that the "majority of OS/2 apps today are character based apps". On the subject of native NT applications, we were told that there are currently 1200 ports from 16 bit Windows and that 3600 new applications were currently being developed from scratch. Of these 3600, 2300 were "in house, business-specific apps." As a part of the demo, the MS salesman started trying to bring up SQL Server for NT. As the software package displayed the same error messages several times and seemed to be bringing the machine to a standstill, another participant asked if NT was available now and if what we were looking at was the generally available code. We were assured that NT had "shipped" to manufacturing and that we were indeed seeing the final version of Windows NT Advanced Server. As the MS rep finally gave up on showing SQL Server, he told us that "with SQL Server running, is has a tendency to completely take over the machine". Someone asked a few moments later what level of machine he was demoing on we were informed that this was a 486/33 with 24 MB of memory. "The target for NT is Client-Server." "C2 security cannot be shut off." NT is "C2 certifiable" -- not certified. someday, maybe. We saw Intergraph demoed. It was painfully slow. There's no way anyone would have wanted to run this package on this platform. The MS rep told us it "runs much better on a RISC machine". I certainly hope so. The question came up again later when NT started faltering again about the code we were actually seeing and this time we were told that this was not the final version of NT but rather a late beta. Quite a number of attendees started murmuring at this point because this was a direct contradiction of the MS rep's earlier declaration that this was final, shipping code that we were seeing. "Lie and hope no one notices." At the end of the MS presentation, during the question and answer session for both reps, an attendee stood up and asked the MS rep how long he was going to be made to wait for an object oriented user interface from Microsoft. The rep told him that it wouldn't be here until some time in 1994 and he even hedged on his response that far in the future. He mentioned that the future offerings, whenever they arrive, will be based to some degree on Microsoft's OLE 2.0, etc. There was a long pause and the IBM rep simply said "and if you'd like to have all that now...". The audience erupted in applause. MMOUG mailbag ============= Mail sent to us about the User Group and what we're doing. Marc Clemente ------------- Date: Sun, 25 Jul 1993 11:20 CST From: "MARC F. CLEMENTE" Subject: MMOUG To: UC545502@MIZZOU1.MISSOURI.EDU Hi. I heard about the MMOUG. I was wondering if you could give me a bit of information on it. What is it? When is the next meetingg, and where? What do I have to do to be a member? What do I get for becoming a member? As you can see from my internet address, I am (relatively) close, and I am interested in what you guys are doing. Thank you, Marc Date: Sun, 25 Jul 93 13:37:52 CDT From: Dale Hackemeyer Organization: University of Missouri at Columbia Subject: Re: MMOUG To: "MARC F. CLEMENTE" In-Reply-To: Your message of Sun, 25 Jul 1993 11:20 CST On Sun, 25 Jul 1993 11:20 CST you said: >Hi. I heard about the MMOUG. I was wondering if you could give me a >bit of information on it. What is it? When is the next meetingg, and >where? What do I have to do to be a member? What do I get for becoming >a member? > We're a non-profit group dedicated to supporting all users of OS/2. We meet on the third Wednesday of each month at 4:00pm, meeting at the Columbia IBM office on even months and at the Jefferson City IBM office on odd months. Everyone is welcome to attend our meetings, and a $30 check entitles you to a one year membership. Right now joining nets you a OS/2 2.0 Birthday T-shirt and 1hr / 1meg a day on our BBS, currently the OS/2 Woodmeister, which carries all the Fidonet OS/2 conferences, as well as an extensive OS/2 file collection. We also are putting out a newsletter in .INF format for viewing under OS/2. We currently don't have a printed newsletter to help keep costs down, however we voted at the last meeting to start sending out either a postcard or a single letter sized bulletin to all members. We've also been having giveaways at the meetings which only members are eligible to win. So far we've given away PMFOCUS, Stacker for OS/2 and DOS, OS/2 2.1 Unleashed, World Atlas CDROM, OS/2 2.0, and other assorted OS/2 books and promo items. We're currently working on setting up a point BBS in Jefferson City that mirrors the Woodmeister (located in Columbia) so our Jeff City members don't have to make long distance calls. We had our first meeting in April with an OS/2 2.0 birthday party, as well as laying some groundwork for the group with the election of officers, deciding meeting times, etc. At the May meeting a reprensentative of Information Builders demoed PMFOCUS, a PM application for building interactive database applications. At the June Meeting a representative of DeScribe Corporation demoed their premier OS/2 word processor, DeScribe 4.0. At the July meeting, Ben Hoffman, one of the local higher-ups in IBM Personal Software Products gave a talk on OS/2 and PSP in general. Coming up at the August meeting we'll have a member of Datastorm's Technical Support team coming in to give tips on running Procomm for DOS or Windows run well under OS/2. We'll also be having a demo of Offline Mail readers for OS/2, and rumor has it we'll be giving away a copy of Lotus 123 for OS/2. >As you can see from my internet address, I am (relatively) close, and >I am interested in what you guys are doing. It's good to hear from you and to know the word is getting out that we're here. If you haven't seen our newsletter, try ftp'ing to ftp-os2.cdrom.com and look in /pub/os2/2_x/info/newsltr for the June newsletter and in /pub/os2/incoming for the July issue. The files are MM0693.ZIP and MM0793.ZIP. If your ever around Columbia or Jeff City on the 3rd Wednesday of the month, feel free to drop in and join us! Dale Hackemeyer ÿ Mat Kramer ---------- From: Mat Kramer <75746.2404@CompuServe.COM> To: Dale Hackenmeyer Subject: Hi from Minnesota Hi Dale, I was looking at your MMOUG newsletter (INF version), and I just thought I'd connect, since I do the Minnesota OS/2 User Group newsletter (Threads). Your INF newsletter looks really nice -- do you have a hardcopy version? We have a hardcopy version done with DeScribe, and I'm in the process of writing macros to help me in the conversion from DeScribe to IPF. Do you have any of that process automated? We currently have only been putting the DeScribe version online, but as of the coming month, I"m going to take charge of the distribution, and I'll put a TXT version out there along with an INF, if I get it done. Also, do you have any policy for re-use of your articles? We would occasionally like to re-publish your articles is that would be OK with you. Of course, you could then do the same. Hope to hear from you later, Mat Kramer, MekTek Date: Thu, 05 Aug 93 11:16:43 CDT From: Dale Hackemeyer Organization: University of Missouri at Columbia Subject: Re: Hi from Minnesota To: Mat Kramer <75746.2404@CompuServe.COM> In-Reply-To: Your message of 03 Aug 93 20:35:44 EDT On 03 Aug 93 20:35:44 EDT you said: >I was looking at your MMOUG newsletter (INF version), and I just thought I'd >connect, since I do the Minnesota OS/2 User Group newsletter (Threads). Your >INF newsletter looks really nice -- do you have a hardcopy version? We have >a hardcopy version done with DeScribe, and I'm in the process of writing >macros to help me in the conversion from DeScribe to IPF. Do you have any of >that process automated? Thanks, always glad to hear positive feedback. I downloaded your May and June issues last night, and I'm impressed. We don't have a hard copy version, but plan on starting a monthly mailing of postcards with the latest group info, meeting reminder, and how to get the latest copy of the online newsletter. We're trying to save as much money as possible since we just formed in April and want to spend the money we have carefully. I don't have any conversion macros, but I've made up 2 small C programs that convert ASCII text to IPF format and back again. Nothing fancy, one just converts critical characters such as : and & to their IPF counterparts and adds :p. on blank lines. The other strips all IPF tags and converts symbols back to their ASCII counterparts. I'd be happy to get you a copy of them if you think they'd help out. >Also, do you have any policy for re-use of your articles? We would >occasionally like to re-publish your articles is that would be OK with you. >Of course, you could then do the same. Your welcome to reprint our articles as long as you give credit to the author, and possibly mention that it came from our newsletter. I'd love to be able to use some of your articles as well. I've created an area on our BBS just for that purpose. I've even started uploading the IPF source to some articles and the Internet, BBS, and User Group listings. You might take a look there for some stuff too. Let me know if you need any help! Dale Hackemeyerÿ MAJ Bart Cook ------------- Date: Wed, 11 Aug 93 11:42:04 KOR From: "MAJ Bart D. Cook" To: Dale Hackemeyer Subject: MMOUG Dale: I am a very new OS2 user (got it about 2 weeks ago). I have been in touch with Timothy Sipples and several other people via e-mail while in the process of deciding to move to OS2. I have a CD drive, and the Hobbes OS2 CD from Walnut Creek, which is where I first saw your newsletter. I have just obtained the July edition from ftp.cdrom (or some such). Thank you for the detailed information about how to subscribe to the various electronic mailing lists (new in the July issue). I have sent subscriptions to about 4 of them. However, in both this and the previous newsletter, you give a group of newsgroups. I asked Mr. Sipples how to go about making use of these groups, but he didn't know. Can you tell me, or perhaps put in a paragraph in the next newsletter, about how to get the information in the various newsgroups? Is it a subscription process, like the mailing lists? Are the newsgroups on an FTP site somewhere? I have no idea how it works. Thank you in advance for your time and effort. I have enjoyed the newsletters very much, and have gotten some good tips from them. Keep up the good work. I might join the MMOUG, but the commute from Korea for the monthly meetings might be a bit much. Bart D. Cook bcook@seoul-emh1.army.mil Date: Thu, 12 Aug 93 11:01:45 CDT From: Dale Hackemeyer Organization: University of Missouri at Columbia Subject: Re: MMOUG To: "MAJ Bart D. Cook" In-Reply-To: Your message of Wed, 11 Aug 93 11:42:04 KOR On Wed, 11 Aug 93 11:42:04 KOR you said: > I am a very new OS2 user (got it about 2 weeks ago). I have been in >touch with Timothy Sipples and several other people via e-mail while in >the process of deciding to move to OS2. Glad to hear you made the move. I did so about a year ago and haven't looked back. > I have a CD drive, and the Hobbes OS2 CD from Walnut Creek, which >is where I first saw your newsletter. I have just obtained the July >edition from ftp.cdrom (or some such). Didn't even realize we were on the new Hobbes CD. Neat! > Thank you for the detailed information about how to subscribe to >the various electronic mailing lists (new in the July issue). I have >sent subscriptions to about 4 of them. No problem. I've subscribed to most of them myself as well. > However, in both this and the previous newsletter, you give a group >of newsgroups. I asked Mr. Sipples how to go about making use of these >groups, but he didn't know. Can you tell me, or perhaps put in a >paragraph in the next newsletter, about how to get the information in >the various newsgroups? Is it a subscription process, like the mailing >lists? Are the newsgroups on an FTP site somewhere? I have no idea how >it works. The newsgroups are like a netwide bullentin board system. You don't have to subscribe, but you do need a site that carries the newsgroups and will let you have access (my listing in the newsletter gives a few that let you on as a "guest"). This is where things get tricky. A lot of it depends on what kind of computer you use (to access the internet), and whether or not you've got the software to access the newsgroups. You've obviously got internet access (both mail and FTP), so all you really need is software. What kind of computer system do you do your email and ftp on? I access the newsgoups (aka "Usenet") through either an IBM mainframe or a NeXT workstation. If you have access to one of these types of computers I might be able to help. If not, you're best bet would be to ask around there and see if anyone else there knows of a way (assuming you haven't gone this route already :) ). > Thank you in advance for your time and effort. I have enjoyed the >newsletters very much, and have gotten some good tips from them. Keep >up the good work. I might join the MMOUG, but the commute from Korea >for the monthly meetings might be a bit much. You're welcome! The best part about doing it is getting mail from people like yourself in far off places who somehow got a copy. I've got the August issue done and it should be on ftp-os2.cdrom.com in the incoming directory by this weekend. Look for it next week. Get back to me with some more info on your internet access and I'll see if I can't help you find a way to Usenet. Dale Hackemeyer Date: Fri, 13 Aug 93 10:34:02 KOR From: "MAJ Bart D. Cook" To: Dale Hackemeyer Subject: Re: MMOUG Dale: Thanks for the quick return. I am a computer professional for the US Army, have been since 1985, but I am relatively new to the world of global communications. I have used e-mail for several years, but haven't really dug into it until lately. It is a real interesting experience to be able to tele-communicate with folks like yourself, and hook up to other computers around the world using ftp and telnet, but you know that. >The newsgroups are like a netwide bullentin board system. You don't have >to subscribe, but you do need a site that carries the newsgroups and >will let you have access (my listing in the newsletter gives a few >that let you on as a "guest"). >This is where things get tricky. A lot of it depends on what kind of >computer you use (to access the internet), and whether or not you've >got the software to access the newsgroups. You've obviously got >internet access (both mail and FTP), so all you really need is >software. What kind of computer system do you do your email and ftp on? I work on an Everex 386-25. I use it to access, for e-mail purposes, an Intel 320 e-mail sub-host running in my office, which runs MMDF-II as its mail transfer agent. So e-mail comes to my desktop. At home I still have a lowly 16MHz 386SX (Packard Bell) that I am using the play with OS2. I am working on a way to convince my wife that I "need" a 486DX2 66MHz machine for play! I use a DOS program called Telemate (a really neat shareware comm program, and I have used Procomm, Procomm+, Procomm+ for Windows, Telix, and a few others) for most direct access, and I use a DOS program called PC Max-E-Mail to handle my e-mail. (This is kind of an Army standard e-mail front end.) For ftp and telnet and other direct access to the Internet resources, I have a login on a Sperry (Unisys) 5000-95 minicomputer, which serves as the e-mail host for several thousand US users here in the Seoul-based US military community. It is behind a gateway. My Everex PC runs DOS 5.0, the Intel runs Xenix, and the Sperry runs Unix SVR3.2 (I think). Anyway, I suspect that, if I can telnet or ftp to a host that allows guest logins, I can access the newsgroups, if I know how. Thanks for your help. Bart Cook Date: Sun, 15 Aug 93 16:03:55 CDT From: Dale Hackemeyer Subject: Re: MMOUG To: "MAJ Bart D. Cook" Bart, OK, you just reminded me that you CAN telnet into certain gopher servers that carry the USENET newsgroups. After a bit of searching around, I found a site in Korea that carries USENET! (I was even able to login and read the news from here). Try telneting to: gopher.nic.nm.kr Login as: gopher If it has trouble recognizing you terminal type, try forcing vt-100 (how you would do this with your telnet, I don't know). Once in, you should have menu entries to choose from, and the path to USENET is as follows: Top level menu: USENET Newsgroups USENET Newsgroups comp os os2 Once your at this level you should see most if not all of the OS/2 Newsgroups. Give this a try and let me know if it works. Good luck! Dale Hackemeyer Date: Fri, 20 Aug 93 14:48:50 KOR From: "MAJ Bart D. Cook" To: Dale Hackemeyer Subject: Re: OS2-L Dale: My experience with OS2 is getting weirder. Am having troubles with the PAS16 sound board that I think are effecting the entire system. At least I got an e-mail address for Media Vision as a result of a posting to the Mmos2-L list. I am really happier on my work machine with DOS5/Win3.1 than with OS2 at home right now, and I was happier with DOS5/Win3.1 at home. But, I had growing pains with Windows, and worked through those, so I figure it is just time and knowledge. I have ordered the OS2 Unleashed book, and hopefully these mailing lists will get me straight. It just isn't as smooth as I think it would need to be for IBM to really replace DOS/Windows in the near term. Oh well, I thought it would be an adventure, and I have been right so far. Bart Date: Sun, 22 Aug 93 13:48:24 CDT From: Dale Hackemeyer Organization: University of Missouri at Columbia Subject: OS/2... To: MAJ Bart Cook > My experience with OS2 is getting weirder. Am having troubles with >the PAS16 sound board that I think are effecting the entire system. At >least I got an e-mail address for Media Vision as a result of a >posting to the Mmos2-L list. I've heard of various problems with the PAS16, but never really paid too much attention since I haven't got one. When does the problem occur? Is it in a DOS program or are when you're using MMPM/2? Both? Are you running a CDROM off of it's SCSI port? I know some of the troubles I've seen in the past had something to do with the drivers. I'm not sure if they're fixed yet or not. > I am really happier on my work machine with DOS5/Win3.1 than with >OS2 at home right now, and I was happier with DOS5/Win3.1 at home. But, >I had growing pains with Windows, and worked through those, so I figure >it is just time and knowledge. I have ordered the OS2 Unleashed book, >and hopefully these mailing lists will get me straight. It just isn't >as smooth as I think it would need to be for IBM to really replace >DOS/Windows in the near term. Really? What are the things that make you feel better about DOS/Win3.1 than OS/2? I know you have an Everex 386-25, but how much memory do you have? Do you run the OS/2 Multimedia extensions? What kind of video card do you have and what resolution and color depth are you running it at? How much HD space do you have? How do you have it partitioned? What programs do you run and depend on the most? Also, give me some info on the work machine as well so we can compare the two. > Oh well, I thought it would be an adventure, and I have been right >so far. Yeah, OS/2 can be an adventure at first, but a little practice and some fine tuning can really make a difference. Get back to me about the stuff above and I can probably give you some tips to improve. Dale Hackemeyer ÿ