Startup problem

I

ilyaz

I have Windows XP SP2 on my eMachine T1105. This machine is on my wireless
network (2 computers). Everything was fine until recently when on a bootup I
got this warning: <Resource Conflict - PCI Network controller in slot 02.
Bus: 01, Device: OD, Function: 0. Press F1 to continue>. Pressing F1
advances the bootup and Windows starts and works normally.
May someone please tell me how to correct this problem?
 
S

Sharon F

I have Windows XP SP2 on my eMachine T1105. This machine is on my wireless
network (2 computers). Everything was fine until recently when on a bootup I
got this warning: <Resource Conflict - PCI Network controller in slot 02.
Bus: 01, Device: OD, Function: 0. Press F1 to continue>. Pressing F1
advances the bootup and Windows starts and works normally.
May someone please tell me how to correct this problem?

"Press F1" messages typically come from BIOS instead of Windows. This would
be BIOS complaining about the configuration of the network controller
within the BIOS settings. On some systems, I've disabled COM port 2 in
BIOS. If using a dialup connection, everything should still work (COM port
1 is still available) but if not, easy to reverse the setting again. This
frees up a resource that could be used instead for the NIC.

Another tack would be to set "plug and play" operating system to yes. "Yes"
allows the operating system to handle the assignment of resources - BIOS
skips all but the most basic enumeration. "No" means BIOS enumerates the
hardware and the OS works with those results - building or moving stuff
around within the OS config to get the hardware operable. Because of the
alterations on the OS level, your computer appears to work fine even though
BIOS complains. By changing to Yes the BIOS should not complain about
configuration for the NIC.

NOTE: By changing to yes, you may trigger activation. All hardware is the
same but you are forcing the operating system to look at it differently.
Hopefully that won't happen but feel that I must mention the possibility.

An updated BIOS might get rid of the resource problem too but seems heavy
handed for such a small error.

A painless thing to try would be entering BIOS. Look over the config for
the NIC. Make no changes and exit choosing "save changes." Even though
there were no changes, the act of "saving" sometimes sets the proper
configuration info back to what it should be.
 
I

ilyaz

Sharon,
thanks for your detailed suggestions. I appreciate it. Apparently, I fixed
the problem by setting BIOS to Default and saving it. Although there were no
previous changes (at least not by me!), the trick worked. Exactly as you
suggested...
Thanks for your help!
Ilya
 
S

Sharon Fink

ilyaz said:
Sharon,
thanks for your detailed suggestions. I appreciate it. Apparently, I fixed
the problem by setting BIOS to Default and saving it. Although there were no
previous changes (at least not by me!), the trick worked. Exactly as you
suggested...
Thanks for your help!
Ilya

You're most welcome, Ilya!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top