SATA problem stops system booting
Richard
quickly.
Following the removal of a pair of SATA drives configured for 0 RAID
which I reformatted before their removal, I now cannot run this mainly
SCSI system with any of the other SATA drives connected. This is what
happens:
After displaying the TYAN message for a time I then get a system error
message giving two options. Continue and run setup. If I continue I
then get a screen saying hit any key but if I do nothing it just moves
on and then stops at the error message Operating system not found.
Obviously taking the run setup option takes me to the BIOS screens.
In boot priority I have Legacy floppy drives, IDE CD, PCI SCSI and my
SCSI boot drive identified. It is still like this when I connect a SATA
drive.
In the excluded from boot order are the following:
PCI BEV: NVIDIA Boot Agent 229.052
PCI BEV: 2-NVIDIA Boot Agent229.0
PCI SCSI: 02,39320A B: 0 SEAGATE S
IDE CD: and then the name of that drive (I've got two CD drives on the
system)
Legacy Network card
I have all the other SCSI drives disconnected at this stage apart from
the C boot drive which is a SCSI drive whilst trouble shooting to keep
things as simple as possible.
Hope that gives someone thoughts as to why connecting one SATA drive
brings up the booting problem and when it is unplugged there is no
booting problem.
Many thanks
Richard
PS this is an XP Pro 64 system
--
Conor
Have you reconfigured the nVidia Boot Agent?
--
Conor
www.notebooks-r-us.co.uk
I'm not prejudiced. I hate everybody equally.
Richard
snip
>>
>> PS this is an XP Pro 64 system
>
>Have you reconfigured the nVidia Boot Agent?
>
Thanks for stepping forward Conor, much appreciated <G>
No but I have to admit to ignorance as to what would be involved and why
it should be necessary as the system worked fine before the removal of
the two RAID drives. There was a temp file on them if I remember
correctly and it was warned before deleting the partition on them that
they were in use and did I want to proceed! Neither of these drives
are now on the system, and it is only when I plug in one of the two
other SATA drives that were connected that the system will not boot off
the SCSI boot drive.
Hope this may throw some light on the problem.
Cheers
Richard
--
Richard
>In his posting of Sun, 20 Dec 2009, Conor writes
>snip
>
>>>
>>> PS this is an XP Pro 64 system
>>
>>Have you reconfigured the nVidia Boot Agent?
Can anyone help me with how one does the above as it strikes me that
this could be significant<G> BTW I've got the system booting reliably
whilst connected to the two SATA drives. Only problem is that they are
not seen! What a bummer of a weekend this has been!
Cheers
Richard
Jaimie Vandenbergh
wrote:
Sounds like your BIOS forces SATA as boot priority over PCI-SCSI. That
is, it's not really paying close attention to the boot settings you've
set.
Is there a later BIOS for this board?
I had something similar with an Epox board some time ago, where it
would insist on booting off an IDE hard drive if there was one in the
system (optical drives didn't bother it). Fixed with a BIOS update.
Cheers - Jaimie
--
I love VoIP. You don't get people phoning up to complain that the
network is down. -- Peter Corlett, ASR
Richard
>On Sun, 20 Dec 2009 11:48:46 +0000, Richard <ric...@spamfree.co.uk>
>wrote:
>
>>In his posting of Sun, 20 Dec 2009, Conor writes
>>snip
>>
>>>>
>>>> PS this is an XP Pro 64 system
>>>
>>>Have you reconfigured the nVidia Boot Agent?
>>>
>>
>>Thanks for stepping forward Conor, much appreciated <G>
>>
>>No but I have to admit to ignorance as to what would be involved and why
>>it should be necessary as the system worked fine before the removal of
>>the two RAID drives. There was a temp file on them if I remember
>>correctly and it was warned before deleting the partition on them that
>>they were in use and did I want to proceed! Neither of these drives
>>are now on the system, and it is only when I plug in one of the two
>>other SATA drives that were connected that the system will not boot off
>>the SCSI boot drive.
>>
>>Hope this may throw some light on the problem.
>
>Sounds like your BIOS forces SATA as boot priority over PCI-SCSI. That
>is, it's not really paying close attention to the boot settings you've
>set.
Thanks Jamie for your post.
>
>Is there a later BIOS for this board?
Yes and when I have a moment I will with fear and trepidation have a go.
>
>I had something similar with an Epox board some time ago, where it
>would insist on booting off an IDE hard drive if there was one in the
>system (optical drives didn't bother it). Fixed with a BIOS update.
Sounds like a sensible way to go!
Cheers
Richard
>
> Cheers - Jaimie
--
Clint Sharp
<ric...@spamfree.co.uk> writes
>Hope that gives someone thoughts as to why connecting one SATA drive
>brings up the booting problem and when it is unplugged there is no
>booting problem.
and then try again.
>
>Many thanks
>
>Richard
>
>PS this is an XP Pro 64 system
--
Clint Sharp
Richard
Thanks Clint
I find it very puzzling that this computer was quite happy to run the
SCSI boot drive and three other SCSI drive in addition to two SATA
drives and two SATA drives in a Raid configuration, but when the RAID
drives are removed then it will not play nicely with the remaining two
SATA drives. I cannot return to where I was because I wiped the two
Raid drives before removing them.
Why in the heck should it be such a problem to get the SATA drives to
run without all this hassle. SCSI seems for easy by comparison! I
must be very stupid or something to be having all this difficulty.
Cheers
Richard
--
Glyn Morgan
"Richard" <ric...@spamfree.co.uk> wrote in message
news:G6EUm4Tv...@eclipse.co.uk...
>
> I find it very puzzling that this computer was quite happy to run the SCSI
> boot drive and three other SCSI drive in addition to two SATA drives and
> two SATA drives in a Raid configuration, but when the RAID drives are
> removed then it will not play nicely with the remaining two SATA drives.
> I cannot return to where I was because I wiped the two Raid drives before
> removing them.
>
> Why in the heck should it be such a problem to get the SATA drives to run
> without all this hassle. SCSI seems for easy by comparison! I must be
> very stupid or something to be having all this difficulty.
>
I'm no expert at this but I wonder if the raid controller is still looking
for for a pair of SATA drives to implement raid0 and when it does not find
the the original striped pair goes on the allocate the other SATA drives,
which I assume are not formated as a striped pair.
I think the bios on one of our compurters has a setting to disable the raid
controller so it might be worth having a look at the bios settings. If you
are not aiming to use a raid pair anymore I guess you may need to disable
the raid controller.
Glyn
Richard
>
>"Richard" <ric...@spamfree.co.uk> wrote in message
>news:G6EUm4Tv...@eclipse.co.uk...
>>
>> I find it very puzzling that this computer was quite happy to run the
>>SCSI boot drive and three other SCSI drive in addition to two SATA
>>drives and two SATA drives in a Raid configuration, but when the RAID
>>drives are removed then it will not play nicely with the remaining two
>>SATA drives. I cannot return to where I was because I wiped the two
>>Raid drives before removing them.
>>
>> Why in the heck should it be such a problem to get the SATA drives to
>>run without all this hassle. SCSI seems for easy by comparison! I
>>must be very stupid or something to be having all this difficulty.
>>
>
>
>I'm no expert at this but I wonder if the raid controller is still
>looking for for a pair of SATA drives to implement raid0 and when it
>does not find the the original striped pair goes on the allocate the
>other SATA drives, which I assume are not formated as a striped pair.
Thanks Glyn
I have an idea, and this is what rather confuses me is that one needs
the RAID drivers on the system for SATA to work, however I do have the
RAID option disabled in the BIOS.
Cheers
Richard
>
>I think the bios on one of our compurters has a setting to disable the
>raid controller so it might be worth having a look at the bios
>settings. If you are not aiming to use a raid pair anymore I guess you
>may need to disable the raid controller.
>
>Glyn
--
Jaimie Vandenbergh
wrote:
>I have an idea, and this is what rather confuses me is that one needs
>the RAID drivers on the system for SATA to work, however I do have the
>RAID option disabled in the BIOS.
That's fairly normal - SATA drivers that also support RAID get called
RAID drivers. It's confusing, but it happens.
Cheers - Jaimie
--
BE PURE
BE VIGILANT
BEHAVE
Richard
>On Tue, 22 Dec 2009 11:13:58 +0000, Richard <ric...@spamfree.co.uk>
>wrote:
>
>>I have an idea, and this is what rather confuses me is that one needs
>>the RAID drivers on the system for SATA to work, however I do have the
>>RAID option disabled in the BIOS.
>
>That's fairly normal - SATA drivers that also support RAID get called
>RAID drivers. It's confusing, but it happens.
Thanks Jaimie Now if only I could get the SATA drives to work again it
would be a great step forward. At the moment to get the files off them
I have to plug them into another computer and drag the files across the
network! UGH.
Cheers
Richard
--
Richard
Still no SATA drives seen but I have managed to get of the TYAN screen
that was obscuring the boot process and can now get to the SCSI card
BIOS which I could never previously do so there has been progress of a
sort!
I have copped out of updating the BIOS at the moment because if I come
unstuck and need to get a replacement BIOS chip I want to be sure that I
have a suitably powerful spare system to fall back on to carry on
working with!
Just as a quick reminder of the history:
This system was built for me some years ago and is configured as
follows:
2 dual Opterons
4 SCSI drives one of which is the boot drive
2 SATA storage drives
2 WD Raptors in RAID 0
I have removed the two WD Raptors having first deleted the partitions on
both, and now although I can boot up and run the system fine, my two
remaining SATA drives are not seen. Can anyone please help me on this.
In the BIOS in the section below the line Excluded from boot order I
have the following entries:
PCI BEV: NVIDIA Boot agent 229.052
PCI BEV: NVIDIA Boot Agent 229.0
and then the listing of my non boot SCSI drives followed by
2nd CD drive
Legacy network card.
In the device manager I see under SCSI and RAID controllers my Adaptec
SCSI controller card and two entries for NVIDIA nForce4 Serial ATA RAID
Controller.
I have spent ages in trying to fathom out how to fix the SATA drive
problem but without any success and really do hope that someone can help
me. Thanks of course to all those who have tried previously, much
appreciated.
Cheers
Richard
--
Jaimie Vandenbergh
wrote:
>I have copped out of updating the BIOS at the moment because if I come
>unstuck and need to get a replacement BIOS chip I want to be sure that I
>have a suitably powerful spare system to fall back on to carry on
>working with!
Just do it. I've never, ever had a BIOS update problem, and no-one I
know ever has either. Even if you have a power outage or similar
halfway through the flash, the Tyan will have a rescue BIOS flasher
that you can trigger (alt-F2 or something, it should tell you now you
have the BIOS boot sequence visible).
Ah, memories... the time I had to hot-swap the BIOS chip itself for a
larger one! In order: boot up with the old 512k EEPROM chip only just
in place, pull it out with a plastic spudger when booted, replace it
with a 1meg one, press it down, and flash that with the latest update.
Cheers - Jaimie
--
"The idea that Bill Gates has appeared like a knight in shining armour to
lead all customers out of a mire of technological chaos neatly ignores
the fact that it was he who, by peddling second-rate technology, led them
into it in the first place." - Douglas Adams
Richard
>On Sat, 26 Dec 2009 13:03:33 +0000, Richard <ric...@spamfree.co.uk>
>wrote:
>
>>I have copped out of updating the BIOS at the moment because if I come
>>unstuck and need to get a replacement BIOS chip I want to be sure that I
>>have a suitably powerful spare system to fall back on to carry on
>>working with!
>
>Just do it. I've never, ever had a BIOS update problem, and no-one I
>know ever has either. Even if you have a power outage or similar
>halfway through the flash, the Tyan will have a rescue BIOS flasher
>that you can trigger (alt-F2 or something, it should tell you now you
>have the BIOS boot sequence visible).
>
>Ah, memories... the time I had to hot-swap the BIOS chip itself for a
>larger one! In order: boot up with the old 512k EEPROM chip only just
>in place, pull it out with a plastic spudger when booted, replace it
>with a 1meg one, press it down, and flash that with the latest update.
> Cheers - Jaimie
Jamie
Thanks for those reassuring words! I have flashed the BIOS on a MB many
years ago and it went OK, and this system is on a large UPS so outages
should not be an issue. However I'm still a little apprehensive as this
is my main work machine....what I earn my living with<G>
I remember that when the system was still only a year or so old I had
this same non recognition of the SATA drives problem and the boss of
Vadim computers, the people who had assembled it took me through the
steps on the phone. None of his support people has a clue how to do it
and had sent me off on various wild goose chases! Sadly Vadim Computers
folded some time ago...where are you Vadim when I need you! Which is
a long way of saying that I am likely to have the same problem even
if/when the BIOS are updated!
Cheers
Richard
--
Richard
>On Sat, 26 Dec 2009 13:03:33 +0000, Richard <ric...@spamfree.co.uk>
>wrote:
>
>>I have copped out of updating the BIOS at the moment because if I come
>>unstuck and need to get a replacement BIOS chip I want to be sure that I
>>have a suitably powerful spare system to fall back on to carry on
>>working with!
>
>Just do it. I've never, ever had a BIOS update problem, and no-one I
>know ever has either. Even if you have a power outage or similar
>halfway through the flash, the Tyan will have a rescue BIOS flasher
>that you can trigger (alt-F2 or something, it should tell you now you
>have the BIOS boot sequence visible).
>
>Ah, memories... the time I had to hot-swap the BIOS chip itself for a
>larger one! In order: boot up with the old 512k EEPROM chip only just
>in place, pull it out with a plastic spudger when booted, replace it
>with a 1meg one, press it down, and flash that with the latest update.
> Cheers - Jaimie
Well Jamie, I've taken the step but am presented with a red warning that
says this:
Phoenix Phlash 16 error Cannot flash if memory managers (eg. HIMEN)
present. Press any key to exit.
Now having escaped with my life intact can you suggest what I should do
please<G>
Cheers
Richard
--
Jeff Gaines
>Well Jamie, I've taken the step but am presented with a red warning that
>says this:
>
>Phoenix Phlash 16 error Cannot flash if memory managers (eg. HIMEN)
>present. Press any key to exit.
>
>Now having escaped with my life intact can you suggest what I should do
>please<G>
You need an absolutely plain boot disk. No himem.sys, no emms86.exe - in
fact you don't need autoexec.bat or config.sys (just rename them).
--
Jeff Gaines Dorset UK
640k ought to be enough for anyone.
(Bill Gates, 1981)
Richard
>On 26/12/2009 in message <vWXedYFn...@eclipse.co.uk> Richard wrote:
>
>>Well Jamie, I've taken the step but am presented with a red warning
>>that says this:
>>
>>Phoenix Phlash 16 error Cannot flash if memory managers (eg. HIMEN)
>>present. Press any key to exit.
>>
>>Now having escaped with my life intact can you suggest what I should
>>do please<G>
>
>You need an absolutely plain boot disk. No himem.sys, no emms86.exe -
>in fact you don't need autoexec.bat or config.sys (just rename them).
>
Thanks Jeff
I reads on the Tyan site that I should hit F5 when the floppy starts
which is what I did and all seems to go fine and the BIOS were
successfully flashed from what the messages said, but then the computer
hung. I had also read that I should take the precaution to clear the
CMOS, I looked at the Tyan manual but could not see the switch where it
showed it should be at the Tyan manual the spot where this should be
located so I unplugged the power cable and waited ten minutes. I has
read somewhere that I should do this after resetting the CMOS so figured
it would be a good thing to do.
I then reset the BIOS to boot from my C drive and the system booted to
the point where I was offered a start normally, safe mode etc. so I
tried to take the normally but nothing happened. I then turned off and
restarted and managed to take the Safe option and the screen filled with
stuff see below and is now stalled there. I so not want to just turn
off and start again in case I case more problems!
This is what is on screen at
thmulti(0)disk(0)rdisk(0)partition(2)\WINDOWS\system32\e moment.
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS\system32\drivers\colsnap.sys
then line after line of the same but different endings after drivers
The last two lines are different:
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS\appPatch\drvmain.sdb
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS\system32\acpitabl.dat
Hope someone can throw me a rope.
Cheers
Richard
--
Jaimie Vandenbergh
wrote:
>I had also read that I should take the precaution to clear the
>CMOS, I looked at the Tyan manual but could not see the switch where it
>showed it should be at the Tyan manual the spot where this should be
>located so I unplugged the power cable and waited ten minutes. I has
>read somewhere that I should do this after resetting the CMOS so figured
>it would be a good thing to do.
Unplugging the power cable won't do anything. You need to reset the
CMOS, because the new BIOS won't necessarily understand the old
settings that are saved in the CMOS.
Usually there's no switch, but a pair of jumper posts that you need to
pop a jumper on for a few seconds.
Cheers - Jaimie
--
"Phnglui mgwlnafthth Cthulhu rlyey wghnagl fthagn." "In his flat in Bromley,
drunk Cthulhu waits knitting? I think a few subtle typos may have crept into
into that one." "That explains why this shoggoth I summoned is only 3mm tall."
-- Peter da Silva and Peter Gutmann, asr
Jaimie Vandenbergh
wrote:
>multi(0)disk(0)rdisk(0)partition(2)\WINDOWS\system32\acpitabl.dat
This is probably the important one - the new BIOS is perhaps in the
wrong ACPI mode, which confuses the crap out of Windows.
Scratch what I said about jumpers in my other post. Go into the BIOS
and choose "set all to default", and then save and reboot.
If that still sticks during boot, go into the BIOS again and try other
ACPI modes until you either get a boot or run out.
Cheers - Jaimie
--
"It's people like that who make you realize how little you've accomplished.
It is a sobering thought, for example, that when Mozart was my age, he had
been dead for two years" - Tom Lehrer
Richard
>On Sat, 26 Dec 2009 23:44:18 +0000, Richard <ric...@spamfree.co.uk>
>wrote:
>
>>multi(0)disk(0)rdisk(0)partition(2)\WINDOWS\system32\acpitabl.dat
>
>This is probably the important one - the new BIOS is perhaps in the
>wrong ACPI mode, which confuses the crap out of Windows.
>
>Scratch what I said about jumpers in my other post. Go into the BIOS
>and choose "set all to default", and then save and reboot.
>
>If that still sticks during boot, go into the BIOS again and try other
>ACPI modes until you either get a boot or run out.
>
> Cheers - Jaimie
Thanks Jamie
After waiting an age after doing this with a - flashing at the top left
of the screen it eventually did boot up and after seeing that all seemed
to be OK I closed down hoping that it would then restart correctly.
Well it has only just and I thought it never was going to Can you
suggest what may need changing to avoid this huge delay>
Cheers
Richard
--
Jaimie Vandenbergh
wrote:
>In his posting of Sun, 27 Dec 2009, Jaimie Vandenbergh writes
>>
>>Scratch what I said about jumpers in my other post. Go into the BIOS
>>and choose "set all to default", and then save and reboot.
>
>After waiting an age after doing this with a - flashing at the top left
>of the screen it eventually did boot up
Phew!
>and after seeing that all seemed
>to be OK I closed down hoping that it would then restart correctly.
>Well it has only just and I thought it never was going to Can you
>suggest what may need changing to avoid this huge delay>
Does it have a huge delay second and subsequent boots? It might be a
one time thing from resetting the CMOS.
If it does, please specify where in the boot sequence it happens.
Cheers - Jaimie
--
Power corrupts, but intermittent power corrupts absolutely
-- Jeff Bell, asr
Richard
>On Sun, 27 Dec 2009 00:49:49 +0000, Richard <ric...@spamfree.co.uk>
>wrote:
>
>>In his posting of Sun, 27 Dec 2009, Jaimie Vandenbergh writes
>>>
>>>Scratch what I said about jumpers in my other post. Go into the BIOS
>>>and choose "set all to default", and then save and reboot.
>>
>>After waiting an age after doing this with a - flashing at the top left
>>of the screen it eventually did boot up
>
>Phew!
>
>>and after seeing that all seemed
>>to be OK I closed down hoping that it would then restart correctly.
>>Well it has only just and I thought it never was going to Can you
>>suggest what may need changing to avoid this huge delay>
>
>Does it have a huge delay second and subsequent boots? It might be a
>one time thing from resetting the CMOS.
>
>If it does, please specify where in the boot sequence it happens.
>
> Cheers - Jaimie
Jamie thanks for staying the course<G>
It happens after telling me about the SCSI controller and checking the
slots but this time it has gone straight in to the options for starting
in safe mode etc. I hit enter as it had high lighted the start in
normal mode but it did what it did on a previous occasion which is to
stick and I decided to start again, but I've done nothing this time as
I've been busy replying to you and loo and behold it has booted up!
Cheers
Richard
--
Richard
>
>After waiting an age after doing this with a - flashing at the top left
>of the screen it eventually did boot up and after seeing that all
>seemed to be OK I closed down hoping that it would then restart
>correctly. Well it has only just and I thought it never was going to
>Can you suggest what may need changing to avoid this huge delay>
>
>Cheers
>
>Richard
Jamie
I thought I would have a go with one of the SATA drives connected and
the system stalled with an error message as follows:
ERROR
Out of space for option ROMS! The option ROM for the following
device-PCI Mass Storage Controller in slot 02 bus:11, Device:04,
Function:01 was unable to run due to memory constraints.
Press F1 to resume, F2 to setup.
I cannot see what device the above is referring to as looking in D
manager neither the onboard SCSI controller or the Adaptec card have
this address.
Cheers
Richard
--
Richard
I am off to bed now just in case you wonder why no response <G>
Many thanks for you encouragement and help.
Cheers
Richard
--
Richard Kenward
Jeff Gaines
>Jamie
>
>I am off to bed now just in case you wonder why no response <G>
>
>Many thanks for you encouragement and help.
There's quite a few reports of this message with Tyan boards, e.g.:
http://www.tomshardware.co.uk/forum/page-177592_12_0.html
I've lost track of which board you have, sorry :-(
May be worth a Google for the message and your board model?
--
Jeff Gaines Dorset UK
All those who believe in psychokinesis raise my hand.
Richard
>There's quite a few reports of this message with Tyan boards, e.g.:
>http://www.tomshardware.co.uk/forum/page-177592_12_0.html
Thanks Jeff...Wow what an onslaught that poor guy had to take!
>
>I've lost track of which board you have, sorry :-(
It is the Tyan K8WE S2895
>
>May be worth a Google for the message and your board model?
>
>
I seem to have spent the last couple of days doing that but with my
limited technical knowledge of computers I have found it difficult to
understand all the issues.
Just to quickly fill you in. When the system was supplied at the end of
2005 it worked on the onboard SCSI and the SATA drives worked and it
booted up reasonably fast without large delays. However I soon found
that it was apt to loose the SCSI drives during the day's work, and the
system went back to the builders several times for the problem to be
solved. I suspected the SCSI controller and said as much, and in the
end I simply bought an Adaptec controlled and slapped it in .....problem
solved! However on the one or two occasions when the SATA drives
stopped working......brought on by on one occasion by my wiping the OS
drive (SCSI) to remove the dual boot, the builders boss took me through
a routine that fixed the problem. I know therefore that it is fixable
if one knows the hoops to jump through.
Thanks for your help.
Cheers
Richard
--
Richard
After further hours spent in going through all the possibilities in the
BIOS I connected one SATA drive up and then tried to boot up and after
about 40 seconds we arrived (with two beeps) at the screen telling me
that the 16384M of ram had passed and the error announcement of out of
space for Option ROMS (whatever they are) and the two options F1 to
continue and F2 to set up.
I decided to take the F1 option and then up came the flashing cursor at
the top left of the screen. Think that perhaps if I gave it enough
time I would have a successful boot up. After waiting for 140seconds
we arrived at the Windows XP Pro 64 setting up screen much to my
amazement!
With great apprehension I then went to disk management and could hardly
believe what I saw.....the SATA drive was visible!!!! I then closed
down and attached the second SATA drive and went through the same slow
boot process and that rive was also seen. I've now repeated this and
have again been successful.
I would like to thank all those who have stepped forward to help
me....you have been great...many, many thanks.
All that I need to do now is to work out why the heck the computer has
that 140 seconds where it does not appear to be doing anything. Oh
yes, and I need to set up a RAID 0 for four 15K Cheetah drives on an
additional Adaptec RAID controller card. Hope that will be trouble
free. Not something I have ever done...should be fun<G>
Cheers
Richard
--
Groove
news:rNUvrcRr...@eclipse.co.uk:
> All that I need to do now is to work out why the heck the computer has
> that 140 seconds where it does not appear to be doing anything..
Seen delays like this before where the system is looking for a network
boot. Might be worth checking this is not enabled in BIOS.
John Jordan
>
> I thought I would have a go with one of the SATA drives connected and
> the system stalled with an error message as follows:
>
> ERROR
>
> Out of space for option ROMS! The option ROM for the following
> device-PCI Mass Storage Controller in slot 02 bus:11, Device:04,
> Function:01 was unable to run due to memory constraints.
Option ROMs are chunks of code that devices use for pre-Windows
activities such as booting and setup screens. There's likely to be one
for the add-in SCSI controller, one for the onboard SCSI controller, one
for the onboard SATA controller (at least if it's in RAID or possibly
AHCI mode) and one for each boot-capable network adapter.
I'd strongly recommend disabling any of these that you don't need to
boot from. For network and SATA controllers you can usually disable the
ROMs without actually disabling the device.
Running out of space for option ROMs isn't necessarily a critical error,
as you're probably only using one of them.
--
John Jordan
Richard
snip
>Option ROMs are chunks of code that devices use for pre-Windows
>activities such as booting and setup screens. There's likely to be one
>for the add-in SCSI controller, one for the onboard SCSI controller,
>one for the onboard SATA controller (at least if it's in RAID or
>possibly AHCI mode) and one for each boot-capable network adapter.
>
>I'd strongly recommend disabling any of these that you don't need to
>boot from. For network and SATA controllers you can usually disable the
>ROMs without actually disabling the device.
>
>Running out of space for option ROMs isn't necessarily a critical
>error, as you're probably only using one of them.
>
John thanks in my quest for speeding the boot sequence up. I am a bit
fearful of disabling the wring option Rom....such as the video card! I
cannot at the moment see how I can tell which number slot applies to
which card! I'm sure that there must be a straightforward way. There
usually is when you know.
Cheers
Richard
--
John Jordan
>
> John thanks in my quest for speeding the boot sequence up. I am a
> bit fearful of disabling the wring option Rom....such as the video
> card!
Generally a BIOS will always load one video card BIOS, and the only
thing you can change is which it loads when you have multiple cards. In
the worst case you just reset the CMOS again.
> I cannot at the moment see how I can tell which number slot applies
> to which card! I'm sure that there must be a straightforward way.
> There usually is when you know.
Most of the devices will be onboard anyway, so the slot number won't be
useful. Device manager will tell you this information under properties
for each device though.
--
John Jordan
Richard
>Richard wrote:
>> John thanks in my quest for speeding the boot sequence up. I am a
>> bit fearful of disabling the wring option Rom....such as the video
>> card!
>
>Generally a BIOS will always load one video card BIOS, and the only
>thing you can change is which it loads when you have multiple cards. In
>the worst case you just reset the CMOS again.
Thanks John
Just tried it and the BIOS failed to load a video card and I had a
rather worrying time but after pressing the CMOS button all was well
again but not something I am going to do again...just in case I cannot
recover the situation!
>
>> I cannot at the moment see how I can tell which number slot applies
>> to which card! I'm sure that there must be a straightforward way.
>> There usually is when you know.
>
>Most of the devices will be onboard anyway, so the slot number won't be
>useful. Device manager will tell you this information under properties
>for each device though.
>
>
Thanks for trying to help.
Richard
--