Cycle By Cycle Emulator

["Bryan Parkoff" <nospam@nospam.com>]

    I agree with someone who they posted under "The Perfect Emulator".  I
understand that 1 MHz Cycle by Cycle has nothing to do with Video
Refresh/Update, Disk II, and Sound.
    Let says, Lock and Unlock method by DirectX 9.0 update 7 pixels each MPU
one instruction might be faster than Lock and Unlock method by DirectX 9.0
update 53,760 (280x192) pixels each MPU's 17030 cycles.  I mean that 7
pixels must be updated every 17030 times, but 53,760 pixels can be updated
once every 17030 cycles.  Do you see the difference?  Please mention what
you compare using DirectX 9.0 Lock and Unlock methods.  Did you notice the
difference which improves performance?  It must be used with Global Variable
Storage for video memory so memcpy function is not needed.
    It would be great if it has gone through Accelerator Graphic video card
(GPU) rather than overload CPU.  Let says, Emulator will run much faster on
CPU WHILE video update processes faster on GPU.
    Now -- about sound and Disk II.  Michael mentioned that it has nothing
to do with MPU's cycle that will work with sound and Disk II.  Let says, MPU
operates at 1 MHz while sound operates at 28Hz.  Would 28Hz be stealing 1
MHz's time?  It is very difficult to make the frequency to match the sound
28Hz.  MPU instructions have to spend 1 MHz to make sound works.  Now,
compare to Disk II.  Disk II must use the same 1 MHz that Disk II must spend
36 cycles to create one valid byte through LDA C08x,X loop.  If MPU's 1 MHz
is not fixed, 36 cycles will be wrong in the wrong time.
    Please advise.

-- 
Bryan Parkoff