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.

    Windows, dell slows down when dvd spins down

    Discussion in 'Dell' started by jeffmd, Feb 27, 2008.

  1. jeffmd

    jeffmd Notebook Evangelist

    Reputations:
    65
    Messages:
    554
    Likes Received:
    20
    Trophy Points:
    31
    I have an inspiron 1505, E2300 cpu and the cdrw/dvdrom drive.

    namely when viewing images off a dvd, if the dvdrom is spinning and pictures are being loaded off the cd, everything is fine. Also if I scroll backwards and the images are being read from disk cache and the dvd is still spining, then everything is fine.

    However, if I am viewing images still stored in the disk cache and the dvd spins down to a stop, even though I am not accessing the dvd and its not spinning, anything related to accessing files on the dvd like viewing images that are still in cache (no disc spin up) or browsing the file list in file explorer (usualy dosnt spin up the disc until I call on file information like hovering over a new image/media file) is extremely slow. Images in the viewer program (dosnt matter what I use..windows or acdsee) don't take long to render, but there is any where from 2-4 seconds in the viewer (next/prev image).. to as much as 12 seconds of delay if I open an image from explorer before the next image shows up. Also I just selected and right clicked about 80 images I just viewed (so the disc has stoped spinning) and it took about 30 seconds before the right click menu would show up. It also took about 15 seconds for the copy operating to start (but once it did, the file copy was fast. dvd didn't need to spinup at this point).

    This has happened in windows xp when I first got the computer, in windows vista, and it is still happening in my current XP install. Its not a big problem but an annoyance that I can't figure out. Anyone read about it before?