#860 Snapshot loading breaks tape loading

[MurlocQ Darkheart]

Hi!

Sorry if I did something wrong, but this is the first time I report a bug here.
I tested this bug on the following versions of WinVICE where it exists:
WinVICE 3.0 x64 (win64 x64 mingw)
WinVICE 3.0 x86 (win32 x86 mingw)
WinVICE 3.0 rev 32660M (win32 x86 mingw)

After I loaded a snapshot for a game (Curse of the Azure Bonds) I tried to autostart a tape image (T64 or TAP) it won't load anything. If I try it manually loading it produces the same results: it says to "press play on tape", but the clicking on the DATASETTE CONTROL's START won't start the loading. The tape icon won't turn yellow. The counter stays at 0. If I press the STOP the icon changes accordingly. Actually nothing happens, yet the emulator works it loads disk images fine after that.

If I restore the default settings it seems to solve it until I load a snapshot again. Then trying to load anything from any tape image won't work at all.

[Stefano Bodrato]

I have a similar problem with the T64 format, I have tape images where the machine code block is just stored before tiny BASIC block jumping in it.
After issuing the LOAD command, the X128 loads the code block, answers with READY, but then no cursor appears.
The previous version works fine.
The program in attachment is my own build (no copyright infringement), and is supposed to be run with the "LOAD", "LOAD", "RUN" sequence. You will notice that the first binary block will hang the latest version of the X128 emulator.

[Louis Cyphre]

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 :-(

[compyx]

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.

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.

Third, VICE doesn't use any Windows registry stuff. Old VICE (< 3.0) used the directory where VICE was installed, I think, modern VICE uses %APPDATA/vice to store vice.ini etc.

Also VICE >= 3.0 changed quite a few defaults, one of those being enabling TDE by default and disabling device traps by default, meaning T64 won't work with default settings. (T64 should really die already).

So, is it really a TAP issue or a T64 issue, and if it's a proper TAP, please post a link to the image so we can at least test something.

[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 doesn't use any Windows registry stuff. Old VICE (< 3.0) used the directory where VICE was installed, I think, modern VICE uses %APPDATA/vice to store vice.ini etc.
As far as I've seen, file associations and other seemingly non-relevant stuff stays in the registry after WinVICE has been properly deinstalled (you could easily check it with any trustable registry cleaner).I really don't know if that may have caused anything, but whatever… I deinstalled WV and then cleaned every other trace of it before reinstalling. Unsuccessfully, though.

Also VICE >= 3.0 changed quite a few defaults, one of those being enabling TDE by default and disabling device traps by default, meaning T64 won't work with default settings. (T64 should really die already).
Yes, I am aware of those changes. T64 is not the thing, but TAP, since the trouble comes with Datasette controls: the emulator acts as if the Datasette had been unplugged.

So, is it really a TAP issue or a T64 issue, and if it's a proper TAP, please post a link to the image so we can at least test something.
I'm afraid it is not a TAP issue, since the very same TAP works fine in previous WV releases, and even worked fine in 3.1 until that odd state came up. But I'll post back soon.

Update: Querino nailed it, please read below

[Querino]

i tested the SDL version (windows)

• launch x64sc
• save snapshot
• load snapshot
• load some t64 or tap file

i only get "press play on tape"

and what i see is: loading a snapshot sets "Datasette=0"
i don't know what that entry is supposed to do, i can set it in the sdl-vice.ini to 0 or 1, loading a tap file fails. i need to remove this entry from the ini to get proper tap loading again.

[Querino]

^ the above is also true for winvice.

also, the following fails:

• load Summer Games.tap
• wait until you get to the menu, after opening veremony
• save snapshot, don'd forget to include ROMs

now reload that snapshot. the tape counter is 000, and if you try to get any further from the menu (practice), nothing happens.

[Louis Cyphre]

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.

[NLS]

The issue still remains in WinVICE 3.2 (yes I got the "we will not fix WinVICE before Gtk3 UI port").
I tried to autostart several (zipped) tap files. It stays in PRESS PLAY and cannot start it.
No loading or saving of snapshots.
My ini is still in WinVICE folder not appdata (and this is how I want it to be too), and indeed had "DATASETTE=0" in it. I switched it to 1 while WinVICE was running and it reverted to 0. Changing it without WinVICE running, does keep it 1.
I suspect I did load a snapshot some weeks ago and that may have switched the parameter originally to 0.

BTW, can someone point me to a post or anything talking about the switch to Gtk3?

[gpz]

I am closing this - it seems to be working in trunk. Please reopen if the problem persists