From: Andre Fachat (afachat_at_gmx.de)
Date: 2004-07-10 12:49:44
Hi Ruud,
this is not a matter of being fast enough, but a matter of where to
actually read the data. If I remember correctly, I had quite some pains
with my IEEE488 implementations until I (think I) decided to simply
read the data during the open, when the drive receives the UNLISTEN (from
open, and maybe even during UNTALK from the previous read). The the
PET would wait with the open until the data is available and would not
time out when it sends the TALK.
(But that is from my memory only, so take it with a grain of salt).
Andre
On Tue, Jul 06, 2004 at 01:21:56PM +0200, Baltissen, GJPAA (Ruud) wrote:
> If someone wonders why 64HDD can do the job W/O the hardware, I can give you
> the answer. My CBM-HD is based on PC-Disk, an equivalent of Nick's 64HDD.
> And I soon found out that the CBM is more time critical then the C64. For
> example: originally I did actually collect the needed data for displaying
> the directory AFTER receiving the TALK-command from the C64. And that was on
> a 486/66. But a P3/450 was not fast enough as my 8032 timed out displaying
> "FILE NOT FOUND?". So I had to change the program to collect the data
> immediatly after receiving the actual command (as the 1541 does).
Message was sent through the cbm-hackers mailing list
Archive generated by hypermail pre-2.1.8.