WTware RDP client

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.

No way. Chromium is too large and too slow now

6.2.20 was the last wtware version with chromium on pi2/pi3:

https://wtware.com/files/pi2.pi3.chromium.last/

Sorry, your mails were moved to junk. I will send you now link for previous version and look at the logs.

Kernel version upgraded from 6.6.x to 6.12.x. Sound device file name has been changed in new kernel

Will be fixed in the next wtware version, thank you.

Guest wrote: Mon Apr 28, 2025 4:59 pm Server ist startet and my choosen test-usb is found.
VH client can not find any server, can anyone push me in the right direction?

Don't make the client search for the server. Give the client the server's IP address.

Thank you, it's our error. Will be fixed in the next version.

Not a problem but a lot of coding. Replace hardcoded boolean variables "main monitor" (true for first, false for second monitor) with list of monitors everywhere. We'll do it after three monitor outputs will be common for thin client hardware.

Not with wtware until devices with three regular video outputs hit the mass market.

In theory, you can connect 5 displays to a Raspberry. In practice, third HDMI display is not possible at a reasonable price.

It should work. "Alt Gr" key used in "Alt Gr + Q" should make Euro with "Alt Gr + E" in recent wtware version.

Please, show me terminal log after "Alt Gr + E" : http://wtware.com/logs.html
And photo of the screen with wtware interface you try to enter Euro sign in.

Mail it to support@wtware.com

No way, sorry. We are focused on network boot and don't want to make wtware so big.

Win + E is redirected now. It took only year and a half

Windows TFTP client is easier to reproduce for me.

Do I understand correctly, on the same virtual machine, with the same network environment, no other changes, only:

1. Turn off SolarWinds TFTP, start WTware TFTP service, and Windows TFTP client tftp.exe from another windows machine won't download ...

When a Thin Client is starting, I can see that it obtained an IP, I can also see in Wireshark that the read request packets are incoming on port 69/udp. WTware doesn't bother to reply to those requests or even to log anything.

Firewall. Or broken IP stack on Windows. WTware TFTP service logs ...

I attempted to network boot. THe DHCP options are all set correctly (verified with test software) but every client gets a DHCP IP address and then shows a TFTP timeout. Testing locally on the WTware server the TFTP file can be obtained with a test client. Remotely from any different PC the TFTP ...