Boot your system using a floppy disk. Insert your Drive Image floppy(s) and attempt to run Drive Image from these floppy disks. If this doesn't succeed, do not continue until you've resolved why a floppy based execution of Drive Image fails. (Once you format your disk, you'll need to rely on a floppy based Drive Image to continue)
Next issue...
When you boot with a floppy, your system needs COMMAND.COM to operate. Without it, the booting is incomplete, and you'll get a "Non-System Disk" error.
Once you've booted your system successfully, COMMAND.COM displays a prompt A:> and waits for you to type a command. One of the commands you'll be typing is FORMAT. When you type this command, COMMAND.COM reads the file FORMAT.COM and turns control of your system over to the code found in FORMAT.COM, and while FORMAT.COM is running, COMMAND.COM remains idle. When FORMAT.COM finishes, control of your system reverts back to COMMAND.COM and a new A:> prompt is displayed, indicating that COMMAND.COM is ready to process another command.
In short, COMMAND.COM furnishes an environment in which FORMAT.COM performs its work.
Cheers, PW.
P.S. In earlier posts, I typed FORMAT.EXE instead of FORMAT.COM -- sorry for the confusion. |
