Script to flash firmware then delete unwanted addons

  • This topic is empty.
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #2437
    ConfGen
    Keymaster
    • Total Post: 11409
    • Jedi Master
    • ★★★★★★★

    I’m trying to image some old WT3235LE WinTerms with Windows CE 5.0 (build 529.2, the last build that was available for this model) but without any unwanted/not needed addons taking up extra space.

    From what I’ve read, I need the CE primer for this model and build in order to build my image without the addons, however when I phoned WYSE to get one, they told me that didn’t have a primer for that model.

    So, what I’m trying to do instead is flash the WinTerms with the “full” firmware image available from Wyse’s website and then delete the unwanted addons through the same script that sent the image.

    Unfortunately, no matter what I do, the WinTerm refuses to execute any script commands after the SF which sends the image. The WinTerm will accept and install the firmware sent from WDM, but then do absolutely nothing after rebooting, while the scheduled update’s status on the WDM side sits at “in progress” until I manually move it to an error state and delete it.

    This is my current script:

    [Version]
    Number=WT3235LE
    Description=WT3235LE Image
    OS=CEN
    Category=Images
    ImageSize=32
    USE_PXE=NO


    [Script]
    WL
    CO "CEN"
    LU "This terminal is currently being updated. Please wait."
    SF "CEFirmware" "WT3235LE.bin"
    ST*
    DF* "CEAddon" "ACTIONTEC"
    DF* "CEAddon" "DIALUP"
    DF* "CEAddon" "ELOTOUCH"
    DF* "CEAddon" "JETCET"
    DF* "CEAddon" "MS-STORAGE"
    DF* "CEAddon" "IE"
    DF* "CEAddon" "PPTP"
    DF* "CEAddon" "PPPOE"
    DF* "CEAddon" "PCSC_DRIVER"
    DF* "CEAddon" "RDP"
    DF* "CEAddon" "ELOTOUCHUSB"
    DF* "CEAddon" "SCRLOCK"
    DF* "CEAddon" "SCRSAVER"
    DF* "CEAddon" "TEC"
    DF* "CEAddon" "USBMGCOM"
    DF* "CEAddon" "USBMODEM"
    DF* "CEAddon" "CERTIFICATES"
    EL*
    RB

    Is there any way to get the WinTerm to actually delete these addons through a script? According to what I’ve read, this is the proper syntax for deleting CE addons, though I’m new to rsp scripting so there may be something I’m missing.

    Any help, information, or suggestions would be appreciated.

    #15745
    ConfGen
    Keymaster
    • Total Post: 11409
    • Jedi Master
    • ★★★★★★★

    Try to add a “RB” after the “SF” command.

    CG

    #15753
    ConfGen
    Keymaster
    • Total Post: 11409
    • Jedi Master
    • ★★★★★★★

    Thanks for the suggestion. Unfortunately, adding a RB command after the SF caused the WinTerm to get stuck in a loop where it would flash the firmware, reboot, come back online, reboot, then flash the firmware again, reboot, etc. until WDM spit out an error.

    I changed the category to “other packages” and tried my script again. Tis time, the WinTerm actually deleted the addons, however it was not locking the terminal while doing so. Maybe adding another LU command after the SF would fix that.

    #15756
    ConfGen
    Keymaster
    • Total Post: 11409
    • Jedi Master
    • ★★★★★★★

    Honestly I would go the other way round and create my own CE version which only includes the needed addons.
    Contact Wyse to send you the needed CE firmware as a so called primer version. This is a CE version without any addons at all.
    Then use WDM Package Manager to create your own CE bundle.
    Pretty straight forward and the package that has to be transferred to the client is much smaller.

    CG

    #15757
    ConfGen
    Keymaster
    • Total Post: 11409
    • Jedi Master
    • ★★★★★★★

    Thanks again for the reply. I already contacted WYSE and tried to get a primer, but they told me that there is no primer for the 3235LE (or the 3150SE), which was my initial problem. The only one they were able to give me was an outdated build of CE for the S30. I’m pretty sure that the primers do exist for the 3235 and 3150, but it looks like they aren’t giving them out anymore.

    I made some changes to my script after I had it deleting the addons without locking the terminal, and now it gets stuck in that loop no matter what I do. When it reboots after flashing the firmware, it will try to flash the firmware again instead of going onto the ST and DF commands. The “working” version was slightly different than the one I posted, but I tried to get my script back to the way it was. It’s still “looping”. I should also point out that I’m using a bundled image this time which includes a configuration addon generated by ConfGen.exe, whereas I was using the unmodified firmware when it was working.

    Here’s my current script:

    [Version]
    Number=WT3235LE
    Description=WT3235LE Image/Configuration
    OS=CEN
    Category=Other Packages
    ImageSize=32
    USE_PXE=NO


    [Script]
    CO "CEN"
    LU "This Terminal is currently being updated. Please wait."
    SF "CEFirmware" "WT3235LE.bin"
    ST*
    DF* "CEAddon" "ACTIONTEC"
    DF* "CEAddon" "DIALUP"
    DF* "CEAddon" "ELOTOUCH"
    DF* "CEAddon" "JETCET"
    DF* "CEAddon" "MS-STORAGE"
    DF* "CEAddon" "IE"
    DF* "CEAddon" "PPTP"
    DF* "CEAddon" "PPPOE"
    DF* "CEAddon" "PCSC_DRIVER"
    DF* "CEAddon" "RDP"
    DF* "CEAddon" "ELOTOUCHUSB"
    DF* "CEAddon" "SCRLOCK"
    DF* "CEAddon" "TEC"
    DF* "CEAddon" "USBMGCOM"
    DF* "CEAddon" "USBMODEM"
    DF* "CEAddon" "CERTIFICATES"
    EL
    RB

    Do you know what causes this “looping” to happen?

    #15760
    ConfGen
    Keymaster
    • Total Post: 11409
    • Jedi Master
    • ★★★★★★★

    What firmware version are you using for that image?

    CG

    #15775
    ConfGen
    Keymaster
    • Total Post: 11409
    • Jedi Master
    • ★★★★★★★

    Windows CE 5.0 build 529.2. It’s the last version available for the 3235LE from WYSE’s website. I’ve heard that build 541 is available for the 3235LE if you phone WYSE, but I have not been able to get any firmware for this model from WYSE customer support so far.

    I do have an update though: My current script is working without that annoying loop issue, but it only works if it’s flashed over a 3235LE that’s running the official 5.0 build 529.2.

    If I apply it to a unit running CE 4.X, it will image it and come back online saying the HAgent.exe failed to load and not go any further nor check in with WDM, despite the fact that I included the WDM HAgent update in the firmware package. This can only be fixed by installing the official build 529.2 and re-applying my custom one. Likewise, if I install my working build onto a unit running one of my old custom builds, I get the loop problem.

    Despite this strange behavior, if I make sure that I push out the official CE 5.0 529.2 and then push out my custom one afterward, I can get the job done. It’s just going to be a bit of pain doing 100+ units this way, especially since I won’t have physical access to most of them…

    for reference, here’s my current script in case you have any suggestions:

    [Version]
    Number=WT3235LE
    Description=WT3235LE Image/Configuration
    OS=CEN
    Category=Images
    USE_PXE=NO
    DeployedSW=NO
    Use_Remote=NO

    [Script]
    LU*
    SF* "CEFirmware" "WT3235LE.bin"
    DF* "CEAddon" "ACTIONTEC"
    DF* "CEAddon" "DIALUP"
    DF* "CEAddon" "ELOTOUCH"
    DF* "CEAddon" "JETCET"
    DF* "CEAddon" "MS-STORAGE"
    DF* "CEAddon" "IE"
    DF* "CEAddon" "PPTP"
    DF* "CEAddon" "PPPOE"
    DF* "CEAddon" "PCSC_DRIVER"
    DF* "CEAddon" "RDP"
    DF* "CEAddon" "ELOTOUCHUSB"
    DF* "CEAddon" "SCRLOCK"
    DF* "CEAddon" "TEC"
    DF* "CEAddon" "USBMGCOM"
    DF* "CEAddon" "USBMODEM"
    DF* "CEAddon" "CERTIFICATES"
    EL*
    RB
    #15789
    ConfGen
    Keymaster
    • Total Post: 11409
    • Jedi Master
    • ★★★★★★★

    Send you a link via PM.

    CG

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