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

On Thu, 16 Feb 2006 16:30:10 GMT, (E-Mail Removed)lid (rigadon)
wrote:

>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?

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

"kony" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Thu, 16 Feb 2006 16:30:10 GMT, (E-Mail Removed)lid (rigadon)
> wrote:
>
>>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?
>
> Try entering the bios, then exiting, "saving changes" (or
> however it's worded) even though you didn't make changes.

On Thu, 16 Feb 2006 23:43:19 GMT, "Clark" <(E-Mail Removed)>
wrote:

>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.

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" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Thu, 16 Feb 2006 23:43:19 GMT, "Clark" <(E-Mail Removed)>
> wrote:
>
> >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.
>
> 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.
>
>

On Sun, 19 Feb 2006 02:26:12 GMT, "don" <(E-Mail Removed)>
wrote:

>Clark is right on, on this one.

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.

"kony" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Sun, 19 Feb 2006 02:26:12 GMT, "don" <(E-Mail Removed)>
> wrote:
>
> >Clark is right on, on this one.
>
> 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.
>
>

On Sun, 19 Feb 2006 04:22:51 GMT, "don" <(E-Mail Removed)>
wrote:

>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.
>

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?

"kony" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Sun, 19 Feb 2006 04:22:51 GMT, "don" <(E-Mail Removed)>
> wrote:
>
> >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.
> >
>
> 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.

On Fri, 24 Feb 2006 02:47:54 GMT, "don" <(E-Mail Removed)>
wrote:

>I have serviced thousands of systems and I call them as I see them........
>how many have you seen?
>


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.