screensaver doesn’t load image

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #53086
    ZijmZijm
    Participant
    • Total Post: 3
    • Newbie
    • β˜…

    Hi all,

    New user here(on forum and with working with Wyse thinclients πŸ™‚Β Β  ).

    We are using Dell/Wyse T10D clients (Dell 3020). (Yes, old, but still supported)

    I’m using the Microsoft broker to connect to our 2012 R2 farm.

    We would like to use the moving picture screensaver, but the image file we would like to use won’t load.

    The line I have in the ini file:

    Screensaver=1 Type=2 Imagefile=screensaver.jpg

    I put screensaver.jpg in the bitmap folder on the FTP server, but it won’t load. Instead I get a “Remote Desktop Services” image bouncing around.

    If I use the type 3 screensaver, it works flawless (loading the images from the picture folder on the FTP server).

    Anyone knows how I can get the moving picture screensaver to load the right image?

     

    Regards,

    Ruud

    #53108
    ConfGenConfGen
    Keymaster
    • Total Post: 9810
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    How big is the picture and is the name really “screensaver.jpg” or anything else?

    CG

    #53138
    ZijmZijm
    Participant
    • Total Post: 3
    • Newbie
    • β˜…

    I’ve tried different sizes (400×400, 100×100, 228×87), different file types (jpg, gif) and different names πŸ™

    NB: The image I use for desktop background loads with no problem from the bitmap folder.

    #53141
    ZijmZijm
    Participant
    • Total Post: 3
    • Newbie
    • β˜…

    Found the problem: I think there was a non-printable character in the ini file between ‘image’ and ‘=’, because after typing the whole ‘ screensaver type=….’ line instead of copy/pasting it, it works.

    #53182
    ConfGenConfGen
    Keymaster
    • Total Post: 9810
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    That’s the reason why I had developed the Configuration Generator πŸ˜‰

    CG

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.