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.

    my e1705 is going back to the repair depot...again

    Discussion in 'Dell' started by carlislegeorge, Jun 23, 2006.

  1. carlislegeorge

    carlislegeorge Notebook Consultant

    Reputations:
    1
    Messages:
    205
    Likes Received:
    0
    Trophy Points:
    30
    :mad: :mad:

    well i tried the sd card reader for the first time today....no go...same problem i had with usb...device correctly identified but the system tries to find a driver...tech support says "replace motherboard" but excuse me they just did that to correct the usb problem...oh well...one month old laptop and two trips to the repair depot...tell me again how reliable dell is compared to ibm... :( ....

    checked out dell community forums and this is a very common problem...downloaded the very latest ricoh drivers...no go...sux...i guess i could just delete the device from the system and reboot to see if it loads properly...what do i have to lose at this point :mad:
     
    carlislegeorge, Jun 23, 2006
    #1
  2. lnd svyr

    lnd svyr Notebook Enthusiast

    Reputations:
    0
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    5
    Oh Boy! I have been meaning to get a card and try it simply to be sure it works. I guess I had better get to steppin'.
     
    lnd svyr, Jun 23, 2006
    #2
  3. carlislegeorge

    carlislegeorge Notebook Consultant

    Reputations:
    1
    Messages:
    205
    Likes Received:
    0
    Trophy Points:
    30
    well that just compounded the problem...the system couldn't even identify the SD card controller after i deleted and rebooted...had to do system restore to get it back...maybe it is the mobo after all...
     
    carlislegeorge, Jun 23, 2006
    #3