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.

    Everex 2053T Cannot find resources, HELP!

    Discussion in 'Other Manufacturers' started by rickyt63, Aug 8, 2009.

  1. rickyt63

    rickyt63 Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    Hi,
    I've recently purchased a refurbished Everex 2053T laptop.
    However device manager show in both XP & Vista the following:
    - Device cannot find enough resource to load (code 12). :mad:
    Ethernet contoller (code 12)
    SDA standard SD host controller (code12)
    Generic Cardbus controller (code12)

    My bios is AMI ver R1.05 Dated 09/24/2008

    Any help solving these problems is greatly appreciated.

    Thanks in advance
     
  2. NJoy

    NJoy Няшka

    Reputations:
    379
    Messages:
    857
    Likes Received:
    1
    Trophy Points:
    31
    have you tried to contact the seller and ask for apropriate drivers?
     
  3. booboo12

    booboo12 Notebook Prophet

    Reputations:
    4,062
    Messages:
    4,272
    Likes Received:
    96
    Trophy Points:
    116
    It appears that Everex has left the US market. Support is limited though the Everex site is providing driver downloads: http://www.everex.com.tw/us

    Find your computer model in the dropdown list system on their site and get not only the drivers for the stuff that's missing in device manager, but all of them. In case you need them in the future.
     
  4. rickyt63

    rickyt63 Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    Hi NJoy & Booboo12,

    First of all, Thanks for response.
    - I do have both recovery CD (XP & Vista) with all the drivers.
    - Also DL'ed all available updated drivers from net.
    I've tried to fresh installs from both OS several times but still having same issues (code12). The only thing I could think of is the Bios dated 09-2008 instead of 2007 (they may changed & screwed up IRQ settings in latter Bios).

    Flash 2007 Bios from Twinhead (same model) but still same problem!!.
    Anyone who still have 2053T original Bios could extract & send to me ???
    Any help is greatly appreciated.

    Thanks
     
  5. NJoy

    NJoy Няшka

    Reputations:
    379
    Messages:
    857
    Likes Received:
    1
    Trophy Points:
    31
    could it be hardware related?
     
  6. rickyt63

    rickyt63 Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    could it be hardware related?
    Hmm ... I really don't know!
    Both XP & Vista detected these hardwares during fresh installations.

    May be it is this:
    90% of system errors are sitting in front of their PCs
    :eek: :eek: :eek:
     
  7. NJoy

    NJoy Няшka

    Reputations:
    379
    Messages:
    857
    Likes Received:
    1
    Trophy Points:
    31
    quite often malfunctioning hardware is detected by windows but fails to go any further. For example, my fried GF6200 on my old machine still works(barely=) but only with default MS drivers, and I've seen many times when Windows would detect hardware but couldn't recognise it due to a hadware problem.
     
  8. NJoy

    NJoy Няшka

    Reputations:
    379
    Messages:
    857
    Likes Received:
    1
    Trophy Points:
    31
    actually, lets solve it. First, download and install Everest. It should help us find the manufacturer for the card reader. Cardbus controller should be part of cardreader. Next, can you open the back where your wifi is (i assume it's the wifi card that is showing as Ethernet Controller) and have a look at it? It must have the make and model number. If it's Atheros, windows won't know where to find drivers for it. The only thing that confuses me is that "device cannot find enough resources to load". Usually, it is a bad sign