home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!uniwa!john
- From: john@gu.uwa.edu.au (John West)
- Newsgroups: comp.sys.cbm
- Subject: Re: Decreased seek times.
- Date: 7 Nov 1992 10:04:38 GMT
- Organization: The University of Western Australia
- Lines: 26
- Message-ID: <1dg4bmINN73i@uniwa.uwa.edu.au>
- References: <1992Oct19.172546.1@pembvax1.pembroke.edu><1992Oct20.003624.1876@netcom.com> <92308.181655K3027E7@ALIJKU11.BITNET> <1992Nov4.015117.7144@pimacc.pima.edu> <sheun.720890127@barney>
- NNTP-Posting-Host: mackerel.gu.uwa.edu.au
-
- sheun@cs.city.ac.uk (Sheun Olatunbosun) writes:
-
- >At what serial rate is the data being transferred between the computer
- >and the disk drive?
-
- I'm not entirely sure, but I think its around 3000 bps
-
- >Also, is the C64's VIA 6522 chip communicating with a similar chip inside
- >the disk drive?
-
- The 6526 (CIA) in the C64 talks to the 6522 (VIA) in the drive. For the
- purposes of C64-drive communication, the two chips are equivalent.
-
- >I do understand that increasing the transfer rate will not speed things
- >up because the bottleneck is the 1541 reading/writing sectors. It's just
- >that I'm curious.
-
- But it does! I disected one of the early fastloaders - they use the
- standard routines for reading and decoding blocks, and just use their
- own serial routine. That was around 5 times faster, I think.
- Lets see... 256 bytes is 2048 bits, which will take over 0.6 seconds
- to transmit. Thats more than 3 disk revolutions. Thats a lot.
-
- John West
- --
- For the humour impaired: Insert a :-) after every third word
-