Xref: utzoo comp.windows.ms:13051 comp.windows.ms.programmer:2654
Newsgroups: comp.windows.ms,comp.windows.ms.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!uunet!odi!ed
From: ed@odi.com (Ed Schwalenberg)
Subject: Re: Low Level i/o under windows
In-Reply-To: donc@microsoft.UUCP's message of 22 May 91 17:37:07 GMT
Message-ID: <1991May24.153119.2252@odi.com>
Organization: Object Design, Inc.
References: <4473@tuna2.UUCP> <72499@microsoft.UUCP>
Date: Fri, 24 May 91 15:31:19 GMT

In article <72499@microsoft.UUCP> donc@microsoft.UUCP (Don CORBITT) writes
in response to article <4473@tuna2.UUCP> in which dhanani@motcid.UUCP
(Iqbal Dhanani) wants to fiddle with disk at sector level:

  Well, you can always do an int 21, int 24, or int 25 as appropriate.
  Windows translates the calls and buffers. 

The Windows Developer's notes claim that INTs 25 and 26 are unsupported
in protected mode and will fail if called.  It also claims that INT 21
functions 14, 15, 21, 22, 27 and 28 are unsupported.  I haven't experimented.
It occurs to me that this may be the reason SWAPDISK runs only in Windows
real mode.

  Don Corbitt, uunet!microsoft!donc, Windows Developer.
  I reserve the right to be totally wrong in all facts and opinions.

Truth in advertising.