Re: Understanding ANSI Output Failure

I don't see how ANSI.COM could affect any 32-bit program. .COM programs are 16-bit DOS programs. ANSI.COM likely intercepts DOS print requests, something 32-bit programs (including 32-bit console programs) do not utilize. ActivePerl is a 32-bit program. Could your C programs have been 16-bit programs?

Comment on Re: Understanding ANSI Output Failure

Replies are listed 'Best First'.
Re^2: Understanding ANSI Output Failure by marinersk (Priest) on Mar 21, 2005 at 20:11 UTC
The C programs were 32-bit console programs, so this probably isn't the source of the problem -- but I hadn't even considered it so thanks for the note.	[reply]
Re^2: Understanding ANSI Output Failure by marinersk (Priest) on Mar 21, 2005 at 20:38 UTC
Hmm. Maybe you're right. The DOS program was a 16-bit program. When I try to use TYPE on a data file containing ANSI codes, I get the same results as my Perl script. Aha!	[reply]