If you are like me, you have always wanted an easy means to boot a command line session for maintenance and have found the published "single boot disk" schemes either did not work, were for the last version of os2, or were otherwise unsatisfactory. You may have even longed for some sort of documentation that would permit creating a simple command line os2 partition which would permit rapid rebooting and maintenance (i.e. CHKDSK for stopped HPFS volumes). Then, again, maybe I have been the only one who could not figure this out for the last eight years. Either way, the following procedure worked for me and it might for you.
This listing of necessary files is adapted from the procedure outlined in the file BOOT.2MB. The procedure as outlined there included much more than I needed and it did not work for me under Warp 4.0; however, you might find some of the documentation that writer went through helpful or interesting.
After creating a small partition around 3 to 5 M making it bootable and adding it to the Boot Manager, copy the following files in the directory structure given below. (The attributes are given before the file name to help you find them on your existing default Warp 4.0 partition. Some are hidden files or system files.)
Clearly, some of these statements like the AUTOCHECK parameter or FILES and PATH statements are unique to the way I have structured my directories. Also, there are a few duplicate files and probably a few files which actually are not needed. I hope it helps get you to a solution suitable for your needs.
