Steve Nickolas escribi�:
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
putchar('\007');
no BIOS, no int29, no delay timing, no direct hardware, just keep it
simple -- the ASCII beep goes to STDOUT, redirected to STDAUX and beeps at
the right place.
in that case, I vote for MS compatibility: don't beep at all.
?
CMD.EXE on NT *does* beep on an unsuccessful tab completion.
(the default BIOS beep is really dull)
tom
I would agree. I don't like beeping on tab completion, personally.
Well, I think it's quite useful that it beeps on unsuccessful TAB
completion. But anyway I seem to remember that there is a BEEP command
that needs to be fullfilled, so... (I also vote for this solution, being
Bart's argument the most convincing to me).
Aitor
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
