🚀 go-pugleaf

Dear All,

The following is a precis of internet communication with the author of the
above and also an AmiTCP lpr client.

I consistently get the same report when outputting anything to port 515.
AmiTCP allows me to do this via a TCP: device i.e copy tcp:hostname/515 or
copy tcp:hostname/service. If I type to console from 515 the message is
clear:

                "Malformed 'from' address"

The lpr client also give the same report.
When  running MacTCP under Mac emulation on the same machine withe the same
serial  port,  hostname, and  everything else, it works!?  I'm using Trumpet
Winsock V2.

Help! This is driving me nuts. Your patience and direct replies appreciated.....

-------------------------------------------------------------
To: dob@INEL.GOV
Subject: WSLPD11a

Dear MrBrooks,

You may be pleased to know I'm trying your daemon with Amiga AmiTCP. The
trouble is I've failed!

I get the Trunpet Winsock (V2.0) report as follows:


event detected 08
eventmask = 0008 eventenabled = 0008
NetMessage(2980,<0401 1 0000 08>)
accept(1,2BC7:0F3E,<16>)
rearm 0008
eventmask = 0008 eventenabled = 0008
send(2,2BC7:0700,25,0)
closesocket(2)
recv(-1,2BC7:11E8,4096,0)
Error: WSAENOTSOCK (-1) by WSLPD11A
WSAAsyncSelect(-1,2980,0000,00)
Error: WSAENOTSOCK (-1) by WSLPD11A
closesocket(-1)
Error: WSAENOTSOCK (-1) by WSLPD11A


With the TIS print manager consistently reporting:

"Error: Recv'ing top level command: [10038] socket operation on non-socket"


The Amiga lpr clients all send to TCP:host/service with the services file
at the end of this message. Net BSD is the basis for AmiTCP.


If you have any advice or data on lpr protocol or indeed any pointers to
ftp sites I'd be very grateful.

TIA
                                        Julian


;
; services -- the services database file for AmiTCP/IP
;
; Copyright  1993 AmiTCP/IP Group, <amitcp-group@hut.fi>
;                  Helsinki University of Technology, Finland.
;                  All rights reserved.
;
; Created      : Thu Jul  1 18:24:20 1993 puhuri
; Last modified: Wed Oct 20 05:35:09 1993 ppessi
;
; $id$
;
; This file shouls be included from netdb-file with following line:
; WITH services PREFIX=S
;
echo		7/tcp
echo		7/udp
discard		9/tcp		sink null
discard		9/udp		sink null
systat		11/tcp		users
daytime		13/tcp
daytime		13/udp
netstat		15/tcp
qotd		17/tcp		quote
chargen		19/tcp		ttytst source
chargen		19/udp		ttytst source
ftp		21/tcp
telnet		23/tcp
smtp		25/tcp		mail
time		37/tcp		timserver
time		37/udp		timserver
rlp		39/udp		resource	; resource location
nameserver	42/tcp		name		; IEN 116
whois		43/tcp		nicname
domain		53/tcp		nameserver	; name-domain server
domain		53/udp		nameserver
mtp		57/tcp				; deprecated
bootp		67/udp				; boot program server
tftp		69/udp
rje		77/tcp		netrjs
finger		79/tcp
link		87/tcp		ttylink
supdup		95/tcp
hostnames	101/tcp		hostname	; usually from sri-nic
csnet-ns	105/tcp
pop		109/tcp		postoffice
sunrpc		111/tcp
sunrpc		111/udp
auth		113/tcp		authentication
sftp		115/tcp
uucp-path	117/tcp
nntp		119/tcp		readnews untp	; USENET News Transfer Protocol
ntp		123/udp
print-srv	170/tcp				; network PostScript
;
; UNIX specific services
;
exec		512/tcp
biff		512/udp		comsat
login		513/tcp
who		513/udp		whod
shell		514/tcp		cmd		; no passwords used
syslog		514/udp
printer		515/tcp		spooler		;line printer spooler
talk		517/udp
ntalk		518/udp
efs		520/tcp				; for LucasFilm
route		520/udp		router routed
timed		525/udp		timeserver
tempo		526/tcp		newdate
courier		530/tcp		rpc
conference	531/tcp		chat
netnews		532/tcp		readnews
netwall		533/udp				; -for emergency broadcasts
uucp		540/tcp		uucpd		; uucp daemon
remotefs	556/tcp		rfs_server rfs	; Brunhoff remote filesystem
rmonitor	560/udp		rmonitord
monitor		561/udp
amimsg		612/tcp
elcsd		704/ucp				; errlog
ingreslock	1524/tcp
GridLock	2900/tcp
chat		2901/tcp
;
; Amiga specific services
;
amiganetfs      2500/tcp
;;;; EOF

------------------------------------------------------------
From: jwarren@tazzy.demon.co.uk (Julian Warren)
To: Urs Utzinger-Brunner <utzinger@biomed.ee.ethz.ch>
Subject: Re: WINSOCKLPD

Hi Urs,

FWD> Hi Julian (Julian Warren), in <9411171105.0673@tazzy.demon.co.uk> on Nov 17 you wrote:
FWD>
FWD> > Where is the new lpr? Hint, hint.
FWD>
FWD> Sorry, I do not understand what you mean with this. My version is on aminet.
FWD>
FWD> > As a matter of interest I've picked up another lpr which already reports
FWD> > back. It fails too! I've obtained rfc1179 AND contacted WSLPDs author who
FWD> > cannot figure it out.


I have just got it working with MacTCP from the Emplant side and the
lpr deaemon seemed OK. Strange. I've posted to the emulation and networking
newsgroups about that.

                                Julian


--------------------------------------------------------------
To: Dave Brooks <dob@inel.gov>
Subject: Re: WSLPD11a

Hi Dave,

FWD> Hi Julian,
FWD>
FWD> Julian Warren writes:
FWD>  > In your docs it said you'd tried it with the Mac. Hopefully under MacTCP.
FWD>
FWD> One of my former co-workers, actually; he had a mac with an LPR client, and
FWD> we printed directly from the Mac to the PC.  It was quite an experience!
FWD>
FWD>  > Where do you get a lpd Mac client? - even a name will do.
FWD>
FWD> I'll have to ask him and get back to you.  If you are searching archives,
FWD> try looking for lpr, rather than lpd.

I  found  a  Mac  client  and it works...so back to the drawing board on my
Amiga.   Still  no ideas why I get socket operation on non-socket reported?
You must have coded the message in (or is it in winsock)?

                                        Julian

--------------------------------------------------------
To: Urs Utzinger-Brunner <utzinger@biomed.ee.ethz.ch>
cc: Dave Brooks <dob@inel.gov>
cc: tech-support@trumpet.com.au
Subject: Re: WSLPD propblems

Hi Urs,

FWD> Hello Julian,
FWD>
FWD> please let me know how the names of the files in the printer spooler directory of your
FWD> windows machine when you use a software which works.
FWD>
FWD> It would be nice receiving an example file. There should be 2 files.
FWD> One controlfile and the datafile. Normally they are named like: df1234hostname
FWD> and cf1234hostname.

Here they are arriving on a PC from a mac emulation....


filename "cfa0001" in c:\spool\nlpd\

H200.19.53.25
Pjwarren
fdfA643200.19.53.25
UdfA643200.19.53.25
Nrussadmacfonts.txt.ps
--------------------------------------------------

filename "dfa0000"

%!PS-Adobe-3.0
%%Title: (russadmacfonts.txt)
%%Creator: (BBEdit: LaserWriter 8 8.1.1)
%%CreationDate: (12:30 17, November 1994, )
%%For: ()
%%Pages: 3
%%DocumentFonts: Courier-Bold Symbol Courier
%%DocumentNeededFonts: Courier-Bold Symbol Courier
%%DocumentSuppliedFonts:
%%DocumentData: Clean7Bit
%%PageOrder: Ascend
-----------------------cut-----(BTW as you can see ,no binary was in this)

Filename "seqno"

4
--------------------------------------------------
and Filename "translat" because dos is so stupid filename-wise

dfa0000 dfA643200.19.53.25
--------------------------------------------------

To  avoid  trouble with nameserving I called my mac host not by name but by
its junk IP number (200.19.53.25, the PC being 200.19.53.24) These are the
same  settings  that  I  use for the AmiTCP link (the same serial port too,
empser.device).  I have, of course, tried this addressing scheme on your lpr.


So there you have it.......I D/Ld your latest archive. Its behaviour was
identical.   I've  learned a lot too both about AmiTCP and the relevant RFC
and  I'm  damned if I can see what could be going wrong.  The winsock error
messages are in winsock.h so I suppose I'll have to get that now!

BTW I've been using Trumpet Winsock V2 with WSLPD11a and have already
Mailed Trumpet about the problem (plus cc: this).


                                        Julian

---------------------------------------------------------

From: Urs Utzinger-Brunner <utzinger@biomed.ee.ethz.ch>
To: jwarren@tazzy.demon.co.uk
Subject: Re: WINSOCKLPD
X-Status: OL

Hi Julian (Julian Warren), in <9411171152.0678@tazzy.demon.co.uk> on Nov 17 you wrote:

> When I tinker with your client so as to read the whole of the intial
> response from the server in ascii it reads "Malformed 'from' address"

This is very intersting.

Try to enter YOUR full hostname with domain e.g. zaturn.ethz.ch as hostname
in my lpr code or without domain name e.g. zaturn or just the decimal numbers
eg. 129.132.82.2.
Tell me if it works.

> Note that the lpr I sent you has a bug and the "M" above gets mashed.

That is normal, because after every comman you get the Ok from the remote
machine which consits of one Character (0 or 1) If you get an error message
the first character will be allready taken from the server response and the
first letter is missing. One could insert it again to get the correct message.

---
Urs Utzinger-Brunner, Institute of Biomedical Engineering and Medical Informatics
ETH and University of Zurich Switzerland

------------------------------------------------------
From: Urs Utzinger-Brunner <utzinger@biomed.ee.ethz.ch>
To: jwarren@tazzy.demon.co.uk

Hi Julian (Julian Warren), in <9411210116.06c6@tazzy.demon.co.uk> on Nov 21 you wrote:

> filename "cfa0001" in c:\spool\nlpd\
> 
> H200.19.53.25
> Pjwarren
> fdfA643200.19.53.25
> UdfA643200.19.53.25
> Nrussadmacfonts.txt.ps
> --------------------------------------------------

The version of my lpr should generate a file like:

H200.19.53.25
Pjwarren
Jtext.ps
C200.19.53.25
Ljwarren
fdfA || 4 Hex digits || hostname
UdfA || 4 Hex digits || hostname
Ntext.ps


> To  avoid  trouble with nameserving I called my mac host not by name but by
> its junk IP number (200.19.53.25, the PC being 200.19.53.24) These are the
> same  settings  that  I  use for the AmiTCP link (the same serial port too,
> empser.device).  I have, of course, tried this addressing scheme on your lpr.
 
If I understand correctly and if I rember your last messages, WSPLD still has
a problem when receiveing your hostname information.

1) writeln(pr,d2c(2) || Printername)
2) writeln(pr,d2c(3) || size || ' dfA' || num || myhostname)

If I am correct the statment 1) is excutet in my script but the second is not.

Please  change  the  code and try to experiment with hardcoded names to see
what happens if the name (dfAxxxxx) gets shorter.  Normally the lpd expects
a space, 6 characters and then your hostname.

I  do  not have the RFC document about remote line printing.  Please take a
look  at  the  paragraph  were  the  code  \3sizeoffile  filename  ...   is
explained.   Maybe I have missed inserting an additional parameter which is
not required by most of the lpdaemons.

What  I  still  do  not know exactly is if your windows machine does access
restrictions and needs to know your hostname by name.  However I think that
this is not the problem because the emplant lpr seems to work.

---
Urs Utzinger-Brunner, Institute of Biomedical Engineering and Medical Informatics
ETH and University of Zurich Switzerland


TIA Julian


-- 
 ||  ||||                                ^
 ||  ||||      Julian Warren             | Southsea, Hampshire, England
 ||  ||||ZZ\   ------------------------  |
 \\ZZ//||  || Voice/Data (+44)705 811871 |
       ||ZZ/                             | jwarren@tazzy.demon.co.uk
 UBIQUITOUS   "I can't even spell it"    | Fido 2:440/20.24
 BROADCAST                               | PGP key on reques