Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!jgreco
From: jgreco@csd4.milw.wisc.edu (Joe Greco)
Newsgroups: comp.sys.cbm
Subject: Re: Zmodem on commodores?
Message-ID: <739@csd4.milw.wisc.edu>
Date: 2 Feb 89 23:05:00 GMT
References: <10978@s.ms.uky.edu> <14095@cup.portal.com> <683@csd4.milw.wisc.edu> <6482@emcard.UUCP>
Sender: news@csd4.milw.wisc.edu
Reply-To: jgreco@csd4.milw.wisc.edu (Joe Greco)
Organization: UW-Milwaukee Home for Out-of-date 8 bit Hackers
Lines: 32

In comp.sys.cbm article <6482@emcard.UUCP>, mat@emcard.UUCP (W Mat Waites) wrote:
]What ever happened to the joker who posted a couple of months ago about
]building a real UART board?

Are you referring to ME?  I don't have the facilities, and I have been
trying to talk somebody into doing it for me  :-)

]Surely the NMI routines run fast enough to allow response to a uart, i.e.
]1 interrupt per character.

Definitely.  I would see very little problems with allowing
simultaneous serial bus access and UART I/O (if the UART NMI is fast
enough).

]Another kludgey possibility (and aren't kludges the tradition in c64

Yes they are.... heh

]telecomm?) would be to allocate a large chunk of memory to hold
]incoming blocks. That would allow you to cut zmodem loose for 20k bytes
]worth of data or so, and then hold up zmodem and write it all out.
]You wouldn't acheive the max throughput of zmodem, but it would be much,
]much better than xmodem or punter.

Z-Modem might time-out while the 64 was saving the data.  I don't
know, I've never tried it.

--
jgreco@csd4.milw.wisc.edu		Joe Greco at FidoNet 1:154/200
USnail: 9905 W Montana Ave			     PunterNet Node 30 or 31
	West Allis, WI  53227-3329	"These aren't anybody's opinions."
Voice:	414/321-6184			Data: 414/321-9287 (Happy Hacker's BBS)