Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!emcard!mat
From: mat@emcard.UUCP (W Mat Waites)
Newsgroups: comp.sys.cbm
Subject: Re: Zmodem on commodores?
Message-ID: <6482@emcard.UUCP>
Date: 1 Feb 89 14:02:15 GMT
References: <10978@s.ms.uky.edu> <14095@cup.portal.com> <683@csd4.milw.wisc.edu>
Reply-To: mat@emcard.UUCP (W Mat Waites)
Organization: Emory Univ CDB
Lines: 38

In article <683@csd4.milw.wisc.edu> jgreco@csd4.milw.wisc.edu (Joe Greco) writes:
}In comp.sys.cbm article <14095@cup.portal.com>, Brendan@cup.portal.com (Brendan P Kehoe) wrote:
}> I'm in the middle of trying to write a reliable zmodem routine...but it's
}>got to be *THE* pickiest protocol on this planet.
}
}I would think that you would run into several problems with the 1541
}as a disk drive.  I would think that the fact that the 1541 and RS232
}are mutually exclusive (can't listen/talk to RS232 while drive is
}being used) would be a problem with Z-Modem.  That's one reason that
}Commodore protocols have always been a little limited.
}
}.									JG
}
}--
}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)

What ever happened to the joker who posted a couple of months ago about
building a real UART board?

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

Another kludgey possibility (and aren't kludges the tradition in c64
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.

Mat

-- 
W Mat Waites
gatech!emcard!mat
8-5 ET: (404) 727-7197