Creating a Pointer to a Specific Memory Address

Last reviewed: July 17, 1997
Article ID: Q23977
5.10 6.00 6.00a 6.00ax 7.00 | 1.00 1.50
MS-DOS                      | WINDOWS
kbprg

The information in this article applies to:

  • Microsoft C for MS-DOS, versions 5.1, 6.0, 6.0a, and 6.0ax
  • Microsoft C/C++ for MS-DOS, version 7.0
  • Microsoft Visual C++ for Windows, versions 1.0 and 1.5

SUMMARY

An application can create a pointer to access a specific address in memory with the FP_SEG and FP_OFF macros or by creating a far pointer in a long value.

MORE INFORMATION

The FP_SEG and FP_OFF macros are defined in the DOS.H header file. These macros can retrieve or specify the segment or offset in a far pointer.

The following code example demonstrates using the FP_SEG and FP_OFF macros to create a pointer to access video memory:

   char far *p;
   FP_SEG(p) = 0xb800;   // point to segment of video memory
   FP_OFF(p) = 0;        // set offset to first screen position

For more information on the FP_SEG and FP_OFF macros, see the Microsoft C "Run-time Library Reference" or see the online help provided with the compiler.

Another method to create a far pointer involves casting a long as a far pointer, as in the following example:

   p = (char far *)0xb8000000L;   // video memory

In the long value, the most significant 16 bits specify the segment and the lower 16 bits specify the offset.


Additional reference words: kbinf 1.00 1.50 5.10 6.00 6.00a 6.00ax 7.00
KBCategory: kbprg
KBSubcategory: CLngIss
Keywords : kb16bitonly


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.