home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
NW_CID.FAX
< prev
next >
Wrap
Text File
|
1994-11-26
|
11KB
|
245 lines
NetWare Redirected Install fax 8/11/93
REDIRECTED INSTALLATION FROM A NETWARE SERVER
DESCRIPTION OF SYMPTOMS
Some procedures are needed on how to install OS/2 Version 2.1
GA (6.514 L or M) code from a Netware server.
SUMMARY OF RESOLUTION
The steps below describe the installation of OS/2 Version 2.1 GA
code from a Netware code server. In the example that follows,
Netware Version 3.11 and 4.0 (4.0 using bindery emulation),
Netware Requester Version 2.01 code, and OS/2 Version 2.1 GA base
are used.
DETAILS OF RESOLUTION
1. This step installs OS/2 Version 2.1 disk images and creates a
CID user.
a. Login to server as SUPERVISOR.
b. Create a host directory for the OS/2 disk images.
Example: OS2IMG
c. Create a CID user ID for the CID process.
Example: CID_USER
d. Take CID_USER out of the group "everyone" and give the
trustee rights to OS2IMG (R F).
e. Create a user login script for CID_USER and map Z: to
the host directory that was created for the OS/2
images.
Example: MAP Z:=fileserver\SYS:OS2IMG
NOTE: Be sure to use SYSCON from the SYS:PUBLIC\OS2
directory.
f. Unpack the archive "CID" from diskette 7 of the OS/2
Version 2.1 installation diskettes. From the OS/2
prompt, type:
UNPACK A:CID
(diskette 7 should be in drive A:)
g. Install the diskette images to the code server. One
of the utilities just unpacked is called SEIMAGE.EXE.
This utility will install the disk images. SEIMAGE is
invoked by entering the following command:
SEIMAGE /S:<drive> /T:<drive><Path>
where /S = source drive and /T:= target drive.
Example: SEIMAGE /S:A:/T:F:\OS2IMG
This utility does prompt when to place the original
OS/2 installation diskettes into the source drive. The
images will be created on the target drive.
2. This step creates the installation diskettes and modifies
the CONFIG.SYS file. Two formatted HD diskettes are
required.
a. Run SEDISK.EXE. SEDISK is invoked by entering:
SEDISK/S:<sourcepath> /T:<target path>
Example: SEDISK /S:F:\OS2IMG /T:A:
This command creates two boot diskettes from images
in the OS2IMG subdirectory. The first diskette will
be a copy of the OS/2 "Install" diskette. The second
diskette created will be called the LT diskette.
NOTE: Diskette images must be installed.
b. Copy the network drivers to the root of the LT diskette.
Below are the files needed from the NETWARE subdirectory:
NWCONFIG.DLL
IPXCALLS.DLL
NWCALLS.DLL
LSL.SYS
TOKEN.SYS (or the driver you are using)
ROUTE.SYS
NWDAEMON.EXE
IPX.SYS,
NWREQ.SYS
NWIFS.IFS,
NWREQOS2.MSG
NETAPI.DLL.
If the NET.CFG is setup to pass INT, PORT, and/or MEM
addresses to the network driver, then include it in the
LT diskette.
c. Create a directory named OS2. Copy CMD.EXE from the
root directory into the OS2 directory.
d. Edit the CONFIG.SYS file on the LT diskette. The
CONFIG.SYS file should look like:
REM - CONFIG.SYS for CID LT diskette
buffers=32
iopl=yes
memman=noswap
protshell=sysinst1.exe
rem - following line is for Dialog-driven
installation
SET OS2_SHELL=CMD.EXE /K A:\STARTPDI.CMD
rem - following line is for Response file
installation
REM- SET OS2_SHELL=CMD.EXE /K A:\STARTRFI.CMD
protectonly=yes
LIBPATH=.;\;\OS2\DLL;R:\
ifs=hpfs.if$ /c:64
pauseonerror=no
codepage=850
devinfo=kbd,us,keyboard.dcp
devinfo=scr,ega,vtbl850.dcp
device=\dos.sys
device=\mouse.sys
SET PATH=\;\OS2\SYSTEM;\OS2\INSTALL;Z:\DISK_1;
SET DPATH=\;\OS2\SYSTEM;\OS2\INSTALL;R:\;
set keys=on
basedev=print01.sys
basedev=ibmflpy.add
basedev=ibm1s506.add
basedev=ibm2flpy.add
basedev=ibm2adsk.add
basedev=ibmscsi.add
basedev=ibmint13.i13
SET SOURCEPATH=Z:\
DEVICE=A:\LSL.SYS
DEVICE=A:\TOKEN.SYS
DEVICE=A:\IPX.SYS
DEVICE=A:\NWREQ.SYS
IFS=A:\NWIFS.IFS
RUN=A:\NWDAEMON.EXE
rem - the following statement is for a Dialog-driven
installation
CALL=\OS2\CMD.EXE /K LOOP.CMD
rem - END CONFIG.SYS
The above CONFIG.SYS will work for both response and
dialog driven installations. This file is setup for a
response type installation. Notice the SET and CALL
statements that must be changed for dialog driven
installations. The lines in all caps are lines that need
to be added or modified.
3. This step creates CMD files for dialog-driven and response
file installations on the LT diskette.
a. The LOOP.CMD file should look like:
REM-LOOP.CMD
@echo off
:start
if exist L:\OS2\login.exe goto exit
echo Waiting for NETWORK connection...
goto start
:exit
REM - on 4.0 server use /B after username...
L:\OS2\login CID_USER
exit
NOTE: A servername may want to be added to the login
command for multi-server configurations.
Example: L:OS2\login <servername>/CID_USER
b. The STARTPDI.CMD file should look like:
REM-STARTPDI.CMD for LT diskette
@echo off
IF exist Z:\DISK_1\sysinst2.exe goto foundit
echo SYSINST2.EXE NOT FOUND! Check CID_USER OS/2
login script! goto end
:foundit
echo Found SYSINST2.EXE....
A:
Z:\disk_1\sysinst2.exe Z:\
:end
c. The STARTRFB.CMD file should look like:
rem - STARTRFB.CMD for CID LT diskette Response file
installation
@echo off
:start
if exist L:\OS2\login.exe goto cidlogin
echo Waiting for NETWORK connection.....
goto start
:cidlogin
rem - for 4.0 server use /B after username...
L:\OS2\LOGIN CID_USER
A:
SET REMOTE_INSTALL_STATE=0
rem-SEINST will not write to mapped drive and there
is limited disk
rem-space on A: So..
if exist login.log del login.log
Z:\SEINST /T:C: /S:Z:\ /R:Z:\CID_USER.RSP
/L1:A:\INSTALL.LOG
NOTE: If the response file installation target drive is
different than drive C:, change:
/T:C:
to
/T:X:
where X is the target drive.
/R: designates the path to the response file that will
be used when SEINST calls RSPINST.
/L1: is the path and filename of the log file that SEINST
will write.
This is mandatory because SEINST will not write to a
Netware Mapped drive.
4. This step creates the response file.
a. Copy SEINST.EXE, RSPINST.EXE, and the response file to
the code server.
NOTE: SEINST.EXE and RSPINST.EXE were unpacked from
diskette 7 in the CID archive. These files should be
unpacked to C:\OS2\INSTALL.
b. Copy SEINST.EXE, RSPINST.EXE, and the Response file to:
Z:\
c. The CID_USER.RSP file should look like:
AlternateAdapter=0
APM=0
BaseFileSystem=2
CDROM=0
SCSI=0
CountryCode=001
CountryKeyboard=US
DefaultPrinter=0
DiagnosticAids=1
DisplayAdapter=0
Documentation=1
DOSSupport=1
WIN-OS/2Support=1
DPMI=1
ExitOnError=1
Fonts=1
FormatPartition=1
MigrateConfigFiles=1
MoreBitmaps=1
Mouse=1
MousePort=0
OptionalFileSystem=1
OptionalSystemUtilities=1
PCMCIA=1
PrimaryCodePage=1
PrinterPort=1
ProcessEnvironment=1
ProgressIndication=1
RebootRequired=0
REXX=1
SerialDeviceSupport=1
SourcePath=Z:
TargetDrive=C:
ToolsAndGames=1
For more information on the above values, review the sample
response file that was unpacked into the \OS2\INSTALL
subdirectory.
5. A batch file or CMD file may be started after the install
by adding a line at the end of the response file:
USEREXIT=Z:\DOTHIS.CMD
If REXX support is needed to run a CMD file, add the REXX
support files to the code server and map R: to that
directory. REXINIT.EXE may be needed for REXX support.
Consult the Red Book GG24-3780-00 "OS/2 2.0 Remote
Installation and Maintenance" and 59G4914 "NTS/2 Redirected
Installation and Configuration Guide" for more information
on using REXX during remote installations.
12/31/99