|
|
#91 |
|
Registrierter Benutzer
|
Genial, lieber Herr Ertl!
Zumal der Fix ja auch den keyb3-Treiber ersetzt! Ich habe gerade einen Beitrag für wpuniverse geschrieben, der auf Ihre zip-Datei verweist und (auf Englisch) erläutert, was damit zu machen ist: http://www.wpuniverse.com/vb/showthr...318#post257318 Gibt es so etwas wie die deutschsprachige und/oder internationale DOS-Website? Wenn ja, möchte ich auch dort auf Ihren Fix hinweisen. Nochmals ganz herzlichen Dank! |
|
|
|
|
|
#92 |
|
Entwickler
|
UPDATE 05-10-2016 // 64 Bit VERSION BEEPXP
SIGNED CERTIFICATE in 64 Bit release. |
|
|
|
|
|
#93 |
|
Registrierter Benutzer
|
I have Windows 7 x86, I've set up beepxp.sys and "vdm speaker fix"
Kernel service beepxp seems running Could you please tell me how can I make "beep" through PC Speaker from commandline? I start ntvdm (Win+R -> command.com) but running "echo •" stiill makes sound through soundcard ![]() What's wrong? |
|
|
|
|
|
#94 |
|
Moderator
|
Hi,
The patch is specifically meant for BEEP support in DOS, so it just patches NTVDM to use the PC speaker and leave the original soundcard beeper of Windows 7 intact. The BEEPXP device driver uses the Device name "BeepXP" to not collide with system's "Beep". Attached you find a BEEPXP.SYS driver that uses the device name "BEEP" instead. For this variant to work, you need to disabe System's BEEP.SYS driver to not get in your way and install attached BEEPXP.SYS, which then takes over. System's own Beep driver can be deactivated with: Code:
sc config Beep start= demand Also the "vdm speaker fix" is not needed in this variant and can be removed. Hope that helps, good Luck! Please look for actual versions here: https://www.waldbauer.com/tmp/reference.php |
|
|
|
|
|
#95 |
|
Registrierter Benutzer
|
Hello,
is this driver compatible with Windows 11? Thank you and best regards Manuel |
|
|
|
|
|
#96 | |
|
Moderator
|
Zitat:
There is nothing we can do about it. The driver signing requirements from Microsoft nowadays are insane. See: https://learn.microsoft.com/en-us/wi...e-code-signing You now have to register yourself as a company, pay thousands of dollars a year for a certificate and then you need a Microsoft certification so that they will sign your drivers. If you know some company which is capable of signings our driver, we would be glad if you manage to do it, as this would help a lot of people. Otherwise, your only option would be to run Windows in Test signing mode Code:
bcdedit /set testsigning on |
|
|
|
|
|
|
#97 |
|
Registrierter Benutzer
|
Thank you for your reply. I see.
With Advanced Start of Windows you can also select "Disable Driver Signature Enforcement". https://support.microsoft.com/en-us/...8-1a1af602b617 Is this is a working alternate to the Test Mode for installing the Beep driver? |
|
|
|
|
|
#98 |
|
Moderator
|
"Disable Driver Signature Enforcement" actually is Test signing mode but only for the current session until shutdown (not permanent). I guess if you want to have beeper work permanently, it's better to enable test signing mode permanently.
|
|
|
|