PackardBell MS2285 CD-ROM DRIVER PLEASE HELP

Jooooles

DW Regular +
Joined
Sep 14, 2006
Messages
6,326
Reaction score
306
Location
St James Park
I have been looking for this driver for 4 hours on the packard bell support site it only gives you the options of the drivers that are not includled in windows 7 updates.

The CD rom driver is not there, I have just upgraded my sisters lappy and I noticed here CD-ROM has a error and its not reconised in devise manager.

Im sure its a Toshiba Drive

heres the model number on the back of the lappy Packard Bell MS2285 Im sure its a easynote running windows 7 premium 64 bit.

cheers for any help guys
 
Failing that you can also try a bit of good old techie detective work :Doc:

Take a look in device manager under the details tab

Under Device Instance ID you'll find details of the hardware in question, your specifically interested in the vendor info and the device info

So in and instance id of PCI\VEN_14E4&DEV_165A&SUBSYS_7051103C&REV_00\4&625283&0&00E5. Vendor is 14E4 and device is 165A.

Either put the whole vendor/device bit in google (VEN_14E4&DEV165A or just VEN_14E4) or go here PCI Vendor and Device Lists and just put the numbers in. Start with device then if that fails try vendor (165A comes back as Broadcom NetXtreme BCM5722 Gigabit, so i know exactly what driver i need to hunt down)

That lot is usually enough to get you on your way. just be wary of where you download your drivers from if its not the manufacturers website.

If all that fails if you have any driver disks or are able to get old of one of the generic driver packs floating around the net just search for files containing the vendor/device string. All reference drivers (one without specific set-up programs) have a .INF file which is used by the install process and the vendor/device/subsys part of the string is what tells windows what the device is, what model and what to install where. If you find the string you've found your driver.

Now bet your glad you asked :proud:
 
this is a common problem its not a driver issue but a registry issue it is sometimes caused by installing certain burning software however i have known it to happen on a clean install of windows with no other software installed
heres how to fix it

Click on the Start button.

If you're using Windows XP, also click on Run.

In the search box (Windows 7 and Windows Vista) or the Run textbox (Windows XP) type regedit and click OK or press the ENTER key.

This will open the Registry Editor program.
Important: Changes to the registry are made in these steps. Take care in making only the changes outlined below. While it's not a necessary step to complete this process, I recommend that you play it safe by backing up the registry keys you're modifying.

Locate the HKEY_LOCAL_MACHINE folder under Computer/My Computer and click the |> or (+) icon next to the folder name to expand the folder.

Continue to expand folders until you reach the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class registry key.

Click on the |> or (+) icon next to the Class key to expand it. You should see a long list of subkeys open up under Class that look something like this: {4D36E965-E325-11CE-BFC1-08002BE10318}.

Note: Each 32-digit subkey is unique and corresponds to a particular type, or class, of hardware in Device Manager.

Determine the Correct Class GUID for the Hardware Device. Using this list, find the correct Class GUID corresponding to the type of hardware that you're seeing the Device Manager error code for.

In the results that appear on the window on the right, locate the UpperFilters and LowerFilters values.

Note: If you don't see either registry values listed, this solution isn't for you. Double check that you're looking at the correct device class but if you're sure you are, you'll have to try a different solution: How to Fix Device Manager Error Codes.

Note: If you only see one or the other value, that's fine. Just complete Step 9 or Step 10 below.

Right-click on UpperFilters and choose Delete.

Choose Yes to the "Deleting certain registry values could cause system instability. Are you sure you want to permanently delete this value?" question.

Repeat Step 9 with the LowerFilters value.

Note: You might also see an UpperFilters.bak or LowerFilters.bak value but you do not need to delete either of these. Deleting them probably won't hurt anything but neither one is causing the Device Manager error code you're seeing.

Close Registry Editor.

Restart your computer.

Check to see if deleting the UpperFilters and LowerFilters registry values solved your problem.

If you've completed these steps due to a Device Manager error code, you can view the device's status to see if the error code is gone. If you're here because of a missing DVD or CD drive, check Computer or My Computer and see if your drive has reappeared.
 
Back
Top