Re: win32 or native NT windows API
- From: "randyhyde@xxxxxxxxxxxxx" <randyhyde@xxxxxxxxxxxxx>
- Date: 14 Jun 2006 08:52:47 -0700
Herbert Kleebauer wrote:
The call of OS functions is done by an INT or SYSCALL and not by
a call to a function in a DLL.
Says who?
BTW, ever hear of call gates?
Any code in the DLL is executed in
the context of the running program and there is no difference whether
you call this code in the DLL or you include the source of this
code in your own program.
And your point is?
And this is the reason why the old DOS
int21 (or the Linux int80) interface is much more appropriate for
learning assembly programming than the DLL calls in Windows.
Why does the OS calling mechanism have *anything* to do with assembly
programming? Indeed, by your own argument DOS calls are not true OS
calls because the code executes in the same environment as the user
program. It makes no difference whether you using the INT instruction
or call the code directly in memory (e.g., by obtaining the address
from the interrupt vector table). Indeed, many DOS programs include
their own INT handlers, hence such code is part of the user program
anyway. Your argument is *seriously* flawed here.
Cheers,
Randy Hyde
.
- Follow-Ups:
- Re: win32 or native NT windows API
- From: Herbert Kleebauer
- Re: win32 or native NT windows API
- References:
- win32 or native NT windows API
- From: Vikas Kumar
- Re: win32 or native NT windows API
- From: Julienne Walker
- Re: win32 or native NT windows API
- From: Herbert Kleebauer
- win32 or native NT windows API
- Prev by Date: Re: Book on Assembly
- Next by Date: Re: win32 or native NT windows API
- Previous by thread: Re: win32 or native NT windows API
- Next by thread: Re: win32 or native NT windows API
- Index(es):
Relevant Pages
|