No Sound (Sound Device Modem Line) (Driver is enabled but has not been started)

Found this solution online, had to sift through to find it so thought it would be best to post it.

  • 1. Check if Plug and Play Software Enumerator is installed on your machine (Device Manager / System devices)
  • 2. If it is not continue to next step.
  • 3. Locate "machine.inf" on your OS, copy it somewhere and modify it (find "ExcludeFromSelect=*" and remove the line or simply exclude it from processing by adding a ";" at the beginning)
  • 4. Go to Control Panel /Ad HW and follow the wizard towards manual selection of device to be added
  • 5. Select Add System device
  • 6. Select Have disk...
  • 7. Navigate to changed machine.inf
  • 8. From the list select standard devices (in the left list) and "Plug and Play Software Enumerator" in the right list
  • 9. Finish the Installation
Here is the original thread:
http://www.techspot.com/vb/all/windows/t-34101-The-driver-has-been-enabled-but-has-not-been-started.html

Comments

Anonymous said…
Thanks for posting this info, it fixed my problem that was eating me up.
October 26, 2009 at 1:58 AM
Unknown said…
No, that was related to VM images as I have resolved the issue by deleted .encoding top row from file.

Thank you very much.

but unfortunately I again stuck with Xen hypervisor dependency, that is related to VMWare as we can't run virtual machine on VMWare window server 2003---> VMWare server 2.0--> PIM-DEM images

Then I tired to run on window vista 32 bit but I failed to configure "virtual network editor" this was not work properly as APPLY button was not available & OK button was not enabling after made change in configurations.

Pl advise if we have any alternate with Vista as well.

Thanks in advance !
December 16, 2010 at 8:24 AM
Post a Comment

Popular posts from this blog

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face and get nowhere be
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnect. Using
Read more

Azure VMware Solution: NSX-T Active/Active T0 Edges...but

Image
Summary: Azure VMware Solution (AVS) delivers by default w/ a pair of redundant Large NSX-T Edge VM's each running a T0 in active/active mode.  So why is my traffic only going out one Edge VM? Short answer: The default T1 that is delivered w/ AVS is an active/passive T1 where you connect your workloads to.  So while it could technically take either T0, it's always going to go out the closest T0 to the active "SR" T1.  Where do the SR's live?  You guessed it, on the Edge VM's.  As you can imagine, this can lead to a bottleneck if you try to shove all your traffic through a single Edge VM. Simple Diagram: Longer answer with Options:
Read more