Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!princeton!udel!rminnich
From: rminnich@udel.EDU (Ron Minnich)
Newsgroups: comp.sys.amiga
Subject: sources to dvi2iff, version -1; tcp/ip for amiga
Message-ID: <503@louie.udel.EDU>
Date: Mon, 14-Sep-87 11:59:37 EDT
Article-I.D.: louie.503
Posted: Mon Sep 14 11:59:37 1987
Date-Received: Tue, 15-Sep-87 05:46:30 EDT
Reply-To: rminnich@udel.EDU (Ron Minnich)
Organization: University of Delaware
Lines: 42

The sources to a very preliminary version (-1) of dvi2iff are 
in pub/dvi2iff.tar.Z on louie.udel.edu. It only does one page, 
cause at the moment it just calls PutPict; if you broke up 
PutPict then you could do many pages. The iff code from EA is real nice,
and the dv.c code is pretty clear. ALl the iff code on the iff disk is 
there. This program has compiled and run on a Sun-3; there is no 
sun-specific stuff in it. I have stopped working on it pending 
a decision to just buy AmigaTeX, which is a real impressive
piece of work. Anyway you wizards out there can probably 
bang this piece of junk into shape. Unfortunately it has to run 
on the Amiga; i was crazy to try dvi2iff on the sun and ftp it 
down, as one full page is a couple k of (compressed) bitmap. too big. 
Questions to me and i will try to help.
  ON a related note, i have been thinking about TCP/ip on amiga. 
My idea is to take ed pucketts pipe device and hack it so that 
it is wired into TCP/IP. Then TCP/IP looks like a device; we could
call it net:. Why do this? Well, consider this mapping:
First, call the modified pipe device net:
Open	->	open a tcp/ip socket. You call it  "tcp.port" (e.g. tcp.25)
                or just "ip". Returns a handle to a unique tcp or ip port
Close	->	close the socket
Dir	->	when applied to net:, just shows you all the open sockets.
Delete	->	close the connection from outside the tcp/ip code
		or the program using the socket, e.g. you could 
		from the CLI do a DIR net:, then delete stuff 
		you are trying to kill.
and so on.

Note that we can also allow taps on connections; useful for debugging.
Now we can migrate telnet, ftp, and so on out of the karn code 
into seperate processes. We can also now run rcp, rsh, and so on. 
Each tcp/ip user will be in its own window. Looks like a win to me; 
it is not possible on a PC or Mac because, as usual, no multi-tasking.
In fact the karn code does a sort of multi-tasking on its own 
because of this lack.
   Anyway, i started to do this, and my shitso Lattice v3.03 gets
a CXERR 28 on iproute.c. Damn. Guess i have to wait for 4.0 and 
then update. Any of you wizards wanna hit this, go to it. It is
actually not too hard.
ron
-- 
Ron Minnich