Re: Why is this code exiting to the basic prompt?

["sicklittlemonkey" <Nick.Westgate@gmail.com>]

> what your doing now is setting $7fd in the reset vector ($3f2) and
> asking the user to CTRL-RESET?

Hopefully reset isn't needed any more. The ACIAs are connected to
reset, which is what was solving the problem, but storing 0 in their
control registers should perform the equivalent by disabling them
manually.

My theory is that IN#0 unhooks the serial port, but the firmware
continues to use the ACIA for interrupt-driven keyboard buffering. In
that case every keypress is captured by the firmware interrupt handler
(which clears the keyboard strobe). This would interfere with directly
grabbing keys from $C000.

[About removing ...]
> 2466: 6da0.719f > 400 (each byte is xor'd with BB -- this is obviously
> the crack screen)

This will not help, since later the game relocates another part of
itself into text page 1 memory. So yes, some screen holes were hurt
during the making of this game. ;-)

In fact, this may explain why only some games were affected.
Screen-holes appear to be involved in enabling the keyboard buffering.

Cheers,
Nick.