Diskchanging-Bug in WinUAE 0.9.92?!

[Flachkoepper]

Sometimes WinUAE puts a disk (adf-file), which is inserted into df3, into df0, so that the same disk is in df0 and df3.

This bug seems to appear only sometimes, so I tried to find a way reproducing it. It might be reproduced on several ways, but I describe it in the way I reproduce it (tested with windows XP on a P4 2,66 GHz):


Do the following steps please:


1) Start WinUAE, use default-configuration (so do not load any config, although the bug appears also with other configs).

2) Choose "Disk Drives"-tab, in default-configuration is df0 and df1 active; activate also diskdrives df2 and df3, so that all 4 diskdrives are active now.

3) Take 4 adf-images (e.g. the game "Sword of Sodan", disks 1-4), (make sure they are write-protected!), insert (in the following order, using the "..."-buttons (for searching each disk)):

disk 1 into df0,
disk 2 into df1,
disk 3 into df2 and disk 4 into df3

4) klick on "start"-button to start the game (or whatever is on the adf-disks).

When WinUAE starts emulation (and loads from disk), do the following:

5) Press F12 for WinUAE-menu (e.g. 1 or 2 seconds after starting emulation).
6) Press "eject"-button for df3, do NOT return to the game yet.
7) Insert disk 4 in df3 again (using "..."-button), return to emulation now.


What do we see? Yep, disk 4 ist in df0 now, too!

(if this is not the case after first try, repeat steps 5-7 several times!! Most often it appears when WinUAE starts loading e.g. an AmigaDOS-screen after booting).

Can anybody confirm this bug please? Or is it just e.g. a synchronization-problem under windows xp?!

[SexyWayne]

haven't tested it myself as i use the real thing, unless i need a amiga fix at work, but why do you need to eject a disk then reinsert the exact same disk?? ,sure it maybe an annoying bug if ejecting and reinserting is your thing

[Flachkoepper]

It does not matter wether it is the same disk or not - it also happens sometimes when you insert a different disk The way I described above is only one possibility to reproduce this bug (for fixing it). This bug is more or less annoying, but in the worst case it might cause data loss when you change a disk in df3 while something is saved to df0 by a game or somewhat ever.