From owner-freebsd-questions Mon Jul 10 11:33:38 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA17579 for questions-outgoing; Mon, 10 Jul 1995 11:33:38 -0700 Received: from driver.nsta.org (driver.nsta.org [199.0.2.2]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA17573 for ; Mon, 10 Jul 1995 11:33:36 -0700 Received: from niblick.nsta.org (niblick.nsta.org [199.0.2.7]) by driver.nsta.org (8.6.11/8.6.9) with ESMTP id KAA12716 for ; Mon, 10 Jul 1995 10:35:07 -0400 Received: from NSTA/SpoolDir by niblick.nsta.org (Mercury 1.21); 10 Jul 95 14:38:10 +0500 Received: from SpoolDir by NSTA (Mercury 1.21); 10 Jul 95 14:38:04 +0500 From: "Alex Mondale" Organization: National Science Teachers Assn. To: questions@freebsd.org Date: Mon, 10 Jul 1995 14:37:54 +0500 Subject: attack of the FAT Reply-to: amondale@nsta.org Priority: normal X-mailer: Pegasus Mail/Windows (v1.22) Message-ID: <121678F743E@niblick.nsta.org> Sender: questions-owner@freebsd.org Precedence: bulk I have tried in vain to get 2.0.5 release to live peacefully with Windows NT Workstation 3.5. They both have different views of the universe, particularly each others' FAT table. I have a promise IDE caching controller with 8mb RAM that occasionally doesn't see the two LBA-mapped drives attached to it (it is capable of mapping four drives via bios address 170), but in this case I power off and back on and it usually sees the drives. Then comes the fun part. After the BSD installation successfully concludes, the #2 partition on the C: drive (where BSD is #3) reports numerous and unrecoverable scrambled files under SCANDISK, most often after Windows NT has "written a harmless disk label on logical drive 0. BSD then reports unrecoverable file errors ("run fsck manually") on the wd0s1e (/usr) partition. It is a nasty see-saw I have yet to figure out a fix for, but to date have reinstalled bsd and dos (and restored data from tape) approximately five times. I have ruled out caching switch in the hdc bios, since it has the same anti-social behavior with caching on and off. I have also ruled out the OS/2 boot manager, which I use to access OS/2 on the second drive (where I intend to install bsd next as an experiment). Can any one out there help? Thanks. Alex Mondale MIS Director National Science Teachers Association (703) 243-7100, ext. 282 (703) 841-8329 (fax)