This is a lengthy posting.
Last week I posted a note containg the Dos/Windows rescue disks that we had
developed. They were good for doing a "Standalone" restore of a machine that
had lost it's whole hard drive, or if it became unstable - Windows doesn't
work, etc.
This note addresses a similar system for OS/2, based on the OS/2 command line
ADSM client. Because you can do a one pass restore with the OS/2 client (no
640K limit), we are now using this as the preferred restore, even on
DOS/Windows machines. More about that later. For OS/2, the first 2 of the 3
disks are very similar to the OS/2 installation disks. See the IBM Red Book
on OS/2 redirected installs for details on detting these up specifically.
Disk 1 (Internally labeled Disk 0)is an image of the OS/2 Installation disk -
as follows:
Directory of A:\
OS2BOOT 1099 1-28-94 10:01p
OS2KRNLI 739474 2-12-94 4:55p
SYSINSTX COM 39472 1-28-94 10:02p
OS2LDR 28160 1-28-94 10:00p
FC0400 BIO 11264 11-02-93 7:05p
FC0500 BIO 9728 11-02-93 7:05p
F80000 BIO 9728 11-02-93 7:05p
OS2LDR MSG 8480 1-28-94 10:01p
F80100 BIO 8704 11-02-93 7:05p
OS2DUMP 7576 1-28-94 10:01p
F80200 BIO 7680 11-02-93 7:05p
F80600 BIO 7168 11-02-93 7:05p
W060100 BIO 6656 11-02-93 7:05p
FC0403 BIO 5632 11-02-93 7:05p
F80C00 BIO 5632 11-02-93 7:05p
F80904 BIO 5632 11-02-93 7:05p
F80903 BIO 5632 11-02-93 7:05p
F80404 BIO 5632 11-02-93 7:05p
F80403 BIO 5632 11-02-93 7:05p
F80D01 BIO 5120 11-02-93 7:05p
F80D00 BIO 5120 11-02-93 7:05p
F80902 BIO 5120 11-02-93 7:05p
F80402 BIO 5120 11-02-93 7:05p
W020101 BIO 4608 11-02-93 7:06p
F81B00 BIO 4096 11-02-93 7:05p
W050101 BIO 3072 11-02-93 7:06p
W020100 BIO 3072 11-02-93 7:06p
W050100 BIO 2560 11-02-93 7:05p
000000 BIO 2560 11-02-93 7:05p
F88000 BIO 2048 11-02-93 7:05p
W0F0000 BIO 1536 11-02-93 7:05p
W050000 BIO 1536 11-02-93 7:05p
F81000 BIO 1536 11-02-93 7:05p
F80A01 BIO 1536 11-02-93 7:05p
F80A00 BIO 1536 11-02-93 7:05p
F80703 BIO 1536 11-02-93 7:05p
F80702 BIO 1536 11-02-93 7:05p
F80701 BIO 1536 11-02-93 7:05p
F80700 BIO 1536 11-02-93 7:05p
F80A02 BIO 1024 11-02-93 7:05p
F80704 BIO 1024 11-02-93 7:05p
OS2VER 89 11-02-93 7:27p
ABIOS SYS 427 11-02-93 6:58p
BUNDLE 461463 2-16-94 10:40p
BLISTLAY OUT 1639 1-29-94 10:55p
45 file(s) 1440967 bytes used
12288 bytes free
Disk 2 (Labeled DISK 0 - This is requried) is as follows:
Directory of A:\
$ICPMOS2 SYS 5568 2-14-94 1:09a
ACSNETB DLL 3349 4-13-94 11:17a
DOSCALL1 DLL 91402 2-02-94 11:01p
CMD EXE 91136 1-29-94 2:29a
OS2CHAR DLL 56080 1-29-94 12:52a
OS2DASD DMD 33610 1-29-94 1:06a
SESMGR DLL 32806 1-29-94 12:53a
KBD01 SYS 29525 1-29-94 2:49a
IBM1FLPY ADD 28526 1-29-94 1:11a
IFCONFIG EXE 13023 4-29-93 3:06p
COUNTRY SYS 25610 1-29-94 2:52a
NPXEMLTR DLL 25280 1-29-94 3:12a
SIPANEL1 DLL 25152 1-28-94 11:52p
CNTRL EXE 10185 8-03-93 11:05a
IBM1S506 ADD 22781 1-29-94 1:13a
IBM2M57 ADD 21182 1-29-94 1:20a
QUECALLS DLL 15282 1-29-94 1:42a
IBMTOKCS OS2 27188 6-02-94 9:01a
HARDERR EXE 14824 1-29-94 12:53a
TCPIPDLL DLL 40995 12-17-92 6:00a
OS2SCSI DMD 10846 1-29-94 1:08a
IBM2ADSK ADD 10838 1-29-94 1:15a
VTBL850 DCP 10478 1-29-94 1:59a
BVHINIT DLL 9443 1-29-94 12:07a
IBMINT13 I13 9728 1-29-94 1:18a
PRINT01 SYS 9134 1-29-94 3:17a
IFNDIS SYS 30263 3-26-92 4:16p
INET SYS 75040 3-27-92 1:14p
OS2ASPI DMD 6302 1-29-94 1:08a
SCREEN01 SYS 6124 1-29-94 3:21a
KEYBOARD DCP 5177 1-29-94 2:45a
TESTCFG SYS 4406 1-29-94 3:45a
SYSINST1 EXE 4240 1-29-94 12:17a
PCMCIA SYS 34903 1-31-94 1:04a
CLOCK01 SYS 3619 1-29-94 2:18a
VIOCALLS DLL 1825 1-29-94 12:52a
DOS SYS 1142 1-29-94 2:30a
NAMPIPES DLL 1024 1-29-94 1:40a
MOUCALLS DLL 1010 1-29-94 1:00a
KBDCALLS DLL 858 1-29-94 1:00a
CONFIG SYS 1319 10-10-94 12:44p
NLS DLL 466 1-29-94 1:39a
MSG DLL 508 1-29-94 1:40a
SYSLEVEL OS2 165 1-29-94 8:29p
BVSCALLS DLL 454 1-29-94 12:49a
BMSCALLS DLL 398 1-29-94 12:47a
BKSCALLS DLL 401 1-29-94 12:46a
ANSICALL DLL 438 1-29-94 12:45a
LANMSGDD OS2 3572 4-13-94 11:41a
DISK NUM 30 1-29-94 10:56p
LANMSGDL DLL 2580 4-13-94 11:41a
LANMSGEX EXE 1099 4-13-94 11:41a
LANTRAN LOG 339 5-20-95 9:35p
LT0 MSG 12328 4-13-94 11:41a
LT2 MSG 2564 4-13-94 11:37a
HPFS IFS 133698 1-28-94 11:23p
VPCMCIA SYS 592 4-22-93 7:19p
NETBIND EXE 13657 4-13-94 11:38a
ICRMU01 SYS 6082 1-27-94 1:05a
PRO MSG 2127 4-13-94 11:38a
PROTMAN OS2 12148 4-13-94 11:38a
UPM DLL 19277 7-07-94 11:37a
XI1 MSG 8497 9-25-92 8:15a
UHPFS DLL 181408 1-28-94 11:59p
TCP CMD 75 10-07-94 1:12p
CLOCK02 SYS 3710 1-29-94 2:18a
KBD02 SYS 25941 1-29-94 2:50a
LTG MSG 4046 9-09-94 2:34p
IBM2SS01 SYS 13312 2-07-94 1:20a
PROTOCOL INI 525 10-06-94 2:36p
PING EXE 14106 4-20-93 5:50p
PRINT02 SYS 8118 1-29-94 3:17a
CONFIG LAP 2137 10-07-94 11:45a
ETC <DIR> 10-07-94 12:13p
TMP <DIR> 10-07-94 12:13p
ROUTE EXE 13487 12-10-92 8:33p
SCREEN02 SYS 6366 1-29-94 3:21a
IBM2FLPY ADD 13913 1-29-94 1:14a
IBM2SCSI ADD 25261 1-29-94 1:17a
CONFIG TPD 1319 10-10-94 12:44p
CONFIG MC 1319 4-26-95 2:33p
81 file(s) 1387686 bytes used
30208 bytes free
The TMP subdirectory is empty. The ETC subdirectory contains the following:
Directory of A:\etc
. <DIR> 10-07-94 12:13p
.. <DIR> 10-07-94 12:13p
PROTOCOL 871 3-14-91 1:54p
SERVICES 5089 4-27-93 9:44a
4 file(s) 5960 bytes used
30208 bytes free
The Config.sys file is as follows:
buffers=32
iopl=yes
memman=noswap
IFS=HPFS.IFS /CACHE:64
protshell=a:\cmd.exe
rem set os2_shell=O:\DISK_1\SYSINST2.EXE O:\
os2_shell=a:\cmd.exe
diskcache=64,LW
protectonly=yes
libpath=.;\;\os2\dll;
rem ifs=hpfs.ifs /c:64
pauseonerror=no
codepage=850
devinfo=kbd,us,keyboard.dcp
devinfo=scr,ega,vtbl850.dcp
device=\dos.sys
set path=\;\os2;\os2\system;\os2\install;A:
set dpath=A:;\;\os2;\os2\system;\os2\install;
set keys=on
basedev=print01.sys
rem basedev=print02.sys
basedev=ibm1flpy.add
rem basedev=ibm2flpy.add
rem basedev=ibm2scsi.add
basedev=ibm1s506.add
basedev=ibm2adsk.add
basedev=ibm2m57.add
basedev=ibmint13.i13
basedev=os2dasd.dmd
device=\testcfg.sys
device = pcmcia.sys
device = vpcmcia.sys
REM device=\refpart.sys
rem *** Start of ThinLAPS additions ***
device = lanmsgdd.os2
run = lanmsgex.exe
device = protman.os2
rem device = IBMTOK.OS2
device = ibmtokcs.os2
rem device = d:\IBMCOM\MACS\smartnd.os2
device = inet.sys
device = ifndis.sys
run = netbind.exe
set etc=a:\etc
set tmp=a:\tmp
timeslice=100,100
run=a:\cntrl.exe
Rem added with ADSM V1R2 Install
SET DSM_CONFIG=A:\DSM.OPT
SET DSM_DIR=A:\
SET DSMG_CONFIG=A:\DSM.OPT
SET DSMG_DIR=A:\
SET DSMG_FONT=10.Helv
DEVICE=$ICPMOS2.SYS
DEVICE=IBM2SS01.SYS /S0=2
DEVICE=ICRMU01.SYS
Please note that the above configuratoion is set to run on a Thinkpad; if you
need to run a a Microchannel device, adjust the device drivers accordingly.
The ones needed are included, but treated as comments, simply swap the
appropriate statements and you should be in business.
The TCP.BAT file is as follows:
ifconfig lan0 %1 netmask 255.255.252.0
route add default 157.209.64.8 1
Disk 3 is as follows - The label is optional
Directory of A:\
DLL <DIR> 10-12-94 3:10p
DSMC EXE 493092 5-25-94 8:30a
DSCAMENG TXT 203200 5-25-94 8:30a
DSM OPT 3220 5-20-95 9:29p
FDISK COM 108196 2-11-94 5:27p
FORMAT COM 66832 1-29-94 2:42a
CHKDSK COM 68656 1-29-94 2:16a
LABEL COM 33805 1-29-94 2:49a
UHPFS DLL 181408 1-28-94 11:59p
NAMPIPES DLL 1024 1-29-94 1:40a
SYSINSTX COM 39472 1-28-94 10:02p
TCPIPDLL DLL 40995 12-17-92 6:00a
LANMSGDL DLL 2580 4-13-94 11:41a
TMP <DIR> 10-13-94 7:27a
OSO001 MSG 171975 4-20-94 10:33p
LANTRAN LOG 441 3-30-95 10:17a
DSMERROR LOG 1273 5-20-95 11:03p
ADSM <DIR> 11-02-94 1:55p
18 file(s) 1416169 bytes used
24576 bytes free
Again, the TMP subdirectory is empty (there is a set temp = A:\TMP statement
in the config.sys). The ADSM subdirectory is also empty. The DLL
subdirectory contains the following:
Directory of A:\dll
. <DIR> 10-12-94 3:10p
.. <DIR> 10-12-94 3:10p
NAMPIPES DLL 1024 1-29-94 1:40a
HPFS386 DLL 5740 2-28-94 8:30a
4 file(s) 6764 bytes used
24576 bytes free
Please note that even though Named Pipes is not being used, the DLLs are
required by ADSM. If you are not using HPFS, the modules could be removed to
gain a little space.
Please note - the above TCP/IP modules are from release 1.2. I am working on
a V2 system, but the modules are bigger than the remaining space. I am
looking at ways to reduce this. Also, ADSM is at an older level also.
Release 7 is also bigger than what is left on the disk. I am also looking at
this. (I am trying to build a system on 2.88 M floppies, but that doesn't
help everyone.) If all you need to do is restores, the older ADSM code should
not be a problem. If you need to do an emergency backup, you might want to
look at upgrading to Level 7. BTW, we have used this as the ultimate rescue -
a guy came into my office with his thinkpad and a failing disk drive. He was
not part of ADSM. We actually added him to the system, then used the rescue
disks to back him up. After we got a new hard drive, we used these disks to
restore his machine, and added him permanently to our ADSM system. And was
he a happy camper when he left!!!!
To use the disks - do the following:
1. Boot from the first Disk. (labeled disk0).
2. At the prompt, switch to disk 2 and continue.
3. At the completion of the boot, you should have an A: prompt.
4. Start TCP/IP by entering TCP and your IP address (1.2.3.4 - sorry - no DNS
support).
5. At the completion you should be able to use the Ping command to test the
connection.
6. Insert the third disk. It contains the format, fdisk, and
SYSINSTX commands as needed.
7. Once formatted - start ADSM by entering DSMC. You can now proceed as
documented in the OS/2 user guide for restore.
8. Of course the DSM.OPT must have the Nodename changed, and the server
address hard coded in it.
We have been developing a restore process with this for DOS/Windows - you
would need one bootable DOS disk for each version of DOS you support - it
would contain the FDISK, Format, etc. Boot from this disk on an empty drive,
then set it up as you need it, and transfer the operating system with a SYS
command. Then, insert the OS/2 disks and boot them as above. Now you can
make a single pass, not the many that are required with the DOS system. When
you're finished, you can remove the floppy and boot from the Hard drive.
Please let me know if you have any questions.
Jerry Lawson
|
