From: tsipple@vnet.IBM.COM Newsgroups: comp.os.os2.networking.misc Subject: OS/2 Warp Connect Tips and Tricks Date: 22 Jun 1995 17:31:07 -0500 Message-ID: <199506222230.RAA24310@mail.cs.utexas.edu> From: Timothy F. Sipples Subject: OS/2 Warp Connect Tips and Tricks OS/2 Warp Connect Tips and Tricks --------------------------------- by Timothy F. Sipples Internet: tsipple@vnet.ibm.com Last Updated: June 22, 1995 By now the first of you are receiving your OS/2 Warp Connect packages. This exciting software package has many new features. I've spent some time with OS/2 Warp Connect, as have many of my colleagues, and I'd like to share some somewhat random bits of advice on the product. This information will be incorporated into a future release of the OS/2 Warp Frequently Asked Questions (FAQ) List. Q: What does OS/2 Warp Connect include? A: OS/2 Warp Connect includes everything now found in OS/2 Warp plus: - Multiprotocol Transport Services (MPTS) - IBM OS/2 Peer Version 1 - IBM OS/2 LAN Requester Version 4 - Novell NetWare requester Version 2.11 - IBM LAN Distance client Version 1.11 - IBM TCP/IP Version 3 - Network SignON Coordinator (client/server) - First Failure Support Technology/2 - Lotus Notes Express "Plus 2" - AskPSP Most of these products (exceptions: Notes Express, AskPSP) are installed using a single, unified installation program which is part of the main OS/2 Warp installation routine. There are also options to install networking software atop an existing OS/2 Warp installation, to install only base OS/2 Warp (without networking software), and to use individual installation programs provided with each separate networking component. Q: Is OS/2 Warp Connect available on diskettes? A: Not from IBM, no. OS/2 Warp Connect is available only on CD-ROM. However, there are at least two ways to install OS/2 Warp Connect on a PC without a CD-ROM drive. The first is to create the diskette version of OS/2 Warp from any CD-ROM-equipped PC. (Diskette images are provided.) This method is not recommended since it is rather time consuming. The second method is to install OS/2 Warp Connect onto one PC with a CD-ROM drive that is connected to your network. Then, using a simple application provided, you can create a pair of "bootstrap" diskettes and use these diskettes to "pull" OS/2 Warp Connect across the network. In other words, you can remotely install OS/2 Warp Connect from any PC on the network from a "code server." To start remote installation, just double click on the new "OS/2 Warp Connect Remote Installation" program object. Everything is menu-driven and easy-to-use. Q: Is OS/2 Warp Connect available with and without Win-OS/2? A: Yes. The version available starting May 19th in the United States includes Win-OS/2. About 60 days later, the version without Win-OS/2 (designed to use an installed copy of Windows, if available, to run Windows applications) will be made available. Q: If I have OS/2 Warp without Win-OS/2 ("for Windows"), the so-called "red box," can I install OS/2 Warp Connect with Win-OS/2? A: IBM changed OS/2 Warp Connect so that the installation program will warn you that you are about to install a "with Win-OS/2" version on top of a "without Win-OS/2" version, something which is not recommended. To force installation in this case, you must delete the SYSLEVEL.* files in the \OS2\INSTALL directory before starting. Q: What is the price of OS/2 Warp Connect? A: The price will vary by dealer, but the non-upgrade price is approximately $155-170 in the United States (street price), according to reports on the Internet. Q: Are upgrades available? A: Yes. IBM is offering discounted upgrades from base OS/2 Warp and OS/2 2.1x to OS/2 Warp Connect. You save more if you are upgrading from OS/2 Warp. Street pricing, according to Internet reports, ranges from about $89 (upgrade from OS/2 Warp) to about $120 (upgrade from OS/2 2.1x). This discount may take the form of an in-store rebate, but some dealers may handle the rebate for you. Q: Is IBM TCP/IP Version 3 available separately? A: No. TCP/IP Version 3 is only available with OS/2 Warp Connect. Q: What happens to IBM TCP/IP Version 2? A: It will continue to be sold and serviced as long as demand warrants. Q: Is NFS or X Window Server (PMX) included with OS/2 Warp Connect? A: No, but... Q: Will the add-on kits (like NFS and X Window Server/PMX) for IBM TCP/IP Version 2 work with OS/2 Warp Connect's TCP/IP Version 3? A: Yes, although IBM recommends you install the latest Service Paks for these add-on kits. Future updates to these add-on kits will be tested and certified for OS/2 Warp Connect. Also, according to reports on the Internet, pricing on these kits has fallen recently at many dealers, so the add-on kits are more affordable. Q: Can IBM TCP/IP Version 3 maintain a dial-up Internet connection and a network card connection at the same time? A: Yes! Q: Does IBM TCP/IP Version 3 include ftp and telnet server software? A: Yes. In fact, OS/2 Warp Connect is an excellent foundation for other TCP/IP software, such as the freely available World Wide Web server software. Q: Does IBM TCP/IP Version 3 include updates to the Internet Connection software (such as Web Explorer Version 1.01 and Ultimail Version 2.1.1)? A: Yes. Q: What else does IBM TCP/IP Version 3 include? A: Quite a lot is new, including integrated REXX FTP and REXXSock capabilities, a revamped configuration notebook, and faster transports. Q: My shareware IRC/2 and NCFTP programs no longer work with OS/2 Warp Connect's TCP/IP when I am dialed into my Internet provider. How can I fix this? A: You need an updated AFINET.SYS file. The update is available on the Internet via anonymous ftp from testcase.boulder.ibm.com in directory ps/fromibm/lan. Place this replacement AFINET.SYS file in your \MPTN\BIN directory. This new AFINET.SYS file also fixes certain SENDMAIL problems over a dial-up Internet connection. It will be incorporated into a future OS/2 Warp Connect FixPak. Q: Can I use OS/2 Warp Connect as a router, say, for TCP/IP? A: Yes. Q: What is IBM LAN Distance? A: LAN Distance provides the ability to use any network protocol over a dial-up or other asynchronous connection (like a modem). This connection is secure (featuring login encryption and password protection, if desired). The client software is used to connect to the IBM LAN Distance Connection Server (usually running on a PC back in the office). The Connection Server is an OS/2 application and is available in 8-port and unlimited port versions. Q: Do I need the IBM LAN Distance Connection Server to use the LAN Distance client? A: No. First, the IBM LAN Distance client includes a "shuttle" feature which automatically reconfigures your PC (such as a notebook computer) for either in-office (network card attached) or out-of-office (modem attached) operation. Even if you don't use LAN Distance, you can still use its shuttle feature. Also, if you are using OS/2 Peer, you can establish a single connection to another OS/2 Warp Connect system running the IBM LAN Distance client to communicate between them, single PC to single PC. Q: What is the LAN Distance shuttle feature, and how do I activate it? A: The shuttle feature in LAN Distance allows you to quickly switch between LAN-attached (with network adapter drivers in CONFIG.SYS, for example) and modem-attached (where you can dial into your office network using LAN Distance or not dial in at all). The shuttle feature is particularly useful for notebook computers, for example, which are carried in and out of the office. When you're on the road, you don't want the network adapter drivers to load. To activate the LAN Distance shuttle feature, simply install LAN Distance and run LDSHUTTL.EXE. You can set up a program object on your desktop to run the LAN Distance Shuttle more easily. Q: Do I need a network card to use OS/2 Warp Connect? A: No, not at all. First of all, you can install base OS/2 Warp (without any networking software) from the OS/2 Warp Connect CD (either locally or remotely, over the network) if you wish. You can also use LAN Distance to dial back into your office for a network connection. Moreover, there is an IBM Parallel Port driver which, when used with a LinkRight/LinkWiz/LapLink-style cable, can be used in place of a network card. This parallel port connection can be used to link two PCs. (It may also be possible to "daisy chain" network connections, using a desktop PC with a network card and a parallel port, for example, to provide network access to another system without a network card.) Consult the file \IBMCOM\MACS\PRNANDIS.TXT for more information on the IBM Parallel Port driver; this file is installed when you install OS/2 Warp Connect. Q: Does the networking software require space on my main OS/2 Warp drive? A: Some. The OS/2 Warp Connect installation program and core networking components expect to be on the same drive as OS/2 Warp itself, but the bulk of OS/2 Warp Connect's networking software can be placed on other drives. Q: Are there any special tips for installation? A: Not really. Installation is quite easy. More device drivers have been provided, the latest fixes have been applied -- in short, it has never been easier to install and configure a fully networked PC. For example, a new device driver, DETNE2.SYS, is included in OS/2 Warp Connect to detect the clone NE2000 network cards which can cause problems in previous OS/2 Warp releases. Also, OS/2 Warp Connect will attempt to autodetect your network card (to the extent possible). You may still wish to confirm, using the settings options provided, that OS/2 Warp is configuring your network card for the correct interrupt, addresses, etc. Make sure you have sufficient disk space on your system prior to installating OS/2 Warp Connect. If you do not have enough space, you will be given the opportunity to exit the installation program to correct the problem. In the new, unified network configuration notebook, note that there are multiple pages for some of the notebook tabs. Please be sure to fill out the correct information on all pages. You will not be allowed to proceed if you miss a vital setting. (This unified notebook appears during the Advanced Installation.) After you install, you may see two or even three icons on your desktop labeled "MPTS." MPTS is important, but you can safely drag any duplicates to the shredder. If you ever wish to reinstall all or part of the networking software included with OS/2 Warp Connect, make sure you run the uninstall utilities provided for each component. Doing so will free up disk space. Q: I can't get OS/2 Warp Connect working with my NE2000 compatible network card. How can I fix it? A: OS/2 Warp Connect includes a driver for the Eagle NE2000plus network adapter, which is the most popular NE2000 adapter. Unfortunately many NE2000 adapters are not quite compatible with the Eagle. A "generic" NE2000 driver package has been created and is available for retrieval from the Internet via anonymous ftp from ftp-os2.nmsu.edu. Look for filename ne2000wc.zip, most likely located in the /os2/network/ndis directory. Instructions are included. Q: Is 3270 or 5250 terminal emulation included with OS/2 Warp Connect? A: Only for TCP/IP connections to a mainframe or midrange system. For SNA connections you may wish to add one of the following products: - IBM Personal Communications 3270 for OS/2 - IBM Personal Communications AS/400 for OS/2 - IBM Personal Communications 3270 and AS/400 for OS/2 - IBM Communications Manager for OS/2 - Third party products (such as Rumba for OS/2 or Attachmate for OS/2) - "Attach Pak" planned as an OS/2 Warp Connect add-on later this year You need not install NTS/2, LAPS, MPTS, or any other network transport software when you install these products. The SNA/802.2 protocol is provided with OS/2 Warp Connect. Q: Will OS/2 Peer connect to other systems? A: OS/2 Peer will connect to any of the following systems: - Other OS/2 Peers (OS/2 Warp Connect) - IBM LAN Server Version 4 - IBM LAN Server (previous releases) - IBM LAN Server for AIX - IBM LAN Server for AS/400 - IBM LAN Server for VM - IBM LAN Server for MVS - IBM PC LAN Program - Artisoft's LANtastic for OS/2 (*) - Artisoft's LANtastic for DOS or Windows (*) - Artisoft's LANtastic for Macintosh (*) - Microsoft LAN Manager - Microsoft Windows for Workgroups - Microsoft Windows NT - Any other SMB-based networking software (*) Providing server only to LANtastic clients in SMB mode, at least with LANtastic Version 1 for OS/2. Q: If OS/2 Peer can connect to IBM LAN Server Version 4, why would I install the OS/2 LAN Requester in OS/2 Warp Connect? A: OS/2 Peer is a superset of the IBM OS/2 LAN Requester, with one exception: to manage IBM LAN Server resources graphically, you must use the OS/2 LAN Requester rather than OS/2 Peer. (OS/2 Peer can administer LAN Server user IDs and groups through User Profile Management. Command line and REXX API administration facilities for resources are still available.) Also, OS/2 Peer requires slightly more memory than the OS/2 LAN Requester. Q: What devices on my PC can I allow access to over the network with OS/2 Peer? A: Other OS/2 Peer users can access directories (folders), drives (including diskette drives, CD-ROM drives, optical drives, etc.), printers (the actual print queue), and ports (both parallel and serial). Non-OS/2 Peer users (such as LANtastic clients) can access printers, drives, and directories only. The ability to share CD-ROM drives and COM ports (modems, for example) over the network is rare or even unique to OS/2 Peer. Q: Tell me more about COM port sharing... A: Sure. Suppose you have a high speed modem attached to one OS/2 Warp Connect PC. You can share out that fancy V.34 modem to other PCs running OS/2 Peer so that they can use standard communications software (not necessarily network-aware communications software) to dial-out with that modem and communicate with other systems. Some communications software (such as HyperAccess/5 for OS/2) can open the COM port in "shared mode," which means that you can have other communications software monitoring and displaying the traffic being passed to/from that COM port, even from somewhere else on the network! IBM LAN Server 4 also supports this feature with OS/2 Warp clients. The NET COMM and NET USE commands facilitate modem sharing (by allowing you to assign the network shared COM port to a local "real" COM port, for example COM3). Q: Why isn't COM port sharing supported with DOS or Windows clients? A: Why do DOS and Windows lack true preemptive multitasking? Why are DOS and Windows still limited to 640K of memory? Why do DOS and Windows lack Crash Protection? Why... :-) Q: Is there any limit to the number of client connections OS/2 Peer supports? A: There's no intrinsic limit (none reachable, anyway). You can have as many users accessing a resource on your OS/2 Peer PC as you wish, up to the performance limits of your PC. You can also limit the number of simultaneous connections to any resource (quite useful for limiting the load on your PC or for enforcing software licensing). Q: If I have the Novell NetWare requester in OS/2 Warp Connect loaded, can I reshare those devices (such as printers) out to other clients using OS/2 Peer? A: Yes. Q: Why should I buy IBM LAN Server 4? Why not use OS/2 Peer for everything? A: For smaller sized networks (typically 10 or fewer PCs), or for a decentralized campus environment (such as a university), OS/2 Warp Connect's OS/2 Peer is ideal. However, IBM LAN Server 4 has several advantages when your network begins to grow. LAN Server 4 resources can be centrally managed, and security is implemented through the domain controller concept. (OS/2 Peer cannot be a domain controller, but it does not require a domain controller to establish connections with other peers.) Also, LAN Server 4 will outperform OS/2 Peer as your network grows (especially LAN Server 4 Advanced). IBM LAN Server 4 also has a unique feature for OS/2 Warp clients called the Network Applications folder. Without touching (electronically, humanly, or otherwise) any OS/2 Warp clients, a network administrator can create icons for applications stored on the server. These icons automatically appear in the Network Applications folder when an OS/2 Warp user logs in, complete with any special settings required. This feature makes deploying a new network application much easier. As a rule of thumb, OS/2 Peer works well with networks of 10 or fewer PCs. Beyond 8 PCs, start considering IBM LAN Server 4 Entry. Beyond about 40 PCs, start considering IBM LAN Server 4 Advanced. There's significant overlap in these rules of thumb, depending on what you need out of your network. There are no hard and fast rules. Q: Can I manage OS/2 Peer from somewhere else on the network? A: For user IDs, groups, and passwords (User Profile Management), yes, you can. However, without some remote control software (such as IBM's DCAF, KopyKat, Poly/PM, etc.) you cannot manage OS/2 Peer shared resources remotely using the graphical application, "Sharing and Connecting." You can, however, use the command NET ADMIN (from the command line) to remotely administer OS/2 Peer shared resources. Q: Other people on my network are using Windows for Workgroups or Windows NT. How do I browse the "workgroups" or "domains" these people use? A: You can define up to four domains (or workgroups) which can be browsed by using a command such as: NET CONFIG REQ /OTH:dom1,dom2,dom3,dom4 where dom1, dom2, dom3, and dom4 are the names of the four domains. However, you must know the names of these domains in advance. (This answer courtesy Charlie Brown, IBM Austin.) Q: Are there any "gee whiz" features in OS/2 Peer? A: You bet. To amaze and impress your friends, try the following: - With two OS/2 Peer PCs, try "crossplaying" of multimedia files. One OS/2 Peer delivers audio or video to the other (and vice versa) for playback at the same time (using shared drives or directories). See how far you can push your PCs. - Set up an OS/2 Peer server on the Internet! OS/2 Peer can work with NetBIOS over TCP/IP, so you can share out a drive or directory (read-only access recommended!) to other OS/2 Peer users on the Internet. Use the MPTS program to set up. - Drag and drop printers and folders (directories) to create a new shared resource using the Sharing and Connecting application. - OS/2 Peer has auditing/logging and REXX interface capabilities. You can monitor access to your OS/2 Peer resources, and you can write REXX scripts to automate routine tasks. - Use the new Network Clipboard/DDE program to cut/paste across the network (or, if using NetBIOS over TCP/IP, even the Internet). Network Messaging can be used to send alerts (such as, "I'm turning off my PC now") and other messages to other users across the network. Q: What exactly is the Lotus Notes Express "Plus 2"? A: Regular Lotus Notes Express includes only five application templates. The Lotus Notes Express software includes two extra application templates as a bonus. Lotus considers OS/2 Warp Connect as a full Lotus Notes Express client so, if you ever need to upgrade to the standard Lotus Notes client software for OS/2 Warp, you can do so for an upgrade price (not full price). Note that the capabilities of a Lotus Notes client are determined at the server. You need not reinstall your Lotus Notes software if you upgrade to the full client capabilities -- Lotus Notes Express "Plus 2" provided with OS/2 Warp Connect is the full software with a license for Express "Plus 2" function. Q: I've installed Lotus Notes, provided with OS/2 Warp Connect, but it doesn't want to start when I double click on the icon. What should I do? A: Try running $LNOTES.EXE directly (instead of through NOTES.EXE). You can change the settings of the Lotus Notes program object to run this executable file instead. Q: What is AskPSP? A: AskPSP is a technical support database shipped on CD-ROM, based on IBM's own technical support services. It includes answers to frequently (and less than frequently) asked OS/2 Warp questions. A friendly front-end application, an expert system tool which accepts plain English questions, facilitates access to this support database. Q: What is First Failure Support Technology/2? A: FFST/2 is software which allows network administrators (mainly at large corporate sites) to monitor and respond to errors which occur on OS/2 Warp PCs, over the network. Q: What is Network SignON Coordinator? A: NSC is software which allows single sign-on to a variety of systems on your network. Q: When I use the Remote Installation program in OS/2 Warp Connect, to install OS/2 Warp Connect across a network, only one PC can "pull" the code at a time. Can I raise this limit? A: Yes. By default, only one remote PC can install OS/2 Warp Connect from the PC where the Remote Installation program is running. This limit is enforced to avoid network congestion and "thrashing" of the CD-ROM (where OS/2 Warp Connect code is usually obtained). However, you can increase this limit by editing the \GRPWARE\CLIENTS\GRPWARE.INI file so that MAXCLIENTS=1 is changed to the number of simultaneous connections allowed, for example MAXCLIENTS=5 Other changes are recommended as well (see the next question). Q: Is there a way to start the Remote Install "code server" without having to answer all those questions every time? I just want the code server to be running whenever I start up my OS/2 Warp Connect PC. A: Yes. However, if you are using your OS/2 Warp Connect system for other things while other PCs on the network are trying to install OS/2 Warp Connect from your PC, you must make some other changes as well to increase the tolerance of NetBIOS to retries. To start the Remote Install server by itself, without answering any questions about building diskettes, use the command: START E:\CID\SRVIFS\SERVICE /INI=C:\GRPWARE\CLIENTS\GRPWARE.INI where E: is the CD-ROM drive containing the OS/2 Warp Connect CD and C: is the drive containing the OS/2 Warp Connect installation program (and the \GRPWARE directory). Change these drive letters in the above example if necessary. If you do any multitasking whatsoever, you should also make the following changes to two files, PROTOCOL.INI and IBMLAN.INI. PROTOCOL.INI is located in the \IBMCOM directory (or in the root directory of Remote Installation Diskette 1 created for the target system, where you must also make these changes) and IBMLAN.INI is located in \IBMLAN. PROTOCOL.INI: In the [netbeui_nif] section of the file: ADAPTRATE=0 TI=60000 T1=10000 T2=2000 NETBIOSTIMEOUT=2000 IBMLAN.INI: SESSTIMEOUT=300 and in the peer section of the file: SRVHEURISTICS (bit 15 set to 8) These changes and/or additions are quite similar to those recommended in the \IBMCOM\MACS\PRNANDIS.TXT file. Remember, you must make these additions to the PROTOCOL.INI file on Diskette 1 for each set of Remote Install diskettes you create. IBM recommends NetView/DM for OS/2 for "heavy duty" software distribution, but these methods may be sufficient, depending on your needs. Q: What protocols can I use for OS/2 Warp Connect Remote Installation? A: The simplified Remote Installation program bundled with OS/2 Warp Connect is designed to use NetBIOS connections only. It is possible to install OS/2 Warp Connect over the network using other protocols with add-on software (such as IBM's NetView/DM for OS/2). Q: Can I copy some files from the OS/2 Warp Connect CD to my hard disk to speed up Remote Installation? A: Yes. You will need enough disk space, certainly, to store OS/2 Warp Connect components required by Remote Install. Suppose, for example, your OS/2 Warp Connect CD is in Drive E and that you will be placing the OS/2 Warp Connect files in a directory called C:\CONNECT. First, using a text editor, modify the following two files: GRPWARE.INI LANSTART.INI located below the \GRPWARE directory on your hard disk. Wherever you see "E:\" you should replace it with "C:\CONNECT\" to redirect the Remote Installation. Second, using XCOPY /S /E, copy the contents of the CD to the C:\CONNECT directory. For example: XCOPY E:\* C:\CONNECT /S /E Remote Install does not actually require everything from the OS/2 Warp Connect CD. You may be able to get by with just the CID, GRPWARE, and OS2IMAGE directories, and the files VROBJ.DLL and OS2SE20.SRC. A: The Remote Installation diskettes I build for a ThinkPad 701 with IBM PCMCIA Token Ring don't seem to work right. What should I do? Q: Modify the PROTOCOL.INI file on Diskette 1 so that the following changes are made: MMIO=0xD400 RAM=0xD800 and that semicolons are removed in front of each of these parameters. You can also use the Settings button to make these changes at the time you create the two Remote Installation diskettes. Q: If I use Remote Installation, how do I add additional networking software later that I didn't install the first time? A: Activate the Remote Installation server and start your PC from the Remote Installation diskettes. Follow the instructions until you see a menu asking if you wish to install all of OS/2 Warp Connect or just Networking. Select Networking only, and proceed as directed. Q: How do I install the OS/2 Warp BonusPak, AskPSP, and Lotus Notes client software using Remote Installation? A: The built-in Remote Installation software is simplified and designed to get base OS/2 Warp Connect networking function installed quickly and easily. If you provide access to the AskPSP and Lotus Notes CD-ROMs somewhere on your network, they can be installed across the network (using OS/2 Peer logins, for example). AskPSP can be installed using the INSTASKP.EXE program (located in the AskPSP directory). Lotus Notes can be installed using the INSTPM.EXE program. The BonusPak expects to be installed from a particular drive (such as a CD-ROM) which has a drive letter assigned to it. Still, you can install the BonusPak across the network. Assume, for example, that all the BonusPak files have been copied to a directory on an OS/2 Peer system called SMITH, and that the directory containing the BonusPak has been given a resource name of BONUSPAK. The resource BONUSPAK has been defined as read-only to every user on the network. (In fact, this resource can be the BonusPak CD-ROM.) The following OS/2 batch file will allow you to install the BonusPak across the network, assuming you are logged on the network. echo Installing BonusPak... NET USE Y: /DELETE NET USE Y: \\SMITH\BONUSPAK Y: CD \US CALL INSTALL.CMD C: NET USE Y: /DELETE In other words, by using the NET USE command to assign drive letter Y: to the network directory \\SMITH\BONUSPAK, the OS/2 Warp BonusPak will install correctly. Note that you should not install the Internet Connection from the BonusPak on top of OS/2 Warp Connect. TCP/IP Version 3, part of the main installation, should be used instead. Q: I've used Remote Install to install OS/2 Warp Connect. Now I want to add a printer or some other feature. How do I tell Selective Install to retrieve code across the network? A: The answer to this question is similar to the last, namely that you can place the OS/2 Warp Connect CD-ROM (or a copy of it) somewhere on your network as a shared resource. Using the NET USE command, you can assign a drive letter to this shared resource. An OS/2 batch (.CMD) file can automate the process, and it would look something like this: @echo off echo Starting Selective Install... NET USE Y: /DELETE NET USE Y: \\SMITH\CD-ROM INSTALL NET USE Y: /DELETE assuming the OS/2 Warp Connect CD-ROM was placed on the machine SMITH and given a resource name of CD-ROM, and that a proper logon was in effect. The source directory for Selective Install becomes Y:\OS2IMAGE (or possibly \\SMITH\CD-ROM\OS2IMAGE if you wish to use Universal Naming Convention). Similar methods would be used for Novell NetWare servers. Q: Is it possible to have some sort of custom routine (such as installing applications) run automatically at the end of OS/2 Warp Connect's Remote Installation? A: Yes indeed. First, create a file called USER.CMD with the OS/2 batch commands (or REXX program) you wish to run at the conclusion of OS/2 Warp Connect's installation. Then copy this file to the \GRPWARE\CLIENTS\LADCLT directory on the OS/2 Warp Connect "code server." On the second diskette (Diskette 1) created for remote installation, modify CONFIG.SYS and add the following line: CALL=\OS2\CMD.EXE /Q /C COPY W:\USER.CMD \GRPWARE\CLIENTS\LADCLT When booting from the diskettes you may get an error. But, when the second phase of OS/2 Warp Connect installation starts, the USER.CMD file should be copied correctly to the remote (target) PC's hard disk. At the end of installation, USER.CMD will be run. One of the tasks USER.CMD should probably perform is to remove the above line from the PC's CONFIG.SYS, to prevent any error messages at bootup. In any event, any file by the name of USER.CMD in the \GRPWARE\CLIENTS\LADCLT directory on the target PC will be run at the conclusion of OS/2 Warp Connect installation. You can use any method you wish to move USER.CMD to this directory. (This answer courtesy Matt Hickmann, Chevron.) Q: Do I have to reinstall the base OS/2 Warp when upgrading to OS/2 Warp Connect, or should I just install the networking software? A: IBM recommends that you reinstall the base operating system at the same time you install OS/2 Warp Connect's networking components. The base operating system included with OS/2 Warp Connect contains the latest fix paks (up until the date it was sent to manufacturing). Your desktop and other customizations will be preserved. Q: Should I install the Internet Connection from the BonusPak on OS/2 Warp Connect? A: Unless you are NOT installing any networking software, no, you should not install the Internet Connection from the BonusPak on OS/2 Warp Connect. Installing TCP/IP Version 3 (part of the networking software included with OS/2 Warp Connect) gives you all the function (and more) of the dial-up Internet Connection (including dial-up capabilities). All other BonusPak applications may be safely installed on top of OS/2 Warp Connect regardless of configuration. Q: I get some error messages about LOG.SYS when I boot into OS/2 Warp Connect. What can I do? A: Use OS/2 Warp's Selective Install program to install Serviceability and Diagnostic Aids (one of the selections on the second panel). LOG.SYS (and other key files for FFST/2) are included with the base OS/2 Warp software. Or you can simply REM out these lines if you do not wish to use FFST/2. Q: Are any of the regular OS/2 Warp BonusPak applications enhanced or improved as a result of OS/2 Warp Connect? A: Yes. The OS/2 Chess application can be used to play chess across a network (NetBIOS, NetBIOS over TCP/IP, or NetBIOS over IPX protocols). Also, IBM's Person to Person can be used across a network for workgroup and video conferencing. Q: Can I uninstall all or part of OS/2 Warp Connect? A: You bet. Uninstall programs are supplied for each individual networking component and for OS/2 Warp itself. In fact, you should use these uninstall programs if for whatever reason you wish to reinstall any OS/2 Warp Connect networking component. Q: Where can I get additional information on OS/2 Warp Connect? A: The printed manuals included with OS/2 Warp Connect include basic installation, setup, and operation instructions. For more detailed instructions, be sure to consult the various pieces of online documentation located on the OS/2 Warp Connect CD-ROM. Also, additional printed publications are available from IBM if you need hardcopy. The IBM part numbers for extra hardcopy manuals are included in the OS/2 Warp Connect announcement letter. Timothy F. Sipples | Certified OS/2 Engineer (312) 245-4003 | IBM Personal Software Marketing FAX (312) 245-7624 | One IBM Plaza (07/SS4), Chicago, IL, 60611 Tie Line: 261-xxxx | Internet: tsipple@vnet.ibm.com