Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site mprvaxa.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!alberta!ubc-vision!mprvaxa!bsmith From: bsmith@mprvaxa.UUCP (Brian Smith) Newsgroups: net.micro.pc Subject: Problems with FORMAT and DISKCOPY Message-ID: <630@mprvaxa.UUCP> Date: Mon, 8-Jul-85 19:29:27 EDT Article-I.D.: mprvaxa.630 Posted: Mon Jul 8 19:29:27 1985 Date-Received: Sat, 13-Jul-85 10:01:04 EDT Organization: Microtel Pacific Research, Burnaby, B.C., Canada Lines: 22 I vaguely recall some discussion in this group about position-dependence of FORMAT and DISKCOPY. At the time (about a year ago), I had not run into the problem, so I didn't pay much attention. However, with the addition of the latest memory-resident program to my system FORMAT and DISKCOPY have begun to act very strangely. FORMAT will (a) format the disk and then display the message "Format Failure" or (b) format the disk as a single-sided 8-sector diskette. DISKCOPY tells me that it is copying a 9-sector double-sided disk as an 8-sector double-sided disk. I have been able to "fix" DISKCOPY by loading a couple extra copies COMMAND.COM on top of each other so that DISKCOPY will start higher in memory. I am running MS-DOS 2.11 on a Corona and have SideKick, FilePath, the drivers for the PC102 terminal emulator, and a couple of other things resident in memory. Can anyone enlighten me on what is happening and perhaps (cross fingers here) provide me with a solution?