INT on windows 2000, XP NET...

[jenk]

Hi
Can any of you tell me if the latest - and next ver of windows
is built ontop of the dos interupts ?

Like I've seen posts telling you what each int. does, but is this
at such low level within the os that this would not be changed?

I hope my question is clear enough...


Regards

j.

[ChimpFace9000]

I dont think anyone here will really know the answer to that, but it doesnt really matter because you cant use int's in windows.

[parksie]

You can use interrupts in any DOS-based Windows. That is, all 16-bit versions of Windows (including 9x ). 2000 you definitely can't, and it will fail with a "priviledged instruction" error. XP is built on the NT core so I would expect the same behaviour.

[ChimpFace9000]

You cant use interrupts in a windows program, console or not. You can use interrupts in a 32-bit dos program, which wont run in dos, but will run in windows. If you use Visual C++ to make a console program, and you use in-line asm, then you can use int's because its a 32-bit dos program.

[parksie]

You just contradicted yourself in one statement - congratulations

Win32 Console programs are Windows programs, and will not run under pure DOS because they rely on the VMM32 services and the PE format requires a Windows executable loader to make it aware of DLLs (like the API).

[ChimpFace9000]

A windows console program and a 32-bit dos program are 2 different things.

[parksie]

Yes I know that. But they can *both* use interrupts unless you're on NT in which case neither can.

[ChimpFace9000]

No they cant. If i were to use masm to write a 32-bit windows console program, i couldnt use..

mov ah, 09h
mov dx, offset String
int 21h

i would have to use the Win32API to write to the screen.

[parksie]

Um...okay I almost see your point. You're going from a different point. I'm talking about handling interrupts, not causing a software interrupt. Windows disables most of int 21h because it does it internally I think.