From owner-freebsd-current Sat Mar 25 1:13:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [24.234.53.177]) by hub.freebsd.org (Postfix) with ESMTP id 8F16437B5AC for ; Sat, 25 Mar 2000 01:13:30 -0800 (PST) (envelope-from freebsd@mrynet.com) Received: (from freebsd@localhost) by mrynet.com (8.9.3/8.9.3) id BAA01976; Sat, 25 Mar 2000 01:13:13 -0800 (PST) (envelope-from freebsd) Posted-Date: Sat, 25 Mar 2000 01:13:13 -0800 (PST) Message-Id: <200003250913.BAA01976@mrynet.com> From: freebsd@mrynet.com (FreeBSD mailing list) Date: Sat, 25 Mar 2000 01:13:12 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Bruce Evans Subject: Re: fd0: Debugger("d_iocmd botch") called. Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce wrote: > On Fri, 24 Mar 2000, Jim Bloom wrote: > > > FreeBSD mailing list wrote: > > > > > > This patch does indeed fix the writing of floppies. However, fdformat(1) > > > still fails as follows: > > > > That is very strange. My patch only applies to formatting floppies. It > > did not touch any routine used in writing a floppy. I have no idea at > > this time what is causing your other problems. > > > > I am unable to write to a floppy at this time. I'm not seeing any > > errors, but nothings is getting written. > > Reading of floppies is broken too. The wrong flags are passed to > isa_dmastart(), so the DMA direction is wrong. It defaults to the most > dangerous direction (ISADMA_WRITE), of course. I've confirmed that writing floppies seemingly works just fine, although I can't read at all. I've written a number of floppy boot images and checked them out, as well as performed a newfs_msdos and verified it on DOS machines. Cheers, -scott -- Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@mrynet.lv To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message