From: manaster@yu1.yu.edu (Chaim Manaster)
Newsgroups: comp.periphs.scsi,comp.sys.ibm.pc.hardware,comp.sys.ibm.pc.misc
Subject: Partition reappeared in new scsi installation (Buslogic)!
Date: 27 Jan 93 09:49:48 GMT
Followup-To: comp.periphs.scsi
Organization: Yeshiva University

Yesterday, I posted a message about the problem I am having,
installing a new Buslogic 747s EISA scsi board and a MIcropolis
2112 drive in addition to the existing Western Digital 1009 ESDI
controller and Maxtor drive.

I described how I had a partition on the scsi drive that had some
funny files on it that I could not delete, and how the volume name
was one I could not change or delete. Then I described how the
BUslogic device driver would not load at boot up, and how the bios
refused to disable itself (reasons unkown) on the scsi board when
so configured from the AMI EISA configuration software. Then, how
the entire partition just dissappeared, andwas not being recognized
from DOS or OS/2 (I have one OS/2 partition on the ESDI).

Well today when I turned the system on, there was the missing
partition again. Chkdsk, again reports all sorts of crosslinks etc?
But most, NOT ALL of the subdirectories are their, but some are
gone. Also chkdsk now reports some other crosslinked files (wierd
names?) that do not appear when you do a DIR. Also the BIOS on the
Buslogic card seems to be playing peek-a-boo with me.

There seems to be some funny relationship, where the new scsi
partition is recognized when the bios is there, but when the bios
does disable itself (i.e. not in the address space, as checked by
DEBUG) then the scsi partition is not recognized as present.

Has any one seen anything like this wierd behavior before???

I could sure use some help.

Thank you very much for the help.

Henry Manaster

-----------------------copy of yesterdays posting--------------

Article: 1182 of comp.periphs.scsi
From: manaster@yu1.yu.edu (Chaim Manaster)
Newsgroups: comp.periphs.scsi,comp.sys.ibm.pc.hardware,comp.sys.ibm.pc.misc
Subject: SCSI drive dissappeared! Need help.
Followup-To: comp.periphs.scsi

I have just added a Buslogic 747s SCSI controller to my ESDI
system. So I now have a Maxtor ESDI drive on the ESDI controller
and a Micropolis Fast SCSI II on the SCSI coontroller.

When I first installed, I had some minor problems but what was
wierd was that the supplied device driver would not get loaded at
boot up, but I somehow still had access to the scsi drive.

Also, I was not able to disable the bios in the EISA config
software from AMI (for the AMI enterprise II motherboard) using the
Buslogic .cfg file supplied for the scsi EISA adapter.

Then after about one day where I was able to store stuff on the
scsi drive, I now can not access the drive. I can now only access
the ESDI drive.
Actually what happened (leaving out some of the trials and
tribulations) was I created a new dir on the scsi, then tried to cd
into the new dir, and the system froze. I had to cold boot. Since
then I can no longer get into the scsi drive.

What is the problem??? Anyone seen anything like this before??

Please help.

-- 
***************************************************************************
	Henry Manaster          *     EMail: manaster@yu1.yu.edu
	Brooklyn, NY            *
                                *
	Disclaimer: The above is not necessarily MY opinion nor that 
				of anyone else :-)  ????!
****************************************************************************
 
Newsgroups: comp.periphs.scsi