In Windows 7, I used the system speaker (motherboard beep speaker) as the default sound device. You don't normally install a driver for this as it is not generally used for Windows, just there as a BIOS beep. But, in Windows 7, I did manage to install a driver so that it could be used as the default Windows sound device. I can no longer locate a driver now that I have upgraded to Windows 10. I think it was called speaker.drv and came from Microsoft. Anyone have an idea where I can locate such a driver? It probably dates back to Windows 3.1!
I haven't see one around. Wouldn't you just get a beep anyways? Why not just open up the PC and connect the system speaker to the sound card output? It also occurred to me that you might have a setting in the BIOS as well but to be honest I might be tempted to just rewire the speaker..
That should have been a fundamental part of the upgrade Howerd, they don't often get that kind of stuff wrong, however my sound didn't work too after a clean install, I needed drivers from Lenovo to fix everything but kudos to Lenovo they had provided the required fixes. You might need to check with the manufacturer Howerd.
The beep speaker does not usually have a driver, since it is only there as a BIOS beeper. But I think my PC does have a Winows speaker after all but I just can't see how to get it working. I remember I had this problem once before but can't remember how I solved it.
Well if your pc has a built in speaker wired to some integrated sound card then that's different. I would suggest obtaining the chipset drivers from the manufacturer since the sound and network are often part of an integrated chipset on vendor supplied pcs...
I have tried with the latest Microsoft driver, which only seems to want to look for an external speaker. If I use the latest HP-supplied driver, it is showing as working but I get no sound.
Here's the history, this is the Microsoft guy that wrote the fix for 64bit Windows http://blogs.msdn.com/b/larryosterm...t-s-up-with-the-beep-driver-in-windows-7.aspx not sure that it will help you but it explains how it is working.
Yeah but what he is saying is that the physical 8254 chip does not exist in later hardware so whatever is going on the beep must be virtualised now! I might be wrong there?
I think I will just plug in an external speaker, just to make life easy! I did have a speaker once, but it was lost in the flood I think
Dot sure what I did, but it is working now! NO need for external speaker. I told it to uninstall Conexant HD Audio (including the speaker driver) and hey presto it now works! The strange thing is though, Conexant is still installed and so is the driver!
What a hassle.. That's why I use a macs now. I find them more reliable and less of a support headache.
Could never afford a Macbook. I use a Chromebook now. The Windows PC will be used by my wife when she gets here.
I understand, really I do, but as a programmer all I want is a laptop with a keyboard that is exactly the same layout as a desktop PC, a traditional PC that is, one with all the keys in the standard IBM keyboard locations. The Mac might have the build quality but it has nothing else to make it the business machine of choice, sadly neither does the only other candidate the IBM ThinkPad, no longer IBM but now owned and built by Lenovo and they ruined it twenty years of perfection binned simply because some Chinese bloke (probably an accountant) thinks that copying a Mac is what engineers and scientists and business professionals need. Yes I am bitter Very bitter! Really seriously bitter, where are the smilies that can express my bitterness :tears:
