#604 C128 Drive 1571, writing to image does not work

[BenDeVil]

The use of the 1571 drive in C128 (40/80col) is not correct. I can attach a disk image, I can "catalog" it to see what are in. But, when I save a program, after saving, the drive light blink red. I must reattach the image to do an opération on the drive.
Sometime, the result of the saving isn't goot too. I can't read from disk again my basic program.

[badco]

The 1571 emulation is certainly broken in 2.4, at least when using it in 128 mode. Any attempt to write to an image results in the drive failing.

[J. E. Klasek]

This is still an issue, even on the last nightly built
WinVICE-2.4.20-x86-r29835.

[gpz]

did this ever work before?

[Soci/Singular]

Works on XAW here, no matter how I try. Upload config file, non-default ROMs, disk image if it's not the one created by VICE.

[J. E. Klasek]

Using x128 2.4 (GTK+ AMD64/x86_64 Linux GCC-4.9.1) running on Linux Fedora 21, but also on WinVice (non SDL-Version, x64) on Win7 x64 the same behavior.
Created an empty d64 image, try to DSAVE a one-liner basic program, fails (23,read error). Disk is not readable anymore (DIR fails with same error). Reattach disk, DIR shows a star-marked file (incomplete written). Try to do a COLLECT, which work until it wants to correct something on disk ... See attachment (screen-shot, d64 image in a ZIP archive)
It looks like the image detaches automatically during write ...

[J. E. Klasek]

Forgot the vicerc file (from the Linux environment) ...

[Soci/Singular]

Right, if I download the old 2.4 tarball and compile it then it does not work, as reported.

2.4.20 (somewere 29786:29797) which I tried before works.

Also compiled the above mentioned 29835 too (XAW), worked as well. No idea about why the Windows build did not.

A single x128 only build takes more than 10 minutes here, so I'll not try to find out when and how 2.4 was fixed (at least on Linux).

[gpz]

i find it hard to believe something like that will work in linux but not in windows... shrug

[J. E. Klasek]

I saw the problem on both platforms, but I don't know the actual build number ... How can I get the build number from Vice binary?

[gpz]

On Monday 13 July 2015, 08:19:03 J. E. Klasek j_e_klasek@users.sf.net wrote:

I saw the problem on both platforms, but I don't know the actual build
number ... How can I get the build number from Vice binary?

its printed at the beginning of the logfile, and shows up somewhere in the
"about" dialog.

--

http://www.hitmen-console.org http://magicdisk.untergrund.net
http://www.pokefinder.org http://ar.pokefinder.org

Who can afford to do professional work for nothing? What hobbyist can put
three man-years into programming, finding all bugs, documenting his product,
and distribute it for free?
<bill gates=""></bill>

[Greg King]

Pokefinder's WinVICE-2.4.20-x86-r29837 works for me, on Windows 7.

[gpz]

so can this be closed? does it work in 3.0?

[BenDeVil]

Yes, now, I haven't any more problem with drive

Thanks

[gpz]

ok, closing then

[compyx]

Really closing now, stupid SF.