Print out with extra character

[ckhsu]

Need help

I'm using 3151 terminal emulator(TinyTERM) on a win 2000 pro to access aix4.3 host through a dial up connection.
Printer=IBM 2381 plus
code page = IBM437
method= pass through printing
When printing a file from aix to a pc attached printer, the print out includes an extra character "u" in the beginning and the end of the print out.

Can any one tell me how to get rid of the extra character?

Thanks
Jason
Network Support

 

[edfair]

Probably need to look at the printer script that is managing the output to see what it is acutally dumping to the terminal. Or hook another terminal in parallel and have it display all and dump a very small file to it to see what the control codes are.
Generally all that dumps is the keyboard off and printer start codes before and the opposite way on the close.
This can be printer problem on unix, multiport problems on hardware, software glitch on receiving end.
And it can be a real joy to troubleshoot. Ed Fair
unixstuff@juno.com
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[ckhsu]

Thank you Ed for your input.

I think the problem is on the windows 2k printer driver .We figured out how to get rid of the extra character "u".
When we set queue's default print job attribute to NOT initialize and restore printer on aix, the "u" disappears. I guess win2k printer driver does not fully understand the control codes from unix.

The terminal emulator works great under win98. The printer prints out files without any extra character. No changes required in aix.


Jason

 

[edfair]

I suspect that you are right about the source of the problem , but I would charge it up to TinyTerm not being fully capable with 2K.
Term gets the control codes, locks the keyboard, directs input to printer for the duration, then redirects the input to the screen and unlocks the keyboard.
You could do the same thing by using and modifying the standard printer script to insert three lines of code before the dump and 3 lines after the dump, code being the turn on and off stuff for the emulation you are using.
I suspect that your extra was the keyboard lock/unlock that wasn't handled correctly by TT/2K. Ed Fair
unixstuff@juno.com
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.