First things first.
Pl let's know how you have burnt it and which version of puppy, 32 or 64 bit, whether your m/c is 32 or 64.
I have seen things going weired due to faulty burn and/or incompatibility.
Unless you provide sufficient info, it would be difficult to help.
Once this doubt gets...
I wonder why puppylinux shouldn't work.
Do tell us details how you tried puppy, which build (because it looks like from the screenshot that the data is corrupt).
And how you are booting it, dual-booting?
Normally I create a bootable flash of Xenialpup7.5 using dd command and boot my ASUS...
Yeah. That makes sense.
Not even 5 minutes, it took me just 2 minutes in disconnecting keyboard by viewing video shared by you.
I am not a traveller. So USB KB is fine with me.
Thanks @Fanboi @Lord Boltar @darry1966 @wizardfromoz for sharing valuable time and advice.
You have been greatly...
1. Yeah. I had posted this issue on puppylinux forum. It is very active forum (Mike Walsh is very helpful). But for this query, I am yet to get any response.
2. url you mentioned is 15 years old and a lot has been changed since then. Further, it talks about usb support not available...
xinput --disable 8
disables both keyboards, laptop's native keyboard and USB keyboard.
$ xinput float 8
also does same thing.
Pl. help me disabling only the native keyboard, and keeping alive USB keyboard.
In LUbuntu, it lists "AT Translated Set 2 keyboard" separately.
I am using puppylinux (xenialpup64 7.5) on Asus x55c laptop.
The laptop's keyboard has aged and behaves weired, typing some letters automatically.
So I have attached another usb keyboard.
In Lubuntu, in order to get rid of weired keyboard, I am using these commands....
$ xinput list