From owner-freebsd-hackers Fri Sep 12 17:27:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA21046 for hackers-outgoing; Fri, 12 Sep 1997 17:27:47 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA21041 for ; Fri, 12 Sep 1997 17:27:45 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id RAA24479; Fri, 12 Sep 1997 17:27:41 -0700 (MST) From: Terry Lambert Message-Id: <199709130027.RAA24479@usr04.primenet.com> Subject: Re: Do *you* have problems with floppies? To: julian@whistle.com (Julian Elischer) Date: Sat, 13 Sep 1997 00:27:41 +0000 (GMT) Cc: joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.ORG In-Reply-To: <3419D133.695678E2@whistle.com> from "Julian Elischer" at Sep 12, 97 04:33:07 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > "I tried to boot the boot floppy but got: > READ ERROR D=0 H=0 C=0 S=1" > > should not be included in the list of FreeBSD problems.. Agreed. BTW, that particular error will occur, I believe, if you use RAWRITE.EXE in a DOS window under Windows 95/NT, and do not first "shutdown to a real mode DOS prompt". I believe the problem is the "antivirus" protection from writing the boot sector, and the TSD miniport taking control of the boot sector region on the disk. Typically, it fails to write that area of the disk. Silently. If someone is interested in doing something about this, they should do an install check for Windows 95/NT, and then assert a level 3 volume lock, followed by a level 0 volume lock, after which they should be able to write track 0. If you aren't interested, it's possible that you can use the DOS command line "lock" command to assert volume locks on drive A: (or B:) to get the same effect. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.