If you don't understand how emulators work internally, why comment about them?
...
I do understand them that's why I never replied to you.
>We've explained how it works already. What happens inside the emulator environment runs cycle-exact. If something takes 500 cycles on the Amiga, it will take 500 cycles in the emulator.
You have a different concept than some others do. My argument is whether it's a real amiga functionally not whether it has good bookkeeping and took into account all the cycles each cycle possibly having a different time span.
>Like how I can run Winvice at 10% speed and see how the C64 games I have update the screen. But the software still works. It doesn't crash because the timing is now off by a factor of 10 because it doesn't matter - inside the emulator the 6502 is still executing it's cycles in the same lockstep with the VIC-II it always has, the raster interrupts still occur at the right lines, the serial IO still happens and doesn't lock up.
Not crashing does not translate to working. Doing a mock-up of raster interrupts (via buffering) and bufferring audio is NOT same as a real machine doing it.
>Even though slowing down a C64 by a factor of ten in real life would make almost any code fail miserably as interrupts would not longer happen at the proper moments.
Okay, we agree here. But speed up can have same problems as well.