Manually Installing File/Print Client

By Daniel M. Pomerantz
 * 1998-02-25


 * GENERAL DISCLAIMER: I MAKE NO GUARENTEE THAT THIS WILL WORK, OR NOT BREAK ANY COMPUTER. THIS IS WHAT I DID ON MY OS/2 WARP 4 (NO FIXPAK) COMPUTER, AND I HAVE BEEN ABLE TO USE THE PEER SERVICES ON IT WITHOUT PROBLEM. THIS PROCESS IS NOT FOR THE SQUEEMISH AND SHOULD ONLY BE PERFORMED BY SOME ONE WHO KNOWS WHAT HE/SHE IS DOING AND HIS/HER WAY AROUND AN OS/2 SYSTEM, AND ITS NETWORKING COMPONENTS.  PLEASE BE CAREFUL.  I MAKE NO GUARENTEES,  BUT IF ANY ONE HAS ANY PROBLEMS OR QUESTIONS, FEEL FREE TO ASK.  IF I KNOW THE ANSWER, I SHALL DO MY BEST TO GET IT TO YOU.  ELSE, I SUGGEST YOU CONSULT ANOTHER SOURCE.  ONES WHICH I HAVE FOUND USEFUL ARE THE #OS/2 AND OS/2WARP CHANNELS ON EFNET IRC, AND THE COMP.OS.OS2.NETWORKING.MISC NEWSGROUP ON USENET.

The PEERINST.EXE program which comes with OS/2 and its File/Print and PEER client does not work on systems with various conditions, including many for no apparent reason. IBM has failed to issue a working fix for the issue, so I had to manually install the client to get SMB based File/Print networking functional. This is a simple text file which explains how to do it.

1)  The first step is to unzip the files.  On the WARP4 installation CD, go to the directory \CID\IMG\IBMPEER.  You will find sub-directories named IBM100R? where ? is 1 through 5.  Copy each of those onto a hard drive directory.  I used C:\NETTEMP.  Then go into each of those five directories on the hard drive and unzip EVERY zip file.  There may be one coflict. error.txt, just overwrite that.  After they are all unzipped, delete all of the zip files.  This is not NEEDED, but will help save space.  Also, in the IBM100R1 directory, delete the other files which are in the root of that directory.  Again, they are not needed.  When you are finished, each of the five directories will have one or more of the following sub-directories in it:

IBMLAN MUGLIB OS2

Consolidate all of those into one tree. There are likely to be conflicts, but from what I can tell, all of the conflicts are the exact same files and can be over written. I used a Norton Commander clone to make it easier, but you can do what you choose. I also moved instead of copiing to save time and space.

2) This step is not required, but I do suggest it. Install the latest FixPak to the new tree of files.  It will pick it up as a complete installation and do what it needs.

3) If you have not already done so, install any other components of your networking,especially MPTN and the IBMCOM components which are required. With these you will install and bind the neccessary NIC drivers and bind the neccessary protocols (NetBEUI or TCPBEUI) to them.  None of the files installed by these utils will need to be edited except for your config.sys.

4) Create the following directories on your Boot Partion: \IBMLAN and \MUGLIB. Copy (or move) the complete directory trees that you just made of the same name and updated to those directories (xcopy /s/e).  The OS2 directory from the tree you just made will also have to be copied.  It should have three subdirectories in it (DLL, HELP, and INSTALL).  Simply copy the contents of those directories to the directories of the same name under \OS2 on your boot partition.

5) Make the following changes to your config.sys

Add the following paths to the beginning of your LIBPATH statement: C:\MUGLIB\DLL;C:\IBMLAN\NETLIB

Add the following paths to your PATH statement right before any references to C:\OS2: C:\IBMLAN\NETPROG;C:\MUGLIB

Add the following paths to your DPATH statement right before any references to C:\OS2: C:\IBMLAN\NETPROG;C:\IBMLAN;C:\MUGLIB

Find one or more of the following statements in your config.sys: DEVICE=C:\IBMCOM\PROTOCOL\TCPBEUI.OS2 DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2 DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2

Ensure that the NETBIOS.OS2 line comes AFTER either of the other two. Add the following lines after it: REM ********************START IBMLAN ******************************* DEVICE=C:\IBMLAN\NETPROG\RDRHELP.200 IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N RUN=C:\IBMLAN\NETPROG\LSDAEMON.EXE DEVICE=C:\IBMLAN\NETPROG\VNETAPI.OS2 RUN=C:\IBMLAN\NETPROG\VNRMINIT.EXE SET NWDBPATH=C:\IBMLAN\NETPROG SET DLSINI=C:\IBMLAN\NETPROG\NETGUI.INI SET INIT_FILE_NAMES=netgui SET INIT_FILE_RANGES=200 SET WPS_COMMUNICATION=YES REM *********************END IBMLAN**********************************

6)Create the following directories on your boot partition: \IBMLAN\ACOUNTS \IBMLAN\USERS

7) Copy the file \IBMLAN\INSTALL\NET.ACC to C:\IBMLAN\ACCOUNTS\NET.ACC

8) Create the file C:\IBMLAN\IBMLAN.INI or copy a previously created one. For a  sample file and advice on what all the settings mean, consult the INF files.

9)  Reboot the computer and it should work.

Typing LOGON will start the requester service and prompt you for a logon. The default is "USERID" and "PASSWORD" Once logged on, MUGACCTS will allow you to create and change accounts (as will NET USER), and UPMCSET will need to be used in order to use long group and uid names if you have an HPFS drive. The WPS icons and other extensions will not be created, but I have not found them required. If any one is interested in creating a REXX script to create these icons/extensions, please let me know. Also, if any one is interested in a REXX script which will do this automatically, please let me know.