I am going to go out on a limb here and assume (at my peril) that VICE doesn't emulate drives talking directly to each other other IEC without the computer directing them. That is what that Maverick copier does. The data is not being sent from drive 8 to the 64 to drive 9 - the custom copier program in the drives are talking directly to each other.
Actually what happens is no matter what I type for the address, it is sent to $D420...
2nd SID addresses $DE00 and $DF00 are ignored
This bug is verified not to be valid. The original reporter has another problem with...
Good point- I will also test with v1/v3 kernal on a real machine. :) i doubt this...
http://www.lemon64.com/forum/viewtopic.php?p=722348#722348
The original reporter now says it's not VIC-II chip-related, so this may not be an...
6567r56a VIC-II behavior (C64 NTSC old profile)
Xbox 360 joystick not working in WinVice
Yes, it now works as it should. I tested a copy, run, and "break" and all functioned...
2.0 works, 3.0+ does not...
Here are 600dpi scans of the front and back. The best I could do was an office document...
I will scan this for you in the next couple days. -Pete no success in tracking down...
Also, oddly enough, the Easyflash version does the same thing on real hardware. So,...
Comal-80 No longer works in SVN builds
I played with the real hardware a bit today. Without the RAM loaded (armed) you can...
prior to 2.3, that is... It worked in 2.2 and 2.1, at least. I played with the source...
I take that last part back- the mmu_translate stuff was added to 2.4 and is just...
It seems that the cart cannot possibly bank in the RAM to $F000 in Ultimax mode before...
I do... Let me know what you need. -Pete On Fri, October 3, 2014 1:43 pm, gpz wrote:...
ISEPIC broken since 2.3 release