Re: [Freedos-devel] beep implementation

Sorry for the late reply! The regular bell character starts to beep, stops beeping after a short time, and then lets me continue. The freecom beep starts to beep, beeps forever (I presume, I haven't tested it that long) and doesn't let me do anything else. I was able to fix my copy via the hex

Re: [Freedos-devel] beep implementation

> Thanks, I will try the patch out when I get a little time. patches are not too helpful in an open source OS. > The regular bell character doesn't hang, so I wonder why freecom > implements its own version. you aren't entirely clear in your bug description: does it start to beep, and then

Re: [Freedos-devel] beep implementation

Hallo Herr Eric Auer, am Mittwoch, 13. Mai 2020 um 12:19 schrieben Sie: > Hi Rugxulo, > Thank you for your binary patch but... >> 1). 2016-May-6: "[Freedos-devel] Beep command can't stop sounding when >> run in Intel Skylelake platorm." >> * https://sourcef

Re: [Freedos-devel] beep implementation

2016-May-6: "[Freedos-devel] Beep command can't stop sounding when > > run in Intel Skylelake platorm." > > * https://sourceforge.net/p/freedos/mailman/message/35068370/ > > > > 2). 2017-Jun-9: "#189 Beep function freezes on recently intel platform > > (s

Re: [Freedos-devel] beep implementation

Hi Rugxulo, Thank you for your binary patch but... > 1). 2016-May-6: "[Freedos-devel] Beep command can't stop sounding when > run in Intel Skylelake platorm." > * https://sourceforge.net/p/freedos/mailman/message/35068370/ > > 2). 2017-Jun-9: "#189 Beep func

Re: [Freedos-devel] beep implementation

Hi, On Fri, May 8, 2020 at 10:48 AM Johnpaul Humphrey wrote: > > I am running FD12 on an HP Pavilion that is about three years old. This was reported at least twice in recent years: 1). 2016-May-6: "[Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake plator

Re: [Freedos-devel] beep implementation

FreeDOS does only hangs for a little bit on the message. My version is "0.84-pre2" the version that ships with the standard USB install. So the problem does not appear to be delay(). Maybe the problem is nosound()? Maybe the keyboard has an error? or the computer itself? I can write a test program

Re: [Freedos-devel] beep implementation

Hi! In short, your FreeCOM beeps are infinitely long. As you saym beep_l.c and beep_n.c implements them as beep_low() and beep() as follows: void beep_low(void) { sound(900); delay(200); /* 400 */ nosound(); delay(100); } void beep(void) { sound(900); delay(200); /* 400 */

[Freedos-devel] beep implementation

Hi Developers, I noticed that when I tab complete in the default shell, (freecom, I think) that it beeps, and is stuck beeping for a long time. I have not been able to see how long till it stops, but if it stops at all, it is much longer than it should be. The only way I have found to stop it is

Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake platorm.

Hi, On Wed, May 11, 2016 at 12:32 PM, Eric Auer wrote: > > Hi Rugxulo et al, > > of course when I said that: > >>> In related news, the tab completion beep of FreeCOM can hang in DOSEMU. > > I was not looking for a work-around like that: I know, but beeping isn't what I'd

Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake platorm.

Hi Rugxulo et al, of course when I said that: >> In related news, the tab completion beep of FreeCOM can hang in DOSEMU. I was not looking for a work-around like that: > You could always zero out the "BEEP\0" string to disable the interactive > command, but the actual beeping code is still

Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake platorm.

Hi, On Fri, May 6, 2016 at 11:03 AM, Eric Auer wrote: > >>> When we test FreeDOS latest version, w found beep command can't stop >>> sounding in Intel Skylake platform. > > In related news, the tab completion beep of FreeCOM can hang in DOSEMU. You could always zero out the

Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake platorm.

l Skylelake platorm. (Eric Auer) -- Message: 1 Date: Fri, 6 May 2016 10:54:11 + From: MikeSun(???) <mike...@ami.com.cn> Subject: Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake. To: "freedos-devel@lists.sourceforge.net"

Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake platorm.

Hi, On Fri, May 6, 2016 at 8:05 AM, wrote: > > On May 6, 2016 6:42 AM, "MikeSun(孙国祥)" wrote: >> >> Hello developer, >> >> I’m BIOS vendor-AMI. >> >> When we test FreeDOS latest version, w found beep command can't stop >> sounding in Intel Skylake

Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake platorm.

Hi :-) >> I’m BIOS vendor-AMI. >> >> When we test FreeDOS latest version, w found beep command can't stop >> sounding in Intel Skylake platform. In related news, the tab completion beep of FreeCOM can hang in DOSEMU. Regards, Eric

Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake platorm.

On May 6, 2016 6:42 AM, "MikeSun(孙国祥)" wrote: > > Hello developer, > > > > I’m BIOS vendor-AMI. > > When we test FreeDOS latest version, w found beep command can't stop sounding in Intel Skylake platform. > > > > But we build beep source code(from FreeDos open source) by

Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake.

shidel.net> Content-Type: text/plain; charset=us-ascii Hello All, Sorry that it took so long, but I have been swamped the last couple weeks. Anyhow, I updated vinfo in V8Power tools to detect QEMU. So, FDI should no longer get stuck by trying to create a RAMDRIVE or have issues under QEMU

[Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake platorm.

Hello developer, I’m BIOS vendor-AMI. When we test FreeDOS latest version, w found beep command can't stop sounding in Intel Skylake platform. But we build beep source code(from FreeDos open source) by Watcom C tool and run beep.exe in FreeDOS. Beep.exe work normally. Did anybody meet

[Freedos-devel] How to detect if fd #0/#1 are the local console (was Re: [Freedos-devel] BEEP)

On Sat, 31 Jul 2004, Bart Oldeman wrote: OK, I had already promised that BEEP can: + be silent, + print \a, + do some PC speaker sounding. And the user decide, what to do. The default would be '\a', as it is the most compatible beep at all. no BIOS, no int29, no delay timing, no direct

Re: [Freedos-devel] How to detect if fd #0/#1 are the local console (was Re: [Freedos-devel] BEEP)

Hi, Steffen Kaiser escribió: Til this time there had be no suggestion to overcome the requirement about how to detect if: 1) FreeCOM's input comes from the local keyboard (in opposite to FreeCOM MUST use the file descriptor #0 or the read from stdin DOS APIs) and 2) FreeCOM's output goes to

Re: [Freedos-devel] BEEP

Hi, At Fri, 30 Jul 2004 4:07pm +0200, tom ehlert wrote: in that case, I vote for MS compatibility: don't beep at all. (the default BIOS beep is really dull) tom I would agree. I don't like beeping on tab completion, personally. -uso. Don't beep, please! It's so alarming after midnight!

Re: [Freedos-devel] BEEP

At Fri, 30 Jul 2004 4:07pm +0200, tom ehlert wrote: Hello Bart, Don't forget that FreeCOM is also supposed to be able to run over a serial line via CTTY. In that case the beep should happen on the terminal and not on the PC where FreeCOM actually runs. So I vote for

Re: [Freedos-devel] BEEP

Hello Bart and Tom, Don't forget that FreeCOM is also supposed to be able to run over a serial line via CTTY. In that case the beep should happen on the terminal and not on the PC where FreeCOM actually runs. So I vote for putchar('\007'); no BIOS, no int29, no delay timing, no direct