buddyorliz said:
I had a dvd drive and needed a burner so online a couple weeks ago I bought a
dvdrw burner. It WORKED for a couple days then I started haveing issues....
In the event viewer there are numerous error messages about the driver.
I have been on here before with questions (and have gotten Some answers)
What I would like to know now is--
Will a drive just loose the driver?
Then - everytime you try to use - the event viewer will put a message on
saying something about that?
Will that cause the Blue screen - memory dump?
Same if it thinks there is a cable problem?
Can you copy the error messages from Event Viewer and post them ?
Under what circumstances are the error messages generated ? When the
DVD drive door opens ? When the media placed in the tray starts to
spin ? When you select "Eject" in a software menu ?
When there is a blue screen, what is the message and any numbers
provided. What happened just before the blue screen ?
Please post the exact text/numbers for the errors, as it makes it easier
to search for references to them.
In a Plug and Play world, a piece of hardware has an identity.
The operating system compared the identity, to the supply of drivers
installed in the system. If something matches, it is used. If it doesn't
match, maybe the "New Hardware Wizard" is called, and it pops up on your
screen. The only way to "lose" a driver, would be to uninstall it. If
the driver is built in to the OS, it would be even harder to lose, as
there is no option (like in Add/Remove) to remove it entirely from the
system. Perhaps disabling the device in the current profile, would prevent
the driver from loading. In that case it is not lost, but it is not
being used either. When a foreign driver is uninstalled, it is no longer
part of the supply or cache of drivers.
A blue screen comes from a serious condition that the kernel cannot
handle. Or that the driver writer didn't expect. For example, there
are probably a few things that could happen to your boot disk,
that would piss off the kernel - like say the kernel could no longer
page memory out to disk. That would be a serious error, and an error
condition that would not allow the system to continue.
For the DVD drive, it is not crucial to system operation. If there was
a cable, and only the DVD drive was affected by the cable, the options
are for the DVD to appear in the file manager, or not to appear. But
if the driver falls over, because an error condition came up that
the driver designer never thought about, that could tip over the system.
As for what is used for drivers, look in Device Manager, to see what is
being used for each item.
My "Ultra ATA Storage Controller" uses atapi.sys, pciide.sys, pciidex.sys .
The PCI refers to the fact that the controller appears in the PCI address
space, rather than the I/O space which is more traditional.
My "Primary IDE Channel" uses atapi.sys and storprop.dll
My hard drive uses disk.sys .
My CDROM uses cdrom.sys, redbook.sys, and storprop.dll
In fact, all of the above drivers, came with the OS, and were not
installed by me. My system uses Win2K, my storage devices all use
ribbon cables. But at least some SATA based systems now, can also
use nothing but system provided drivers.
Bring on the error messages
Paul
