"One week after I'm sure plugin does indeed access correct sectors with every card" is pretty safe assumption. While crashes are bad when loading, they are still pretty harmless compared to random trashing of data during save.

After I've fixed all known bugs I will release read-only version at CSDb, just to get more bug reports. After fixing any new bugs it may be safe to assume that plugin is ready for writing to card.

Please let me know if it works better now. I think I fixed the buffer bug, but I'd like to hear if it still fails with your cards.

d64 browser is messed up it displays junk when you do load "*",8
it does not list d64 files like load "$",8
i think its trying to load the program commands instead of the directory

...hangs while "searching for..."

I found a bug in cluster chain scanner yesterday. It was introduced when I duplicated card reading routines for the entry screen, and results in reading cluster chain into wrong buffer altogether sometimes. Symptoms are hangs in directory/image scanning and apparently garbled image contents (images are ok, they are just read from wrong part of card).

I hope that's the last one.

I thought i cut an long story short. so oliver says thats he trashed the d64 writer in the v3 bois may be tnt you could fit more code in and make it run a side with your plug in.
cheers
paul

that´s weird - I EXPIRIENCED THE SAME THING PAULM DID! just when i thought my card reader would be rubbish... i renamed your last plugin on the sd card just to keep it as a copy. copied the new plugin on the card, gave it a try, saw that it did not work for me, deleted it and renamed the once working plugin back again. now this one does not work either anymore. only loads the first file... i´m getting a little frustrated because i´m having issues i do not understand here. could you give me a link with the former plugin please?

p.s. wasn´t it supposed to say load"*",8,1 when pressing shift and return? i can´t quite remember but at the moment when i press shift and return it just says load"*", loads and runs the first file and then doesn´t continue loading...

thanks in advance!

lO"*",8,1<cr>rU<cr> doesn't fit into keyboard buffer, so there is a kludge which ignores device number for the first load if autostart is used (it also sets last used device correctly, so programs using it don't try to access tape).
That kludge doesn't set the secondary address (",1" part) but as autostart only works with BASIC programs that's not much of a problem. Most load"*",8,1 autostarting programs load over BASIC/kernal vectors and that usually means losing MMC64 patches, so I don't see reason to try supporting them. IDE64 doesn't, either.

Wait until tonight for the (hopefully) fixed version, as I've already found and identified the bug - I just didn't like the idea of another night with only 4-5 hours of sleep so I went to bed instead of fixing it last nigh.

...reminds me of that great hit by faithless... i can´t get no sleep

looking forward for any new release - i´m on my summer holidays, so plenty of time for testing

anyway, take your time!

And when weekend comes

Anyway, plugin might work a bit better now.

yep thanks again tnt it works cool
i rebuilt spot with dir master in d64 format and the new plug now kicks a**

cheers again paul

...used to sing "i can´t get no sleep" in my dentistry exams - horrible time that was...

any place to download?

edit: ok, i got it!

and it seems to work again...

Great.

There were two bugs size of an overweight elephant:
- FAT buffer wasn't initialized correctly in the beginning
- directory scanner used block read meant for resident plugin, reading correct FAT data into wrong buffer

Both result of changes in multidisk support, which I foolishly hacked together just before leaving town for a couple of days.

Ok, final version before grand opening uploaded. Directory display in entry screen works again.