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.

    M1330 + SP1 + IDT Rollback: delayed User log on sound...

    Discussion in 'Dell' started by traveller, May 16, 2008.

  1. traveller

    traveller Notebook Deity

    Reputations:
    120
    Messages:
    958
    Likes Received:
    7
    Trophy Points:
    31
    Yes, a convoluted post title for an odd problem my M1330 was recently plagued with... :confused:

    Symptom:
    Windows Log on sound (wav file) doesn't play immediately upon user log on, but only after certain event(s).

    One way to "trigger" the logon sound is to use the "show desktop" icon located in the quick-launch area (left-hand section of the task bar).

    I didn't even notice it the first few times I logged in but later on while I was busy with one or the other activity I all of the sudden heard the log on sound!

    So I tried to recall when the problem first cropped up and my first thought was my recent update to SP1.

    The second and only other possibility was when I "accidentally" accepted "Windows Update's" offer to install IDT Audio Codec drivers... after noticing the sound was gone, I rolled back to the original Sigmatel drivers.

    Aside from the above two updates, I only installed the usual Windows Defender updates as well as the usual Security and Malicious SW Removal Tool updates.

    I Googled but came up empty. I reviewed active processes, but after "triggering" the log on sound there were still the same number of active processes. Ditto for Task Scheduler entries.

    It's not so much that I'm worried about the untimely arrival of the log on sound (which I could remove) but the fact that there may be other, more critical log on processes "stuck" in the pipeline.

    The problem surfaced on my 3DMark scores (one of the other "events" that triggers the log on sound...) so I know that are other pocesses in the pipeline, which are "stuck", for lack of a better word...

    Audio-wise, everything works fine, so I tend to believe it is most likely a SP1-related "anomaly". Seeing as I haven't installed anything else, I would have thought there might be others with the same problem...

    In any case, Ntebook Review's a great place to start... :D
     
  2. traveller

    traveller Notebook Deity

    Reputations:
    120
    Messages:
    958
    Likes Received:
    7
    Trophy Points:
    31
    I'm still looking for a solution so I thought I'd the liberty to ah, bump this post...
     
  3. squawks

    squawks Notebook Consultant

    Reputations:
    31
    Messages:
    297
    Likes Received:
    0
    Trophy Points:
    30
    Rolling back to the original Sigmatel drivers will not work. What you must do is uninstall the device in device manager (and delete drivers when it asks for that option) and then you must install the Sigmatel driver from the installation file (download this from the Dell website or from your drivers CD).

    The audio device is pretty bad. Everytime you want to install a new driver for it, you must uninstall the device and delete its old drivers before installing the new drivers.
     
  4. traveller

    traveller Notebook Deity

    Reputations:
    120
    Messages:
    958
    Likes Received:
    7
    Trophy Points:
    31
    For the record, the rollback worked just fine.

    I did however decide to install a newer version of the SigmaTel drivers on Dell's website, updating my exisitng drivers from 6.10.0.5515 to 6.10.0.5609 to see if they really did improve the mic.

    Of course I always uninstall older audio & video drivers prior to installing new ones: that's pretty much standard operating procedures ;)

    But long story short, it didn't solve my delayed logon problem, sigh...

    Back to the drawing board: I do hate the thought of rolling back SP1, assuming that's even possible...