So I figured if you lot spent the time doing all these, the least I could do was try them out (even if some are crapola  ).   So here I present the list of all those that I found issues with.  I didn't want to start a topic for each one so I lumped them all together.

Note: most intros with the wavy 'dbug presents', and the dbug logo in the background - the 'use 16mhz',  and trainer options are barely or not at all visible.

--

Arcade Classics - 4 bombs, launched from med/low

Astaroth - music too fast with 8mhz enabled / game goes to start screen, plays in game music - no player character or anything else appears on screen other than the background gfx, all inputs seem to do nothing

Frenetic - after crack screen, just black screen and music (which sounds to fast even if 8Mhz is selected).

Ghosts N Goblins - runs fast even if 8Mhz is selected

Ghouls N Ghosts - runs fast even if 8Mhz is selected

Helter Skelter - runs fast even if 8Mhz is selected.  Basically unplayable

Indiana Jones - 16Mhz doesn't seem to do anything

Mean Machine - runs fast even if 8Mhz is selected

Mercenary III - runs fast even if 8Mhz is selected

Microprose Soccer - runs fast even if 8Mhz is selected

Mudpies - immediately crashes to the desktop, lots 'o' bombs

Munsters - runs fast even if 8Mhz is selected

The New Zealand Story - 'press fire to play' Not here, no way to start the game

Pepsi Challenge - runs fast even if 8Mhz is selected.  Didn't seem to be able to control the player character.

Rainbow Islands - Dbug intro seems to have trouble (music stutter, animation leaving pieces behind occasionally), game loads title screen then just turns black.  8 or 16Mhz selected

Ripcord - 1 player is selected, mouse is active but cannot select start

Spikey In Transylvania - black screen after in game title screen 8/16Mhz

Lands of Havoc - 4 bombs, return to desktop

Wizball - graphics flicker in and out like mad making it unplayable

Wonderboy in Monsterland - music seems to run too fast 8/16Mhz

Zany Golf - depack screen, then three bombs, launched from med/low

--

MSTE (NTSC) 4MB/2.06/Satandisk 1GB SD(250M part)/HDDRIVER8.23/clean boot/Low free 3972870

I can confirm the New Zealand Story bug. Fire (or any other key) doesn´t bring me into game...

And:
"Note: most intros with the wavy 'dbug presents', and the dbug logo in the background - the 'use 16mhz',  and trainer options are barely or not at all visible."

Same problem here. Sometimes when i start my Falcon all Options (16Mhz (Y/N), Cache (Y/N), Trainer (Y/N) etc.) are available. But sometimes i see all those options being selected (very fast) although i don´t press any key at all...Strange...

Since that intro is mine:

Something (or someOne!) is generating keyboard interrupts. I use standard gemdos calls for key input, so I really don't have a clue why this happens. Does this happen on specific games, or on some certain cases?

More than 5 test Falcons and 3 megastes (and 1 tt) never had any problems with this intro, and I haven't changed the code in about 2 years, so up till now I assumed it worked ok...

ggn wrote on 31.01.09 at 17:10:03:

It is on every game with that kind of Intro. The game itself works without problems. But as i said, sometimes i start my Falcon, run the game and none of those option are left available (because they seem to skip). Sometimes i am just left with the last option (let it be the 16/8MHz switch), and sometimes it works fine. It seems that these keys are generated randomly.

What does that mean "someOne is generating keyboard interrupts"?
Every time i start a game on my Falcon, the procedure is always the same. I switch on my Atari and the only two keys that I press are ESC (for skipping the Memory Test) and (holding) CONTROL (for clean boot). Then i always start the game immediately...

Ok, I was just discussing this with GGN and he thought you meant his intro (big D-Bug logo moving in a circle, text over it) and I thought you all meant my intro (static D-Bug logo, wobbly text over it)

However, we both concluded it doesnt matter as they both use standard trap calls to read the keyboard.

I do, however, know that the strobing/disjointed text you are describing does indeed happen on my intro when the falcon is exhibiting the very well known twinsync bug, but this doesnt explain the MSTE problem.

What MIGHT explain that is this: Less cpu cycles/frame in NTSC and the intro running over that time (usually caused by the music taking to long to play)

Try them in 50Hz see if you get the same issue.

Thanks, I know what this is and I believe it's fixed on all the latest single load files... I have no idea why you get that effect tho.

Just tried Captain Fizz.

UK/USA TOS/8Mhz/16Mhz/32Mhz - no flickering - is this one ok for you?

Hrm then all I can say is your machine is 1vbl out of sync to mine and is displaying the work screen instead of the rendered screen.

ok...

btw checked your private messages?

CJ wrote on 01.02.09 at 22:58:23:


I just did.  OMG!  Testing to commence!    

The MSTE is TOS 2.06.  I have a 2.05 set as well that is not installed.