WTware RDP client

1. Use latest wtware version.
2. Update BIOS. Most boot problems are caused by BIOS errors.
3. Install WTware again. When WTware writes: "Installation complete. Reboot computer", do not reboot computer. Press Esc. It should start command line. From command line, write "log" as written in logging ...

Perhaps we should delete all our files? Raspberri Pi imager now can generate official firmwares. Did you try files that generate Raspberry Pi Imager?

Please follow this manual https://wtware.com/logs.html
and make me terminal log. Mail it to support@wtware.com

I' deeply sorry for such delay, we had server issues. Sent you reply. Please, next time I you won't receive answer for a day, contact me by wtware@gmail.com It works anytime.

sgiardi.ali wrote: Sun May 17, 2026 2:24 pm we are happy to wait and assist with testing if needed.

Can you help me to make testing stand? Is it possible to test this stuff on standalone server?

We can not run Veyon or similar tools. All such linux tools work over X Window while wtware is too small and does not include X Window.

WTware includes common VNC server and our own WTRC server for remote control over terminal display. Our own WTRC is faster but we have only Windows viewer now. So ...

Does Touch Display 2 (DSI) work officially with WTware?

No, sorry 🙁

It was hacked off from kernel due to incompatibility with ZaphodHeads X.org functionality. Is I know, wtware is only linux that runs zaphodheads mode dual display on raspberry and we need this functionality to run Chromium on ...

Yes, I see this issue. Will fix this in the next version. Till then you may in configurator switch to "text" tab and enter your license with "=" character. Press "Save", ignore warning. Terminal will process this line without problems.

It is cool already. WTware uses text configs, as everything in unix-based environment. Some config features (Everyone/list.wtc for example) only work from text configs and are not supported by Windows-based Configurator. WTware uses standard DHCP, TFTP and HTTP for boot. We use Debian servers for ...

Please, try this build: https://wtware.com/testing/202510061514 ... .63.en.zip
If won't work, send me terminal log file (http://wtware.com/logs.html) to support@wtware.com

You can not connect microphone to Raspberry 3.5mm jack. There is no hardware for microphone input in Raspberry. You should use USB microphone or USB headset.

What is your Microphone Jack? There is no microphone input in Raspberry Pi sound jack. Not implemented in hardware. You should use USB microphone or USB headset for Raspberry Pi.

WTware sound manual:

https://wtware.com/docs5/sound.html

Logging manual (when you add log, tech support asks less ...

Here is logging manual: http://wtware.com/logs.html
Four simple steps. The problem usually is solved when you do them.
Show me full log here or to support@wtware.com if it won't help.

Also, do not unplug sound device. It never helps and may makes worse.

Despite multiple attempts, we haven’t been able to successfully redirect a webcam image in a remote desktop session.
We tested with several webcam models (including Genius FaceCam), but the result was the same. It also doesn’t work in RAW mode.

Did you test several servers?
2019 or 2022, just ...

Generate multiple .zip files with different names, one for each vm. Put them all into Everyone. In terminal config in extra= option specify name of .zip that wakes vm needed for this terminal.