> The FAR printf is probably good for 16-bit builds with DEBUG defined.
> However, there are at least two potential issues (NOT YET VERIFIED).
> 1. 386 (or higher) builds might fail on a FAR value, as a 32-bit FAR is past
> 4GB. I don't know how the compilers treat FAR in these builds.
exactly as
2009/7/20 :
> Jeremy:
> The FAR printf is probably good for 16-bit builds with DEBUG defined.
> However, there are at least two potential issues (NOT YET VERIFIED).
> 1. 386 (or higher) builds might fail on a FAR value, as a 32-bit FAR is past
> 4GB. I don't know how the compilers treat FAR in th
Jeremy:
The FAR printf is probably good for 16-bit builds with DEBUG defined.
However, there are at least two potential issues (NOT YET VERIFIED).
1. 386 (or higher) builds might fail on a FAR value, as a 32-bit FAR is past
4GB. I don't know how the compilers treat FAR in these builds.
2.Low memor
