Ferenc Wagner wrote:
is there a way to incorporate DOS interrupt testing in the conformance testing framework? I recall that I saw some comments that Win32 applications should not be able to call DOS interrupts. But it should be testable at least... Now I have separate DOS16 programs for that.
Win32 application cannot call interrupts directly. You could use VWIN32 VxD to call some interrupts (int21 for example) and this should even work under Win95/Win98/WinMe. It could even be possible that this works under WinXP, if it has emulation code for supporting old applications, but I doubt it.
Jukka Heinonen jhei@iki.fi writes:
You could use VWIN32 VxD to call some interrupts
In VxDCall_VWin32 I can see int31 and int41 dispatch, but no trace of int21. Am I looking at the wrong place?
Feri.
Ferenc Wagner wrote:
In VxDCall_VWin32 I can see int31 and int41 dispatch, but no trace of int21. Am I looking at the wrong place?
Well, you should be able to call int21 directly under Windows 95 using VxDCall (and VWIN32 VxD). It is possible Wine does not support this because it is unlikely that user programs really use it (lots of viruses do). However, fixing this should be quite simple.
I was thinking more about using DeviceIoControl (see DeviceIo_VWin32) which seems to allow calling int21 under Wine and which is much easier to use than VxDCall. However, it looks like this does not work under Windows. At least all the information I have found about this say that DeviceIoControl can only be used to call a limited set of int21 functionality.
Jukka Heinonen jhei@iki.fi writes:
Well, you should be able to call int21 directly under Windows 95 using VxDCall. It is possible Wine does not support this [...] I was thinking more about using DeviceIoControl [...] However, it looks like this does not work under Windows.
Well, then I give up. I do not understand this whole business enough to do the "easy fix" you mentioned, and it is not that important anyway. Thanks for the guide!
Feri.
-
Ferenc Wagner -
Jukka Heinonen