The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    HEL80 Problem

    Discussion in 'Other Manufacturers' started by csinth, Nov 29, 2008.

  1. csinth

    csinth Snitch?

    Reputations:
    181
    Messages:
    1,277
    Likes Received:
    0
    Trophy Points:
    55
    I encountered a major problem today. First of all, the keyboard wasn't working (which is an occasional problem I have coming out of standby mode; I think it's caused by Windows XP, because if I go back into standby mode and out, it starts working again).

    Then the computer became very slow.. it seemed to be running smooth for a few seconds, then it would go really slowly for a second, and then smooth, and so on. So I restarted it, and during the boot it started repeating this over and over again:

    Code:
    Intel UNDI, PXE-2.1 (build 082)
    Copyright (C) 1997-2000 Intel Corporation
    
    For Realtek RTL8111B/8168 Gigabit Ethernet Controller v2.01 (060109)
    PXE-E61: Media test failure, check cable
    PXE-M0F: Exiting PXE ROM.
    So I tried going to the BIOS, and I disabled LAN, which then resulted in:
    Code:
    Operating system not found.
    But when I turned LAN back on, the first message started appearing.

    I don't think anything out of the ordinary happened to it today, though I accidentally left it on all day on my desk (which really isn't a problem). It hasn't been dropped or anything like that.. although last night, according to Notebook Hardware Control, the hard drive was getting too hot (55 degrees Celsius). Perhaps another hard drive crash?

    Thank you for your help.
     
  2. daljeet

    daljeet Notebook Evangelist

    Reputations:
    31
    Messages:
    366
    Likes Received:
    0
    Trophy Points:
    30
    Try following stuff:

    1)Try to disable programs which you don't need in startup, from msconfig (type in run)
    2) Try Disk cleapup & system defragmenter.
    3) Check realtak drivers under newtwork adapter and try to disable realtak from device hardware and reboot your system, i hope that msg wont appears again, not sure it might be hardware or drivers problem.
     
  3. andyasselin

    andyasselin Notebook Deity

    Reputations:
    140
    Messages:
    1,690
    Likes Received:
    0
    Trophy Points:
    55
    IF your computer get pxe boot msg ether you bios boot order is wrong or you hard disk is failing and try boot to network after fail boot form hard disk

    what is model you hard disk you can get company daignostice to check to the disk
     
  4. csinth

    csinth Snitch?

    Reputations:
    181
    Messages:
    1,277
    Likes Received:
    0
    Trophy Points:
    55
    It won't boot at all... the message simply repeats itself over and over.

    I'm backing up my data right now.. I'm using a bootable linux from a USB drive, and it seems to be copying the data just fine.

    I think the disk manufacturer was Western Digital.. but I'm not positive. I'll check after I back up all my data.
     
  5. andyasselin

    andyasselin Notebook Deity

    Reputations:
    140
    Messages:
    1,690
    Likes Received:
    0
    Trophy Points:
    55
  6. Atook

    Atook Notebook Evangelist

    Reputations:
    80
    Messages:
    308
    Likes Received:
    9
    Trophy Points:
    31
    One thing you can try in these situations is running chkdsk, there may be an error in your MBR that can be fixed, and you'll be up and running again.
     
  7. band-aid

    band-aid Notebook Consultant

    Reputations:
    1
    Messages:
    128
    Likes Received:
    0
    Trophy Points:
    30
    Whats happening is your computer is trying to boot via PXE over the network. This can be because it failed to boot from your hard drive (MBR or bad drive as someone stated earlier) or because your boot order is screwed up in the BIOS.