Message-ID:	<006f01bfe696$d0f233c0$d310603e@nitz>
From:	"Barbara Nitz" <nitz AT gmx DOT net>
To:	<opendos AT delorie DOT com>
References:	<01bfe5e4$44616140$ae57b7d4 AT default>
Subject:	Re: Recognizing SCSI HDD
Date:	Wed, 5 Jul 2000 17:34:21 +0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2314.1300
Reply-To:	opendos AT delorie DOT com

> Maybe I would be wrong, but would  a ramdrive (bootdisk ) help?<

Well, I have found another way to get the newest drivers from the net, so I
don't need those from the EZSCSI floppy anymore.

All attempts to get OpenDOS to cooperate went wong, though.

When I used the ASPIDISK driver with parm /d, I was told that it was not
installed, because the HDD is handled by the Host Adapter BIOS (onboard
SCSI). I was also told that the drive C has been recognized. But a DIR C:
still yields 'Invalid drive specified'.

I contacted Drive Image support today, they told me that the FAT partition
has to be in the first 8G of the HDD for it to be addressable by OpenDOS. I
moved it, same problem.

I got all the files I would need to get a W98-DOS bootable floppy.
Unfortunately, I cannot format a bootable floppy under NT, as the NT format
command does not have an /s parameter. When I boot into OpenDOS and use
drive image to create the bootable floppy, I assume that the system file
written to the first two tracks would be from opendos, while all other files
would be from MSDOS. I'll get a colleague to format a bootable (W98SE)
floppy for me.

The interesting thing is that DOS booting tells me that there is a C drive,
drive image recognizes the C drive (and powerquest support confirmed that
they ask the BIOS for the drive letter), but a dir c: does not work.

I am getting real frustrated.

Barbara

- Raw text -