| Author |
Message |
Eric Gisin
Guest
|
 Posted:
Wed Oct 12, 2005 9:04 pm Post subject:
Re: SCSI as C drive not IDE as C drive |
|
|
Utterly clueless.
"Agent_C" <Agent-C-hates-spam@nyc.rr.com> wrote in message
news:jvajk1tsa3nvodmn48a3plt4paeb9jst9j@4ax.com...
[quote]
Additionally, I believe the SCSI ID has to be 0 for the boot drive.
[/quote] |
|
| Back to top |
|
 |
Agent_C
Guest
|
| Posted:
Thu Oct 13, 2005 3:03 am Post subject:
Re: Re: SCSI as C drive not IDE as C drive |
|
|
On Wed, 12 Oct 2005 09:04:19 -0700, "Eric Gisin"
<ericgisin@hotmail.com> wrote:
[quote]Utterly clueless.
[/quote]
Blow me... |
|
| Back to top |
|
|
Erzsm
Guest
|
| Posted:
Thu Oct 20, 2005 7:21 am Post subject:
Re: SCSI as C drive not IDE as C drive |
|
|
"Aynz"wrote in message...
| Quote: | Hi,
I have trawled Google Groups for an answer but have not got a
definitive one so I am posting this question myself.
I have a server with 3 SCSI drives. I have added an IDE drive (file
drive) to the server also. I am currently installing SBS2003 and when
doing so it brings up the IDE drive as the C drive which is not what I
want. I want one of the SCSI drives to be the C drive.
|
Hi,
Been there and done that. The solution couldn't be simplier.
The solution is exactly what "daytripper" suggested: simply make the entire
IDE drive an extended partition for logical drives. Logical drives are
non-bootable drives strickly for housing data. The extended partition is
their "container". When you bootup, your BIOS will continue to look to see
if it can boot from IDE, discover it can't, and then move on to boot from
SCSI.
(Turning towards group)
Honestly, this message thread has grown needessly long over something so
simple. Especially when two things hold true:
1. Adding a SCSI controller won't (magically) change the BIOS on your m/b.
2. This BIOS doesn't have an option to boot from SCSI. She said this
herself. Yours might, but hers doesn't. She isn't "lying".
(Back to Aynz)
I used PartitionMagic at the time, but fdisk will work just fine for you as
well.
Cheers,
E |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted:
Fri Oct 21, 2005 3:10 am Post subject:
Re: SCSI as C drive not IDE as C drive |
|
|
"Erzsm" <nospam@nowhere.ever> wrote in message news:qaD5f.83219$tD4.61299@tornado.ohiordc.rr.com
| Quote: | "Aynz"wrote in message...
Hi,
I have trawled Google Groups for an answer but have not got a
definitive one so I am posting this question myself.
I have a server with 3 SCSI drives. I have added an IDE drive (file
drive) to the server also. I am currently installing SBS2003 and when
doing so it brings up the IDE drive as the C drive which is not what I
want. I want one of the SCSI drives to be the C drive.
Hi,
Been there and done that.
|
Nope, yours was a different issue.
| Quote: | The solution couldn't be simplier.
|
What makes you think that this is a bios boot issue.
It could easily be an installation issue.
If one doesn't want a drive to be a certain drive letter one can remove
the drive during OS installation and move it back afterwards, or -if 'C:'
is not the boot drive, give it another letter when up and running.
| Quote: |
The solution is exactly what "daytripper" suggested: simply make the entire
IDE drive an extended partition for logical drives.
Logical drives are non-bootable drives strickly for housing data.
|
Wrong.
| Quote: | The extended partition is their "container".
|
Wrong again.
| Quote: | When you bootup, your BIOS will continue to look to see if it can
boot from IDE, discover it can't, and then move on to boot from SCSI.
|
When installing you don't even boot from SCSI (except of course when
your CDRom drive happens to be SCSI).
| Quote: |
(Turning towards group)
Honestly, this message thread has grown needessly long over something so
simple.
|
Yup, but for other reasons.
| Quote: | Especially when two things hold true:
1. Adding a SCSI controller won't (magically) change the BIOS on your m/b.
2. This BIOS doesn't have an option to boot from SCSI. She said this
herself. Yours might, but hers doesn't. She isn't "lying".
|
One doesn't need to be lying. Some people are just without a clue and
need some encouragement to explore their bios setup utility more closely.
| Quote: |
(Back to Aynz)
I used PartitionMagic at the time, but fdisk will work just fine for you as
well.
Cheers,
E |
|
|
| Back to top |
|
|
Erzsm
Guest
|
| Posted:
Sun Oct 23, 2005 4:40 pm Post subject:
Re: SCSI as C drive not IDE as C drive |
|
|
"Folkert Rienstra" wrote in message ...
| Quote: | "Erzsm"wrote in message
"Aynz"wrote in message...
I have a server with 3 SCSI drives. I have added an IDE drive (file
drive) to the server also. I am currently installing SBS2003 and when
doing so it brings up the IDE drive as the C drive which is not what I
want. I want one of the SCSI drives to be the C drive.
Hi,
Been there and done that.
Nope, yours was a different issue.
|
I didn't even say what my "issue" was, so how can you assume that it was
different?
I had a PC, not the Dual-P3, that I put together quite a number of years
ago. The m/b did not have an onboard SCSI controller. Likewise, the BIOS
on the m/b did not have an option to boot from SCSI. From day one, however,
I used a SCSI card controller for SCSI devices. I didn't have any IDE
devices. When it booted up, the m/b BIOS didn't find any valid boot media,
so it simply passed the boot along to the SCSI BIOS (on the SCSI card). It
then booted from the SCSI HDD, being controlled by the card.
Later, I had a spare IDE HDD laying around doing nothing, so figured might
make use out of it as a data drive. Put the thing in and of course the m/b
BIOS (with no SCSI boot option) wanted to either boot from the IDE HDD or
not boot at all. The m/b wouldn't pass the boot along to the SCSI card,
if it saw an IDE (primary) HDD. So, I simply just made the IDE HDD a
non-bootable extended partition (drive). The m/b BIOS no longer saw the IDE
HDD as bootable and allowed the SCSI card BIOS to run.
Uhm.. This was identical to Aynz's "issue"..
Another thing she could do would be simply just find an old IDE cdrom and
use it, along with the IDE HDD. Simple make the cdrom as IDE master and the
HDD as slave, to prevent the m/b BIOS from wanting to boot the IDE HDD even
if it is fdisk'd as a primary drive. The idea crossed my mind at the time,
but I sure as hell wasn't going to go out and buy an IDE cdrom just for
that...
Changing the drive letters played no bearing to the boot sequence. It only
effected how the drives were seen once the OS (Win95 at the time) was
loaded. |
|
| Back to top |
|
|
Jeremy Boden
Guest
|
| Posted:
Sun Oct 23, 2005 5:06 pm Post subject:
Re: SCSI as C drive not IDE as C drive |
|
|
In message <435995f6$0$66398$892e7fe2@authen.white.readfreenews.net>,
Folkert Rienstra <see_reply-to@myweb.nl> writes
| Quote: | "Erzsm" <nospam@nowhere.ever> wrote in message
news:qaD5f.83219$tD4.61299@tornado.ohiordc.rr.com
"Aynz"wrote in message...
Hi,
I have trawled Google Groups for an answer but have not got a
definitive one so I am posting this question myself.
I have a server with 3 SCSI drives. I have added an IDE drive (file
drive) to the server also. I am currently installing SBS2003 and when
doing so it brings up the IDE drive as the C drive which is not what I
want. I want one of the SCSI drives to be the C drive.
Hi,
Been there and done that.
Nope, yours was a different issue.
The solution couldn't be simplier.
What makes you think that this is a bios boot issue.
It could easily be an installation issue.
If one doesn't want a drive to be a certain drive letter one can remove
the drive during OS installation and move it back afterwards, or -if 'C:'
is not the boot drive, give it another letter when up and running.
.... |
Isn't the fundamental problem that Windows forces the creation of a boot
record?
You don't get to choose the disk or the partition - it does that for
you.
--
Jeremy Boden |
|
| Back to top |
|
|
Eric Gisin
Guest
|
| Posted:
Sun Oct 23, 2005 8:47 pm Post subject:
Re: SCSI as C drive not IDE as C drive |
|
|
"Jeremy Boden" <jeremy@jboden.demon.co.uk> wrote in message
news:yvjGxHB7y3WDFwz7@jboden.demon.co.uk...
| Quote: | In message <435995f6$0$66398$892e7fe2@authen.white.readfreenews.net>,
Folkert Rienstra <see_reply-to@myweb.nl> writes
I have a server with 3 SCSI drives. I have added an IDE drive (file
drive) to the server also. I am currently installing SBS2003 and when
doing so it brings up the IDE drive as the C drive which is not what I
want. I want one of the SCSI drives to be the C drive.
Been there and done that.
Nope, yours was a different issue.
The solution couldn't be simplier.
What makes you think that this is a bios boot issue.
It could easily be an installation issue.
If one doesn't want a drive to be a certain drive letter one can remove
the drive during OS installation and move it back afterwards, or -if 'C:'
is not the boot drive, give it another letter when up and running.
...
Isn't the fundamental problem that Windows forces the creation of a boot
record?
You don't get to choose the disk or the partition - it does that for
you.
The problem is WinNT does not know the disk boot order when setup runs from CD. |
It enumerates disk in BIOS order, or perhaps in PCI bus order of adapters.
In any case, IDE comes before SCSI, so you have to disable IDE drives or port. |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted:
Mon Oct 24, 2005 3:50 am Post subject:
Re: SCSI as C drive not IDE as C drive |
|
|
"Erzsm" <nospam@nowhere.ever> wrote in message news:2FK6f.153380$lI5.80974@tornado.ohiordc.rr.com
| Quote: | "Folkert Rienstra" wrote in message ...
"Erzsm"wrote in message
"Aynz"wrote in message...
I have a server with 3 SCSI drives. I have added an IDE drive (file
drive) to the server also. I am currently installing SBS2003 and when
doing so it brings up the IDE drive as the C drive which is not what I
want. I want one of the SCSI drives to be the C drive.
Hi,
Been there and done that.
Nope, yours was a different issue.
I didn't even say what my "issue" was, so how can you assume that it was
different?
|
Because of your solution, maybe?
| Quote: |
I had a PC, not the Dual-P3, that I put together quite a number of years
ago. The m/b did not have an onboard SCSI controller. Likewise, the BIOS
on the m/b did not have an option to boot from SCSI. From day one, however,
I used a SCSI card controller for SCSI devices. I didn't have any IDE
devices. When it booted up, the m/b BIOS didn't find any valid boot media,
so it simply passed the boot along to the SCSI BIOS (on the SCSI card).
It then booted from the SCSI HDD, being controlled by the card.
Later, I had a spare IDE HDD laying around doing nothing, so figured might
make use out of it as a data drive. Put the thing in and of course the m/b
BIOS (with no SCSI boot option) wanted to either boot from the IDE HDD or
not boot at all. The m/b wouldn't pass the boot along to the SCSI card,
if it saw an IDE (primary) HDD. So, I simply just made the IDE HDD a
non-bootable extended partition (drive). The m/b BIOS no longer saw the IDE
HDD as bootable and allowed the SCSI card BIOS to run.
Uhm.. This was identical to Aynz's "issue"..
|
Uhm, no.
| Quote: |
Another thing she could do would be simply just find an old IDE cdrom and
use it, along with the IDE HDD.
Simple make the cdrom as IDE master and the
HDD as slave, to prevent the m/b BIOS from wanting to boot the IDE HDD even
if it is fdisk'd as a primary drive.
|
Clueless. Master or slave makes no difference.
| Quote: | The idea crossed my mind at the time,
but I sure as hell wasn't going to go out and buy an IDE cdrom just for that...
|
Obviously, as you then would have known that it doesn't make a difference.
| Quote: |
Changing the drive letters played no bearing to the boot sequence. It only
effected how the drives were seen once the OS (Win95 at the time) was loaded.
|
Right, now read the OP again. Especially where it says:
" I am currently *installing* SBS2003 and when doing so it brings up the IDE drive as the C drive which is not what I want." |
|
| Back to top |
|
|
Erzsm
Guest
|
| Posted:
Mon Oct 24, 2005 7:26 am Post subject:
Re: SCSI as C drive not IDE as C drive |
|
|
"Folkert Rienstra" wrote
| Quote: | Right, now read the OP again. Especially where it says:
" I am currently *installing* SBS2003 and when doing so it brings up the
IDE drive as the C drive which is not what I want." |
I did. The idea behind making the BIOS not seeing the IDE drive as a
bootable drive was so that during the install SBS2003 would want to install
itself on one of the SCSI drives, not the IDE drive. Thats what I did years
ago for Win95. The same thing applies to SBS2003. Can SBS2003 be installed
to an extended (IDE) partition or a slave (IDE) drive?
In this entire thread, only two people ("daytripper" and "Eric Gisin")
offered working solutions that the OP could've left with and actually used.
I didn't see any solution that you offered to the OP, all I see are spouts
of how everyone else is "wrong" and "clueless" except you. Go ahead include
me in that group as well, if you please. I could /care less/.
Seriously, this is dragging on about something very simple to begin with.
After this post, I won't be following this thread as it is a silly and
pointless waste of time.
Have a good day. |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted:
Thu Oct 27, 2005 6:19 pm Post subject:
Re: SCSI as C drive not IDE as C drive |
|
|
"Erzsm" <nospam@nowhere.ever> wrote in message news:9NZ6f.91020$tD4.61906@tornado.ohiordc.rr.com
| Quote: | "Folkert Rienstra" wrote
Right, now read the OP again. Especially where it says:
" I am currently *installing* SBS2003 and when doing so it brings up the
IDE drive as the C drive which is not what I want."
I did. The idea behind making the BIOS not seeing the IDE drive as a
bootable drive was so that during the install SBS2003 would want to install
itself on one of the SCSI drives, not the IDE drive.
|
But doesn't change the drive lettering for NT/2K/XP etc.
| Quote: | Thats what I did years ago for Win95.
|
Win9x/me doesn't remember drive letters. NT/2K/XP does.
| Quote: | The same thing applies to SBS2003.
|
Nope.
| Quote: | Can SBS2003 be installed
to an extended (IDE) partition or a slave (IDE) drive?
|
Nope. You still don't get it (or refuse to get it).
It is not the issue. The drive letters are.
| Quote: |
In this entire thread, only two people ("daytripper"
|
Only if extended_partitions_only changes drive lettering for NT/2K/XP.
| Quote: | and "Eric Gisin") offered working solutions that the OP could've left
with and actually used.
|
Even someone as stupid as you can find that I offered the same solution as
Eric. Because it isn't *your* solution, that doesn't mean I didn't offer any.
| Quote: | I didn't see any solution that you offered to the OP,
|
So you are a troll, as it is quite obvious that I did.
| Quote: | all I see are spouts of how everyone else is "wrong" and "clueless"
except you. Go ahead include me in that group as well, if you please.
|
You know you are wrong, don't you, and you don't like it one bit.
Isn't that why you conveniently snipped your other mistakes from
this post (master vs slave issue) . I leave it to others to rate you.
| Quote: | I could /care less/.
|
Nonsense. If you didn't care you wouldn't have responded.
| Quote: |
Seriously, this is dragging on about something very simple to begin with.
|
Yup.
Yet you couldn't even understand the real question being about drive
letters, not the drive being booted from.
| Quote: | After this post, I won't be following this thread as it is a silly and
pointless waste of time.
|
That's what they all say when they they got their noses rubbed in their own shit.
You too. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in