1. Calling DOS interrupts from a 32-bit Windows app (was: Redirection of output)
On 2002-07-07, I wrote:
<snip>
> AFAIK it's not possible to call a DOS interrupt from a 32-bit Windows
> application. (At least Euphoria doesn't allow it: The command
> "x = dos_interrupt()" will cause an error in an .EXW program.)
> Converting DOS code to Windows will mean replacing interrupt-based code
> with Windows API calls, I think. But I'm not an expert in this field,
> too. Maybe someone else can tell us something more?
Now I can tell something more myself.
Generally speaking, it seems that I was right, and 32-bit Windows
applications can't call DOS interrupts, but there are a few exceptions.
On Windows 95/98/Me, applications can carry out selected DOS system
functions:
- Int #13
- Int #21 Function #4400 through #4411
(Function #440D is used in the example that Pete provided the day
before yesterday:
http://www.allapi.net/apilist/example.php?example=Eject%20CD )
- Int #21 Function #730x
- Int #25
- Int #26
The DeviceIoControl() Windows API-function is used to perform the
required operation.
Reference:
<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win9x/devio_2b1v.asp>
Best regards,
Juergen
