| delorie.com/archives/browse.cgi | search |
| From: | "stefan fröberg" <traveler AT netti DOT fi> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | EXTREMENLY IMPORTANT (To me...) |
| Date: | Thu, 11 Nov 1999 20:07:34 +0200 |
| Organization: | SAUNALAHDEN SERVERIN asiakas |
| Lines: | 30 |
| Message-ID: | <80f0bb$q68$1@tron.sci.fi> |
| NNTP-Posting-Host: | mmcc.hdyn.saunalahti.fi |
| X-Newsreader: | Microsoft Outlook Express 4.72.3110.5 |
| X-MimeOLE: | Produced By Microsoft MimeOLE V4.72.3110.3 |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
| Reply-To: | djgpp AT delorie DOT com |
Greetings to everyone !
The following questions are maybe too trivial to some of you but for me they
are unclear:
- Is there no other way to call DOS/BIOS interrupt that requires a
pointer to buffer,
than using the "__tb" macro or allocating dos memory as explained by the
FAQ 18.2 ?
- I know that the GCC uses the "Flat" memory mode but it's unclear to me
which segments/selectors it uses by default. I presume that the GCC uses
"CS" segment/selector for the code and "DS" segment/selector for the
data but
what about the "ES","FS" and "GS" segment/selectors ? Are they undefined
?
Can I use them freely in my assembly subroutines and if so, do I have to
save
them at the start and restore them at the end of the routine ?
- Are there any important rules and guidelines for using
segments/selectors in protected mode programming to prevent exceptions
as "General Protection Fault" and other such things to happend ?
Thanks in advance !
traveler AT netti DOT fi
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |