Andreas

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Wyse 3040 V9.1.1131 #93213
    Andreas
    Participant
    • Total Post: 8
    • Newbie

    Seeing the same. Same Version, same Notification. Random.

    Four of my users are on 9.1, all the others still on v8, all 3040. Those four have the weirdest bugs (in Dual-Head mode after a while one monitors resolution breaks, DDC info broken. Or sudden shutdowns and reboots moving the mouse. And this “Host is down”.), so it must be the WTOS version.

    Came to the forum to check and catching up with all the threads regarding 9.1. I’m going to roll back those 4 clients (should be possible via USB) and wait for a new release.

    in reply to: Connect Xenith to XenApp 5 or XenApp 6 #20249
    Andreas
    Participant
    • Total Post: 8
    • Newbie

    nevermind .. found it:

    adding “FixLicense=clean” to the xen.ini .. it’s working now.

    in reply to: Connect Xenith to XenApp 5 or XenApp 6 #20248
    Andreas
    Participant
    • Total Post: 8
    • Newbie

    Hey gilbera did you get it to work? If so .. how? Same Problem here.

    (mixed Presentation Server 4.0 & XenApp 5.0 farm working fine with S10 Clients, problem occur with the Xenith)

    in reply to: Disabling Wake-on-mouse #16835
    Andreas
    Participant
    • Total Post: 8
    • Newbie

    Hi guys .. just hijacking this thread, sorry 🙂

    i don’t know if this was asked before but is there any way to use something like wake on keyboard for s10 devices? our units were all vesa mounted and hard to reach … it would be easier if our users were able to .. dont know .. just hit the space key to boot. found nothing in the s10 bios so far

    in reply to: Serial port ‘laggy’ #11991
    Andreas
    Participant
    • Total Post: 8
    • Newbie

    Hi thinkthin,

    yes of course i did. Our log in script does the mapping and this is not the problem i think because if i start the published desktop with a local installed citrix client on my laptop for example everything works fine.

    But if i access the published desktop with a s10 client the communication with the software running in the citrix session and the hardware behind the COM port is just slow. Processes that normaly takes two or four seconds require 30 seconds or more on the thinclient.

    Our software recognize the hardware in the citrix session .. i mean it say something like “cash terminal found on com1” so the mapping is working fine but when we start a cash operation with this cash terminal it just takes too much time for the terminal to react on commands from the software.

    At the moment there is a fatclient with the cash terminal on local COM1 and a local installed citrix client. On this client we’re running the same published desktop over citrix with the same port mapping and COM settings like i wrote earlier. In this configuration everything works as expected … fast and reliable.

    I contacted wyse support yesterday but till now no answer …

    This is what i call cash terminal:

Viewing 5 posts - 1 through 5 (of 5 total)