In response to "Select the device driver you want to install for this hardware," click the Have Disk button. You will be asked for the name of the folder. You will need to change this as appropriate for your computer system; for example, if your CD-ROM drive is drive E, then replace D: with E: in the folder name you type.
From the taskbar, click Start and then click Control Panel to open it. Click the Driver tab, and click the Uninstall button. Click the OK button. Use the following procedure to change your settings so that you can install the driver. From the Control Panel, open System and click the Hardware tab. Watch the video below to see how I fixed it.
I made the video back in year, but the steps are similar. You can read another post where I share my thoughts on whether you should buy a Mac or PC for music production. The uninstaller allows you to uninstall MIDI devices from other brands and manufacturers as well. Just download it anyway and go to the next step. The worse you can do here is removing used drivers and having to reinstall it so not very problematic Hope it helps, Cheers, Karl.
Thank you! This is good to know. I currently use Korg's driver uninstaller. It has an option that actually lets you view other non-Korg drivers, and uninstall them. In the absence of such device-specific options, there are various manual techniques you can use to track down driver files, and references to them in the Registry. However, anyone who wants to try these techniques should be aware that they can entail grave risks, and if you accidentally delete any system files or Registry entries that may still be required, you may subsequently be unable to boot up Windows at all.
If you want to try the techniques, I would strongly recommend first creating a backup image of your Windows partition, using a suitable utility, such as Norton's Ghost, so that if you run into problems you can use the saved image file to exactly restore Windows to its former state.
Judging by the number of times readers have since asked me for the link to the on-line version, it has since become a well-used routine amongst PC musicians. The Windows NT, and XP Device Manager only normally displays Registry entries for devices that are currently connected, even if you use its'show hidden devices' function, but if you follow these steps you can force it to display redundant devices that are no longer connected, so that you can delete them once and for all.
Here are some additional points that may help. First, before deleting any greyed-out item belonging to old hardware, if you double-click on it or right-click on it and select Properties , select the Drivers page and then click on its Driver Details button, Windows may be able to display a list of all the driver files the old hardware used. Since these are not deleted when you delete the Device Manager entry, it's worth noting down the non-Microsoft ones for later removal by hand, if you want to be thorough.
It's also worth knowing that every time you plug a USB-based interface into a new port, Windows needs to configure the driver for that particular port, and will therefore ask for the drivers to be installed all over again. So if you've got six USB ports and you tend to plug your audio or MIDI interface into whichever one happens to be unused at the time, you could end up with six references to it: one currently valid if the interface is plugged in, and five other 'non-present' or 'ghosted' versions.
This Registry entry duplication also happens if you move a PCI card to another slot, and with some interfaces after you apply a firmware update as part of a new driver release. Uninstalling a soundcard may still leave behind lots of detritus. Here, you can see some of the references to 'Mia' found in my Registry by Regseeker's 'Find in registry' function, even after I'd correctly uninstalled the Mia soundcard's drivers.
If you've got lots of USB devices, you've shuffled your PCI cards around a lot, or your audio interface manufacturer has released lots of firmware updates to add new features like some of RME's range, for instance , you can end up with loads of unwanted references.
Aside from the fact that they clutter up the Registry, these entries may prevent you from installing a new interface properly. This happens because different versions of Windows have various internal limits on the number of device drivers that can be installed.
One notorious example that's hit various musicians is the entry limit on internal bit drivers that affects Windows NT, and XP. In the Registry, MIDI devices, for example, appear in the Drivers32 section see screenshot as 'midi', 'midi1', 'midi2', 'midi3' and so on, up to 'midi9', while audio devices appear as 'wave' to 'wave9', and audio mixer devices as 'mixer' to 'mixer9'.
Although there may be duplicates and unwanted entries in these lists, once the maximum of 10 exists in the Registry, no more can be created, preventing you from installing further devices. The problem can be cured by installing Windows again from scratch, although not surprisingly few musicians want to take this drastic step. A second, but potentially more dangerous, approach is to manually delete some of the offending duplicated entries in your Registry that are causing the problem.
Matthias Carsten of RME has written an in-depth technical page that you can consult if you're prepared to modify the Registry by hand in this way it's at www. Having said all that, according to my experiments, the extra devices should all appear in 'greyed out' form in Device Manager when you follow my instructions above, and deleting them here seems a far safer option. M-Audio also provide Midifixutil. Another potential source of problems is the Windows INF files used during the installation process of each hardware device.
If, after uninstalling old interface drivers, you have problems when trying to install new ones, it may be because Windows has found an old INF file relating to the hardware. Try doing a search for your interface name in these 'oem' files and delete any such INF files you find.
My INF folder contained a massive objects, but to narrow it down you will mostly find those associated with audio and MIDI interfaces named 'oemX. This makes it considerably easier to find files relating to an old audio or MIDI interface. Even after you've run a dedicated uninstall utility that removes the driver files, associated INF files, and sometimes even references to the hardware within the Registry, your old audio and MIDI interfaces can still leave behind loads of Registry entries generated by your music applications when they originally found the new hardware and added it to their list of available options.
No automated utility can be trusted to remove these, since it can't know what's safe to delete and what's not. However, one extremely useful freeware utility that I regularly use to help me do the job manually is Regseeker from Hover Inc www. Apart from a general-purpose 'Clean the Registry' function that's very useful for stripping out invalid items, missing files and bad references, it also includes a 'Find in Registry' function that's perfect for tracking down the final references to old hardware.
Once the search is complete, click on 'Select All' near the bottom of Regseeker's window, then scroll through the list to see if any stray references whose name accidentally incorporates that of your search term have been included.
For instance, before I added that extra space character my search included various references to 'WmiApSrv' and 'WMIAdapter', but including the extra space character produced a list without unrelated entries. Any incorrect ones you happen to find can be individually de-selected from your list by ctrl-clicking on them with the left mouse button.
0コメント