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.

    I have sort of an odd problem

    Discussion in 'Windows OS and Software' started by Algus, Feb 3, 2008.

  1. Algus

    Algus Notebook Deity

    Reputations:
    130
    Messages:
    948
    Likes Received:
    47
    Trophy Points:
    41
    http://img225.imageshack.us/img225/2803/wtfus7.jpg

    I assume the icon file got damaged or something but I'm not exactly sure how to fix it. No idea how long it's been like that, the laptop I'm using is several years old now and it's been like that for some time but I've been spending my free time this weekend doing maintenance on the thing and I'd love to be able to fix this.
     
    Algus, Feb 3, 2008
    #1
  2. Silas Awaketh

    Silas Awaketh Notebook Deity

    Reputations:
    891
    Messages:
    1,676
    Likes Received:
    0
    Trophy Points:
    0
    Silas Awaketh, Feb 3, 2008
    #2
  3. Algus

    Algus Notebook Deity

    Reputations:
    130
    Messages:
    948
    Likes Received:
    47
    Trophy Points:
    41
    Great. Thanks for the links. Now as soon as I figure out where that drive icon is located I'll see if I can get it fixed
     
    Algus, Feb 3, 2008
    #3
  4. Algus

    Algus Notebook Deity

    Reputations:
    130
    Messages:
    948
    Likes Received:
    47
    Trophy Points:
    41
    Alright, I got it to work with the registry key thing. With the icons I need stored in a dll though is there any way to "extract" then or am I just going to have to count through the icons to get the right number?
     
    Algus, Feb 3, 2008
    #4
  5. Algus

    Algus Notebook Deity

    Reputations:
    130
    Messages:
    948
    Likes Received:
    47
    Trophy Points:
    41
    hum, after a bit more tinkering it looks like there was an autorun file that was the guilty party.

    I know I didn't create it so I wonder how it got there...

    edit: Anyway, thanks for the links. I was able to fix my problem perfectly with that.
     
    Algus, Feb 3, 2008
    #5