For recreating the problem you need to have two computers with WinXP, Let's
name one computer - Test1, another - Test2, users with admin rights (and with
nonempty password - for not having problems with terminal access)

On the computer Test1 let's create new printer and reassign its terminal in
a file, put the LPT1 on it:

rundll32 printui.dll,PrintUIEntry /if /b "tofile" /f
%windir%\inf\ntprint.inf /r "file:" /m "Generic / Text Only" /u /Z
rundll32 printui.dll,PrintUIEntry /Xs /n "tofile" sharename "tofile"
attributes +Shared net use lpt1: /d net use lpt1: \\127.0.0.1\tofile

Let's check that everything is ok
echo test 1 >lpt1:

the window must appear with demand for the name of the file, let's introduce
for example d:\1.txt and in the received file you need to see the word "test
1".

Now start up the mstsc.exe, in additional parameters "Local resources" put
the tick on <Serial ports ", connecting to Test2 (permission has to be
opened). Start up the cmd, from the command line call the echo test 2 >lpt1:

If with the linking of ports there were no mistakes, so you will get the
same demand name and in a file "test 2". If there were problems with linking
so usually the tick is helping (see above "serial ports") or the following
thing
net use lpt1: /d
net use lpt1: \\tsclient\lpt1


Why the problem appears - when we want to record several lines. In the same
terminal session let's do the following thing

copy con lpt1
aaaaa
bbbbb
ccccc
^Z (key F6)

And you will see that in the file there is only one line - ccccc !!!!

More that it if you record the same not in lpt but in file, and after that
if you will copy this file in lpt - you will see that everything will be ok,
so the problem appears in cases when it is written in several parts, as by
manual entry of the text for each entry.

Help us, Fank you...