Error GetPlatformDes in WDM

  • This topic is empty.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #279
    rj
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    Hi

    We’re using WDM 4.5.0 and have a lot of Wyse S50. We have had some problems with updating the firmware and also problems when the terminals have updated firmware.

    The situation is:
    I get an error message in WDM like this: “GetPlatformDes: Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.” This is usually a bad warning sign, because everytime this happens someone have a corrupt terminal.

    Some of the corrupt terminals can be turned on but stops with the message “No boot device present. Halting” and others will not start. They have a yellow light on the powerbutton that is constantly lit.

    Any suggestions what’s causing this?

    – rj

    #9052
    thinkthin
    Member
    • Total Post: 1686
    • Jacked into The Matrix
    • ★★★★★★

    Hi RJ,

    WDM 4.5.1 is out and I would upgrade to this one as it has a load of bug fixes. One problem was that the bandwidth control slowed the imaging down too much and caused it to fail. I would upgrade and see how it goes.

    You can use Wyse Simple Imager to recover the half imaged devices or push a new image to the device in WDM then right click on the scheduled job and select “roll to boot”. This should force the image load to run again but if not WSI it,

    Cheers,
    -TT

    #9061
    rj
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    We use the FTP update, so I would guess that WDM has nothing to do with it?

    I find it strange that there should be any bandwith issues with the FTP connection. Our network should be able to deal with the transfer.

    – rj

    #9064
    thinkthin
    Member
    • Total Post: 1686
    • Jacked into The Matrix
    • ★★★★★★

    Ahh, sorry – because you mentioned WDM I assumed you were updating via PXE – WDM is the one with the bandwidth throttle.

    If you are using ftp only make sure you have deployed the upgradexxx.pak file before you deliver the .64m file. If the device does not have this it will be a brick after the upgrade,

    Cheers,
    -TT

    #9070
    rj
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    Follow up question:
    If I have the firmware file in the wlx folder and the upgrade pak file in the addons directory and try to upgrade, will the upgrade be installed first and then the firmware update? Or should I have only the addon file present?

    We have upgraded several S50’s and I know that a lot more than the ones that have become “bricks” have had the 6.2.x firmware.

    – rj

    #9072
    thinkthin
    Member
    • Total Post: 1686
    • Jacked into The Matrix
    • ★★★★★★

    The upgradexxx.pak is required when you move from a 6.2x to a 6.3x binary. You will need to have it deployed before putting the .64m file in the wlx folder as the firmware is loaded first and then the addon.

    In theory you will not need the upgrade.pak to move from say 6.3.018 to 6.3.021 but I leave it in the addons folder all the time just in case,

    Cheers,
    -TT

    #9109
    rj
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    It’s service center next…

    But now we are aware of the problem and have learned from it.

    Thanks!

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