From owner-freebsd-current Thu Mar 4 9: 2:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5C25215064 for ; Thu, 4 Mar 1999 09:02:06 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id RAA37634; Thu, 4 Mar 1999 17:01:44 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA03727; Thu, 4 Mar 1999 10:01:39 -0700 (MST) Message-Id: <199903041701.KAA03727@harmony.village.org> To: Fritz Heinrichmeyer Subject: Re: Getting closer to use ATAPI-ZIP drives Cc: current@FreeBSD.ORG In-reply-to: Your message of "04 Mar 1999 15:53:53 +0100." <86lnhds3um.fsf@jfh00.fernuni-hagen.de> References: <86lnhds3um.fsf@jfh00.fernuni-hagen.de> Date: Thu, 04 Mar 1999 10:01:38 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <86lnhds3um.fsf@jfh00.fernuni-hagen.de> Fritz Heinrichmeyer writes: : mountmsdosfs(): bad bpb : is this a completely different problem (a msdosfs problem)? I've had to, in the past, slightly tweak the mount code for msdosfs to get stuff to mount. It would be interesting to see if this is a data corruption problem (in which case the diagnostic is good) or a slightly oddball dos disk. mtools might be useful in tracking things down. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message