Fixed shell startup (?)

At least on the alternative hardware, this "blindly sending" a reset command causes the shell to be terminated right away:
The driver acknowldges the reset command with a zero byte - and that byte ends up being read by DumpOutput causing it to branch to endOutput.

Maybe that sending a reset command is beneficial on the original hardware. Then another .if is required. Or DumpOutput shouldn't quit on reading a zero byte - the shell handler doesn't seem to send it on purpose(?)
This commit is contained in:
Oliver Schmidt 2022-08-19 16:49:03 +02:00 committed by Terence Boldt
parent 19899d64b7
commit e9aa6612c6
1 changed files with 2 additions and 2 deletions

View File

@ -110,8 +110,8 @@ Start:
lda LastChar
pha
bit ClearKeyboard
lda #ResetCommand
jsr SendByte
; lda #ResetCommand
; jsr SendByte
lda #ShellCommand
jsr SendByte
jsr DumpOutput