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:
parent
19899d64b7
commit
e9aa6612c6
|
@ -110,8 +110,8 @@ Start:
|
|||
lda LastChar
|
||||
pha
|
||||
bit ClearKeyboard
|
||||
lda #ResetCommand
|
||||
jsr SendByte
|
||||
; lda #ResetCommand
|
||||
; jsr SendByte
|
||||
lda #ShellCommand
|
||||
jsr SendByte
|
||||
jsr DumpOutput
|
||||
|
|
Loading…
Reference in New Issue