PMAC.OS2

SSW-Parallel port driver for adapter without NIC.

DEVICE=\IBMCOM\MACS\PMAC.OS2

If there is a printer also connected to the parallel port there must be the BASEDEV=PRINT01(or 2).SYS /IRQ set. To switch between PMAC and printer got to the drive:/IBMCOM directory and execute PMAC.EXE -R. To re-establish connection with PMAC type PMAC.EXE -C.

JERRY ROWE's WARP REMOTE INSTALL PAGE

This page is a preliminary FAQ about installing OS/2 Warp 4 over a Laplink cable from a server to a client.

Set the server up to use the parallel port (SSW Parallel MAC driver) network driver. You do this from MPTS [just type MPTS at the command line]. Select the driver, and add IBM OS/2 NETBIOS as a protocol.
Then edit the SSW Parallel MAC driver in MPTS and note its address. It should be 40000000000A.
Then open up the OS/2 Warp Remote Install object. Create the remote install disks. Be sure to use the same SSW Parallel MAC driver.
Then edit the protocol.ini file on the 2nd disk. Inside it, insure that the MAC address is something other than 40000000000A. Using 40000000000B will work fine.
Save the file.
Now, shutdown and reboot the machine.
Then examine \ibmcom\lantran.log and look for the reference to the adapter # for the parallel port adapter. If you have another adapter in the Server, the number may be 1, otherwise it will be 0.

Find Server Adapter # Note that the Adapter #=1 in the file below. If your parallel port is setup for adapter #=0, then lantran.log will be different.

 ==file lantran.log=========================================
 PARALLEL PORT MAC V 1.0 by Savant Software Inc. Copyright (C) 1994, 1995
 SAVANT SOFTWARE: PORT ADDRESS(ES): LPT1
 SAVANT SOFTWARE: PORT ADDRESS CONFIGURED: LPT1(378)
 IBM LANVDD is loaded and operational.
 IBM OS/2 LAN Netbind
 IBM LANDD is accessing IBM 802.3 LAN Interface.
 Adapter 1 was initialized and opened successfully.
 Adapter 1 is using node address 40000000000A. The Token-Ring
 format is 02000000
 IBM LANDD was successfully bound to MAC: pmac_nif->VECTOR.
 ==end file lantran.log=========================================

Install service.exe and other files.

If they were not installed during the Warp install, follow these instructions.

Given that my CD-ROM drive is I:, and My Warp 4 drive is H:, issue this command:

I:\CID\SRVIFS\thinsrv /s:. /t:h:\cid\SRVIFS /r:h:\ibminst\tables\service.ini /tu:h:\

THINSRV completed successfully.

This creates a line in startup.cmd and creates startup.cmd if necessary.

START H:\CID\SRVIFS\SERVICE.EXE /INI=SERVICE

Thinsrv also adds:

 h:\cid\SRVIFS;

to the PATH and DPATH statements in CONFIG.SYS.

Because these changes will not take effect until a reboot, the command in STARTUP.CMD will not work until then.

However, you can:

 cd \cid\srvifs service /ini=service

to start it right away from the command line.

You will probably want to remove the commands from Startup.cmd at this time to prevent the Server facility from running all the time.

You may also want to create another cmd file with the service command in it if you would like to run it interactively.

Edit h:\cid\service.ini

Note Alias and Path near bottom. Should be correct for the CD Note Adapter #. Should match # from Lantran.log.

;SRVIFS INI file for OS/2 Warp Remote Install Server - 7CPESGDV
Name = 7CPESGDV
GroupName = NO
Adapter = 1
MaxClients = 5
MaxFiles = 9999
ClientWorkers = 8
Path = I:\
Alias = ReadOnly,Single,CDROM,I:\
Alias = ReadWrite,Single,STATUS,H:\IBMINST\RSP\REMOTE

With these changes made, shut down the computer and reboot. After it comes up, the GUI front end for the Remote install should work.

===Config.sys on disk 1 ===================
CALL=A:\SRVATTCH.EXE z: \\7CPESGDV\CDROM
DEVICE=A:\SRVIFS.SYS
IFS=A:\SRVIFSC.IFS * /T
CALL=A:\SRVATTCH.EXE w: \\7CPESGDV\STATUS
RUN=Z:\CID\LOCINSTU\SRVREXX.EXE
libpath=.;\os2\install;\os2\dll;z:\cid\locinstu;
set os2_shell=cdboot.exe
set oemprogram=\ibminst\npconfig.exe
set exitwhendone=1
set ADAPTER_NIF=PMAC.NIF
set SRVNAME1=7CPESGDV
set SAVECONNECT=1

Now, change to H: [warp 4 drive] and start server.

cd \cid
SERVICE.EXE /INI=SERVICE

Now, boot the client off the disk set.

Should work. If it does not, check the hardware configuration of the parallel ports and insure they are set to bi-directional if that option is offered.

I successfully installed Warp 4 on a ThinkPad using this method.

After the install, you should also be able to network between the two computers over the Laplink cable using OS/2 Peer.

Product Support
OS/2 1.3
OS/2 2.0
OS/2 2.1
OS/2 2.11 SMP
OS/2 Warp 3
OS/2 Warp Connect	S
OS/2 Warp 4	S
OS/2 Warp Server for e-Business	S