My CD-ROM Is Gone. Help!

How To Get Windows To See Optical Drives Again

Q: Paul I need your help. Yesterday I put a CD in my computer nothing happened. It has been working fine, and usually it will just start playing the first song. I put in a different disk and again nothing. I opened My computer and there was no icon for the DVD. Just icons for the Floppy A:, Local disk and no CD player. It just vanished! I rebooted and that didn’t help. What happened? How do I get my CD player back?

A: The exact steps required will depend on the cause of the issue, so the following answers are ‘generic’, and may not apply to your particular situation.

1) In Windows XP and older have a reputation for “losing” optical drives (but I have seen it occur in Vista) after uninstalling disc burning software — such as Roxio or Nero. Sometimes.. after installing; but usually it is an uninstall failing to work properly, which leaves incorrect values in your Registry.
Sometimes, though less frequently, a Windows Update, or other software change can cause this as well.

Sometimes Microsoft gets it right:
If this is you — you have uninstalled Roxio, say — the solution is to visit Microsoft Help & Support and click the “Fix It” button. (I have written about using the built in troubleshooter before, see Microsoft “One-click” Fixes)

The appropriate Fix it page/button is found here. One click should do it!

———————————

2) If that doesn’t resolve the issue, you can next try restoring your system to a prior (working) state by using System Restore. Please read How To Use System Restore To Fix Windows for instructions.

3) If that doesn’t help, or isn’t appropriate..
Open your computer’s case and check to make sure the power wires, and the ribbon cable are firmly connected to the back of the drive and to the motherboard — they may have become loose or disconnected.

No? Then open your Device Manager. Right-click on “My Computer” and select “Properties”. In Vista, click on Device Manager in the left column; in XP, click on the “Hardware” tab, and then click the “Device Manager” button.

In Device Manager, find “Optical drives” on the list, and expand the category by clicking once on the “+” sign. You should now see the device and a yellow triangle – which is telling you there’s an error.

Right click on the device’s name, and click “Uninstall” from the menu which opens. Answer “Yes”, you want to do that. Then restart (aka “reboot”) your machine. Windows should “find” a “new” CD-ROM and install it for you, thus restoring functionality.

4) If these steps fail, there is something else going on (maybe malware) and I recommend you contact a knowledgeable repair tech.. such as myself (shameless plug).

Today’s free link: KidsEmail.org. Along with ZooBah, something to consider when your child wants their own e-mail address.

Today’s free download: GOM Player is a free multimedia player with popular video and audio codecs built-in. GOM Player supports file formats such as AVI, DAT, MPEG, DivX, XviD, WMV, ASF. Users don’t have to install codecs separately. GOM Player is capable of playing incomplete or damaged AVI files by skipping the damaged frames. It can also play locked or partially downloaded files.

Copyright 2007-9 © Tech Paul. All rights reserved. post to jaanix

Share this post :

Stop Error Solution #8 – SigVerif

Vista Stop Error: “A recent hardware changes, or unsigned driver, has prevented Windows from loading..”

The Blue Screen of Death (BSOD) is an error screen displayed by  Microsoft Windows after encountering a critical system error which can cause the system to shut down to prevent damage. (They are not always blue anymore – sometimes you see a black screen, saying only “Stop: 0x000000F1”, or some other similar, ‘helpful’ hexadecimal string – but they are still called “bluescreens”.)

Bluescreen (Stop errors) on NT-based Windows systems are usually caused by poorly-written device drivers or malfunctioning hardware. Way back when dinosaurs roamed, in the Win9x era, incompatible DLLs or bugs in the kernel of the operating system could also cause BSOD’s. (There are different types and causes of stop errors, a good summary can be seen here.)
With Vista, Microsoft got a bit more restrictive, and it can happen when an unsigned device driver is found.

Microsoft got a a little tired, I guess, of taking the rap for the poorly written, and often amateur, device driver-caused BSOD’s. (People tend to blame Windows for the crash..) And so they, over the years, have tried various ways to get the hardware vendors to write and release good driver software, and rewarding those that did with the coveted Microsoft Compatible seal of approval (usually a logo on the box), and placement on the WHQL (Windows Hardware Compatibility List). But.. hardware vendors build, box, and ship, devices.. not program code, or study all the minutia of the OS kernel.

Digital “signatures” (in this instance) are one way to determine if the driver was written by the kid down the street. When a driver has been tested and approved in Microsoft’s own labs, it gets a super-special digital certificate. And with Vista, you pretty much gotta have that driver, or expect stop errors. These Microsoft-signed drivers are available through Windows Update, and the “Update driver” feature (a subset of “Add new hardware”).

(For more on troubleshooting and/or installing device drivers, see my Plug and Play series.)

Tip of the day: In Windows XP and Vista there is a utility that you can use to scan your all your installed drivers. It will report any it finds that don’t have a “signature”. This is a great way to ‘zero in’ on the (possible) cause of the Stop error.

Use the Sigverif.exe tool to identify unsigned device drivers installed on your Windows XP/Vista computer. To use the tool, perform the following steps:

1) Open Start menu, select Run, type Sigverif and then click OK.

The File Signature Verification tool will open. Click “Start”.

The scan will run, and ideally produce the following result…

But if it finds anything, it will produce a list of funny-named files… like “msndis5.sys” which are your unsigned drivers (or, they’re signed.. but not Microsoft super-specially signed). Hopefully it will be a list of one.

2) Use your favorite search engine to find out what the funny-looking driver belongs to. (In my example, it turns out that msndis5.sys is a part of NetStumbler – a very popular wireless “hotspot” locator.) Now you will know which device, or program, needs your attention to cure the BSOD.

3) Remove the offensive device driver.
There’s options to how you go about this. In the case of my example, it is a program. So, I can uninstall the program, or look for a newer version (update) of the program.
If it were a device, I would go into Device Manager (see, If It Ain’t Broke – Don’t Fix It), select the device in question and try:
* “Update driver. If that says ‘no dice’ (“The best software is already..”),
* “Rollback driver”. If that is not available, or fails to stop the Stop errors,
* “Uninstall”, then reboot. Windows will reinstall the device, and it will grab the driver from the WHQL.

Hopefully, this will resolve your issues. If not, you should start looking at your hardware itself. I’ve run long, so..

Today’s free download: Google Calendar Sync.
For anyone who relies on a digital calendar to keep them on track, Google Calendar Sync is a must-have application. The free download isn’t fancy or even pretty–a simple log-in and options list comprises the system tray icon. However, the meat of the application is what it can do, which is flawlessly add details of Outlook calendar items to Google’s Calendar, and vice versa.

Copyright 2007-9 © Tech Paul. All rights reserved. post to jaanix

Share this post :