cli: phantom keypress (real amiga, not emulation)

[honx]

in emulation and on real amiga500plus equipped with aca500plus and aca1221 there is a weird problem in cli using lha.
there is some additional letter at the beginning of commands which i didn't type. happens after paused scrolling text.
so, if there is "Paused. Press any key to continue..." then this kind of error occurs after running lha command again...
for example: if i type lha, error says "Alha: unkown command" or "Blha:...", there is additional letter at the beginning.
it occurs on os3.1 system and on os3.9 as well! what is this and how can i fix this? this behavior is really annoying!

//edit it's not only lha. lzx or anything else does the same if there is scrolling involved.

[daxb]

Do you use Amiga Shell or any replacement like VNC, KingCON, ...? How do you pause the scrolling text (via Space key?)? Is the "phantom key" visible when you enter a command or only after executing it?

[honx]

using standard cli. text is paused by default if it doesn't fit cli window.
to continue i press any key (space, arrow keys,...), no key preferred...

just try typing lha or lzx in cli. i think, you might be able to reproduce...

[DamienD]

Originally Posted by honx

just try typing lha or lzx in cli. i think, you might be able to reproduce...

I definitely can't using a standard WB 3.1 or Classic WB Lite 3.1 install...

[honx]

i tried both lha 2.15 and lzx 1.21 on workbench 3.1 which comes with aca500plus and on workbench 3.9 in emulation.
did you repeat typing the command? it happens more often if repeat command from history instead of typing it again.

[DamienD]

honx; I don't need to try / test...

I've been using both "LHA 2.15" & "LZX 1.21" in various setups over the many years now and never once experienced what you've detailed...

Something's going on with your setup

[honx]

but how can it be a setup? there are TWO DIFFERENT setups having this problem with TWO DIFFERENT operating system versions?
setup 1: emulated amigaos 3.9 with all boingbags. setup 2: real hardware amiga500plus+aca500plus, using standard workbench 3.1
there's still no magicwb or anything installed. it's just plain amigaos 3.1, installed using aca500plus 3.1 installer module 0.8 (latest).

//edit: just tried THIRD setup. emulated workbench 3.1 with magicwb installed, same problem regarding lha/lzx occurs on this one.
so this problem affects at least THREE DIFFERENT setups (the setups i have checked). screenshot from new setup test attached.

so it can't be "just the setup" otherwise ONLY ONE setup would be affected and not (at least) THREE DIFFERENT setups...

[DamienD]

I don't really know not else to say to you honxy...

Never happened here in over a decade; and I guess not for anyone elsewhere either otherwise there would be existing threads already

...you do seem to have your own weird and wonderful issues on you emulated systems.

[honx]

just tested emulated amiga 600 hd environment running workbench 2.1, same problem here.
it's four different setups and three different operating system/workbench versions already.

as said, it's NOT just emulated systems, also REAL HARDWARE (a500+ with aca500plus)!

[emufan]

it's also new to me, and doesn't happen here.
maybe some sort of "fun virus" thing?

try in your shell, for example: more s:startup-sequence
this does have a page-stop feature too.

[honx]

more doesn't do this, just tried it. but both lha and lzx do it.

how can new os3.1 install on aca500plus contain fun virus?
install was done using original aca500plus installer module.

[daxb]

What if you start without S-S and then type "lha"? Do you use the same ROM's (original, other)? Patched libraries or something else?

[thomas]

Originally Posted by honx

to continue i press any key (space, arrow keys,...), no key preferred...

Do not press cursor keys, help, F-keys or anything else which translates into an escape sequence rather than a single ASCII character.

The cursor-up key for example translates into CSI A ($9b $41).

The CSI character is "eaten" by LhA, but the A character is still in the buffer when you enter the next command.

Just press Space. It's the largest key anyway, you can't miss it.

[honx]

Originally Posted by daxb

What if you start without S-S and then type "lha"? Do you use the same ROM's (original, other)? Patched libraries or something else?

on amiga500plus i use 3.1 rom included on aca500plus. startup-sequence is unaltered.
on emulation i used different roms as i tested different workbench versions (2.0/2.1, 3.1).
on boot without s-s it doesn't seem to occur, but there is also no interlace screenmode.
maybe is there the problem? screenmodes > pal:highres?

Originally Posted by thomas

Do not press cursor keys, help, F-keys or anything else which translates into an escape sequence rather than a single ASCII character.

The cursor-up key for example translates into CSI A ($9b $41).

The CSI character is "eaten" by LhA, but the A character is still in the buffer when you enter the next command.

Just press Space. It's the largest key anyway, you can't miss it.

okay, thx. it figures, sounds like the explanation for this!

[daxb]

Originally Posted by honx

on boot without s-s it doesn't seem to occur, but there is also no interlace screenmode.
maybe is there the problem? screenmodes > pal:highres?

I don't think the screenmode has something to do with it but you can easily test it by using different screenmodes. Start without U-S and WBStartup. If the problem still is there must be something in S-S.

[honx]

Originally Posted by daxb

I don't think the screenmode has something to do with it but you can easily test it by using different screenmodes. Start without U-S and WBStartup. If the problem still is there must be something in S-S.

needs further watching, but i think, this is the solution already:

Originally Posted by thomas

Do not press cursor keys, help, F-keys or anything else which translates into an escape sequence rather than a single ASCII character.

The cursor-up key for example translates into CSI A ($9b $41).

The CSI character is "eaten" by LhA, but the A character is still in the buffer when you enter the next command.

Just press Space. It's the largest key anyway, you can't miss it.

[daxb]

I get the problem with F-Keys and Help Key. Cursor keys are fine. Usually I use a key that isn't too far away what is in most case the Space bar or any character. How lucky are you that you often hit the wrong far away key?

[honx]

it has been mostly space or cursor keys or enter. other keys were used much less.
now that i know about these escape sequences translating keys i only use space.