WTware Technical Support

No. WTware only works on x86 and Raspberry.

There is no "microphone=on" in this log. Show me log with "microphone=on" after you try to capture sound.

Very "not that easy" In the next build, WTware will print correct error message. Disable NLA at all to allow user to change password in Windows interface: https://wtware.com/win/nla.html

(the less wires the better). No. Especially onboard Wifi. I guess this leads me to ask, can a raspberry pi3 with wtware provide a seamless audio/video experience? RDP will not provide a seamless audio/video experience. Install Raspbian and run local video player to get better video on raspberry.

Noone writes us "hardware works" when hardware works. Your log was first intel log we received this year where we can not run second display. Others should work. Try another manufacturer, not zodac. With intel graphic.

Four month ago! Just use the latest version from https://wtware.com

1. Boot device.
2. Move pointer with touchscreen.
3. Make a log: https://wtware.com/logs.html
4. Find "touchscreen=" with values in log.
5. Copypaste "touchscreen=" line to config and replace values in first pair.

In order to use configurator, you should configure WTware on Raspberry to load config file over network (tftp or http). Press Del in the beginning of boot and enter text menu. Now terminal is configured to store config on local SD. You can edit config on local SD from setup menu (press Del while it ...

It would be great. Mail me to aka@wtware.com and I'll give you address.

How did you manage to add "sound=on" into config.txt?

Remove "sound=on" from config.txt and add "sound=on" into configs/config.wtc, after server=10.85.4.13

We have no such setting.

I have no ideas Google doesn't find this error "HDMI2 is an invalid output for screen"

Show me log with video=i915(f) and the same display= and m2_display=

I don't understand why it does not work. Try new build: http://wtware.com/testing/201712181803.zip

I see only 43 seconds since start in the log. It should display error and use local config after about two minutes. Less than minute if you switch from tftp to http.

From your log, I see that you do NOT boot by network. Please, do not use words you're not absolutely sure. Make screenshots, screen photos and attach logs.