Louis Cyphre

First off, we won't be fixing any WinVICE bugs anymore, the new Gtk3 UI will replace the Windows UI. And then any Windows-specific bugs might get fixed. Good to know! Second, using snapshots very much depends on the VICE version used, ie you can't use a VICE 2.2 snapshot on (the non-existent) WinVICE 3.3. Sorry, I meant WinVICE 3.1. I am not swapping snapshots between versions. Just mentioned those snapshots because I was using them with some game, right before the tape issue appeared. Third, VICE...

Thanks, Querino, I'll follow that "Datasette=0" lead. Update: you were right. Saving a WinWICE 3.1 snapshot sets Datasette=0 in INI file (...\AppData\Roaming\vice\3.1\vice.ini), thus letting the tape disabled for next sessions. Now I know, I'll edit the INI manually whenever it happens again or use a previous version.

I'm having the same TAP issue. Deinstalling WinVICE 3.1 completely, cleaning the Windows register for related keys and deleting any persistent data in the system didn't revert the situation either. I've had to downgrade to 2.2 :-(

Thanks, Querino, I'll follow that "Datasette=0" lead

First off, we won't be fixing any WinVICE bugs anymore, the new Gtk3 UI will replace the Windows UI. And then any Windows-specific bugs might get fixed. Good to know! Second, using snapshots very much depends on the VICE version used, ie you can't use a VICE 2.2 snapshot on (the non-existent) WinVICE 3.3. Sorry, I meant WinVICE 3.1. I am not swapping snapshots between versions. Just mentioned those snapshots because I was using them with some game, right before the tape issue appeared. Third, VICE...

I'm having the same TAP issue. Deinstalling WinVICE 3.3 completely, cleaning the Windows register for related keys and deleting any persistent data in the system didn't revert the situation either. I've had to downgrade to 2.2 :-(