I am trying again - What I send into the printqueue is NOT what comes out in the other end :-(

[Ebbe]

I have a printing device with a serial interface.
It is connected to a serial port of a print server, that is connected to the
network.
To day I am printing from a UNIX box, but I am moving the system to a
Windows platform.

The application is printing to a LPT-port (e.g. LPT9).
LPT9 is redirected to \\server\sharename using NET USE LPT9:
\\server\sharename

My problem is: What I am sending into LPT9 is NOT what the printing device
is receives.

My best guess is that the printerdriver on \\server\sharename is trying to
interpreter the data received from LPT9.

Here is a little example:

The \\server\sharename is installed with a driver: Generic/Text only

LPT9 receives:
01 50 02 31 41 4B 53 45 .P.1AKSE
4C 42 03 0D 01 56 02 30 LB...V.0
31 34 34 34 34 03 0D 01 14444...
56 02 30 32 33 33 33 33 V.023333
03 0D 01 56 02 30 33 32 ...V.032
32 32 32 03 0D 01 56 02 222...V.
30 34 31 31 31 31 03 0D 041111..

The printing device receives:
0D 0A 0D 0A 20 50 31 41 .... P1A
4B 53 45 4C 42 0D 0A 20 KSELB..
56 30 31 64 64 64 64 0D V01dddd.
0A 20 56 30 32 63 63 63 . V02ccc
63 0D 0A 20 56 30 33 62 c.. V03b
62 62 62 0D 0A 20 56 30 bbb.. V0
34 61 61 61 61 0D 0A 0D 4aaaa...
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A 0D 0A 0D ........
0A 0D 0A 0D 0A .....

How can I define a printer, that is totally transparent?

Ebbe

[GTS]

The 0A 0D pairs are line feed / carriage return codes. In properties on the
Generic/Text only driver / Advanced tab / Print Processor button, is default
data are you set to type set to RAW? If not, that might be the problem.
What print server device are you using?
--

"Ebbe" > wrote in message
...
>I have a printing device with a serial interface.
> It is connected to a serial port of a print server, that is connected to
> the
> network.
> To day I am printing from a UNIX box, but I am moving the system to a
> Windows platform.
>
> The application is printing to a LPT-port (e.g. LPT9).
> LPT9 is redirected to \\server\sharename using NET USE LPT9:
> \\server\sharename
>
> My problem is: What I am sending into LPT9 is NOT what the printing device
> is receives.
>
> My best guess is that the printerdriver on \\server\sharename is trying to
> interpreter the data received from LPT9.
>
> Here is a little example:
>
> The \\server\sharename is installed with a driver: Generic/Text only
>
> LPT9 receives:
> 01 50 02 31 41 4B 53 45 .P.1AKSE
> 4C 42 03 0D 01 56 02 30 LB...V.0
> 31 34 34 34 34 03 0D 01 14444...
> 56 02 30 32 33 33 33 33 V.023333
> 03 0D 01 56 02 30 33 32 ...V.032
> 32 32 32 03 0D 01 56 02 222...V.
> 30 34 31 31 31 31 03 0D 041111..
>
> The printing device receives:
> 0D 0A 0D 0A 20 50 31 41 .... P1A
> 4B 53 45 4C 42 0D 0A 20 KSELB..
> 56 30 31 64 64 64 64 0D V01dddd.
> 0A 20 56 30 32 63 63 63 . V02ccc
> 63 0D 0A 20 56 30 33 62 c.. V03b
> 62 62 62 0D 0A 20 56 30 bbb.. V0
> 34 61 61 61 61 0D 0A 0D 4aaaa...
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A 0D 0A 0D ........
> 0A 0D 0A 0D 0A .....
>
> How can I define a printer, that is totally transparent?
>
> Ebbe
>

[Klaus Jorgensen]

"Ebbe" > wrote in message
...
>I have a printing device with a serial interface.
> It is connected to a serial port of a print server, that is
> connected to the
> network.
> To day I am printing from a UNIX box, but I am moving the system to
> a
> Windows platform.
> ...
> My problem is: What I am sending into LPT9 is NOT what the printing
> device
> is receives.
> ...
> How can I define a printer, that is totally transparent?
>

If printing to a shared printer using the Windows NT LPD service,
control codes are sometimes added to the data stream - it doesn't
matter which driver is being used. This can be disabled using the
SimulatePassThrough regkey:
http://support.microsoft.com/support/kb/articles/Q150/9/30.asp


/klaus

[Klaus Jorgensen]

"Klaus Jorgensen" > wrote in message
...
>
> If printing to a shared printer using the Windows NT LPD service,
> control codes are sometimes added to the data stream - it doesn't
> matter which driver is being used. This can be disabled using the
> SimulatePassThrough regkey:
> http://support.microsoft.com/support/kb/articles/Q150/9/30.asp
>

Ooops - if printing via "net use" you are probably not using the
LPDSVC... /-:
What is the source platform, and does it support printing to a file
instead of a device to determine if the codes are being added/modified
by the local platform or the printer server?
If the printer server is a small network box, it might support
NetBEUI - these can be addressed directly from Windows clients.


/klaus

[Ebbe]

Hey!

Unfortunately I discovered, that the problem was what I sent into the
LPT-port :-(
I had'nt control over the application.
After more tests I discovered an error in the application adn then ---- It
all worked.

Ebbe

"Klaus Jorgensen" > skrev i en meddelelse
...
> "Klaus Jorgensen" > wrote in message
> ...
>>
>> If printing to a shared printer using the Windows NT LPD service,
>> control codes are sometimes added to the data stream - it doesn't
>> matter which driver is being used. This can be disabled using the
>> SimulatePassThrough regkey:
>> http://support.microsoft.com/support/kb/articles/Q150/9/30.asp
>>
>
> Ooops - if printing via "net use" you are probably not using the
> LPDSVC... /-:
> What is the source platform, and does it support printing to a file
> instead of a device to determine if the codes are being added/modified
> by the local platform or the printer server?
> If the printer server is a small network box, it might support
> NetBEUI - these can be addressed directly from Windows clients.
>
>
> /klaus
>
>
>