#17 cbmforng is not fixed _enough_ for the "1571 mysteries" bug

[Womo]

After analysing an issue with cbmforng at an users 1571,
it was concluded that again the "1571 mysteries" bug
occured. For more read:

http://listserver.jonet.org/mailman/private/cbm4win/2005-May/000699.html
http://www.softwolves.pp.se/misc/arkiv/cbm-hackers/10/10471.html

Although cbmforng (as well as cbmformat) got fixes
included for such a case, it seems that there is not
enough delay between switching back from writing into
read mode again.

But I don't want to give even bigger delays as a general
fix, since it makes cbmforng slower and slower on all
drives, the 1541, 1541-II, 1570 and 1571cr too. On
these the fix not needed at all.

Another possibility for a fix may be to do that delay
on-demand only. Only then, when the verifier detects
that the wrong or a corrupted SYNC makr is read back, it
does delay for a complete sector (header with data
block) and tries the test again...
This will become somewhat difficult to code but may
worth a try.

[Womo]

Logged In: YES
user_id=1434341

Lowered priority to 4 since it seems that only few people's
1571 disk drives seem to be affected. Further the drive
failure can easily be worked around by using the original
format patrtern.

[Spiro Trikaliotis]

Moved over to github