Boot Device Change

  • Thread starter Thread starter rigadon
  • Start date Start date
R

rigadon

Hi everyone

I have a Shuttle SK43G and I have recently purchased a Shuttle 802.11
Wireless Adapter to connect to my home wireless network. Havin
installed the adapter (and attached it to an onboard USB connector a
advised in the manual) I now receive the following message on boo
up

Warning: The boot devices have been changed
BBS boot priority will be affected. Please enter setup to check

Press F1 to continue. Del to enter setup

If I press F1 the Shuttle boots us as per usual and the wireles
adapter works as expected. Pressing Del takes me into BIOS setting
but I'm not really familiar with these so they don't tell me much

Can someone please tell me what changes I need to make to get rid o
this message

Thank
Ja
 
Hi everyone!

I have a Shuttle SK43G and I have recently purchased a Shuttle 802.11b
Wireless Adapter to connect to my home wireless network. Having
installed the adapter (and attached it to an onboard USB connector as
advised in the manual) I now receive the following message on boot
up:

Warning: The boot devices have been changed.
BBS boot priority will be affected. Please enter setup to check.

Press F1 to continue. Del to enter setup.

If I press F1 the Shuttle boots us as per usual and the wireless
adapter works as expected. Pressing Del takes me into BIOS settings
but I'm not really familiar with these so they don't tell me much.

Can someone please tell me what changes I need to make to get rid of
this message?
Click to expand...

Try entering the bios, then exiting, "saving changes" (or
however it's worded) even though you didn't make changes.
 
You may have some type of "Boot from Network" setting that sees the wireless
card and tries to boot from it. That should be in the boot priority area of
the Bios, although there may be a setting elsewhere to enable or disable it.

Clark
 
You may have some type of "Boot from Network" setting that sees the wireless
card and tries to boot from it. That should be in the boot priority area of
the Bios, although there may be a setting elsewhere to enable or disable it.
Click to expand...

That may be true but if Pressing F1 to continue still boots,
there isn't a change necessary, only to get rid of the
warning message. That is, unless there is a lengthly pause
while the system looks for networked boot.
 
Clark is right on, on this one.

kony said:
it.

That may be true but if Pressing F1 to continue still boots,
there isn't a change necessary, only to get rid of the
warning message. That is, unless there is a lengthly pause
while the system looks for networked boot.
Click to expand...
 
Clark is right on, on this one.
Click to expand...

It is true that there may be some "boot from network"
option, but that doesn't mean much... for example there is
also likely to be a "boot from floppy" option, but it need
not be disabled, only set lower in the boot priority list.
Further, because the system does still boot, the boot
priority list is only an issue if there is a significant
delay. If there is no delay, the only remaining issue is
the cosmetic display on the screen and that user has not yet
entered bios and saved it again.

In short, there is no need to disable network boot
functionality to resolve this.
 
Your right(kind of)
Many systems will hang up, despite the boot hierarchy if the divice does not
report back, which would be the case if the boot rom was not actually
installed in the adapter.
 
Your right(kind of)
Many systems will hang up, despite the boot hierarchy if the divice does not
report back, which would be the case if the boot rom was not actually
installed in the adapter.
Click to expand...

No, it is the issue when there IS a boot rom. Without the
boot rom present there isn't any pause at all.

Further, it is not "despite the boot hierarchy" unless you
only mean some very isolated case where there was a severe
bios flaw. Generally speaking it does not happen.
 
I have serviced thousands of systems and I call them as I see them........
how many have you seen?
 
I have serviced thousands of systems and I call them as I see them........
how many have you seen?
Click to expand...


I think you'll overlooking some detail then, because it is
as I described- the network boot only causes a pause when it
TRYS to network boot, which it does IF a boot rom is
installed, not when there isn't one. If you've really come
across that many systems with this problem, I suspect
they're all very similar (even same) and have one specific
flaw in the bios- and suggest you update their bios. Again-
generally it does not happen as you describe.
 
Are you speaking theoretically or from experience, because as I said earlier
I have seen this happen on many occasions.

Things do not always go as planned (or designed)
 
By the way you can set your system to boot from the network in the Cmos
settings evan if you do not actually have a boot rom installed on the NIC.
 
By the way you can set your system to boot from the network in the Cmos
settings evan if you do not actually have a boot rom installed on the NIC.
Click to expand...


If the system has an integrated network adapter, it
"almost" always has a boot rom. I'd expect they all do but
not having done a survey...

As for a system with a NIC, but no boot rom, or really no
matter what the situation is, you still overlook one basic
fact- The problem is not "what it does" relating to network
booting, the problem is a notification of a device, a
cosmetic prompt to the user and a need to press a key NOT to
network boot (or not network boot) but simply an
acknowledgement of this by the user.

In other words, again no no no. The only solution that is
"usually" needed is to save the settings with NO change.
There was no call to change any network boot settings- the
system was booting fine!
 
This has gone on for so long that I forget what the original post was about.

How ever you still seem to be having a problem with what can (and has)
happened in many situations.

I am sure you have seen this one.

You set your first boot device to be your floppy drive.
Your second boot drive is your C:
Your third drive might be your CD

I f you start your computer with no disk in the floppy drive the system (int
19) checks the next drive in the sequence for boot code and if it finds it
your computer starts.

Now if you have been using your floppy (one without boot code) and forget to
remove it when you shut down your computer, and subsequently restart your
computer, you will get an error message and the system will halt until you
deal with it.

The same scenario can (and I have personally seen it happen) when "Boot from
Network Device" is selected and the NIC does not have a Boot Rom.

And you are not correct in stating that if it has an integrated NIC that it
has a Boot Rom, Boot Roms are not as common as they once were.

Now I have spent too much time debating this with you. Because this debate
seems to be the only thread left in this stream. I will no longer be
checking on it.

See you on the next problem
 
This has gone on for so long that I forget what the original post was about.

How ever you still seem to be having a problem with what can (and has)
happened in many situations.

I am sure you have seen this one.

You set your first boot device to be your floppy drive.
Your second boot drive is your C:
Your third drive might be your CD

I f you start your computer with no disk in the floppy drive the system (int
19) checks the next drive in the sequence for boot code and if it finds it
your computer starts.

Now if you have been using your floppy (one without boot code) and forget to
remove it when you shut down your computer, and subsequently restart your
computer, you will get an error message and the system will halt until you
deal with it.
Click to expand...

Unless the bios is buggy, this should not happen. When a
boot device is tried and fails, it is designed to proceed to
the next device. However, there was no mention of any
associated long-pause as would be seen if the network boot
were repetitively timing out.

The same scenario can (and I have personally seen it happen) when "Boot from
Network Device" is selected and the NIC does not have a Boot Rom.
Click to expand...

This should not happen. Many systems have the bios set to
"try other" or something to that effect and it can proceed
through the network boot option. It should not require user
intervention to proceed.
And you are not correct in stating that if it has an integrated NIC that it
has a Boot Rom, Boot Roms are not as common as they once were.
Click to expand...

Yes, they do!
Show me any semi-modern (say in the last 10 years) board
that does not.
 
Back
Top