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 hardware, just keep it simple -- the ASCII beep goes to STDOUT, redirected to STDAUX and beeps at the right place.
You're right, Bart! I vote for putchar('\a') too! ('\a' is the C "alert/bell" character, ASCII 7.)
in that case, I vote for MS compatibility: don't beep at all.
But MS COMMAND.COM before XP doesn't do autocompletion at all. The XP and Windows 2003 COMMAND.COM copy the 4DOS behaviour (just display the next matching name on each TAB key press, and beep only if there are no matching names). But FreeCOM copies the "bash" behaviour - beep on the first TAB key press and show all maching names on next TAB key press. Where is the MS compatibility here?
(the default BIOS beep is really dull)
But it's definitely better than a fancy beep hanging the machine. And an '\a' character sent to the console is the only way to make a teminal sound, as Bart points out.
Regards, Lucho
------------------------------------------------------- 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
