saulot wrote:no proper output. I've tried to set VIDEL video modes in SV.INF (for example $001a), but it didn't help much.
Patched MON TT resets machine or displays white screen with black rectangle in upper part of the screen (I'm attaching screenshot).
ADEBUG doesn't run at all (4 bombs), but I'm not sure if it ran with 060 at all (,but someone had patched it for 060, FroST(?) some ages ago).
I've got 060 rev.6, tos 1.03c with ctcm (,but not overclocked), latest SV firmware(005). During startup I've got also some garbage output on Videl.
What kind of garbage output on VIDEL? The driver often moves the logical screen to SV videomemory (even on VIDEL-resolutions) since this is faster, but prior to loading the driver, the VIDEL screen should be intact (the SV counterpart have a garbled Atari-logo though - this is normal).
Some questions (don't have access to my Falcon right now)!
- Are you using the resident MON TT?
- Does MON TT change the screen resolution when invoked?
- Does MON TT re-use the "current" screen memory, or allocate its own?
... the last question is significant (and I don't blame you if you don't know the MON TT internals), because there's a bad scenario which can't really be dealt with in an easy way. Let's say the screen is located above 0x01000000... this is outside the range of the 24-bit VIDEL physbase registers. The SV has two additional frame buffer pointers for this very reason. If MONTT tries to re-use the current screen buffer, and decides the location of it based on the 24-bit physbase registers, things can go horribly wrong. If this is the case, maybe a workaround can be invented, or I could patch MON TT to behave a bit better. If my theory is right, it's really a general problem with having a graphics card in the machine, than an actual SV problem. Still it could/should be addressed, imo.
About ADEBUG - just make sure you have a version which actually works on the 060, otherwise it's a waste of time to think about it..