Thanks for replies,
The most unusual idea is to suspect the monitor and because the most unusual suspect it is the last one to tackle..
mouse, keyboard, 2 Pi's boards, 3 SD cards and the 2 power supplies are al interchanged and changed out and (mouse keyboard and monitor) tested separately on a lap top PC and/or a desk top PC with windows operating systems.. They work as aspected, not a single problem.
Only difference: the keyboard works on a PC with Capslock, Numlock, and Scrollllock LEDS active, I never saw them lit on a Pi.
IS THIS NORMAL??
ONLY the monitor plus DVI-HDMI cable is the same AND above that problems with NOOBS (freezing mouse and keyboard) are the same as with transfering an Raspbian image on an SDcard . They are all the same: Keyboard and mouse problems. freezing, slowing fast down or stopping to work. Only a mouse connected or only a keyboard connected on any Pi_USB connector; doesn't matter SAME PROBLEMS ALWAYS with NOOBS and with Image Raspbian transferred with Etcher.
Of course all changes are tested after a power down and boot.
So finallly the ONLY suspect can be the monitor including the HDMI--> DVI cable. BECAUSE that is the only stable present component in ALL the tests. Unbelievable. because it is working fine, and now works fine on a VGA input on another place, not on a Pi but a desktop PC,
The monitor did never give me any reason for suspection, and is now swapped working on another computer on his VGA connector,
So as far I can decide now, it MUST be the monitor with HDMI-DVI cable because it was the only stable present component in all the setups that all gave the same problems with keyboard and or mouse,..
It can't be the keyboard when I connect only a mouse
It can't be the mouse when I only connect a keyboard
Keyboard and mouse just work fine errorfree on a USB of a PC
So I am NOT focussing on NOOBS because Raspbian image transfer to a SDcard yields the same mouse and or keyboard problems. Also the old SD cards with Debian starting up in control line mode have heavy keyboard problems and after startx command heavy mouse problems with the GUI.
Thank you for thinking about my problem. It does me thinking about old rules created by previous generations that every man is loaded with problems he just can or cannot handle.
I am really missing beginners luck.
The monitor has both DVi and VGA connections, a straightforward "HDMi to DVi Cable" would suffice, no need for adaptors, therefore would suspect a dodgy cable or one which is wired DVi to HDMi. Though having come across this type of monitor they default to VGA and must use the menu buttons to change input source:
I obtained such a cable. New, so I had no suspect with the monitor, after set up according to manual worked fine.
The monitor including the cable did not give any reason for suspect up to now, because it just displays what it had to display in command line mode and in GUI mode of the PI boards. However it is the only present system component in ALL the tests that fail up to present a normal operating Pi. What do you mean with "or one which is wired DVi to HDMi." I used a cable DMI on one side connected to the monitor and HDMI male on the other side, connected to the Pi. Are there two different kind of cables with these specs?