Custom boot.ini file required for raid/scsi hard drives

[Jimbo]

I have an Adaptec 2120s raid card which feeds two scsi hard drives in raid
0(stripe) as Drive C
I also have an Adaptec 39320 Scsi card which runs two hard drives each with
XP (Drives G and H) on.
Normally, if they where all scsci I would be able to boot to any of the 3
os's by virtue of a standard boot ini selection menu at boot time.
However, as one OS is cofigured in raid, and the other two in scsi, with the
runtime bios enabled on both these two cards, what I need is a custom boot
ini that will give me the option of selecting any of the 3 hard drives at
boot
time.
If the 'standard' boot ini on Drive C is left in when the two cards run,
they conflict and everything comes to a halt.
Adaptec tell me that a custom boot ini will solve the problem, they will not
supply the info!!
Does any one have any idea as to what the custom boot ini should look like?
Thanks
Jim

 

[Guest]

my i suggest that you copy and paste your current boot.ini herein?

You can open it via notepad. Just be sure that the open dialog box is set to
see "all files" and not just txt.

 

[Jimbo]

Hi Ben
Herewith as asked.
The "New Seagate...." line will be the new raid paired with another
identical drive, the Fuji and HP
will be the single scsi drives......
Thanks
Jim


[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="New Seagate Microsoft Windows
XP Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Fuji Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(3)partition(1)\WINDOWS="HP146G Microsoft Windows XP
Professional" /fastdetect

 

[Guest]

yeh, just as an offhand thought, i looks like that 2 seperate boot.ini files
would help resolve the conflict. I remembered reading something about not
beng able to boot from one hd to another when raid's are involved.

I don't have a real solution but what comes to mind quickly is to make an
autoexec.bat file that gives you the option to load either boot.ini

But i think that autoexec.bat files are msdos and can not launch before
win.ini

Then the other thing that comes to mind is to make a boot cd for the os that
cannot be launched with your current boot.ini.

hmm, maybe you would be able to launch either os's from a cd boot disk that
had a boot.ini..... just a thought. Unfortunately, I have never incurred
this issue and I suppose that i have willfully refrained myself from creating
a somewhat perplexing scenerio like you have.

If i find anything that will help, i will be happy to forward the info to
you. Please leave an email address in your next reply......

Wished I could have provided the exact answer for you.....
--
~~~~~~~~~~

"Ordinary guy trying to help ordinary people w/ ordinary problems w/
ordinary solutions. Hey Luigi ! That''sa extraordinary!

Hi Ben
Herewith as asked.
The "New Seagate...." line will be the new raid paired with another
identical drive, the Fuji and HP
will be the single scsi drives......
Thanks
Jim


[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="New Seagate Microsoft Windows
XP Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Fuji Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(3)partition(1)\WINDOWS="HP146G Microsoft Windows XP
Professional" /fastdetect

my i suggest that you copy and paste your current boot.ini herein?

You can open it via notepad. Just be sure that the open dialog box is set
to
see "all files" and not just txt.

 

[Guest]

just some clues, I've visited some sites that mentioned "multiboot cd's"

also, i wonder if the dos command bootcfg / redistribution might help... do
a bootcfg /? to see the option...

I'll keep looking
--
~~~~~~~~~~

"Ordinary guy trying to help ordinary people w/ ordinary problems w/
ordinary solutions. Hey Luigi ! That''sa extraordinary!

yeh, just as an offhand thought, i looks like that 2 seperate boot.ini files
would help resolve the conflict. I remembered reading something about not
beng able to boot from one hd to another when raid's are involved.

I don't have a real solution but what comes to mind quickly is to make an
autoexec.bat file that gives you the option to load either boot.ini

But i think that autoexec.bat files are msdos and can not launch before
win.ini

Then the other thing that comes to mind is to make a boot cd for the os that
cannot be launched with your current boot.ini.

hmm, maybe you would be able to launch either os's from a cd boot disk that
had a boot.ini..... just a thought. Unfortunately, I have never incurred
this issue and I suppose that i have willfully refrained myself from creating
a somewhat perplexing scenerio like you have.

If i find anything that will help, i will be happy to forward the info to
you. Please leave an email address in your next reply......

Wished I could have provided the exact answer for you.....
--
~~~~~~~~~~

"Ordinary guy trying to help ordinary people w/ ordinary problems w/
ordinary solutions. Hey Luigi ! That''sa extraordinary!

Hi Ben
Herewith as asked.
The "New Seagate...." line will be the new raid paired with another
identical drive, the Fuji and HP
will be the single scsi drives......
Thanks
Jim


[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="New Seagate Microsoft Windows
XP Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Fuji Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(3)partition(1)\WINDOWS="HP146G Microsoft Windows XP
Professional" /fastdetect

my i suggest that you copy and paste your current boot.ini herein?

You can open it via notepad. Just be sure that the open dialog box is set
to
see "all files" and not just txt.


--
~~~~~~~~~~~
"To be a 0 or is it to be the 1 ?
That is the data".......W.Gatespeare


:

I have an Adaptec 2120s raid card which feeds two scsi hard drives in
raid
0(stripe) as Drive C
I also have an Adaptec 39320 Scsi card which runs two hard drives each
with
XP (Drives G and H) on.
Normally, if they where all scsci I would be able to boot to any of the 3
os's by virtue of a standard boot ini selection menu at boot time.
However, as one OS is cofigured in raid, and the other two in scsi, with
the
runtime bios enabled on both these two cards, what I need is a custom
boot
ini that will give me the option of selecting any of the 3 hard drives at
boot
time.
If the 'standard' boot ini on Drive C is left in when the two cards run,
they conflict and everything comes to a halt.
Adaptec tell me that a custom boot ini will solve the problem, they will
not
supply the info!!
Does any one have any idea as to what the custom boot ini should look
like?
Thanks
Jim

 

[Jimbo]

Hi Ben
I think the trick must be to identify which Adaptec Card it needs to boot
from
in the boot ini.
The bios must be enabled on both Cards otherwise boot managers cannot see
the
prospective drives......... to switch too.
Why Adaptec cannot provide some ideas on this situation, which must be
fairly
common, I have no idea.
Jim

just some clues, I've visited some sites that mentioned "multiboot cd's"

also, i wonder if the dos command bootcfg / redistribution might help...
do
a bootcfg /? to see the option...

I'll keep looking
--
~~~~~~~~~~

"Ordinary guy trying to help ordinary people w/ ordinary problems w/
ordinary solutions. Hey Luigi ! That''sa extraordinary!

yeh, just as an offhand thought, i looks like that 2 seperate boot.ini
files
would help resolve the conflict. I remembered reading something about
not
beng able to boot from one hd to another when raid's are involved.

I don't have a real solution but what comes to mind quickly is to make an
autoexec.bat file that gives you the option to load either boot.ini

But i think that autoexec.bat files are msdos and can not launch before
win.ini

Then the other thing that comes to mind is to make a boot cd for the os
that
cannot be launched with your current boot.ini.

hmm, maybe you would be able to launch either os's from a cd boot disk
that
had a boot.ini..... just a thought. Unfortunately, I have never
incurred
this issue and I suppose that i have willfully refrained myself from
creating
a somewhat perplexing scenerio like you have.

If i find anything that will help, i will be happy to forward the info to
you. Please leave an email address in your next reply......

Wished I could have provided the exact answer for you.....
--
~~~~~~~~~~

"Ordinary guy trying to help ordinary people w/ ordinary problems w/
ordinary solutions. Hey Luigi ! That''sa extraordinary!

Hi Ben
Herewith as asked.
The "New Seagate...." line will be the new raid paired with another
identical drive, the Fuji and HP
will be the single scsi drives......
Thanks
Jim


[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="New Seagate Microsoft
Windows
XP Professional" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Fuji Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(3)partition(1)\WINDOWS="HP146G Microsoft Windows
XP
Professional" /fastdetect



my i suggest that you copy and paste your current boot.ini herein?

You can open it via notepad. Just be sure that the open dialog box is
set
to
see "all files" and not just txt.


--
~~~~~~~~~~~
"To be a 0 or is it to be the 1 ?
That is the data".......W.Gatespeare


:

I have an Adaptec 2120s raid card which feeds two scsi hard drives
in
raid
0(stripe) as Drive C
I also have an Adaptec 39320 Scsi card which runs two hard drives
each
with
XP (Drives G and H) on.
Normally, if they where all scsci I would be able to boot to any of
the 3
os's by virtue of a standard boot ini selection menu at boot time.
However, as one OS is cofigured in raid, and the other two in scsi,
with
the
runtime bios enabled on both these two cards, what I need is a
custom
boot
ini that will give me the option of selecting any of the 3 hard
drives at
boot
time.
If the 'standard' boot ini on Drive C is left in when the two cards
run,
they conflict and everything comes to a halt.
Adaptec tell me that a custom boot ini will solve the problem, they
will
not
supply the info!!
Does any one have any idea as to what the custom boot ini should
look
like?
Thanks
Jim