The PMTape program allows you to boot OS/2 from two floppy disks and then run a stand-alone restore of an entire disk (no selective restore with this option). The instructions that come with PMTape for setting up the floppy disks are a bit out of date. The following is a discussion of the disk setup and the CONFIG.SYS files used for this procedure. Note that a 3rd diskette is used to contain the pieces of PMTape. NOTE: One problem with the instructions contained within the PMTape manual is that they were written for an IBM PS/2. There is a problem with clone computers in that two pieces of the setup must be placed on the disk to be reformatted (after it has been formatted, if necessary). The following setup was done using the March '93 BETA of OS/2 2.1. It should be close to or the same as needed with 2.1GA CONTENTS OF THE VARIOUS DISKETTES: DISK 1: (boot disk) ==================================================== 000000 .bio 2560 1-04-93 11:24 \ abios .sys 427 1-04-93 11:05 \ blistlay.out 1862 3-08-93 21:27 \ bundle 457772 3-08-93 21:59 \ f80000 .bio 9728 1-04-93 11:24 \ f80100 .bio 8704 1-04-93 11:24 \ f80200 .bio 7680 1-04-93 11:24 \ f80402 .bio 5120 1-04-93 11:24 \ f80403 .bio 5632 1-04-93 11:24 \ f80404 .bio 5632 1-04-93 11:24 \ f80600 .bio 7168 1-04-93 11:24 \ f80700 .bio 1536 1-04-93 11:24 \ f80701 .bio 1536 1-04-93 11:24 \ f80702 .bio 1536 1-04-93 11:24 \ f80703 .bio 1536 1-04-93 11:24 \ f80704 .bio 1024 1-04-93 11:24 \ f80902 .bio 5120 1-04-93 11:24 \ f80903 .bio 5632 1-04-93 11:24 \ f80904 .bio 5632 1-04-93 11:24 \ f80a00 .bio 1536 1-04-93 11:24 \ f80a01 .bio 1536 1-04-93 11:24 \ f80a02 .bio 1024 1-04-93 11:24 \ f80c00 .bio 5632 1-04-93 11:24 \ f80d00 .bio 5120 1-04-93 11:24 \ f80d01 .bio 5120 1-04-93 11:24 \ f81000 .bio 1536 1-04-93 11:24 \ f81b00 .bio 4096 1-04-93 11:24 \ f88000 .bio 2048 1-04-93 11:24 \ fc0400 .bio 11264 1-04-93 11:24 \ fc0403 .bio 5632 1-04-93 11:24 \ fc0500 .bio 9728 1-04-93 11:24 \ os2boot 1099 2-22-93 19:42 \ os2dump 2728 2-22-93 19:43 \ os2krnli 729670 2-26-93 18:21 \ os2ldr 28160 2-22-93 19:43 \ os2ldr .msg 8441 2-15-93 21:04 \ os2ver 89 2-08-93 17:50 \ sysinstx.com 39472 2-26-93 17:46 \ w020100 .bio 3072 1-04-93 11:27 \ w020101 .bio 4608 1-04-93 11:27 \ w050000 .bio 1536 1-04-93 11:24 \ w050100 .bio 2560 1-04-93 11:24 \ w050101 .bio 3072 1-04-93 11:27 \ w060100 .bio 6656 1-04-93 11:24 \ w0f0000 .bio 1536 1-04-93 11:24 \ DISKETTE 2: (2nd half of boot) =============================================== aha152x .add 23631 2-16-93 0:44 \ aha154x .add 19431 2-16-93 0:45 \ aha164x .add 18839 2-16-93 0:46 \ aha174x .add 16851 2-16-93 0:47 \ ansicall.dll 438 2-15-93 23:52 \ bkscalls.dll 401 2-15-93 23:56 \ bmscalls.dll 398 2-15-93 23:57 \ bvhinit .dll 9299 2-22-93 19:47 \ bvscalls.dll 454 2-16-93 0:03 \ cdfs .ifs 40292 2-26-93 18:53 \ clock01 .sys 3694 2-16-93 1:44 \ clock02 .sys 3710 2-16-93 1:45 \ cmd .exe 89088 2-22-93 21:00 \ config .bak 422 5-21-93 0:04 \ config .sys 411 5-21-93 1:22 \ country .sys 25610 2-26-93 19:28 \ disk .num 20 3-08-93 21:27 \ dos .sys 1142 2-16-93 2:02 \ doscall1.dll 91014 2-26-93 19:18 \ dpt20xx .add 15830 2-16-93 0:57 \ fd16-700.add 29182 2-26-93 19:18 \ fd7000ex.add 19862 2-16-93 0:51 \ fd850ibm.add 29076 2-16-93 0:54 \ fd8xx .add 29074 2-16-93 0:55 \ fig-run .sys 414 5-21-93 0:52 \ fig-strt.sys 411 5-21-93 1:22 \ harderr .exe 14424 2-26-93 19:01 \ hitcds1 .flt 7190 2-16-93 2:08 \ hpfs .ifs 128578 2-27-93 16:54 \ ibm1flpy.add 25086 2-16-93 0:30 \ ibm1s506.add 22737 2-16-93 0:33 \ ibm2adsk.add 10816 2-16-93 0:36 \ ibm2flpy.add 13873 2-16-93 0:34 \ ibm2m57 .add 21186 2-23-93 7:53 \ ibm2scsi.add 25241 2-16-93 0:38 \ ibmint13.i13 9684 2-26-93 19:12 \ ip2idrv .sys 35292 4-24-92 2:00 \ itdmn .exe 6583 4-24-92 2:00 \ kbd01 .sys 29525 2-16-93 2:27 \ kbd02 .sys 25941 2-16-93 2:29 \ kbdcalls.dll 858 2-16-93 0:18 \ keyboard.dcp 5177 2-16-93 2:22 \ moucalls.dll 1010 2-16-93 0:17 \ mouse .sys 14495 2-22-93 21:20 \ msg .dll 508 2-16-93 0:54 \ nampipes.dll 1024 2-16-93 0:55 \ neccds1 .flt 8170 2-16-93 2:12 \ nls .dll 466 2-22-93 20:45 \ npxemltr.dll 25280 2-22-93 21:21 \ os2aspi .dmd 6146 2-16-93 0:27 \ os2cdrom.dmd 22726 2-16-93 2:07 \ os2char .dll 56064 2-22-93 20:25 \ os2dasd .dmd 33042 2-16-93 0:24 \ os2scsi .dmd 10842 2-16-93 0:26 \ print01 .sys 9118 2-16-93 3:01 \ print02 .sys 8166 2-16-93 3:01 \ quecalls.dll 15042 2-26-93 19:13 \ screen01.sys 7258 2-26-93 19:37 \ screen02.sys 7408 2-22-93 21:25 \ sesmgr .dll 32294 2-22-93 20:32 \ sipanel1.dll 24992 2-17-93 23:08 \ sonycds1.flt 7366 2-16-93 2:11 \ sysinst1.exe 4224 2-17-93 23:24 \ sysinst2.exe 130720 3-08-93 17:39 \ syslevel.os2 165 2-26-93 19:26 \ testcfg .sys 4402 2-22-93 21:44 \ toshcds1.flt 7348 2-16-93 2:10 \ viocalls.dll 1825 2-22-93 20:24 \ vtbl850 .dcp 10478 2-16-93 1:18 \ DISKETTE 3: (PMTape pieces) ======================================== autotape.exe 21504 4-24-92 2:00 \ backall .cmd 818 4-24-92 2:00 \ changed .cmd 822 4-24-92 2:00 \ cmd .exe 89088 2-22-93 21:00 \ doscall1.dll 91014 2-26-93 19:18 \ exclude .cfg 68 4-24-92 2:00 \ format .com 66832 2-26-93 19:27 \ ibm2flpy.add 13040 4-24-92 2:00 \ install .exe 38672 4-24-92 2:00 \ install .o11 356 4-24-92 2:00 \ insthlp .hlp 6576 4-14-92 2:01 \ ip2bb .dll 37090 4-24-92 2:00 \ ip2bkp .dll 49104 4-24-92 2:00 \ ip2idrv .sys 35292 4-24-92 2:00 \ ip2mb .dll 49294 4-24-92 2:00 \ ipbsinfo.dll 16384 4-24-92 2:00 \ iphelp .dll 24576 4-14-92 2:01 \ iphelp .hlp 54080 4-24-92 2:00 \ ipqual .dll 9467 4-24-92 2:00 \ iprst .dll 37730 4-14-92 2:01 \ iprules .dll 58368 4-14-92 2:01 \ ipspwin .dll 13824 4-24-92 2:00 \ iptxtra .dll 4434 4-24-92 2:00 \ ipucgen .dll 109588 4-24-92 2:00 \ ipugui .dll 22016 4-24-92 2:00 \ itdmn .exe 6583 4-24-92 2:00 \ pmtape .exe 224768 4-24-92 2:00 \ pmtape .ezs 1184 4-24-92 2:00 \ pmtape .ini 382 4-24-92 2:00 \ readme .txt 11816 4-24-92 2:00 \ restall .cmd 223 4-24-92 2:00 \ shrtbkll.tpf 15 4-24-92 2:00 \ shrtchgd.tpf 15 4-24-92 2:00 \ shrtrstl.tpf 15 4-24-92 2:00 \ sr .exe 5993 4-24-92 2:00 \ sr .msg 56651 4-24-92 2:00 \ uhpfs .dll 179344 2-26-93 18:57 \ viocalls.dll 1825 2-22-93 20:24 \ USE OF CONFIG FILES: As mentioned above, two of the pieces needed to run the stand-alone restore MUST reside on the actual disk being restored. In the case where the disk might be new, or has to be reformatted because it is totally destroyed, this can lead to a problem as to getting these two pieces over to that disk as well as providing for the formatting. I took the approach that I wanted to have three diskettes for the entire process, and only the three diskettes. This is a bit harsh, since it would be no problem at all to use a standard set of OS/2 install diskettes to boot up and reformat the drive, and to also move the two needed pieces over to the newly formatted disk. The two items that must be placed on the restore disk are: CMD.EXE ITDMN.EXE In order to accomplish my goal of only three diskettes, I provide two different CONFIG.SYS files on diskette 2. They are called: FIGRUN .SYS 414 5-21-93 0:52 \ FIG-STRT.SYS 411 5-21-93 1:22 \ The procedure is to boot up at first using FIG-STRT. So the diskettes are always left in a state where CONFIG.SYS is a copy of the FIG-STRT.SYS file. The FIG-STRT file will allow for boot up, and a runnable copy of OS/2 for formatting, FDISK, and whatever else is needed but it WILL NOT allow the SR (stand-alone restore) program to run because it points to CMD.EXE as being located on the a: drive whereas the FIG-RUN.SYS file points to the D: drive (the drive being restored in this case). Note also that FIG-STRT assumes that the ITDMN.EXE file (which really isn't used for formatting) is assumed to be on the boot-drive whereas the FIG-RUN.SYS file points to the D: drive (in this case) for the ITDMN.EXE file. After doing all of the formatting, I then copy FIG-RUN.SYS to be the current CONFIG.SYS and re-boot. This will cause the drivers to be loaded and the restore can be run. Detailed instructions for the entire procedure are provided below. CONTENTS OF FIG-STRT.SYS ================================================================= REM must copy CMD.EXE and ITDMN.EXE to target drive first buffers=50 memman=noswap protshell=a:cmd.exe protectonly=yes libpath=A:\; ifs=hpfs.ifs /c:64 /AUTOCHECK:D Set path=a:\; Set dpath=a:\; basedev=print01.sys basedev=ibm1flpy.add basedev=ibm1s506.add basedev=ibm2flpy.add basedev=ibm2adsk.add basedev=ibm2scsi.add basedev=ibmint13.i13 basedev=os2dasd.dmd device=ip2idrv.sys run=itdmn.exe CONTENTS OF FIG-RUN.SYS ====================================== REM must copy CMD.EXE and ITDMN.EXE to target drive first buffers=50 memman=noswap protshell=D:\cmd.exe protectonly=yes libpath=A:\; ifs=hpfs.ifs /c:64 /AUTOCHECK:D Set path=a:\; Set dpath=a:\; basedev=print01.sys basedev=ibm1flpy.add basedev=ibm1s506.add basedev=ibm2flpy.add basedev=ibm2adsk.add basedev=ibm2scsi.add basedev=ibmint13.i13 basedev=os2dasd.dmd device=ip2idrv.sys run=D:itdmn.exe INSTRUCTIONS FOR STAND-ALONE RESTORE with PMTAPE 1. Boot OS/2 using diskettes 1 and 2. If the CONFIG.SYS was setup properly, the CONFIG.SYS points to the A: (boot) disk for CMD.EXE and ITDMN.EXE. This is proper for formatting, but the SR program will not run with this configuration. Do any formatting necessary using the FORMAT command found on diskette 3. 2. Put disk 3 in the A: drive. 3. Copy FIG-RUN.SYS to be CONFIG.SYS. This will (on next boot) point to the disk to be restored for CMD.EXE and ITDMN.EXE. At that point, SR.EXE will run. 4. Format the target partition. If this is not the D: drive, you will have to change the CONFIG.SYS file on disk 2. 5. COPY ITDMN.EXE to the newly formatted drive. COPY CMD.EXE to the newly formatted drive. 6. Boot from disk 1 & 2 7. At the A: prompt, COPY FIG-STRT.SYS to be CONFIG.SYS (for next time). 8. Put disk 3 into drive A: 9. Put the proper tape into the tape drive. 10. TYPE: SR 11. When the tape finishes restoring, check the CONFIG.SYS file again. (for next time) That's all!! The SR restore is very slow. I estimate it takes about 4 hours to restore 64 megs but it sure beats trying to reinstall OS/2 and restore over it. Go for a walk, go to bed, read a book, etc.