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.

Latitude E6510 Imaging & Network Problems

Discussion in 'Dell Latitude, Vostro, and Precision' started by jlacroix, Sep 16, 2010.

Thread Status:
Not open for further replies.
  1. jlacroix

    jlacroix Notebook Consultant

    Reputations:
    30
    Messages:
    200
    Likes Received:
    1
    Trophy Points:
    31
    I'm hoping someone can help me, I've looked through Google and cannot figure this out.

    My company bought five E6510's, and we're going to be buying more for our sales force. I am setting up the base image for sysprep (we're using Windows XP) and a couple of things in the Device Manager have yellow exclamation marks (PCI to Cardbus Bridge and IEEE 1394 Controller).

    I have tried reinstalling the chipset drivers, but it doesn't work. If I rightclick either device in the Device Manager and click "update driver", you see the file copy animation like it found the driver it needed, but then fails out and says "An error occurred during the installation of this device. Access is denied".

    I want to ensure you that I am indeed logged in as administrator. Have you guys run into this?

    Also a second problem. At least two of the E6510's cannot connect to the network, by ethernet or wireless. In fact, not even the Clonezilla disc I used for imaging on the reference machine (that worked fine) works on several of them for a network connection.
     
  2. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,839
    Likes Received:
    2,154
    Trophy Points:
    581
    The free-fall sensor driver (under applications) has been overlooked by a few people. I also needed to install the AMT-HECI driver on my E6410 to get rid of an unknown device.

    I can't explain the network problem. Can't you start moving to Windows 7? There's XP mode available for any backwards-compatible software problems.

    John
     
  3. jlacroix

    jlacroix Notebook Consultant

    Reputations:
    30
    Messages:
    200
    Likes Received:
    1
    Trophy Points:
    31
    Alright, I solved the first issue. Damn Kaspersky antivirus. It wasn't supposed to be in the base image, but it was. Once I removed it, everything as far as drivers go was fixed.

    The network issue still remains. It's really weird. All five laptops are the exact same, bought at the exact same time. The network (wireless and wired) does not function on at least two of them, regardless of OS. I am going to be testing this further in about an hour.

    The director here hasn't approved Windows 7 yet for rollout. We had one computer that had to be Windows 7 (vendor requirement for their software) and I found that Sysprep is a major PITA with Windows 7 and consumed three days of my time just to get it working half right. I still get prompts during Sysprep on that Windows 7 image that I don't want, so we would have some issues to figure out first.
     
  4. GKDesigns

    GKDesigns Custom User Title

    Reputations:
    115
    Messages:
    1,080
    Likes Received:
    2
    Trophy Points:
    56
    Check if LAN WLAN is enabled in the BIOS. Does that side slide switch switch OFF the LAN as well as the WLAN?

    GK
     
  5. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,839
    Likes Received:
    2,154
    Trophy Points:
    581
    Thanks for the update. That product seems to be over-zealous. IIRC it has fouled up BIOS updates on Samsung notebooks.

    John
     
  6. jlacroix

    jlacroix Notebook Consultant

    Reputations:
    30
    Messages:
    200
    Likes Received:
    1
    Trophy Points:
    31
    Alright, everything is solved. Thanks guys. Kaspersky was responsible for the driver problem. It wasn't supposed to be in the base image, but it was there. Even when I disabled its protection, it still prevented drivers from installing. I had to completely remove Kaspersky to get it working and as soon as I did, the drivers were perfect (on their own without any tweaking).

    Second, the first two laptops had no issues contacting our server via the network to get the image, but the last three would not get an IP address no matter what. I think either the DHCP server was down, or perhaps it ran out of leases because now it's fine. This explains why the first two laptops worked while the other three didn't, they already had leases and a default gateway set up.

    D'oh!
     
Loading...
Thread Status:
Not open for further replies.

Share This Page