ICE

Raster should work for everything. If it isn't then your unix application is sending formatting codes for a specific printer.

What printer do you have?
How is it connected to your computer??

I missed something, the version I tested no problem for printing is 5.1.06.
It's unable to auto-connect in SSH session, so I want to use new version.

Thanks for fast reply.
1. Already tried turning on & off for "print while transferring", and yes, I know that I have to reload the problem when I change settings.

2. Tested with HP laser 4200, Ricoh 1515, PDF Creator, and please noted that I've tested to print in software, i.e. should not related to compatibility of printer.

3. Yes, it's on the same machine, same environment, I just need to re-install the older version and I can print without problem.

The thing I don't understand, is TCP-Pro trying to get pass letting windows driver to handle print job?

There are 3 print options in PRO. They work as follows:

Normal: sends the print job to the windows spooler telling the spooler to consider the data to be preformatted for the printer (this is what a unix application normally does with a print stream). Note that not all windows print drivers seem to support the notion of a raw print stream.

Direct: Send the print job byte for byte unchanged directly to the specified DEVICE. This means that you can only use this with printers directly connected to the windows PC.

Raster: Convert the incoming unix print job into a windows raster style output. There is LIMITED line printer emulation in this mode, it will handle the following control codes
Form Feed (control-L)
Line Feed (control-J)
Carriage Return (control-M)
Condensed Print (control-O)
Normal Print (control-R)

The Raster driver should print any TEXT job to any windows printer, even a "winprinter". It will NOT handle unix binary print jobs.

NOTE, these are the settings for transparent print in PRO, they do NOT apply to icelp.

If you are using transparent print, try changing from ssh to telnet and see if that changes your printing behavior. Report back..

I've tested all the versions of the tcp-pro from your ftp, except the beta ones.
the latest version I can print is 5.1.19, it fails at 5.1.21 or any later version.

The only thing I can see the difference between is that, I can see 3 options  in the print dialog when I try to print.

In "print range"
1. All
2. Print screen
3. Selection

I can print without any problem for 2 & 3.
It will print some garbage code if I select "all", it's the same result as if I use "raster" in profile settings.

Start from version 5.1.21, the option of "print screen" is gone.
I cannot print anything for "All" nor "Selection", no matter I change any option in "profile" or "print option" for this version.

5.1.26:
I can only print with "raster" option in "profile" setting, but it also print with some garbage control codes.

Hope this information helps for you.

tried normal telnet.

I tried print at the login screen, or in any screen in the system, it just print blank screen.
Should be no special setting for the server, and I tried to use it to connect to a normal linux I just set up, same result.

Tested using a newly installed windows, and note it's a windows 2000.

I'm using pro version.

Are you TRYING TO DO A PRINT SCREEN???

If so, in the new versiond, just click on the printer icon on the toolbar
or right-click and do a print->screen from the right click menu.

The print function from the pull-down now prints the whole buffer by default.

Try the printer icon and report back.

It looks like you are having a problem with MFC42.DLL then. The OLD version 5.1.19 uses a DYNAMIC version of that library and the newer versions have it compiled in. Using the compiled in version FIXED a lot of problems we were having with people who had corrupted versions of MFC42.DLL on their machines. It looks like your only option is to use the 5.1.19 version or TelnetPro.