>The problem is you're sending output through the GDI, which converts your control sequences to graphical characters based on the current font. Either send it using ???, bypassing the GDI (but also starting a new print job), and take responsibility for all formatting for the entire output, opr create output to a file, parse the resultant file, insert your string at the right point, and then queue it to a print port bypassing the GDI by using CopyFile() - there's code in the FAQ for this.
>
>You could also end the first string, then issue an EJECT PAGE, then send the remaining string.
>
>In general, where I need detailed, hardware-specific behaviors, I don't want the GDI involved - I give up on hardware independence and Windows printer behavior, using a direct port driver to directly control the port and bypass all normal Windows GDI services.

Ah! Thanks Ed. Although I can't do anything about it at the moment, it is nice to understand what is happening or in my case not happening. As I mentioned to Rick, I was able to come up with a solution so for now the problem is solved.

-Isaac