[Coco] DriveWire issues with Coco 1 F/285 Board

[Retro Canada]

aaron,

the best config i could make was;

readdelay=1 and writebytedelay=0

does it make sense for you?

i get timed out after 2xx ms if i dont set the read delay.

btw not setting writebytedelay (leaving default value) seems to not work. maybe an unitialized variable causes the bug?

Sent from my iPhone

On 2013-07-01, at 2:57 PM, Aaron Wolfe <aawolfe at gmail.com> wrote:

> On Sat, Jun 29, 2013 at 2:34 PM, Luis Antoniosi (CoCoDemus)
> <retrocanada76 at gmail.com> wrote:
>> 
>> Hi all,
>> 
>> First thing: i have a computer with serial-usb dongle and it works fine
>> with Coco2 and 3. In 57kbps and 110kbps respectively. And I use DriveWire
>> 4.3.3
>> 
>> But for the coco1 i get a Timed out when reading about 252ms.
>> 
>> I noticed if i change DW advanced setting to: ReadDelay = 1 and
>> WriteByteDelay = 1 it works. But is pretty laggy now. A directory listing
>> is stopped at the middle while it waits half second for the next read and
>> so on.
> 
> Hello,
> 
> I think you would need only WriteByteDelay, this inserts X ms
> artificial delay on each byte sent.  ReadDelay is an artificial pause
> when returning disk sectors, I don't think you should need it.  You
> might get more acceptable performance this way, obviously still not
> ideal.
> 
> It might be that a slight delay on the first byte would be enough to
> let the bitbanger routine sync up.. I will add such an option in the
> next version just in case.  I don't have a CoCo 1 here to test with so
> my apologies, the CoCo 1 support is not well tested at all.
> 
> -Aaron
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco