From: "Anant Aneja" <anantaneja@rediffmail.com>
To: gcc-help@gcc.gnu.org, linux-gcc@vger.kernel.org
Subject: Inerupts handling
Date: 2 Mar 2003 17:20:22 -0000 [thread overview]
Message-ID: <20030302172022.26733.qmail@webmail31.rediffmail.com> (raw)
My problem is i was using turbo c++ compiler before and
frequently
used ROM-BIOS interupts for
certain functions ( like handling the screen, calling the mouse
etc all in dos based programs
using 386 based registers like ah al etc).
Now I've started using gcc and find that even a basic screen
clearing function requires me to use the
"ncurses" library. this i did but it handles the screen only
using
windows and does not treat the console as an
unlimited buffer.
I dont wanna use the library therefore. plus it was a lot easier
calling interupts for most simple tasks.
I've read somewhere that Linux does not allow BIOS interupts
since
it runs in 'protected' mode.
therefore, I cant do simple stuff like clearing a screen myself.
Is there some way to do the above task easily (with or without
assembly ?)
Please help.
Anant
reply other threads:[~2003-03-02 17:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030302172022.26733.qmail@webmail31.rediffmail.com \
--to=anantaneja@rediffmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=linux-gcc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).