Google Groups Home
Help | Sign in
Zmodem PD 65c02 Source
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  5 messages - Collapse all
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
Andrew Nicholas  
View profile
 More options Jul 29 1991, 8:04 pm
Newsgroups: comp.sys.apple2
From: shrin...@Apple.COM (Andrew Nicholas)
Date: 29 Jul 91 06:18:58 GMT
Local: Mon, Jul 29 1991 4:18 pm
Subject: Zmodem PD 65c02 Source
FYI, I just posted the source code to my GBBS Zmodem drivers to
comp.binaries.apple2 -- the source code is public domain now (and is marked as
such).  Feel free (and please do!) to use it in any projects you might do.

RZ and SZ each take up about 5k as binaries without the 1.5k CRC lookup tables.

Both RZ and SZ each need at least 8k of buffer space, but no more than 16k
of buffer space.  Both use CRC-32 error checking.

andy

--
Andy Nicholas                   GEnie & America-Online: shrinkit
System Software Engineer                    CompuServe: 70771,2615    
Apple Computer, Inc.                          InterNET: shrin...@apple.com


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Joe Quilici  
View profile
 More options Jul 31 1991, 5:56 pm
Newsgroups: comp.sys.apple2
From: ta...@pro-odyssey.cts.com (Joe Quilici)
Date: 30 Jul 91 11:57:21 GMT
Local: Tues, Jul 30 1991 9:57 pm
Subject: Re: Zmodem PD 65c02 Source
In-Reply-To: message from shrinkit@Apple.COM

I remember someone stating that Z-modem is impossible to do on an Apple //,
mainly because it is a streaming protocol and the Apple can't directly
write the incoming data to the HD; instead having to pause to write.  Does
your code automatically pause the send, load the data or save the necessary
data, and continue sending?
----
ProLine:  talon@pro-odyssey
Internet: ta...@pro-odyssey1.cts.com
UUCP:     crash!pro-odyssey!talon
ARPA:     crash!pro-odyssey!ta...@nosc.mil


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Todd P. Whitesel  
View profile
 More options Jul 31 1991, 9:34 pm
Newsgroups: comp.sys.apple2
From: tod...@nntp-server.caltech.edu (Todd P. Whitesel)
Date: 31 Jul 91 04:27:42 GMT
Local: Wed, Jul 31 1991 2:27 pm
Subject: Re: Zmodem PD 65c02 Source

ta...@pro-odyssey.cts.com (Joe Quilici) writes:
>In-Reply-To: message from shrin...@Apple.COM
>I remember someone stating that Z-modem is impossible to do on an Apple //,
>mainly because it is a streaming protocol and the Apple can't directly
>write the incoming data to the HD; instead having to pause to write.  Does
>your code automatically pause the send, load the data or save the necessary
>data, and continue sending?

At the risk of putting words in Andy's mouth, his code has to do one of two
things:

        tell the other end to pause sending
        just write to the disk and let the garbled packet be retransmitted

ANY micro using a disk controller that causes interrupt blackouts faces the
same choice, and in no way does it prevent one from implementing Zmodem. It
does put take a bite out of the maximum transfer rate though.

Todd Whitesel
toddpw @ tybalt.caltech.edu


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Andrew Nicholas  
View profile
 More options Aug 1 1991, 1:14 am
Newsgroups: comp.sys.apple2
From: shrin...@Apple.COM (Andrew Nicholas)
Date: 31 Jul 91 05:33:33 GMT
Local: Wed, Jul 31 1991 3:33 pm
Subject: Re: Zmodem PD 65c02 Source

In article <1991Jul30.115721.5...@crash.cts.com> ta...@pro-odyssey.cts.com (Joe Quilici) writes:
>I remember someone stating that Z-modem is impossible to do on an Apple //,
>mainly because it is a streaming protocol and the Apple can't directly
>write the incoming data to the HD; instead having to pause to write.  Does
>your code automatically pause the send, load the data or save the necessary
>data, and continue sending?

Yes.  That's one of the provisions of Zmodem; you can specify a buffer size
if you are the receiver or respect the buffer size of your receiver if you are
the sender.  ProTerm v2.2 does the latter, but not the former.  My code does
both.

And, whoever said that Zmodem is impossible to do on an Apple II didn't know
anything about Zmodem.

andy

--
Andy Nicholas                   GEnie & America-Online: shrinkit
System Software Engineer                    CompuServe: 70771,2615    
Apple Computer, Inc.                          InterNET: shrin...@apple.com


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
David Empson  
View profile
 More options Aug 1 1991, 6:33 am
Newsgroups: comp.sys.apple2
From: David.Emp...@actrix.gen.nz (David Empson)
Date: 31 Jul 91 14:20:10 GMT
Local: Thurs, Aug 1 1991 12:20 am
Subject: Re: Zmodem PD 65c02 Source

In article <1991Jul30.115721.5...@crash.cts.com> ta...@pro-odyssey.cts.com (Joe Quilici) writes:
> In-Reply-To: message from shrin...@Apple.COM

> I remember someone stating that Z-modem is impossible to do on an Apple //,
> mainly because it is a streaming protocol and the Apple can't directly
> write the incoming data to the HD; instead having to pause to write.

ZMODEM doesn't have to be used in 'streaming' mode.  There is an
initial handshake in which the sender and receiver decide how they
will talk to each other.  If the receiver can't handle streaming, it
can tell the sender to wait for an acknowledgement before sending the
next block.  Alternatively it could send a message saying 'hang on,
I've lost some data.  Can you please re-send from byte XXX'.

Streaming doesn't require writing incoming data directly to the hard
drive.  It only requires that incoming data is not lost while the hard
drive is being accessed (i.e. interrupts are not disabled for very
long) and that the hard drive can be written to faster than the data
is coming in.

This is usually the case, unless you are writing to a floppy disk...

--
David Empson

USENET: David.Emp...@bbs.actrix.gen.nz


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2008 Google