Unsolved
This post is more than 5 years old
2 Posts
0
517283
June 24th, 2010 08:00
Wndows 7 operating system fails to load
Please help...
When starting my Studio 17 equipped with windows 7, I am receiving the following error message after the Dell screen.
Intel UNDI, PXE-2.1 (build 082)
Copyright (C) 1997-2000 Intel Corporation
This product is covered by one or more of the following patents:
US5,307,459, US5,434,872, UD5,732,094, US6, 570, 884, US6,115,776 and
US6,327,625
Realtek PCI Express Gigabit Ethernet Controller Series v2.26 (090219)
CLIENT MAC ADDR: <
ADMIN NOTE: MAC id removed per privacy policy> GUID: 44454C4C-####-####-####-############
DHCP.../ (<-- spinning curser for just under 2 miniutes, then DHCP .../ disappears and the following appears
PXE-E53: No Boot Filename Received
PXE-MOF: Exiting PXE ROM:
Then cycle continues indefinately...
Intel UNDI, PXE-2.1 (build 082)
Copyright (C) 1997-2000 Intel Corporation
This product is covered by one or more of the following patents:
US5,307,459, US5,434,872, UD5,732,094, US6, 570, 884, US6,115,776 and
US6,327,625
Realtek PCI Express Gigabit Ethernet Controller Series v2.26 (090219)
CLIENT MAC ADDR: 01 23 45 67 89 AB GUID: 44454C4C-####-####-####-############
PXE-E53: No Boot Filename Received
PXE-MOF: Exiting PXE ROM:
No Events found!
jackshack
6.4K Posts
0
June 24th, 2010 09:00
It appears your computer is set to boot from a network card. If this is what it is supposed to be doing, it can't find the boot files on the server and you need to speak to the administrator of your network.
If you are supposed to be booting from the hard drive in the machine you need to go to system setup and adjust the boot order, or disable the pxe function to show that it is not available.
In2Jesus
2 Posts
0
June 24th, 2010 12:00
Thank JackShack, I was able to correct the issue moments ago. In the set up utility I restored defaults, saved and the system rebooted OK. Not sure how systems defaults were changed.
jackshack
6.4K Posts
0
June 24th, 2010 13:00
You're welcome, I'm glad to see the issue has been resolved.
The setup parameters are not supposed to change on their own, but sometimes they change anyway. I've seen this happen on desktops when the NVRAM back-up battery voltage gets to be too low, but it usually causes the default settings to load rather than the unusual settings you have experienced.