Windows Server

Xabaras · Guest

I have several 4247 printers connect to the network via ethernet NIC. I
cerated the connection in SNA. Inside the connection created an LU, in
the print service created a session (3270) for the printer. All it's
up, connected and in session, but the print sent to to this printer(s)
are modified by the driver. Where I can look to bypass the driver? (I
already tried with "Do not format print job" way...)

TY.

Neil Pike · Guest

Xabaras,

I'm off-line at the mo so can't look up a 4247 to see what it is. What driver
are you using? If you don't want any formatting then use the generic/textonly
driver.

You could also check the "bypass gdi" driver.

It's a case of trial and error with a "new" printer I'n afraid. You may end
up needing to use a PDT.

With every PCL "laser" type printer out there I just use the HP Laserjet 4
driver which works a treat.

Xabaras · Guest

Thanks for the answer. The 4247-003 it's an IBM printing machine,
'till now used by coax cable. I put the NT4 Driver in the 2003 Server
with HIS on board (no good), and it's working quite fine, but the
printing are "manipolated" by the driver. Now I'll try the "generic"
way. Thanks again.

Charles Ezzell (MSFT) · Guest

Printing pretty much has to go through the driver. Using the "Generic / Text
Only" print driver from Windows 2000 or Windows XP, or Windows 2003, it will
send the datastream directly to the printer without modifications. Earlier
versions of this print driver did not act as a null printer driver. See the
following article:

182889 Generic/Text Only Printer Driver Acts as Null Printer Driver
http://support.microsoft.com/?id=182889

If that does not solve the problem, you would need to contact IBM to see if
they have a Windows compatable print driver for this printer.

Also, if you are using the snaprint service to print to this printer, you
could try setting "Do Not Format Print Job" on the print session properties.
This has the following effect:

Do Not Format Print Job

Do Not Format Print Job allows print jobs that are formatted with host
software to bypass the Microsoft® Windows®-based printing format system. The
Windows-based Host Print service treats all received data as transparent.
All data is passed directly to the printer.

--
HTH,
Charles Ezzell
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Xabaras" <xabaras@gmail.com> wrote in message
news:1128674145.716826.101100@g14g2000cwa.googlegroups.com...

Neil Pike · Guest

No problem - let us know how the generic/text driver does for you

Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP

Xabaras · Guest

The solution was a little more tricky, but I want to share with the
group.
I removed the NT4 driver and used the "Generic" one, but nothing
changed. Even the "do not format" don't change the situations. Only way
out was using an PDF-PDT file, prepared and compiled for this
situation. With this I can change the printer fonts, the quality and
the width of printing. I founded the info for this kind of file in the
IBM Website, in the HOD (Host on Demand) section.

Thanks Again
Xabaras (G.O.) MCSA - MCSE

Neil Pike · Guest

Thanks Xabaras. I'd be interested to know exactly what the issues you had
that required the PDT file to resolve.

I've never personally had to use a PDT yet, but if I did the whitepaper I'd
start with is this one :-

http://www.microsoft.com/technet/archive/sna/support/snaprint.mspx

Charles Ezzell (MSFT) · Guest

If you are on NT4, the "Generic Text" print driver adds code. Only Windows
2000/2003 (and XP) acts as a true null print device. See my previous mail on
this.

--
HTH,
Charles Ezzell
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Xabaras" <xabaras@gmail.com> wrote in message
news:1129199198.888978.199490@g47g2000cwa.googlegroups.com...

Charles Ezzell (MSFT) · Guest

2003 drivers are just XP drivers, but signed (basically). And, XP drivers
are an "upgrade" of 2000 drivers. At least that is the way I look at them
<vbg>. NT4 drivers ran in the kernel, and these don't (user mode).

--
HTH,
Charles Ezzell
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.00006341.09e26b0d@compuserve.com...

Neil Pike · Guest

Charles - would be useful if that KB article had it's "applies to" section
amended to include XP, Windows 2003 and, of course, Host Integration Server

Neil Pike · Guest

Charles - all I was getting at is that if someone search for "generic text"
and "host integration server" on the Knowledgebase, then they wouldn't find
this article as HIS isn't mentioned/indexed.

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1