IDE drives recognised as SCSI - UPDATE - Solved ...

[Folkert Rienstra]

I think I do my best thinking when I am asleep, because I often awaken
with the solution to a vexing problem at hand.

Last night I awoke thinking of my problem with my two IDE drives
connected to the ITE EIDE connector on my ASUS MB (such connector
described as PTR_EIDE) and according to the manual as supporting "two
IDE HDDs for data storage). This connector is supported by the ITE
8211F controller.

Having installed them, jumpering one as master and one as slave, they
would be recognised in Windows as SCSI devices, and were not available
for use.

I wrote this and a couple other for a asking for advice on how to make
these drives accessible.

I received alot of advice - some friendly and some not so.

I received advice - especially here, to RTFM. I explained that I had
RTFM - many times and as far as I could tell had done everything by
the book. The RTFMers were not deterred in their opinion that the
solution lay in me reading TFM more carefully. (I got the hint).
Reading it again carefully revealed no new news.

From others,I received and direction to ensure that I had installed
the ITE 8211F driver. I had. I was told to do it again. on a related
theme, I was repeatedly reminded to enable the ITE 8211F controller in
the BIOS. I had. I was told to check it again. It was still enabled
from the last time!

From others, I received advice that I had connected my drives "the
wrong way around". Despite my explanation that I had a properly
configured and functional S-ATA disk running on the MB S-ATA connector
as my boot disk, a properly configured and functional IDE disk and
DVD drive running on the Primary IDE connector, and the two
nonfunctional IDE disks hooked up to the ITE IDE connector, I was
advised to switch them around. Interestingly, the counselor in this
case advised me to switch them to the configuration that I had just
described as my current one. I refrained him from telling him to RMFM
(Read My F***ing Message).

I was advised several times to uninstall the SCSI driver that Windows
insisted on installing, and reinstall the proper ITE 8211F driver from
the disc that came with my motherboard. This was not a possibility,
because as many times as I tried to uninstall the SCSI driver and
commanded Windows to look for the proper driver, Windows would not
install the proper driver because it still "saw" the drives as SCSI
drives and would not accept the .inf file containing (pointing to) the
driver because this driver was for IDE disks -- not for SCSI disks.

The Solution:
It occurred to me that perhaps the two nonfunctional IDE disks needed
to be examined to see if they had been partitioned and formatted.

Like you wouldn't know whether you did that or not.

I moved them to the other Primary IDE connector, examined them with
Partition Magic, and found that, in fact, they had not. I created
extended partitions on both of them formatted both of them, and
reinstalled them on the ITE IDE connector, and

PRESTO! - I had two perfectly functional and accessible IDE drives.

That still show up as SCSI.

I relate my experience with no intent of sarcasm or unfriendliness but
only to provide feedback to those who attempted to assist me, to
perhaps help others who have, are, or will experience the same problem
as I, and to gently remind those that offered me well-meaning but
persistent advice that just occasionally those to whom they attempt to
provide advice are not quite as mentally challenged as they might think,
and that there may in fact to be another reason why the problem exists.

Usually the correct advice will given at some time or other in the thread.
It is a bit weird that that didn't happen this time.
It probably has to do with your utterly stupid conduct that threw people off and go away thinking that it would come up sooner or
later by others.

 

[Diver_Doc]

I think I do my best thinking when I am asleep, because I often awaken
with the solution to a vexing problem at hand.

Last night I awoke thinking of my problem with my two IDE drives
connected to the ITE EIDE connector on my ASUS MB (such connector
described as PTR_EIDE) and according to the manual as supporting "two
IDE HDDs for data storage). This connector is supported by the ITE
8211F controller.

Having installed them, jumpering one as master and one as slave, they
would be recognised in Windows as SCSI devices, and were not available
for use.

I wrote this and a couple other for a asking for advice on how to make
these drives accessible.

I received alot of advice - some friendly and some not so.

I received advice - especially here, to RTFM. I explained that I had
RTFM - many times and as far as I could tell had done everything by
the book. The RTFMers were not deterred in their opinion that the
solution lay in me reading TFM more carefully. (I got the hint).
Reading it again carefully revealed no new news.

From others,I received and direction to ensure that I had installed
the ITE 8211F driver. I had. I was told to do it again. on a related
theme, I was repeatedly reminded to enable the ITE 8211F controller in
the BIOS. I had. I was told to check it again. It was still enabled
from the last time!

From others, I received advice that I had connected my drives "the
wrong way around". Despite my explanation that I had a properly
configured and functional S-ATA disk running on the MB S-ATA connector
as my boot disk, a properly configured and functional IDE disk and
DVD drive running on the Primary IDE connector, and the two
nonfunctional IDE disks hooked up to the ITE IDE connector, I was
advised to switch them around. Interestingly, the counselor in this
case advised me to switch them to the configuration that I had just
described as my current one. I refrained him from telling him to RMFM
(Read My F***ing Message).

I was advised several times to uninstall the SCSI driver that Windows
insisted on installing, and reinstall the proper ITE 8211F driver from
the disc that came with my motherboard. This was not a possibility,
because as many times as I tried to uninstall the SCSI driver and
commanded Windows to look for the proper driver, Windows would not
install the proper driver because it still "saw" the drives as SCSI
drives and would not accept the .inf file containing (pointing to) the
driver because this driver was for IDE disks -- not for SCSI disks.

The Solution:
It occurred to me that perhaps the two nonfunctional IDE disks needed
to be examined to see if they had been partitioned and formatted. I
moved them to the other Primary IDE connector, examined them with
Partition Magic, and found that, in fact, they had not. I created
extended partitions on both of them formatted both of them, and
reinstalled them on the ITE IDE connector, and PRESTO! - I had two
perfectly functional and accessible IDE drives.

I relate my experience with no intent of sarcasm or unfriendliness but
only to provide feedback to those who attempted to assist me, to
perhaps help others who have, are, or will experience the same problem
as I, and to gently remind those that offered me well-meaning but
persistent advice that just occasionally those to whom they attempt to
provide advice are not quite as mentally challenged as they might
think, and that there may in fact to be another reason why the problem
exists.

I in no way mean to demean the advisors, and participants in this and
other fora. Over the (many) years I have worked on my computers, I
have (almost) unfailingly received excellent advise form forum
participants and for that I remain grateful.

Cheers, and my wishes for a safe and healthy Christmas season for you
all.

Doc

 

[Rod Speed]

I think I do my best thinking when I am asleep, because I
often awaken with the solution to a vexing problem at hand.

Looks more like it was the progress of time that did it rather than the sleep.

Last night I awoke thinking of my problem with my two IDE drives
connected to the ITE EIDE connector on my ASUS MB (such connector
described as PTR_EIDE) and according to the manual as supporting "two
IDE HDDs for data storage). This connector is supported by the ITE
8211F controller.

Having installed them, jumpering one as master and one as slave, they
would be recognised in Windows as SCSI devices, and were not available
for use.

I wrote this and a couple other for a asking for advice on how to make
these drives accessible.

I received alot of advice - some friendly and some not so.

I received advice - especially here, to RTFM. I explained that I had
RTFM - many times and as far as I could tell had done everything by
the book. The RTFMers were not deterred in their opinion that the
solution lay in me reading TFM more carefully. (I got the hint).
Reading it again carefully revealed no new news.

From others,I received and direction to ensure that I had installed
the ITE 8211F driver. I had. I was told to do it again. on a related
theme, I was repeatedly reminded to enable the ITE 8211F controller in
the BIOS. I had. I was told to check it again. It was still enabled
from the last time!

From others, I received advice that I had connected my drives "the
wrong way around". Despite my explanation that I had a properly
configured and functional S-ATA disk running on the MB S-ATA connector
as my boot disk, a properly configured and functional IDE disk and
DVD drive running on the Primary IDE connector, and the two
nonfunctional IDE disks hooked up to the ITE IDE connector, I was
advised to switch them around. Interestingly, the counselor in this
case advised me to switch them to the configuration that I had just
described as my current one. I refrained him from telling him to RMFM
(Read My F***ing Message).

I was advised several times to uninstall the SCSI driver that Windows
insisted on installing, and reinstall the proper ITE 8211F driver from
the disc that came with my motherboard. This was not a possibility,
because as many times as I tried to uninstall the SCSI driver and
commanded Windows to look for the proper driver, Windows would not
install the proper driver because it still "saw" the drives as SCSI
drives and would not accept the .inf file containing (pointing to) the
driver because this driver was for IDE disks -- not for SCSI disks.

The Solution:
It occurred to me that perhaps the two nonfunctional IDE disks needed
to be examined to see if they had been partitioned and formatted. I
moved them to the other Primary IDE connector, examined them with
Partition Magic, and found that, in fact, they had not. I created
extended partitions on both of them formatted both of them, and
reinstalled them on the ITE IDE connector, and PRESTO! - I had two
perfectly functional and accessible IDE drives.

Thanks for the feedback. Clearly we got a bit sidetracked on the
original SCSI question and missed the fact that you just said that
you couldnt see those drives in Explorer. They would have been
visible in Disk Management.

 

[Egil Solberg]

Having installed them, jumpering one as master and one as slave, they
would be recognised in Windows as SCSI devices, and were not available
for use.

You talk a lot about SCSI, but it has nothing to do with it. Windows treats
all add on (not native) controllers as SCSI devices, but that does not have
any practical consequences. Adding a regular harddrive to your native
IDE-controller would give the same scenario. You have to partition and
format the drive when installing it. The drive will then be accessible via
explorer. Before that it will only show in disk management.
You seem upset being told to RTFM, but the above is in fact regarded as
common knowledge installing a harddrive, and consulting an online basic
tutorial for installing drives would have made the trick.

 

[Diver_Doc]

You talk a lot about SCSI,

I don't in fact "talk a lot about SCSI" - I only related what Windows
displayed the disk as in Device Manager - period.

Windows treats all add on (not native) controllers as SCSI devices, but that does not have
any practical consequences. Adding a regular harddrive to your native
IDE-controller would give the same scenario.

Except that it didn't.

You seem upset being told to RTFM,

I am not upset at all - as I mentioned above, I only related in my
post what I was told to do here and elsewhere by forum members, (even
after stating repeatedly that I had already done so)

but the above is in fact regarded as common knowledge installing a harddrive,
and consulting an online basic tutorial for installing drives would have made the trick.

So if it was such simple and common kowledge, it has to make one
wonder why it wasn't suggested.

Best regards,

Doc

 

[Rod Speed]

So if it was such simple and common kowledge, it
has to make one wonder why it wasn't suggested.

We got side tracked on the SCSI question and the rather odd
way that controller is documented in the motherboard manual.

I didnt register that you were saying you couldnt see the drives
in Explorer until you remarked that partitioning and formatting
made them visible. I have often pointed out that that needs to
be done when others have complained about drives not visible.

 

[Diver_Doc]

Like you wouldn't know whether you did that or not.

Exactly - the drives had been sitting in a drawer for a year and a
half - I had not memorised their status.

That still show up as SCSI.

They don't actually - would you care to see a screen shot?

Usually the correct advice will given at some time or other in the thread.
Correct

It is a bit weird that that didn't happen this time.

Correct again.

It probably has to do with your utterly stupid conduct

Hah! LOL! There we go! That is more what I expected from you having
read this group for a while.

Hook, line and sinker huh?

that threw people off and go away thinking that it would come up sooner or
later by others.

Right - like: "Gee - I won't offer what I think must be the real
solution - someone else surely will". Uh huh.

Feeling a bit defensive Mr Rienstra? Seems you always resort to this
behaviour sooner or later - usually sooner.

I have been nothing but polite, friendly and appreciative throughout
this entire thread, but in the end I get this.

You sir, need some Christmas spirit - all year long.

If you are lucky, the Three Spirits of Christmas may pay you a call.

Good night, and good bye.

Doc

 

[Jim]

I think I do my best thinking when I am asleep, because I often awaken
with the solution to a vexing problem at hand.

Last night I awoke thinking of my problem with my two IDE drives
connected to the ITE EIDE connector on my ASUS MB (such connector
described as PTR_EIDE) and according to the manual as supporting "two
IDE HDDs for data storage). This connector is supported by the ITE
8211F controller.

Having installed them, jumpering one as master and one as slave, they
would be recognised in Windows as SCSI devices, and were not available
for use.

I wrote this and a couple other for a asking for advice on how to make
these drives accessible.

I received alot of advice - some friendly and some not so.

I received advice - especially here, to RTFM. I explained that I had
RTFM - many times and as far as I could tell had done everything by
the book. The RTFMers were not deterred in their opinion that the
solution lay in me reading TFM more carefully. (I got the hint).
Reading it again carefully revealed no new news.

From others,I received and direction to ensure that I had installed
the ITE 8211F driver. I had. I was told to do it again. on a related
theme, I was repeatedly reminded to enable the ITE 8211F controller in
the BIOS. I had. I was told to check it again. It was still enabled
from the last time!

From others, I received advice that I had connected my drives "the
wrong way around". Despite my explanation that I had a properly
configured and functional S-ATA disk running on the MB S-ATA connector
as my boot disk, a properly configured and functional IDE disk and
DVD drive running on the Primary IDE connector, and the two
nonfunctional IDE disks hooked up to the ITE IDE connector, I was
advised to switch them around. Interestingly, the counselor in this
case advised me to switch them to the configuration that I had just
described as my current one. I refrained him from telling him to RMFM
(Read My F***ing Message).

I was advised several times to uninstall the SCSI driver that Windows
insisted on installing, and reinstall the proper ITE 8211F driver from
the disc that came with my motherboard. This was not a possibility,
because as many times as I tried to uninstall the SCSI driver and
commanded Windows to look for the proper driver, Windows would not
install the proper driver because it still "saw" the drives as SCSI
drives and would not accept the .inf file containing (pointing to) the
driver because this driver was for IDE disks -- not for SCSI disks.

The Solution:
It occurred to me that perhaps the two nonfunctional IDE disks needed
to be examined to see if they had been partitioned and formatted. I
moved them to the other Primary IDE connector, examined them with
Partition Magic, and found that, in fact, they had not. I created
extended partitions on both of them formatted both of them, and
reinstalled them on the ITE IDE connector, and PRESTO! - I had two
perfectly functional and accessible IDE drives.

I relate my experience with no intent of sarcasm or unfriendliness but
only to provide feedback to those who attempted to assist me, to
perhaps help others who have, are, or will experience the same problem
as I, and to gently remind those that offered me well-meaning but
persistent advice that just occasionally those to whom they attempt to
provide advice are not quite as mentally challenged as they might
think, and that there may in fact to be another reason why the problem
exists.

I in no way mean to demean the advisors, and participants in this and
other fora. Over the (many) years I have worked on my computers, I
have (almost) unfailingly received excellent advise form forum
participants and for that I remain grateful.

Cheers, and my wishes for a safe and healthy Christmas season for you
all.

Doc

How did you manage to format an extended partition?

 

[Diver_Doc]

How did you manage to format an extended partition?

Jim:

I dunno - as you can see I am no techie - I used Partition Magic, and
when it created the partition, it showed (and shows) it as an Extended
Partition. Then I just used PM to format it.

What is the significance of your question?

Should I not be able to accomplish that?

BTW, why is there a small unallocated space (and apparently
unrecoverable) of 7.8 MB at the beginning of each of these drives?
What is the purpose of this?

Thanks in advance,

Doc

 

[Diver_Doc]

On Sat, 17 Dec 2005 20:17:40 +0100, "Folkert Rienstra"


They don't actually - would you care to see a screen shot?

Oooops!

Time for an apology - they DO still show up as SCSI drives!

(I certainly don't dispute your superior knowledge - only your
manners)

Doc

 

[Jim]

Jim:

I dunno - as you can see I am no techie - I used Partition Magic, and
when it created the partition, it showed (and shows) it as an Extended
Partition. Then I just used PM to format it.

What is the significance of your question?

Should I not be able to accomplish that?

BTW, why is there a small unallocated space (and apparently
unrecoverable) of 7.8 MB at the beginning of each of these drives?
What is the purpose of this?

Thanks in advance,

Doc

If you've located that information, you also know the genuine type of
partition that was formatted. Won't play your silly blame game.